Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=pj+ALy/VVhCCSqJ6OZM9t9MCtClucYD53ICYX4SaGrWkiyoqegWsuM9w+dq62Z0x;
  h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Message-ID: <47DADE05.8080901@earthlink.net>
Date: Fri, 14 Mar 2008 16:20:21 -0400
From: Joe Bohn <joe.bohn@earthlink.net>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: [VOTE] genesis 1.4 take 5
References: <AE19E2E2-193C-4D19-91BD-23AE726415C0@yahoo.com>
In-Reply-To: <AE19E2E2-193C-4D19-91BD-23AE726415C0@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+1

Joe


David Jencks wrote:
> Hi,
> 
> Changes in v5:
> legal files in all the jars (I hope)
> fix a typo in the NOTICE template
> make the generated site work better (parent link, maven feather)
> remove logging-config and checkstyle-config per jdillons advice.
> move modules to base pom, not a profile; change how bootstrap works.
> 
> Changes in v4:
> make the legal-bundle version fixed rather than equal to the version of 
> whatever subproject is trying to use it.
> Fix noise in DEPENDENCIES file generation
> Change legal verifier to expect LICENSE and NOTICE files by default
> add the rat plugin so you can run mvn rat:check for a project check 
> (note that rat does not look inside jars so we still need the verifier)
> add some more commonly used plugins to the project-config and 
> alphabetize them.
> 
> Changes in v3:
> Change the legal-bundle to have really simple NOTICE file and put all 
> the dependency info in a separate DEPENDENCIES file.  This corresponds 
> to what appears to be current thinking on legal-discuss about what 
> should be in these files.  We should be able to use this bundle with the 
> maven-remote-resources-plugin everywhere now.
> 
> Fiddle around with the maven site generation and site deployment so it 
> more or less works.  Add some instructions in the project-config site.
> 
>       
> 
> Changes in v2:
> Change in the release plugin configuration to use the default tagBase in 
> release profiles in projects that inherit from the project-config pom. 
>  It is also possible to override tagBase but this should not be 
> necessary as we adhere to standard svn layout. There are also some 
> plugin version upgrades.
> 
> The new root pom includes a release profile that sets up the standard 
> javadoc, source and gpg plugins and uses the default tagBase location.
> 
> This sets us up for using the release process also now under vote 
> described 
> at _http://cwiki.apache.org/confluence/display/GMOxPMGT/Proposed+%28updated%29+release+process_
> 
> The only Jira I know about 
> is _https://issues.apache.org/jira/browse/GERONIMO-3895_
> 
> Staging repo: (note, this is a different location)
> http://people.apache.org/~djencks/staging-repo/genesis/org/apache/geronimo/genesis/
> site staging:
> _http://people.apache.org/~djencks/staging-site/maven/genesis/1.4/___
> 
> This time I was able to use mvn site site-deploy -Prelease to deploy the 
> site all at once to the staging-site.
> 
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> thanks
> david jencks