Yes, this is by design. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
Gilles Dodinet <[EMAIL PROTECTED]> wrote on 02/09/2003 02:49:55 AM: > ive encountered such a problem some time ago. i solved it by adding a > namespace pointing to the plugin (or so it seems) : > > <project xmlns:test="test" ..> ... </project> > > where test is the test plugin (maven-test-plugin). - please note that > after that the 'test' namespace was never used. > > im really not sure if this should work (perhaps if this was just a > side-effect), tho it has for me. maybe this can help. > > -- gd > > > > Brett Porter wrote: > > >Most plugins have a hook that you can add as a prereq (although not on a > >preGoal - you'd need to do that differently by preGoal calling attainGoal on > >the content). > > > >Eg. War:load does nothing but bring the plugin into action. > > > >This is likely to change in the future. > > > >- Brett > > > > > > > >>-----Original Message----- > >>From: khote [mailto:[EMAIL PROTECTED] > >>Sent: Monday, 1 September 2003 3:43 PM > >>To: Maven Users List > >>Subject: Re: plugin.jelly variables not available in <postGoal> > >> > >> > >>I can use > >>${pom.getPluginContext('maven-WHATEVER-plugin').getVariable('X > >>XX')} only if that WHATEVER plugin was invoked prior to the > >>pre or post Goal I'm working with. I think it has to load > >>that stuff from the plugin's project.properties, I don't yet > >>know of a way to "easily" load those properties files. > >> > >>I was using the xdoc plugin, and for some reason wanted to > >>include the target/docs in my WAR. Since it's always > >>convenient to use the default properties when they work, I > >>wanted to use the xdoc properties. If I run: > >> > >>$ maven xdoc > >>$ maven war > >> > >>rather than: > >> > >>$ maven xdoc war > >> > >>then the xdoc properties would not be available to my > >>war:webapp postGoal using the > >> > >>${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven > >>.xdoc.dest.dir > >>')} (or whatever it was). > >> > >>What if I have several versions of the plugin, including a > >>SNAPSHOT? Maven seems to know how to load the latest and > >>greatest, perhaps I'd have to write a plugin to do all that > >>for me: maven-loadUninvokedPluginProperties-plugin > >>or some such. > >> > >>----- Original Message ----- > >>From: <[EMAIL PROTECTED]> > >>To: "Maven Users List" <[EMAIL PROTECTED]> > >>Sent: Sunday, August 31, 2003 9:53 PM > >>Subject: Re: plugin.jelly variables not available in <postGoal> > >> > >> > >> > >> > >>>Does ${pom.getPluginContext('maven-war-plugin').getVariable('XXX')} > >>>help? > >>>-- > >>>dIon Gillard, Multitask Consulting > >>>Blog: http://blogs.codehaus.org/people/dion/ > >>> > >>> > >>>"khote" <[EMAIL PROTECTED]> wrote on 30/08/2003 10:25:26 AM: > >>> > >>> > >>> > >>>>I'm playing around with a postGoal for webapp ... > >>>> > >>>><postGoal name="war:webapp"> > >>>>.... > >>>></postGoal> > >>>> > >>>>I'm copying the docs directory generated by the xdoc > >>>> > >>>> > >>plugin into my .war > >> > >> > >>>>I notice in the plugin documentation that certain values such as > >>>>maven.war.webapp.dir have default values. I look in the > >>>> > >>>> > >>>maven-war-plugin's > >>> > >>> > >>>>plugin.jelly and see where they are set. Yet these values are not > >>>> > >>>> > >>>available > >>> > >>> > >>>>to my maven.xml postGoal, in fact they have no value at > >>>> > >>>> > >>all by the time > >> > >> > >>>they > >>> > >>> > >>>>get there. I have to manually set them in > >>>>project.properties/build.properties or even reset them to the same > >>>> > >>>> > >>>values in > >>> > >>> > >>>>my maven.xml postGoal. It would be nice if I could use > >>>> > >>>> > >>the expected > >> > >> > >>>>defaults in postGoals, is there a setting somewhere that > >>>> > >>>> > >>can take care > >> > >> > >>>of > >>> > >>> > >>>>this? > >>>> > >>>>K > >>>> > >>>> > >>>> > >>>> > >>>> > >>--------------------------------------------------------------------- > >> > >> > >>>>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] >
