Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.5
-
Labels:None
-
Number of attachments :
Description
I believe this is also true for several other plugins (javadoc, etc). This means that if you use something like:
<path id="maven.j2ee.compile.src.set" location="$
{pom.build.sourceDirectory}/../j2ee$
{cactus.j2ee.version}"/>
<maven:addPath id="maven.compile.src.set" refid="maven.j2ee.compile.src.set"/>
it won't work with several plugins...
I'm starting to think that allowing multiple source directories in project.xml wouldn't be so bad at all and that there are valid cases (I believe Cactus is one - I'm happy to discuss that though).
Thanks
-Vincent
Jason did a good job for a similar request:
http://jira.codehaus.org/browse/MAVEN-130
This would be good for jxr too. I am voting +1!
Additionally I think configuration of multiple source folders
in the project.xml might really clean up the hacking in maven.xml.
I am bored of all this "re-think why you need several source folders...".
Explanation why it's bad may be easy but explanation how to do without
it for a mature project that uses it for reasonable purposes is harder.