Maven Integration for Eclipse

Can't access org.apache.maven classes

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 0.9.7
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Eclipse 3.4.0 (with Eclipse 3.3.2 target platform),Windows XP
  • Number of attachments :
    1

Description

I'm working on a plugin (several, actually) that depends on the m2eclipse plugins. I've declared dependency on the following in my plugin.xml:
org.maven.ide.eclipse
org.maven.ide.components.archetype_common

The latter one contains the Archetype JAR file (archetype-common-2.0-alpha-2.jar) and exports its packages. However, I still can not see any of the classes in the Archetype JAR (for example, org.apache.maven.archetype.catalog.Archetype).

It is very common practice for a plugin to expose the packages from a JAR that it contains, so I'm not sure why this is not working. Any ideas?

I am running Eclipse 3.4.0 and have my target platform set to a 3.3.2 Eclipse SDK + WTP + some of the m2eclipse plugins (listed below). I will attach a sample project that demonstrates the problem using this setup.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eric Rizzo added a comment -

The attached project does not compile (it fails to locate the org.apache.maven.archetype.catalog.Archetype class) as it is configured, when m2eclipse is included in the workspace's Target Platform.
If you change the Runtime settings of the test plugin's manifest to include lib/archetype-common-2.0-alpha-2.jar then it compiles successfully. However, the point of the org.maven.ide.components.archetype_common plugin is to export the packages from the JAR, so it should not be necessary to depend on the JAR directly.

Show
Eric Rizzo added a comment - The attached project does not compile (it fails to locate the org.apache.maven.archetype.catalog.Archetype class) as it is configured, when m2eclipse is included in the workspace's Target Platform. If you change the Runtime settings of the test plugin's manifest to include lib/archetype-common-2.0-alpha-2.jar then it compiles successfully. However, the point of the org.maven.ide.components.archetype_common plugin is to export the packages from the JAR, so it should not be necessary to depend on the JAR directly.
Hide
Permalink
Eugene Kuleshov added a comment -

Eric, you need to import org.maven.ide.components.* projects into your workspace, because of the limitation in PDE.

Show
Eugene Kuleshov added a comment - Eric, you need to import org.maven.ide.components.* projects into your workspace, because of the limitation in PDE.
Hide
Permalink
Eric Rizzo added a comment -

Eugene,
Are you saying that the need to import the org.maven.ide.components.* plugins into the workspace is only for compile-time in the IDE and that headless build and runtime will both work correctly otherwise?

Show
Eric Rizzo added a comment - Eugene, Are you saying that the need to import the org.maven.ide.components.* plugins into the workspace is only for compile-time in the IDE and that headless build and runtime will both work correctly otherwise?
Hide
Permalink
Eugene Kuleshov added a comment -

Exactly.

Show
Eugene Kuleshov added a comment - Exactly.

People

  • Assignee:
    Unassigned
    Reporter:
    Eric Rizzo
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: