Jochen Wiedmann wrote:
I haven't yet had the time to evaluate how to exclude classes
dynamically in Maven
<build>
<sourceModifications>
<sourceModification>
<className>com.sun.org.apache.xerces.internal.impl.xpath.regex.RegularExpression</className>
<excludes>
<exclude>**/Java5REHandler.java</exclude>
</excludes>
</sourceModification>
</sourceModifications>
</build>
Means that if RegularExpression is NOT found then exclude
Java5REHandler.java on the build process. Similarly you could include
other files with the includes tag.
I must say, though that there is an outstanding bug when using multiple
sourceModifications. See:
http://jira.codehaus.org/browse/MPJAVA-38
I think the most important point is that we should have a set of
documented goals in the main project. We developers will typically be
able to find the available goals easily. For a user, however, who is
just using the svn version or source distribution, it should be
possible to find the required steps easily. May be, an XDoc page in
the main project would do?
then it's probably easier to have them as .properties
PD: I'll try to investigate why we need commons-jelly-tags-fmt
I'd assume that this is a bug in Maven. We can live with that, if the
workaround works.
I'll try to use newer versions of xdoc plugin to see if this was fixed
(1.0.2 comes with xdoc-1.8 and they are currently on 1.9.1)
best regards,
nacho
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
