Capability to ignore the container
classpath entry 'org.eclipse.jdt.launching.JRE_CONTAINER'
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09
[
https://jira.codehaus.org/browse/MECLIPSE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brent N Atkinson updated MECLIPSE-468:
--------------------------------------
Attachment: MECLIPSE-468.patch
Patch based on 2.8 version of the plugin that adds configuration to disable
mandatory addition of JRE_CONTAINER.
> 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'
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-468
> URL: https://jira.codehaus.org/browse/MECLIPSE-468
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.5.1, 2.6
> Environment: linux (ubuntu 8.04), Sun JDK 1.6, maven 2.0.8
> Reporter: Guillaume Wallet
> Attachments: MECLIPSE-468.patch
>
>
> 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
