You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Jencks <da...@yahoo.com> on 2008/03/12 07:37:43 UTC
[VOTE] genesis 1.4 take 5
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
Re: [VOTE] genesis 1.4 take 5
Posted by Jarek Gawor <jg...@gmail.com>.
+1
Jarek
On Wed, Mar 12, 2008 at 2:37 AM, David Jencks <da...@yahoo.com> 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
Re: [VOTE] genesis 1.4 take 5 (passed) (pre-announcement questions)
Posted by David Jencks <da...@yahoo.com>.
Stage plugin works great, although I'd like advice on the best way to
install it. I updated my copy of genesis trunk to pull it down, I'll
plan to commit this -- feel free to undo this if appropriate.
Added chgrp step to release instructions for the site
It looks like there might be a dist location as well as the m2 rsync
location. Am I supposed to copy the stuff anywhere except ibiblio
rsync?
thanks
david jencks
On Mar 16, 2008, at 10:36 AM, David Jencks wrote:
> Vote concludes a bit late with 8 +1 (binding) 1 +1 (non-binding)
> and no other votes (after some discussion).
>
> I'll now try to figure out how to use the stage plugin and update
> the release docs :-)
>
> thanks
> david jencks
>
>
>
> On Mar 11, 2008, at 11:37 PM, 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
>
Re: [VOTE] genesis 1.4 take 5 (passed)
Posted by David Jencks <da...@yahoo.com>.
Vote concludes a bit late with 8 +1 (binding) 1 +1 (non-binding) and
no other votes (after some discussion).
I'll now try to figure out how to use the stage plugin and update the
release docs :-)
thanks
david jencks
On Mar 11, 2008, at 11:37 PM, 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
Re: [VOTE] genesis 1.4 take 5
Posted by Jason Dillon <ja...@planet57.com>.
Okay, I detract my -1 and assert a +1 for this release. As for the
other items you mention below we can look into that after this release
is out and in use.
--jason
On Mar 15, 2008, at 12:23 PM, David Jencks wrote:
> ya, bootstrap doesn't work too well, but you can build it, I did, as
> you can see from the existence of the release candidate.
>
> mvn -N
> cd legal-bundle;mvn install
> cd ../plugins;mvn install
> cd ..
> mvn clean install
>
>
> I'd appreciate you reconsidering this -1.
>
> I suggest that the next genesis release consist of 2 unrelated things:
> - a parent pom for geronimo projects containing a release profile
> and some plugin versions and configurations, such as for the legal
> bundle (soon to be the official apache one IIUC)
> - a geronimo skin using the default-site.vm or a site.vm with
> explicit annotations on every difference from default-site.vm
> indicating why they are improvements.
>
> My view is that the problems with the current 1.4 release candidate
> are not serious enough to prevent its use until we can get this
> simplified version working. If you disagree, I suggest we separate
> the artifacts and have the legal bundle, skin, project-config, and
> plugins all build entirely independently with no parent-child
> relationships. This would result in 3 fewer projects and a build
> that is likely to work without contortions.
>
> thanks
> david jencks
>
> On Mar 14, 2008, at 9:34 PM, Jason Dillon wrote:
>
>> Sorry...
>>
>> -1
>>
>> The tag does not build :-(
>>
>> This problem has been resolved since the tag from trunk was made a
>> few days ago... and really should be re-rolled. Sorry again David,
>> I know how hard you have been trying to get this puppy out, and I
>> thank you for that... but I think we need one more time... :-(
>>
>> <snip>
>> svn co https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-1.4/
>> cd genesis-1.4
>> ./bootstrap
>> Buildfile: bootstrap.xml
>>
>> init:
>> Starting bootstrap build...
>>
>> clean:
>> Cleaning...
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO] Genesis
>> [INFO] Genesis Legal Bundle
>> [INFO] Genesis Plugins
>> [INFO] Genesis Plugins :: Tools
>> [INFO] Genesis Configuration
>> [INFO] Genesis Configuration :: Project
>> [INFO] Genesis Configuration :: Geronimo Skin
>> [INFO] Genesis Plugins :: Maven
>> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Plugin could not be found - check that the goal name is
>> correct: Unable to download the artifact from any repository
>> Try downloading the file manually from the project website.
>> Then, install it using the command:
>> mvn install:install-file -
>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
>> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
>> file
>> Alternatively, if you host your own repository you can deploy the
>> file there:
>> mvn deploy:deploy-file -
>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
>> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
>> file -Durl=[url] -DrepositoryId=[id]
>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>> plugin:1.4
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2)
>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>> plugin:1.4
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 7 seconds
>> [INFO] Finished at: Sat Mar 15 11:31:59 ICT 2008
>> [INFO] Final Memory: 2M/5M
>> [INFO]
>> ------------------------------------------------------------------------
>> Result: 1
>>
>> stage1:
>> [INFO] Scanning for projects...
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Genesis
>> [INFO] task-segment: [install]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [site:attach-descriptor]
>> [INFO] Unable to load parent project from a relative path: Could
>> not find the model file '/Users/jason/ws/geronimo/genesis-1.4/../
>> pom.xml'. for project unknown
>> [INFO] Parent project loaded from repository.
>> [INFO] [install:install]
>> [INFO] Installing /Users/jason/ws/geronimo/genesis-1.4/pom.xml to /
>> Users/jason/.m2/repository/org/apache/geronimo/genesis/genesis/1.4/
>> genesis-1.4.pom
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 5 seconds
>> [INFO] Finished at: Sat Mar 15 11:32:05 ICT 2008
>> [INFO] Final Memory: 8M/15M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> stage2:
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO] Genesis Plugins
>> [INFO] Genesis Plugins :: Tools
>> [INFO] Genesis Plugins :: Maven
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Genesis Plugins
>> [INFO] task-segment: [install]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Setting property: classpath.resource.loader.class =>
>> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>> [INFO] Setting property: resource.loader => 'classpath'.
>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>> [INFO] [remote-resources:process {execution: default}]
>> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/legal-bundle/1.4/legal-bundle-1.4.jar
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>> GroupId: org.apache.geronimo.genesis
>> ArtifactId: legal-bundle
>> Version: 1.4
>> Reason: Unable to download the artifact from any repository
>> Try downloading the file manually from the project website.
>> Then, install it using the command:
>> mvn install:install-file -DgroupId=org.apache.geronimo.genesis -
>> DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/
>> to/file
>> Alternatively, if you host your own repository you can deploy the
>> file there:
>> mvn deploy:deploy-file -DgroupId=org.apache.geronimo.genesis -
>> DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/
>> to/file -Durl=[url] -DrepositoryId=[id]
>> org.apache.geronimo.genesis:legal-bundle:jar:1.4
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2),
>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository
>> )
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 4 seconds
>> [INFO] Finished at: Sat Mar 15 11:32:09 ICT 2008
>> [INFO] Final Memory: 9M/17M
>> [INFO]
>> ------------------------------------------------------------------------
>> Result: 1
>>
>> stage3:
>> [INFO] Scanning for projects...
>> [INFO] Reactor build order:
>> [INFO] Genesis
>> [INFO] Genesis Legal Bundle
>> [INFO] Genesis Plugins
>> [INFO] Genesis Plugins :: Tools
>> [INFO] Genesis Configuration
>> [INFO] Genesis Configuration :: Project
>> [INFO] Genesis Configuration :: Geronimo Skin
>> [INFO] Genesis Plugins :: Maven
>> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Plugin could not be found - check that the goal name is
>> correct: Unable to download the artifact from any repository
>> Try downloading the file manually from the project website.
>> Then, install it using the command:
>> mvn install:install-file -
>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
>> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
>> file
>> Alternatively, if you host your own repository you can deploy the
>> file there:
>> mvn deploy:deploy-file -
>> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
>> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
>> file -Durl=[url] -DrepositoryId=[id]
>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>> plugin:1.4
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2)
>> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
>> plugin:1.4
>> from the specified remote repositories:
>> central (http://repo1.maven.org/maven2)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 1 second
>> [INFO] Finished at: Sat Mar 15 11:32:12 ICT 2008
>> [INFO] Final Memory: 2M/5M
>> [INFO]
>> ------------------------------------------------------------------------
>> Result: 1
>>
>> BUILD SUCCESSFUL
>> Total time: 21 seconds
>> </snip>
>>
>> --jason
>>
>>
>>
>> On Mar 15, 2008, at 2:32 AM, David Jencks wrote:
>>
>>> This vote concludes tonight and we have 2 other votes pending on
>>> this one. So far I'm the only one to have voted here.... unless
>>> you want to redo all 3+ releases please take a look and vote.
>>>
>>> thanks
>>> david jencks
>>>
>>> On Mar 12, 2008, at 12:50 AM, David Jencks wrote:
>>>
>>>> +1
>>>> david jencks
>>>>
>>>> On Mar 11, 2008, at 11:37 PM, 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
>>>>
>>>
>>
>
Re: [VOTE] genesis 1.4 take 5
Posted by David Jencks <da...@yahoo.com>.
ya, bootstrap doesn't work too well, but you can build it, I did, as
you can see from the existence of the release candidate.
mvn -N
cd legal-bundle;mvn install
cd ../plugins;mvn install
cd ..
mvn clean install
I'd appreciate you reconsidering this -1.
I suggest that the next genesis release consist of 2 unrelated things:
- a parent pom for geronimo projects containing a release profile and
some plugin versions and configurations, such as for the legal bundle
(soon to be the official apache one IIUC)
- a geronimo skin using the default-site.vm or a site.vm with
explicit annotations on every difference from default-site.vm
indicating why they are improvements.
My view is that the problems with the current 1.4 release candidate
are not serious enough to prevent its use until we can get this
simplified version working. If you disagree, I suggest we separate
the artifacts and have the legal bundle, skin, project-config, and
plugins all build entirely independently with no parent-child
relationships. This would result in 3 fewer projects and a build
that is likely to work without contortions.
thanks
david jencks
On Mar 14, 2008, at 9:34 PM, Jason Dillon wrote:
> Sorry...
>
> -1
>
> The tag does not build :-(
>
> This problem has been resolved since the tag from trunk was made a
> few days ago... and really should be re-rolled. Sorry again David,
> I know how hard you have been trying to get this puppy out, and I
> thank you for that... but I think we need one more time... :-(
>
> <snip>
> svn co https://svn.apache.org/repos/asf/geronimo/genesis/tags/
> genesis-1.4/
> cd genesis-1.4
> ./bootstrap
> Buildfile: bootstrap.xml
>
> init:
> Starting bootstrap build...
>
> clean:
> Cleaning...
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Genesis
> [INFO] Genesis Legal Bundle
> [INFO] Genesis Plugins
> [INFO] Genesis Plugins :: Tools
> [INFO] Genesis Configuration
> [INFO] Genesis Configuration :: Project
> [INFO] Genesis Configuration :: Geronimo Skin
> [INFO] Genesis Plugins :: Maven
> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/
> genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Plugin could not be found - check that the goal name is
> correct: Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -
> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
> file
> Alternatively, if you host your own repository you can deploy the
> file there:
> mvn deploy:deploy-file -
> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
> file -Durl=[url] -DrepositoryId=[id]
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
> plugin:1.4
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
> plugin:1.4
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 7 seconds
> [INFO] Finished at: Sat Mar 15 11:31:59 ICT 2008
> [INFO] Final Memory: 2M/5M
> [INFO]
> ----------------------------------------------------------------------
> --
> Result: 1
>
> stage1:
> [INFO] Scanning for projects...
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Building Genesis
> [INFO] task-segment: [install]
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] [site:attach-descriptor]
> [INFO] Unable to load parent project from a relative path: Could
> not find the model file '/Users/jason/ws/geronimo/genesis-1.4/../
> pom.xml'. for project unknown
> [INFO] Parent project loaded from repository.
> [INFO] [install:install]
> [INFO] Installing /Users/jason/ws/geronimo/genesis-1.4/pom.xml to /
> Users/jason/.m2/repository/org/apache/geronimo/genesis/genesis/1.4/
> genesis-1.4.pom
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 5 seconds
> [INFO] Finished at: Sat Mar 15 11:32:05 ICT 2008
> [INFO] Final Memory: 8M/15M
> [INFO]
> ----------------------------------------------------------------------
> --
>
> stage2:
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Genesis Plugins
> [INFO] Genesis Plugins :: Tools
> [INFO] Genesis Plugins :: Maven
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Building Genesis Plugins
> [INFO] task-segment: [install]
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [remote-resources:process {execution: default}]
> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/
> genesis/legal-bundle/1.4/legal-bundle-1.4.jar
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Failed to resolve artifact.
> GroupId: org.apache.geronimo.genesis
> ArtifactId: legal-bundle
> Version: 1.4
> Reason: Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=org.apache.geronimo.genesis -
> DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/
> to/file
> Alternatively, if you host your own repository you can deploy the
> file there:
> mvn deploy:deploy-file -DgroupId=org.apache.geronimo.genesis -
> DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/
> to/file -Durl=[url] -DrepositoryId=[id]
> org.apache.geronimo.genesis:legal-bundle:jar:1.4
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-
> repository)
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Sat Mar 15 11:32:09 ICT 2008
> [INFO] Final Memory: 9M/17M
> [INFO]
> ----------------------------------------------------------------------
> --
> Result: 1
>
> stage3:
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Genesis
> [INFO] Genesis Legal Bundle
> [INFO] Genesis Plugins
> [INFO] Genesis Plugins :: Tools
> [INFO] Genesis Configuration
> [INFO] Genesis Configuration :: Project
> [INFO] Genesis Configuration :: Geronimo Skin
> [INFO] Genesis Plugins :: Maven
> Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/
> genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD ERROR
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Plugin could not be found - check that the goal name is
> correct: Unable to download the artifact from any repository
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -
> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
> file
> Alternatively, if you host your own repository you can deploy the
> file there:
> mvn deploy:deploy-file -
> DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-
> maven-plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/
> file -Durl=[url] -DrepositoryId=[id]
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
> plugin:1.4
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-
> plugin:1.4
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 1 second
> [INFO] Finished at: Sat Mar 15 11:32:12 ICT 2008
> [INFO] Final Memory: 2M/5M
> [INFO]
> ----------------------------------------------------------------------
> --
> Result: 1
>
> BUILD SUCCESSFUL
> Total time: 21 seconds
> </snip>
>
> --jason
>
>
>
> On Mar 15, 2008, at 2:32 AM, David Jencks wrote:
>
>> This vote concludes tonight and we have 2 other votes pending on
>> this one. So far I'm the only one to have voted here.... unless
>> you want to redo all 3+ releases please take a look and vote.
>>
>> thanks
>> david jencks
>>
>> On Mar 12, 2008, at 12:50 AM, David Jencks wrote:
>>
>>> +1
>>> david jencks
>>>
>>> On Mar 11, 2008, at 11:37 PM, 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
>>>
>>
>
Re: [VOTE] genesis 1.4 take 5
Posted by Jason Dillon <ja...@planet57.com>.
Sorry...
-1
The tag does not build :-(
This problem has been resolved since the tag from trunk was made a few
days ago... and really should be re-rolled. Sorry again David, I know
how hard you have been trying to get this puppy out, and I thank you
for that... but I think we need one more time... :-(
<snip>
svn co https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-1.4/
cd genesis-1.4
./bootstrap
Buildfile: bootstrap.xml
init:
Starting bootstrap build...
clean:
Cleaning...
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Genesis
[INFO] Genesis Legal Bundle
[INFO] Genesis Plugins
[INFO] Genesis Plugins :: Tools
[INFO] Genesis Configuration
[INFO] Genesis Configuration :: Project
[INFO] Genesis Configuration :: Geronimo Skin
[INFO] Genesis Plugins :: Maven
Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Plugin could not be found - check that the goal name is
correct: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-maven-
plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-maven-
plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/file -
Durl=[url] -DrepositoryId=[id]
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.4
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.4
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Sat Mar 15 11:31:59 ICT 2008
[INFO] Final Memory: 2M/5M
[INFO]
------------------------------------------------------------------------
Result: 1
stage1:
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building Genesis
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] [site:attach-descriptor]
[INFO] Unable to load parent project from a relative path: Could not
find the model file '/Users/jason/ws/geronimo/genesis-1.4/../pom.xml'.
for project unknown
[INFO] Parent project loaded from repository.
[INFO] [install:install]
[INFO] Installing /Users/jason/ws/geronimo/genesis-1.4/pom.xml to /
Users/jason/.m2/repository/org/apache/geronimo/genesis/genesis/1.4/
genesis-1.4.pom
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 seconds
[INFO] Finished at: Sat Mar 15 11:32:05 ICT 2008
[INFO] Final Memory: 8M/15M
[INFO]
------------------------------------------------------------------------
stage2:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Genesis Plugins
[INFO] Genesis Plugins :: Tools
[INFO] Genesis Plugins :: Maven
[INFO]
------------------------------------------------------------------------
[INFO] Building Genesis Plugins
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/legal-bundle/1.4/legal-bundle-1.4.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.geronimo.genesis
ArtifactId: legal-bundle
Version: 1.4
Reason: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.genesis -
DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/to/
file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.geronimo.genesis -
DartifactId=legal-bundle -Dversion=1.4 -Dpackaging=jar -Dfile=/path/to/
file -Durl=[url] -DrepositoryId=[id]
org.apache.geronimo.genesis:legal-bundle:jar:1.4
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository
)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Sat Mar 15 11:32:09 ICT 2008
[INFO] Final Memory: 9M/17M
[INFO]
------------------------------------------------------------------------
Result: 1
stage3:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Genesis
[INFO] Genesis Legal Bundle
[INFO] Genesis Plugins
[INFO] Genesis Plugins :: Tools
[INFO] Genesis Configuration
[INFO] Genesis Configuration :: Project
[INFO] Genesis Configuration :: Geronimo Skin
[INFO] Genesis Plugins :: Maven
Downloading: http://repo1.maven.org/maven2/org/apache/geronimo/genesis/plugins/tools-maven-plugin/1.4/tools-maven-plugin-1.4.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Plugin could not be found - check that the goal name is
correct: Unable to download the artifact from any repository
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-maven-
plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -
DgroupId=org.apache.geronimo.genesis.plugins -DartifactId=tools-maven-
plugin -Dversion=1.4 -Dpackaging=maven-plugin -Dfile=/path/to/file -
Durl=[url] -DrepositoryId=[id]
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.4
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
org.apache.geronimo.genesis.plugins:tools-maven-plugin:maven-plugin:
1.4
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Sat Mar 15 11:32:12 ICT 2008
[INFO] Final Memory: 2M/5M
[INFO]
------------------------------------------------------------------------
Result: 1
BUILD SUCCESSFUL
Total time: 21 seconds
</snip>
--jason
On Mar 15, 2008, at 2:32 AM, David Jencks wrote:
> This vote concludes tonight and we have 2 other votes pending on
> this one. So far I'm the only one to have voted here.... unless you
> want to redo all 3+ releases please take a look and vote.
>
> thanks
> david jencks
>
> On Mar 12, 2008, at 12:50 AM, David Jencks wrote:
>
>> +1
>> david jencks
>>
>> On Mar 11, 2008, at 11:37 PM, 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
>>
>
Re: [VOTE] genesis 1.4 take 5
Posted by Dan Becker <da...@gmail.com>.
David Jencks wrote:
> This vote concludes tonight and we have 2 other votes pending on this
> one. So far I'm the only one to have voted here.... unless you want to
> redo all 3+ releases please take a look and vote.
+1
--
Thanks, Dan Becker
Re: [VOTE] genesis 1.4 take 5
Posted by David Jencks <da...@yahoo.com>.
This vote concludes tonight and we have 2 other votes pending on this
one. So far I'm the only one to have voted here.... unless you want
to redo all 3+ releases please take a look and vote.
thanks
david jencks
On Mar 12, 2008, at 12:50 AM, David Jencks wrote:
> +1
> david jencks
>
> On Mar 11, 2008, at 11:37 PM, 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
>
Re: [VOTE] genesis 1.4 take 5
Posted by David Jencks <da...@yahoo.com>.
+1
david jencks
On Mar 11, 2008, at 11:37 PM, 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
Re: [VOTE] genesis 1.4 take 5
Posted by Kevan Miller <ke...@gmail.com>.
+1
--kevan
Re: [VOTE] genesis 1.4 take 5
Posted by Joe Bohn <jo...@earthlink.net>.
+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
Re: [VOTE] genesis 1.4 take 5
Posted by Donald Woods <dw...@apache.org>.
+1
-Donald
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
Re: [VOTE] genesis 1.4 take 5
Posted by Gianny Damour <gi...@optusnet.com.au>.
+1
Thanks,
Gianny
On 12/03/2008, at 5:37 PM, 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
Re: [VOTE] genesis 1.4 take 5
Posted by Vamsavardhana Reddy <c1...@gmail.com>.
+1
++Vamsi
On Wed, Mar 12, 2008 at 12:07 PM, David Jencks <da...@yahoo.com>
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
> *<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*<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/<http://people.apache.org/%7Edjencks/staging-repo/genesis/org/apache/geronimo/genesis/>
> site staging:
> *http://people.apache.org/~djencks/staging-site/maven/genesis/1.4/***<http://people.apache.org/%7Edjencks/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
>