geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: [VOTE] genesis 1.4 take 3 (cancelled)
Date Mon, 10 Mar 2008 06:22:05 GMT

On Mar 9, 2008, at 10:50 PM, David Jencks wrote:

> We'll get to take 5 yet!
> Problems identified so far:
> - version of legal-bundle needs to be fixed not variable in project- 
> config/pom
fixed, although I'm not sure what releasing will do.
> - tools plugin verifier is looking for LICENSE.txt and NOTICE.txt  
> but we are supplying LICENSE and NOTICE
See below.
> - velocity complaints noted by jdillon
> - in the generated website there are no parent links.  On the other  
> hand I can't find them in any other maven generated website either  
> so it might not be our fault.
Anyone have a clue?  I don't and don't want to spend more time on this.
> I'm also thinking of including the rat plugin and wondering if we  
> need the legal verifier as well?  I don't think rat produces  
> failures but does do more extensive checks.
added for manual runs.  Rat does fail the build but I don't think it  
checks inside jars and it doesn't know about a lot of the generated  
files.  I don't know if it can be taught.

What I'm not sure about is how to deal with the name change in  
default license/notice files.  One solution is to change the  
hardcoded default values in the plugin.  I'd like to do this unless  
someone (jdillon?) objects.  Another is to change the generated file  
names.  I'd rather not do this as it takes us farther from the maven  
"standard" for no good reason I can see.  We could also override the  
defaults in either project-config or each individual top-level child  

Preferences anyone?

david jencks

> thanks
> david jencks
> On Mar 9, 2008, at 3:59 PM, David Jencks wrote:
>> Hi,
>> 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 
>> Proposed+%28updated%29+release+process
>> The only Jira I know about is 
>> browse/GERONIMO-3895
>> Staging repo:
>> genesis/
>> site staging:
>> This time I was able to use mvn site site-deploy -Prelease,default  
>> to deploy the site all at once to the staging-site.
>> Vote open for 72 hours.
>> [ ] +1
>> [ ] +0
>> [ ] -1
>> thanks
>> david jencks

View raw message