commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig McClanahan" <>
Subject Re: VOTE: Migrate commons-fileupload to Maven 2
Date Sat, 02 Sep 2006 06:13:43 GMT
On 9/1/06, Phil Steitz <> wrote:
> <snip>
> We also need to definitively settle the artifact naming conventions
> and think carefully about the impact of relocating the fileupload jar.

I *think* the following strategy will deal with this situation ... and
should generic to all the commons packages:

* If version x.y.z of Commons package "foo" is published as Maven artifact
  "commons-foo:commons-foo:x.y.z", publish an *additional* copy of that
  same version under "".

* For all future versions, use only the"org.apache.commons" group id.

That way, we won't disrupt current Maven-based users of the current
versions, and we also don't have to wait until each individual package revs
to publish versions under the new id.  Users who are updating their projects
to depend on a new version number can easily update the group id at the same

Does that make any sense?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message