Filtering deployable files
--------------------------
Key: MOJO-1551
URL: http://jira.codehaus.org/browse/MOJO-1551
Project: Mojo
Issue Type: Improvement
Components: native
Affects Versions: apt-maven-plugin-1.0-alpha-4,
buildnumber-maven-plugin-1.0-beta-5
Environment: Any
Reporter: Jean-Marie Dautelle
When source directories are deployable, everything is included in the .inczip.
The .cpp, others resources, sub-directories, etc.
For our legacy projects, this results in unnecessarily large .inczip files.
I understand that you recommend keeping the .h/.hpp files in separated
directories but this is not always possible when working with legacy projects.
A simple fix (which would help us greatly) would be to have the deployable
property to take values others than simple true/false. For example:
<deployable>*.hpp</deployable> to deploy only the .hpp files,
<deployable>all</deployable> could be equivalent to
<deployable>true</deployable> and <deployable>none</deployable> could be
equivalent to <deployable>false</deployable> (still we can keep the old values
true/false for backward compatibility)
--
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