You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 03:55:12 UTC
[jira] Updated: (MNG-3348) Add new dependency scope "bootstrap" to
support concept of boot class path
[ http://jira.codehaus.org/browse/MNG-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3348:
------------------------------
Fix Version/s: 2.x
> Add new dependency scope "bootstrap" to support concept of boot class path
> --------------------------------------------------------------------------
>
> Key: MNG-3348
> URL: http://jira.codehaus.org/browse/MNG-3348
> Project: Maven 2
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 2.0.8
> Reporter: Benjamin Bentmann
> Fix For: 2.x
>
>
> When it comes to cross-platform compilation, one needs to feed in a bootclasspath into various JDK tools like javac or javadoc (see MCOMPILER-20, MOJO-606). Currently, the affected Maven plugins provide a configuration parameter on their own to deal with this concept. Usually, this configuration needs to be configured with file system paths (either to some JARs in the local repo or to the user's JDK installation).
> That's not really the Maven way. Maven builds classpaths from dependencies and hence, the bootclasspath should be configurable via dependencies, too. Having a dedicated scope for such dependencies would make plugin development and configuration more straightforeward in the case of cross-platform compilation.
> My post MCOMPILER-20#action_112355 may be used as an inspiration, how such a new scope could look like.
--
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