maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCOMPILER-20) add bootclasspath support to forked java compiler
Date Wed, 31 Oct 2007 22:58:10 GMT

    [ http://jira.codehaus.org/browse/MCOMPILER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112295
] 

Benjamin Bentmann commented on MCOMPILER-20:
--------------------------------------------

bq. <library>xerces:xerces</library>

Wouldn't something like
{code:xml}
<library>
  <groupId>bla<groupId>
  <artifactId>bla<artifactId>
  ...
<library>
{code}
be more Maven-like? Personally, I don't like the single string approach for artifact naming
in configurations as it requires one to remember the proper order of its components. This
single string introduces another syntactical element that users must learn to understand and
developers must properly parse. I would argue that XML's parsing facilities are sufficient
to avoid such artifical constructs.

bq. The bootclasspath should be configurable not only for the forked version but should be
a general feature.
+1

bq. [...] that the ability to specifiy the bootclasspath also lacks in the underlying plexus
compiler plugin.

The maven-compiler-plugin already knows how to pass arbitrary arguments using the <compilerArguments>
element. The hint given at http://docs.codehaus.org/display/MAVENUSER/Compile+and+Test+with+Different+JDK+Versions
makes use of this. The remaining work would be to avoid hard-coding local repo paths but to
make use of Maven's artifact resolution from remote repos.

> 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

        

Mime
View raw message