Sounds like a good improvement to put in JIRA. - Brett
On 11/16/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > > Hi, > > the maven-eclipse-plugin typically generates the following entry in the > .classpath file: > > <classpathentry kind="var" rootpath="JRE_SRCROOT" > path="JRE_LIB" sourcepath="JRE_SRC"/> > > Eclipse (3.2M3) understands, that it has to add the rt.jar file to the > classpath. > > The problem is, that the JRE has more jar files than just rt.jar: In > particular, jsse.jar and jce.jar are separate files. IMO, these should > be added to the classpath too. This can be done with an entry like > > <classpathentry kind="con" > path="org.eclipse.jdt.launching.JRE_CONTAINER"/> > > Obviously, one can set the maven-eclipse-plugin property > classpathContainers to add the org.eclipse.jdt.launching.JRE_CONTAINER. > That works fine, and the complete JRE jar files are now in your classpath. > > But wait: Eclipse refuses the classpath now, because rt.jar is > configured twice! > > Am I doing something wrong? IMO, the maven-eclipse-plugin should either > > a) Offer a property that replaces the "var" definition of the JRE with > the "con" definition. (Or even better, do this by default.) > b) Remove the "var" definition, if the JRE_CONTAINER is present. > > Is this a bug? Any workarounds? > > > Regards, > > Jochen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
