[
https://jira.codehaus.org/browse/MEXEC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MEXEC-53.
-------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
This doesn't seem right. The order in which Maven resolves the dependencies to
build should be exactly the same as it should run.
> Prioritise dependencies in classpath tag
> ----------------------------------------
>
> Key: MEXEC-53
> URL: https://jira.codehaus.org/browse/MEXEC-53
> Project: Maven 2.x Exec Plugin
> Issue Type: New Feature
> Components: java
> Affects Versions: future
> Environment: patch built on top of trunk at revision 7287
> Reporter: Tristan King
> Assignee: Robert Scholte
> Priority: Trivial
> Attachments: exec-maven-plugin.diff
>
>
> I had a problem where I needed to prioritise specific jars to ensure they
> appear at the start of the classpath so I wrote this patch.
> to use it, simply put <priority> tags in the <classpath> section.
> i.e. the following will ensure that commons-io and commons-lang appear in the
> front of the classpath of everything else.
> {code:xml}
> <configuration>
> <executable>java</executable>
> <arguments>
> <argument>-classpath</argument>
> <classpath>
> <priority>commons-io:commons-io</priority>
> <priority>commons-lang:commons-lang</priority>
> </classpath>
> </arguments>
> </configuration>
> {code}
> As far as i can tell the patch doesn't disrupt any existing functionality,
> and <dependency> tags can be used in unison with the <priority> tags.
> still to do: testing (maybe someone who is more familiar with this would be
> better suited to build the tests).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
