[ http://issues.apache.org/jira/browse/CACTUS-211?page=comments#action_64688 ] Vincent Massol commented on CACTUS-211: ---------------------------------------
The only case I have found the usage of maven.compile.src.set useful is for source code generation. So yes, there is a valid use case if someone generates Cactus tests. I just hope that people won't use it in other weird use cases that go against the Maven philosophy... ;-) Please go ahead. Thanks. PS: I don't understand your reason for not having a multi-project... ;-) I've done that several times and it works just fine. For example, I don't understand why the common project couldn't be a jar, etc. > Support multiple source directories > ----------------------------------- > > Key: CACTUS-211 > URL: http://issues.apache.org/jira/browse/CACTUS-211 > Project: Cactus > Type: Improvement > Components: Maven Integration > Versions: 1.7 > Reporter: Felipe Leme > Assignee: Felipe Leme > Fix For: 1.8 > > Cactus should allow tests to be defined in multiple directories. Although > this is against the "Maven way", tha maven-java-plugin allows that, so Cactus > should mimic its behaviour. > Right now, the source is defined using the following Ant task: > <ant:src path="${cactus.src.dir}"/> > While on maven-java-plugin it is slightly different: > <ant:src> > <ant:path refid="maven.compile.src.set"/> > </ant:src> > I will write some test cases for this improvment and then committ the changes > (hopefully on time for 1.7.1). > -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
