[ 
http://jira.codehaus.org/browse/MNG-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129545#action_129545
 ] 

B. Garvelink commented on MNG-3345:
-----------------------------------

+1

An alternative to introducing a new {{<classpath>}} element to the archiver 
configuration would be to concatenate entries with the same key, instead of 
relying on the overwrite / use-last-inserted behaviour that's there now. This 
way, no new configuration element is required. It seems unlikely to me that 
anyone is deliberately relying on the current behaviour, but that could be 
awfully naive of me. I'm fine with either solution, really.

{code:xml}
<manifestEntries>
        <Class-Path>plugins/framework</Class-Path>
        <Class-Path>plugins/checkservices</Class-Path>
        <Class-Path>plugins/transferservices</Class-Path>
</manifestEntries>
{code}

> Ability to list Class-Path: elements individually
> -------------------------------------------------
>
>                 Key: MNG-3345
>                 URL: http://jira.codehaus.org/browse/MNG-3345
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: maven-archiver
>    Affects Versions: Reviewed Pending Version Assignment
>         Environment: All
>            Reporter: Robert Egan
>            Priority: Minor
>             Fix For: Reviewed Pending Version Assignment
>
>
> I'd like a method to list my classpath elements in a manner other than in one 
> long string. For example, one of my production jars contains the following 
> entry
> Class-Path: plugins/framework plugins/checkservices plugins/transferse
>  rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap
>  ps securityUtil-hotfix.jar securityUtil.jar wcmCache-hotfix.jar wcmCa
>  che.jar wcmPrincipals-hotfix.jar wcmPrincipals.jar  lib/gnu/gnu-crypt
>  o.jar lib/oracle/jdbc-10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1
>  .0/jdbc_rowset_tiger1.0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.ja
>  r lib/emory.edu/backport-util-concurrent-2.2/backport-util-concurrent
>  .jar lib/apache/jakarta-commons/commons-cli-1.0.jar lib/apache/jakart
>  a-commons/commons-collections-3.1.jar lib/apache/jakarta-commons/comm
>  ons-dbcp-1.2.1.jar lib/apache/jakarta-commons/commons-lang-2.1.jar li
>  b/apache/jakarta-commons/commons-pool-1.2.jar lib/apache/jakarta-comm
>  ons/commons-logging-1.0.4/commons-logging.jar lib/rsa/authapi.jar lib
>  /apache/log4j/log4j-1.2.8.jar lib/jradius/jradius.jar lib/jradius/jra
>  dius-dictionary.jar lib/httpclient/commons-codec-1.3.jar lib/httpclie
>  nt/commons-httpclient-3.0.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswe
>  go.edu/util-concurrent-1.3.4.jar
> And it sure would be nice to have something like
> <classpath>
> <entry>plugins/framework</entry>
> <entry>plugins/checkservices</entry>
> <entry>plugins/transferservices</entry>
> <entry>...etc</entry>
> </classpath>

-- 
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

        

Reply via email to