I think the deploy plugin was moved, so after bootstrapping you'll need to check out maven-plugins from CVS and run maven plugin:install on the deploy plugin.
Alternatively, your plugin could have a dependency on the deploy plugin <dependency> <type>plugin</type> <artifactId>maven-deploy-plugin</artifactId> <version>WHATEVER_IT_IS_ON_IBIBLIO</version> <groupId>maven</groupId> </dependency> This is probably a good idea. What will your JWSDP plugin do? I have previously written one for JAXB's xjc task. When you contribute it, it will need to go to maven-plugins.sf.net for licensing reasons, instead of Maven's CVS (at least for now). - Brett > -----Original Message----- > From: Scott Tavares [mailto:[EMAIL PROTECTED] > Sent: Friday, 7 November 2003 1:24 PM > To: Maven Users List > Subject: copying the dependencies > > > Hi all, I'm writing a maven plugin for the JWSDP-1.3. I was > using maven > rc-1 with the following tag in a goal: > > > <deploy:copy-deps todir="${jwsdp.build}/WEB-INF/lib"/> > > which worked well. But I decided to build maven from cvs and to start > using artifact and group ID's. Now the above tag does not > work anymore. So my question is, is there a replacement tag I > should be using or did > something break between rc1 and what's in CVS as of 9:00 pm est. us? > > TIA, > > -ScottTavares- > > p.s. I plan on contributing my jwsdp plugin once it is done > if anyone is > interested in it. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
