This isn't currently possible. I don't understand the need to filter andromda.xml. Can you elaborate?
This essentially means a parameter to the build completely changes the sources, completely changing the project - meaning that it should be at least in a profile if not a separate project. Also, I get the feeling andromda.xml is not actually a resource, but a configuration file for the build not included in the resulting JAR - if that's correct, you probably need to use the (reusable) filtering code to load the xml file instead of processing it as a resource. -Brett On 10/26/05, Chad Brandon <[EMAIL PROTECTED]> wrote: > Jason van Zyl wrote: > > On Tue, 2005-10-25 at 18:02 -0700, Chad Brandon wrote: > > > >> Hello, > >> > >> I'm currently writing am m2 plugin for AndroMDA > >> (http://www.andromda.org), at the moment our build is > >> based on m1, but I'll be converting that to m2 > >> shortly. Anyway I have a question: how would I force > >> the "process-resources" phase to be called before the > >> "generate-sources" phase within my plugin? I need the > >> process-resources phase to happen before > >> generate-sources because we have a configuration file > >> (andromda.xml) that needs to have resource filtering > >> occur before its passed to the AndroMDA engine that > >> processes the model(s). > >> > > > > The default life cycle has a fixed ordering. > > > > So you want to : > > > > 1) filter andromda.xml > > 2) generate sources from the filtered andomda.xml file > > > Exactly. > > You have a template andromda.xml file that users can interpolate their > > options into and then you generate sources from that? > Yep. > > Just so I > > understand what you're trying to do. You probably don't need to wrangle > > with the life cycle. > > > In that case how do I cause the filtering of resources (i.e. the > "process-resources" phase) to occur before the generate-sources phase > (since my andromda:run goal is executed during that phase?). > > Thanks again, > > Chad > > > >> Thanks in advance, > >> > >> Chad > >> > >> --------------------------------------------------------------------- > >> 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]
