Along these same lines, it concerns me that we're in essence publishing
two versions of the same release. The one built by ant and the one built
by maven which is published to the incubating repository. The resulting
jars will be slightly different.
The easiest way to resolve this IMO is to just have Maven do all the
release publishing (mvn release:prepare, mvn release:perform
-DreleaseRepository...). We would have to add another module to the
maven build to build the release assembly, but that is done easily enough.
The other way is to manually upload POMs & Jars for the artifacts.
I would be more than willing to get the Maven build in shape so that
releases are possibly with it, but wondering what people think about
doing releases with Maven in the first place.
- Dan
Chris Berry wrote:
Greetings,
This morning I thought I might switch from my manually created 0.3.0
JARs to the official bits from the Abdera site.
And I noticed a naming discrepancy.
The versions here;
http://incubator.apache.org/abdera/#abdera.0.3.0-incubating
are named, e.g. abdera.client-0.3.0-incubating.jar (Note the
abderaDOTclient)
And the versions here;
http://people.apache.org/repo/m2-incubating-repository/org/apache/abdera/
are named "the old way" :: e.g. abdera-client-0.3.0-incubating.jar
(Note the abderaDASHclient)
This is a problem when creating Maven dependencies.
Should the repo structure above be made to match the new naming?? Or
vise versa??
We need POMs that match.
Thanks,
-- Chris
On Oct 5, 2007, at 2:02 PM, Brian Moseley wrote:
On 10/5/07, James M Snell <[EMAIL PROTECTED]> wrote:
The Apache Abdera community is pleased to announce the 0.3.0-incubating
release.
You can download binary and source distributions from:
http://people.apache.org/dist/incubator/abdera/0.3.0-incubating
And if you're so inclined, you can grab it from the m2 repository at
http://people.apache.org/repo/m2-incubating-repository/ .
S'all good --- chriswberry at gmail dot com
--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog
