[ http://issues.apache.org/jira/browse/TUSCANY-1?page=comments#action_12364670 ]
Jack D. Unrue commented on TUSCANY-1: ------------------------------------- Yes, I should have documented this in my previous email. First, try running the pom.xml from the acceptance directory -- that should get you past this. The larger question is whether the configuration for the maven-antrun-plugin should be moved down into each acceptance POM, which I suppose is the easiest solution. Or if there is a way to keep that where it's located now, but get the path to the build.xml to resolve correctly in either case, that would be ideal. > port build process to Maven2 > ---------------------------- > > Key: TUSCANY-1 > URL: http://issues.apache.org/jira/browse/TUSCANY-1 > Project: Tuscany > Type: Improvement > Components: Build System > Environment: Java > Reporter: Jack D. Unrue > Assignee: Jeremy Boynes > Attachments: acceptance_poms.zip, tuscany_m2_poms.zip > > Port the existing Tuscany/Java build process from Maven1.x to Maven2.x. Leave > the existing maven files in place until the new build is working and there is > consensus to remove the old build. -- 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
