You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2007/11/01 16:36:10 UTC
[jira] Commented: (MCOMPILER-20) add bootclasspath support to
forked java compiler
[ http://jira.codehaus.org/browse/MCOMPILER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112355 ]
Benjamin Bentmann commented on MCOMPILER-20:
--------------------------------------------
bq. 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.
The maven-javadoc-plugin is a further example of a plugin that would need to use the boot class path (using javadoc's -bootclasspath option), so Frank's suggestion is really reasonable.
To give some inspiration for an implementation, I could imagine to introduce a further artifact scope like "bootstrap" and a method MavenProject.getBootstrapClasspathElements() that would allow plugins to get those artifact paths. The tricky task would be to properly define the semantics for this new scope in regard to the other scopes and transitive dependency resolution.
I guess the existing scope "provided" is the most similar to "bootstrap":
- only use bootstrap entries for compilation, not for runtime or test (e.g. compile against JSE 1.3 but test using JSE 1.5)
- never include boostrap entries during transitive dependency resolution
- never package bootstrap entries into WARs or similar assemblies
The whole difference between "provided" and "bootstrap" would be that plugins can access those dependency sets independently such that they can be fed into SDK tools using separate command line options (i.e. -bootclasspath vs. -classpath).
> add bootclasspath support to forked java compiler
> -------------------------------------------------
>
> Key: MCOMPILER-20
> URL: http://jira.codehaus.org/browse/MCOMPILER-20
> Project: Maven 2.x Compiler Plugin
> Issue 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