[ http://jira.codehaus.org/browse/MNG-1020?page=comments#action_47164 ]
Holger Hoffstätte commented on MNG-1020: ---------------------------------------- Trygve, thanks for looking into this. I reported MPECLIPSE-104 to fix an undetected *compile* time problem (resulting in an undetected runtime problem) in an IDE. Any bootclasspath business should IMHO be considered a *runtime* problem, and as such they don't really compare. My take is that 99.9% of all users will not have any involvement with the bootclasspath and for them having the JRE at the end is the correct setup for both compile- and runtime - regardless of JRE - especially since you have to explicitly set up the bootclasspath in an eclipse launch config anyway. I really do not see how modifying the classpath.jelly template for the generated .classpath file influences any related bootclasspath/runtime problems? > Improve JRE_CONTAINER classpath entry > ------------------------------------- > > Key: MNG-1020 > URL: http://jira.codehaus.org/browse/MNG-1020 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Versions: 2.0-beta-1 > Reporter: Mark Hobson > > > Same as MPECLIPSE-104 but for m2, although this only really makes sense for > dependencies in the bootclasspath as only they can override the JRE. Hence > this issue depends on MNG-973. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
