Historical reasons. I imagine deploy and artifact will merge at some point in the future. Most new stuff gets done with artifact, but site:deploy and dist:deploy have been around a lot longer than artifact have, and never got changed over.
- Brett > -----Original Message----- > From: Dominik Roblek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 28 October 2003 11:28 PM > To: [EMAIL PROTECTED] > Subject: "deploy" and "artifact" plugins > > > I'm pretty confused when looking at "artifact" and > "deploy" plugins. It seems to me, that they offer very > similar functionality. Some plugins depends on > "artifact" plugin (e.g. "ejb", "war", "ear", > "javadoc") and some on "deploy" plugin (e.g. "dist"). > And "deploy" plugin doesn't delegate its work to > artifact plugin. Why? > > Also "deploy" plugin depends on "maven.repo.central" > property and "artifact" plugin depends on somewhat > redundant "maven.repo.list” property. > > There seems to be another "site" plugin which offer > quite similar functionality to "deploy" plugin but it > is implemented in its one way. Why such diversity? Is > it necessary or is it so because of historical > reasons? > > Otherwise Maven seems great tool, as far as I learned > about it! Just all these deployers make me confused me > and I don't know how to use them in right way. > > Thanks for your help, > Dominik Roblek > > > __________________________________ > Do you Yahoo!? > Exclusive Video Premiere - Britney Spears > http://launch.yahoo.com/promos/britneyspears/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
