Assuming that you want to continue to use your build.xml for 1-3, then you just need to bind the antrun plugin's run goal to the compile phase.
Maven doesn't have tasks. It has goals and phases. Justin On 8/25/10 11:05 AM, Jacob Beard wrote: > Hi, > > I'm working on a Commons sandbox component which is written mostly in > JavaScript. I currently have an ant build which includes tasks to do the > following: > > 1. combine all of the JavaScript modules into a single file > 2. minify the combined JavaScript file using the Google Closure > JavaScript compiler > 3. compile the combined JavaScript file to a single Java class file > using the Rhino jsc compiler > 4. create an executable JAR containing the class file. > > I'm interested in working toward releasing the project, and so I'm > trying to determine what would be the most elegant way to now build this > project with Maven. Based on my understanding of the tasks performed by > Maven when staging a release, it seems to me that the compiler task > would need to be made to delegate to tasks 1-3 of the project's Ant > script. After the class file has been created with jsc, I believe the > Maven jar and assembly tasks should work as though the project were a > regular Java project. > > If my understanding so far is correct, I'm wondering what is the best > way to override or customize the behaviour of Maven's compiler task so > that it delegates to Ant (probably via the antrun Maven plugin)? > > I'd appreciate any guidance anyone can provide. Thanks, > > Jake > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
