[Announce] Apache Abdera 0.3.0

[James M Snell]

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

Builds are available for Java 1.5 and Java 1.4.2.

For further information, visit our web site at:
http://incubator.apache.org/abdera

Introduction
============

The goal of the Apache Abdera project is to build a
functionally-complete, high-performance implementation of the IETF Atom
Syndication Format (RFC 4287) and Atom Publishing Protocol (in-progress)
specifications.

Abdera is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process
have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the project
has yet to be fully endorsed by the ASF.

Release Summary
===============

 * Support for the Atompub final draft
 * Refactored and simplified Server framework
 * Refactored and simplified AbderaClient
 * ExtensionFactory can now provide the mime type for extension elements
 * Improved extensibility
 * Updated dependencies
 * XPath support improvements
 * Geotagging extensions
 * Simple Sharing extensions
 * WSSE Authentication
 * Bidi extensions (experimental)
 * Atompub features extensions (experimental)
 * Feed paging extensions
 * Feed license extensions
 * XML Encryption with Diffie-Hellman key exchange
 * Spring integration support
 * Extensions now packaged in separate jars for modular distribution
 * Improved error handling
 * More examples
 * Less bugs
 * Lots of other improvements

Please feel free to send any feedback to our mailing lists:
abdera-dev@...
abdera-user@...

Any contribution in the form of coding, testing, improving the
documentation, and reporting bugs is always welcome. For more
information on how to get involved with the development of Abdera, visit
our website at: http://incubator.apache.org/abdera

Thank you for your interest in Apache Abdera!

- Apache Abdera Project

[Brian Moseley]

On 10/5/07, James M Snell <jasnell@...> 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/ .

[Chris Berry]

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 <jasnell@...> 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-2]

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 <jasnell@...> 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

[Garrett Rooney]

On 10/23/07, Dan Diephouse <dan.diephouse@...> wrote:

> 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.

As long as someone is willing to do the leg work I have no problem with this.

I was hoping to get around to an ant+ivy build that would give us some
of the benefits of maven but without the issues, but honestly it's
unlikely I'll get to it any time soon.  Real Live (tm) has cut into my
hacking time considerably lately, and I don't see that changing much
over the next 6 months or so.

-garrett

[James M Snell]

... must ... resist ... maven ... bashing ... must ... not ... give in
... to ... natural ... impulse ...

... then again, I'm also not going to have the time to keep serving as
the release manager and, like Garrett, I don't have the time to change
the build process.  If someone is willing to do the work and provide
non-mavenites like myself with proper step-by-step build instructions,
go for it.

- James

Dan Diephouse wrote:

> 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 <jasnell@...> 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-2]

James M Snell wrote:
> ... must ... resist ... maven ... bashing ... must ... not ... give in
> ... to ... natural ... impulse ...
>  
Haha, I do understand, really I do.

<philosphizing>The larger picture though is that I work on a dozen or so
open source projects and I find it insanely difficult to learn new
builds every time. Maven standardizes all that. So if a project is
configured correctly I can get it going within a minute. I can do
releases with just a few commands I already know. As can other people. I
don't dispute that Ant has its advantages. Its just that on average, it
doesn't pay for me to use Ant :-)</philosophizing>
> ... then again, I'm also not going to have the time to keep serving as
> the release manager and, like Garrett, I don't have the time to change
> the build process.  If someone is willing to do the work and provide
> non-mavenites like myself with proper step-by-step build instructions,
> go for it.
>  
Well how about I whip something up for 0.4 and we can evaluate things
from there? You never know, you might like it ;-)

- Dan

--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog

[Brian Moseley]

On 10/23/07, Dan Diephouse <dan.diephouse@...> wrote:

> <philosphizing>The larger picture though is that I work on a dozen or so
> open source projects and I find it insanely difficult to learn new
> builds every time. Maven standardizes all that. So if a project is
> configured correctly I can get it going within a minute. I can do
> releases with just a few commands I already know. As can other people. I
> don't dispute that Ant has its advantages. Its just that on average, it
> doesn't pay for me to use Ant :-)</philosophizing>

same.

> Well how about I whip something up for 0.4 and we can evaluate things
> from there? You never know, you might like it ;-)

+1