cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Pötz <reinh...@apache.org>
Subject Re: Test and verify Cocoon 3 alpha-1 release artifacts
Date Tue, 25 Nov 2008 12:52:56 GMT
sorry for my late response. I was ill and then I had some hardware
problems that prevented me from reading my Apache mails.

Simone Tripodi wrote:
> Hi Reinhard,
> first of all, please excuse me I'm late to reply to your mail... I've
> been busy in some meeting with the customer and I was focused more on
> providing patches :P
> Notes follow inline
> 
> 2008/10/22 reinhard@apache.org <reinhard@apache.org>:
>> It took me a while but now I finished the creation of all release
>> artifacts for a Cocoon 3 alpha-1 release. Since this is the initial
>> creation of Maven artifacts and distribution files, I don't call for a
>> vote at this point of time but rather want to wait for some feedback.
>>
>> I would like to ask you to check the release artifacts whether they meet
>>  the legal requirements (checksums, pgp signatures, license files,
>> notice files) of the ASF.
> 
> I noticed the 'doap' files are missing: they can be created by hand or
> using the maven doap plugin:
> 
> http://maven.apache.org/plugins/maven-doap-plugin/
> 
> I suggest you the second choice, maintaining 2 identical metadata sets
> in 2 different formats could be a little confusing, in that way you're
> sure the 'doap' is always 'synched' with the pom.

thanks for the hint. I haven't thought of DOAP files yet. I will try to
integrate it into the site generation process.

>> Maven artifacts
>> .......................................................................
>> Maven artifacts are available at http://people.apache.org/builds/cocoon/
>> If you want to use Cocoon 3, add this location as an additional
>> repository to your settings:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <settings xmlns="http://maven.apache.org/POM/4.0.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> http://maven.apache.org/xsd/settings-1.0.0.xsd">
>>  <profiles>
>>    <profile>
>>      <id>cocoon-staging</id>
>>      <repositories>
>>        <repository>
>>          <id>cocoon.staging</id>
>>          <name>Cocoon staging repository</name>
>>          <url>http://people.apache.org/builds/cocoon</url>
>>        </repository>
>>      </repositories>
>>      <pluginRepositories>
>>        <pluginRepository>
>>          <id>cocoon.staging</id>
>>          <name>Cocoon staging repository</name>
>>          <url>http://people.apache.org/builds/cocoon</url>
>>        </pluginRepository>
>>      </pluginRepositories>
>>    </profile>
>> </settings>
>>
>> and use it: e.g.
>> mvn install -P cocoon-staging
> 
> I removed all cocoon libraries from my local maven repository to start
> from scratch, then I modified the settings.xml as you explained and
> finally I created a new project, importing the pipeline and everything
> worked fine. It seems the checksums have been retrieved correctly.
> 
> Best regards, I hope to hear you soon!

Thanks for your feedback! I will start a vote this week.

-- 
Reinhard Pötz                           Managing Director, {Indoqa} GmbH
                         http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard@apache.org
________________________________________________________________________

Mime
View raw message