Re: build finesse documentation?
You should check out the goals and properties for the war plugin. http://maven.apache.org/reference/plugins/war/ There are some include/exclude properties that should help. You can also see which goals to create pre and post goals for. Keith Irwin wrote: Folks-- I'm trying to convert from ant to maven, but can't find anything about how to use maven.xml to do some fancy stuff. For instance, what I want to do is be able to filter out certain classes, and use a different web.xml depending on the lifecycle of the app. Using the ant war task, I can do things like: classes dir=${classes.dir} patternset refid=exclude.devel/ /classes which removes all classes in **/devel/** if devel.tweak is set. I'm guessing that this kind of thing might be solved either by 1. creating a new goal to generate the war file rather than using the default or 2. using the resources stuff in project.xml. My main question, though, is if anyone knows of any documentation about this sort of thing somewhere on the maven site? Thanks, Keith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build finesse documentation?
On Tue, 2003-12-30 at 13:36, __matthewHawthorne wrote: You should check out the goals and properties for the war plugin. http://maven.apache.org/reference/plugins/war/ There are some include/exclude properties that should help. You can also see which goals to create pre and post goals for. Hm. Thanks. I think this is a good place to start. The problem I'm having, though, is understanding what goes in the pre/postGoal sections. For instance, when it says something like create a postGoal then set a property, I'm not sure if it's possible to set that property dynamically. In ant, you can't do that, for instance. Well, I'll play around. Keith Keith Irwin wrote: Folks-- I'm trying to convert from ant to maven, but can't find anything about how to use maven.xml to do some fancy stuff. For instance, what I want to do is be able to filter out certain classes, and use a different web.xml depending on the lifecycle of the app. Using the ant war task, I can do things like: classes dir=${classes.dir} patternset refid=exclude.devel/ /classes which removes all classes in **/devel/** if devel.tweak is set. I'm guessing that this kind of thing might be solved either by 1. creating a new goal to generate the war file rather than using the default or 2. using the resources stuff in project.xml. My main question, though, is if anyone knows of any documentation about this sort of thing somewhere on the maven site? Thanks, Keith - 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]
Re: build finesse documentation?
Okay, I'm getting it. You can use jelly inside the goals to take care of some of the things that ant did with its target directive. I can't wait for the book on this subject. ;) Keith On Tue, 2003-12-30 at 13:48, Keith Irwin wrote: On Tue, 2003-12-30 at 13:36, __matthewHawthorne wrote: You should check out the goals and properties for the war plugin. http://maven.apache.org/reference/plugins/war/ There are some include/exclude properties that should help. You can also see which goals to create pre and post goals for. Hm. Thanks. I think this is a good place to start. The problem I'm having, though, is understanding what goes in the pre/postGoal sections. For instance, when it says something like create a postGoal then set a property, I'm not sure if it's possible to set that property dynamically. In ant, you can't do that, for instance. Well, I'll play around. Keith Keith Irwin wrote: Folks-- I'm trying to convert from ant to maven, but can't find anything about how to use maven.xml to do some fancy stuff. For instance, what I want to do is be able to filter out certain classes, and use a different web.xml depending on the lifecycle of the app. Using the ant war task, I can do things like: classes dir=${classes.dir} patternset refid=exclude.devel/ /classes which removes all classes in **/devel/** if devel.tweak is set. I'm guessing that this kind of thing might be solved either by 1. creating a new goal to generate the war file rather than using the default or 2. using the resources stuff in project.xml. My main question, though, is if anyone knows of any documentation about this sort of thing somewhere on the maven site? Thanks, Keith - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]