Re: [RT] Standardizing on Maven names

2004-10-14 Thread Stefan Bodewig
On Wed, 13 Oct 2004, Brett Porter [EMAIL PROTECTED] wrote: I'll get rid of it and cut a new version of the plugin. Thanks. Are there any still needing mapping that need be kept? I don't know. We usually have something like tpl-project for Apache projects, so log4j went from jakarta-log4j to

Re: [RT] Standardizing on Maven names

2004-10-14 Thread Stefan Bodewig
On Wed, 13 Oct 2004, Stefano Mazzocchi [EMAIL PROTECTED] wrote: I think, personally, that Gump and Maven should start talking about creating a more serious infrastructure and joining forces from the POM point of view. I think we are already doing that with Brett helping out a lot 8-) In the

Maven gump goal (was Re: [RT] Standardizing on Maven names)

2004-10-14 Thread Adam R. B. Jack
I'll get rid of it and cut a new version of the plugin. Are there any still needing mapping that need be kept? BTW: If you are making tweaks, would you mind moving the nag element out if projects and up onto the module? That way if we get a CVS|SVN error folks would be notified. If this isn't

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Stefan Bodewig
On Tue, 12 Oct 2004, Stefano Mazzocchi [EMAIL PROTECTED] wrote: We are having all sort of issues because maven and gump use different naming schemes. Now, why don't we just adopt their naming conventions and live peacefully together from that point on? Wholeheartedly yes when it comes to

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Brett Porter
The maven repository uses ant and I guess cocoon would be used for these. Let me clarify some terminology, just so I understand: In gump there are projects, where a project id is unique globally, and there are jar ids, where jar ids are unique within project, right? So this parallels quite

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Niclas Hedhman
On Wednesday 13 October 2004 18:17, Brett Porter wrote: Let me clarify some terminology, just so I understand: In gump there are projects, where a project id is unique globally, and there are jar ids, where jar ids are unique within project, right? So this parallels quite nicely to Maven's

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Stefan Bodewig
On Wed, 13 Oct 2004, Brett Porter [EMAIL PROTECTED] wrote: The maven repository uses ant and I guess cocoon would be used for these. When Niclas generated the Fulcrum descriptors it contained things like jakarta-ant, jakarta-turbine-torque, jakarta-log4j or jakarta-avalon that had to be fixed

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Brett Porter
Maybe the Gump plugin needs an update, or Niclas used an old version, dunno. There's only been one version with the maven tag. I've just discovered http://cvs.apache.org/viewcvs.cgi/maven-plugins/gump/src/plugin-resources/maven2gump.properties which apparently maps ids to gump ids. Among

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Stefano Mazzocchi
Stefan Bodewig wrote: On Tue, 12 Oct 2004, Stefano Mazzocchi [EMAIL PROTECTED] wrote: We are having all sort of issues because maven and gump use different naming schemes. Now, why don't we just adopt their naming conventions and live peacefully together from that point on? Wholeheartedly yes

Re: [RT] Standardizing on Maven names

2004-10-13 Thread Niclas Hedhman
On Thursday 14 October 2004 00:33, Stefano Mazzocchi wrote: I think, personally, that Gump and Maven should start talking about creating a more serious infrastructure and joining forces from the POM point of view. What do you guys think about that? Definately... RDF, perhaps :o) Cheers

Re: [RT] Standardizing on Maven names

2004-10-12 Thread Adam R. B. Jack
/how we'd make such a change. regards, Adam - Original Message - From: Stefano Mazzocchi [EMAIL PROTECTED] To: Apache Gump [EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 10:11 AM Subject: [RT] Standardizing on Maven names We are having all sort of issues because maven and gump use