Maven 2.x Eclipse Plugin

Capability to ignore classpath container 'It would be nice too when using alternate JRE like J2MELIB for example withe pyx4me maven plugin. Capability to ignore the container classpath entry 'org.eclipse.jdt.launching.JRE_CONTAINER'

Details

  • Number of attachments :
    1

Description

I try to add J2MELIB container library but the plugin force the add of org.eclipse.jdt.launching.JRE_CONTAINER that I do not want (I develop mobile application so I do not use JRE).

It would be nice, when using alternate JRE like J2MELIB, to de activate the default add of 'org.eclipse.jdt.launching.JRE_CONTAINER'

I think it not a hard work, I can produce a patch if needed, for inspiration, just tell me

best regards

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Arnaud Heritier added a comment -

It doesn't work if you add a classpathContainers Entry in the plugin config ?
You can have a look at the EclipsePlugin.verifyClasspathContainerListIsComplete() method which adds the default JRE_CONTAINER if there is no other container added.

Show
Arnaud Heritier added a comment - It doesn't work if you add a classpathContainers Entry in the plugin config ? You can have a look at the EclipsePlugin.verifyClasspathContainerListIsComplete() method which adds the default JRE_CONTAINER if there is no other container added.
Hide
Permalink
Martin Schonaker added a comment -

I'm having a similar issue with Android. With this configuration:

<configuration>
   <classpathContainers>
     <classpathContainer>com.android.ide.eclipse.adt.ANDROID_FRAMEWORK</classpathContainer>
   </classpathContainers>
     ...
</configuration>

I'm having this warning during a mvn eclipse:eclipse

[WARNING] You did specify a list of classpath containers without the base org.eclipse.jdt.launching.JRE_CONTAINER.
       If you specify custom classpath containers you should also add org.eclipse.jdt.launching.JRE_CONTAINER to the list

And the .classpath file contains:

<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>

despite the fact that I didn't include it. The JRE container causes a lot of compiling pain. The output needs to contain only the Android CP container in order to have the project being built properly.

Regards.

Show
Martin Schonaker added a comment - I'm having a similar issue with Android. With this configuration: <configuration> <classpathContainers> <classpathContainer>com.android.ide.eclipse.adt.ANDROID_FRAMEWORK</classpathContainer> </classpathContainers> ... </configuration> I'm having this warning during a mvn eclipse:eclipse [WARNING] You did specify a list of classpath containers without the base org.eclipse.jdt.launching.JRE_CONTAINER. If you specify custom classpath containers you should also add org.eclipse.jdt.launching.JRE_CONTAINER to the list And the .classpath file contains: <classpathentry kind= "con" path= "org.eclipse.jdt.launching.JRE_CONTAINER" /> <classpathentry kind= "con" path= "com.android.ide.eclipse.adt.ANDROID_FRAMEWORK" /> despite the fact that I didn't include it. The JRE container causes a lot of compiling pain. The output needs to contain only the Android CP container in order to have the project being built properly. Regards.
Hide
Permalink
Brent N Atkinson added a comment -

Patch based on 2.8 version of the plugin that adds configuration to disable mandatory addition of JRE_CONTAINER.

Show
Brent N Atkinson added a comment - Patch based on 2.8 version of the plugin that adds configuration to disable mandatory addition of JRE_CONTAINER.

People

  • Assignee:
    Unassigned
    Reporter:
    Guillaume Wallet
Vote (2)
Watch (3)

Dates

  • Created:
    Updated: