[
http://jira.codehaus.org/browse/MEXEC-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lacoste updated MEXEC-30:
--------------------------------
Attachment: MEXEC-30.diff
The attached patch adds the requested functionality for the exec mojo. Not the
java one.
The patch also:
* allows to use regular expressions to match dependencies
* adds a warning if one uses in his/her path a <dependency> that matches none
of the project dependencies
* keep the dependencies in the order they are defined in the <classpath> section
With that patch, one is forced to use the <classpath> element to specify these
new path elements, hence the implementation of the regular expression support.
Below is the example of the change in documentation which should give a feel
how this would work.
Adding the same functionality to the java mojo would require a different user
configuration. So I am unsure if this is the right way to do it.
Feel free to comment on the patch. I don't intend to commit it as is as I am
not satisfied with the way the user configuration is going nor the way the 2
main exec mojos stay in sync. There must be a better way.
+ dependencies can also be regular expressions:
+-------------------
+ ...
+ <classpath>
+ <dependency>commons.*</dependency>
+ </classpath>
+ ...
+-------------------
+
+Finally one can also add extra locations (e.g. for resources that one don't
want to be packaged)
+
+-------------------
+ ...
+ <classpath>
+ <element>src/main/nonpackagedresources</element>
+ <dependency>.*</dependency>
+ </classpath>
+ ...
> A directory cannot be added to the classpath in exec or java
> ------------------------------------------------------------
>
> Key: MEXEC-30
> URL: http://jira.codehaus.org/browse/MEXEC-30
> Project: Maven 2.x Exec Plugin
> Issue Type: New Feature
> Affects Versions: 1.0.2, 1.1-beta-1
> Environment: WinXP/Java 1.5
> Reporter: Tim Pizey
> Assignee: Jerome Lacoste
> Attachments: MEXEC-30.diff
>
>
> There is no mechanism for adding a directory to the classpath for the plugin,
> there is only a mechanism for adding a jar.
> Use case: adding a properties file to the claspath of the plugin without
> wishing that properties file to be included in the artifact jar.
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
