[ 
http://jira.codehaus.org/browse/MDEP-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brian Fox closed MDEP-125.
--------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-alpha-5

A plugin can't set a property that would then affect a pom because the poms are 
already interpolated prior to executing a plugin. However, I modified the 
source to optionally output the classpath file using the filter format 
(classpath=xxxx) so that the resulting file can then be used by the resource 
plugin to filter other files with the classpath.

> Build-classpath should store the classpath in a Filter
> ------------------------------------------------------
>
>                 Key: MDEP-125
>                 URL: http://jira.codehaus.org/browse/MDEP-125
>             Project: Maven 2.x Dependency Plugin
>          Issue Type: Improvement
>          Components: build-classpath
>    Affects Versions: 2.0-alpha-4
>            Reporter: Ludovic Claude
>            Assignee: Brian Fox
>             Fix For: 2.0-alpha-5
>
>
> I have some web.xml files which contain in their environment parameters a 
> list of jars to be downloaded by the client applets, for example:
>       <env-entry>
>               <description>Shared jars parameter</description>
>               <env-entry-name>applet/shared_jars</env-entry-name>
>               <env-entry-value>ejb.jar, axis.jar, axis-ant.jar, jaxrpc.jar, 
> saaj.jar, wsdl4j.jar, commons-discovery.jar, commons-logging.jar, 
> [...]</env-entry-value>
>               <env-entry-type>java.lang.String</env-entry-type>
>       </env-entry>
> (don't ask me why it's done like that, it's legacy software...)
>  It would be great to be able to isolate this list of jars in a project, and 
> then create from that project the classpath, store it in a filter which can 
> then be applied on the web.xml file.
> Then I could rewrite my web.xml like this: 
>       <env-entry>
>               <description>Shared jars parameter</description>
>               <env-entry-name>applet/shared_jars</env-entry-name>
>               <env-entry-value>${shared.jars}</env-entry-value>
>               <env-entry-type>java.lang.String</env-entry-type>
>       </env-entry>
> The list of shared jars would be defined in a new shared-jars project, which 
> would list the shared jars in its dependencies section, in pure Maven style 
> ;-)
> Thanks,
> Ludovic

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