[ http://jira.codehaus.org/browse/MCOMPILER-20?page=comments#action_61639 ]
Frank Seidinger commented on MCOMPILER-20: ------------------------------------------ The bootclasspath should be configurable not only for the forked version but should be a general feature. I'm working on a J2ME plugin for m2 and lack the ability to specify the CLDC api set for the java compiler. In this special case the bootclasspath must be used later on to preverify the compiled classes. Only after preverification the classes can be packed and transferred to a J2ME device. Therefore I would suggest to configure the bootclasspath not only for the compiler, but on a higher level so plugins on other life cycle phases can take this configuration as a reference. I would like to help with the change request but digging into the sources realized, that the ability to specifiy the bootclasspath also lacks in the underlying plexus compiler plugin. > add bootclasspath support to forked java compiler > ------------------------------------------------- > > Key: MCOMPILER-20 > URL: http://jira.codehaus.org/browse/MCOMPILER-20 > Project: Maven 2.x Compiler Plugin > Type: Bug > Reporter: Brett Porter > > > this can be required to override the DOM library used, f.e. > M1 supports arbitrary paths, and an extdirs for the same thing. Perhaps we > have add extdirs for the paths, and select dependencies for the > bootclasspath, ie: > <bootclasspath> > <libraries> > <library>xerces:xerces</library> > </libraries> > <extdirs> > <extdir>...</extdir> > </extdirs> > </bootclasspath> -- 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
