This is a known issue, should be fixed by RC2. The previous workaround is that the cactus plugin should call one goal in java to make sure it is loaded. An example of such a dummy goal is war:load.
This also breaks the appserver/webserver plugin combo, which I filed in JIRA the other day. - Brett > -----Original Message----- > From: Sean Timm [mailto:[EMAIL PROTECTED] > Sent: Thursday, 16 October 2003 3:05 AM > To: Maven Developers List > Subject: RE: Context variables only available if plugin > previously loaded... > > > This is with the RC1 version, btw... > > > -----Original Message----- > > From: Sean Timm > > Sent: Wednesday, October 15, 2003 11:04 AM > > To: [EMAIL PROTECTED] > > Subject: Context variables only available if plugin > > previously loaded... > > > > I've run into a problem while attempting to use the Cactus > plugin. It > > references several variables from the java plugin. For example: > > ${pom.getPluginContext('maven-java-plugin').getVariable('maven > .compile.t > > arget')} > > > > At the command-line, I call the cactus-compile goal. The > > problem seems > > to be that the java plugin never gets accessed, so these > variables are > > empty. If I do the following instead, everything works: > > > > maven java:compile cactus:compile > > > > Is this a known issue? I made an account on Jira to look up > > bugs...should I be logging issues I run into there? > > > > Thanks! > > > > -- > > Sean Timm > > > > > --------------------------------------------------------------------- > > 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] >
