cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: Releasing to
Date Tue, 19 Dec 2006 10:30:55 GMT
Reinhard Poetz wrote:
> Vadim Gritsenko wrote:
>> Reinhard Poetz wrote:
>>>>> Reinhard Poetz wrote:
>>>>>> On a separate issue, as David pointed out some time ago, we have

>>>>>> to make the files available at

>>>>>> too. 
>>> I'd say the jar files (cocoon-core, cocoon-template-impl, 
>>> cocoon-flowscript-impl, cocoon-blocks-fw-impl) only. The pom 
>>> artifacts and the archetypes are pretty useless without Maven so I 
>>> don't think it makes much sense to put them there.
>> What's the point of uploading jars to mirrors if nothing usefule can 
>> be done with it? 
> Right, a Maven 2 user wouldn't need them but for those that use an 
> alternative build tool, it is the default place where Apache projects 
> put there released artifacts and where people look for them.
> Also, reading, I understand that 
> we have to put our releases there, haven't we?
>> It should at least be accompanied with a webapp archive. 
> would be great
>> And source code archives.
> right, forgot about the source artifacts.

As Vadim pointed out, the value of publishing all the released artifacts to isn't high as the usage without Maven requires 
some understanding of how Cocoon 2.2 works. As there aren't any guides 
available, the barrier for somebody who is unfamiliar will be too high.

On the other hand I want to work on the guide and is the official location for all Apache releases.

Therefore I would like to see the artifacts being signed and also released from


Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}


Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail:

View raw message