> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 19, 2005 4:21 AM > To: Maven Developers List > Cc: 'Henri Yandell' > Subject: payload > > > http://www.osjava.org/payload/index.html > > This seems very much related to what we were talking about > with respect > to filtering - applying deployment profiles to previously > built artfiacts. > Yes. Now I am sure that we are on the same page :).
I have one question - what's really the signification of <packaging> tag in POM? Does it activate a plugin or does it tell maven what will be the type of the main artifact or both? (I am not only asking about current state of the implementation but also about your plans regarding it- so please don't send me to read sources!) Say that I have a plugin which takes existing war and somehow mutates it and produces another war on output. Will I still use <packaging>war</packaging> in such case? I belive that multiple plugins can create artifacts of the same type. so somehow I feel that either a <type> tag is also needed in pom or plugins should inform mave core (via metadata?) what types of artifacts are they creating. Also how install and deploy plugins will work when secondary artifacts are going to be present? Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
