> From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 30 September 2003 11:52 PM > > On Tue, 2003-09-30 at 09:45, Tim Anderson wrote: > > I not sure I see how the caller plugin helps > > in this regard. The objective is to run rmic after > > java:compile, not replace it. > > A small rmi plugin (as Brett indicated) which simply > > invokes rmic as a postGoal to java:compile would be all > > that is required no? > > Yes, but what Vincent is trying to do is capture a notion like > "compiling the project". So he has started this process with the caller > plugin. > > So if someone is using aspects and RMI then your plugin would still be > off use. Vincent is trying not to tie a particular goal, the the RMI > goal, to java:compile but to the notion of "compiling the project". I'm > not sure how far Vincent has gone or if it is possible but for your use > case we probably want to decorate the "compile a project" notion with a > postGoal that does the RMI stuff. > > In this way various compilation mechanisms can be used any your RMI > plugin would remain useful for all of them, even when you don't know in > advance what those compilation mechanisms will be. > > Make sense? >
Think so. However for prereqs, preGoals and postGoals to work, won't there also need to be a proxy goal for each WKGI specified in the caller plugin? E.g: <goal name="proxy-compile-java"> <!-- invoke java:compile or aspectj:compile etc --> <caller:call goalInterface="compile-java"/> </goal> <postGoal name="proxy-compile-java"> <!-- do rmic stuff --> </postGoal> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
