I read it, I just don't think it's intuitive. "If a "+" is found then the artifact name is a concatenation of the lhs and rhs of the "+" where the "+" is replaced with a "-". If there are"
ant+optional version 1.4.1 becomes ant-optional-1.4.1.jar, whereas ant version 1.4.1 becomes ant-1.4.1.jar... I understand it and why..........but intuitive it aint. To me it looks like the <id> is playing double duty as a tag. It'd more intuitive to give it another name rather than cramming it into the same tag, IMHO. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers Jason van Zyl <[EMAIL PROTECTED]> wrote on 07/22/2002 08:00:30 AM: > On Sun, 2002-07-21 at 17:57, [EMAIL PROTECTED] wrote: > > I don't get it. > > > > Why make plugin dependencies different from normal.....what's the '+' > > about? > > They are not different. Read the 'Summary of Changes' message I posted, > the rational for the dependency notation is fully explained under the > dependencies heading. Here's the link: > > http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgNo=2305 > > > The download worked once I put the jar up into jars2..... > > -- > > dIon Gillard, Multitask Consulting > > Work: http://www.multitask.com.au > > Developers: http://adslgateway.multitask.com.au/developers > > > > > > Jason van Zyl <[EMAIL PROTECTED]> wrote on 07/22/2002 03:20:57 AM: > > > > > On Sun, 2002-07-21 at 12:51, [EMAIL PROTECTED] wrote: > > > > How do plugins now declare their dependencies on each other? > > > > > > It's just another project so you declare it in the <dependencies/> but > > > before it will work I think I'm going to change the plugin name pattern > > > from: > > > > > > <name>-maven-plugin-<version>.jar > > > > > > to: > > > > > > maven-<name>-<version>.jar > > > > > > So using a concrete example changing j2ee-maven-plugin-1.0.jar to > > > maven-j2ee-plugin-1.0.jar. > > > > > > Then I will deploy all the plugin jars to the <remote-repo>/maven/jars/ > > > directory and the following dependency entry will work: > > > > > > <dependency> > > > <id>maven+j2ee-plugin</id> > > > <version>1.0</version> > > > </depedency> > > > > > > > I've noticed the struts plugin which depends on classes in the j2ee > > plugin > > > > is royally stuffed in the current builds. > > > > > > Won't be for long. > > > > > > > I'm trying adding the j2ee plugin in as a dependency. > > > > > > Use the above entry and I will change the names of the plugins today and > > > then they can be deployed and managed like anything else. > > > > > > > -- > > > > dIon Gillard, Multitask Consulting > > > > Work: http://www.multitask.com.au > > > > Developers: http://adslgateway.multitask.com.au/developers > > > -- > > > jvz. > > > > > > Jason van Zyl > > > [EMAIL PROTECTED] > > > http://tambora.zenplex.org > > > > > > In short, man creates for himself a new religion of a rational > > > and technical order to justify his work and to be justified in it. > > > > > > -- Jacques Ellul, The Technological Society > > > > > > > > > -- > > > To unsubscribe, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: < > > > mailto:[EMAIL PROTECTED]> > > > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > -- > To unsubscribe, e-mail: < > mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < > mailto:[EMAIL PROTECTED]> >
