You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Wallet (JIRA)" <ji...@codehaus.org> on 2008/07/21 16:17:28 UTC

[jira] Created: (MECLIPSE-468) 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'
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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: http://jira.codehaus.org/browse/MECLIPSE-468
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Improvement
          Components: Core : Dependencies resolution and build path
    Affects Versions: 2.5.1, 2.5.2
         Environment: linux (ubuntu 8.04), Sun JDK 1.6, maven 2.0.8
            Reporter: Guillaume Wallet


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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MECLIPSE-468) Capability to ignore classpath container 'It would be nice too when using alternate JRE like J2MELIB for example withe pyx4me maven plugin.

Posted by "Martin Schonaker (JIRA)" <ji...@codehaus.org>.
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: 4e90ceb663894a42f12c0e28abbab431


    [ http://jira.codehaus.org/browse/MECLIPSE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229684#action_229684 ] 

Martin Schonaker commented on MECLIPSE-468:
-------------------------------------------

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

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

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

{code}
[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
{code}

And the .classpath file contains:

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

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.

> 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: http://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
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MECLIPSE-468) Capability to ignore classpath container 'It would be nice too when using alternate JRE like J2MELIB for example withe pyx4me maven plugin.

Posted by "Brent N Atkinson (JIRA)" <ji...@codehaus.org>.
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