On Jun 4, 2010, at 5:22 PM, Jarek Gawor wrote: > I'm not sure how critical this is but there is a bunch of "server" > modules that are not built by default (only with 'mini-servers' > profile) that still use 3.0-M1-SNAPSHOT version in their poms. > > Similar thing with in testsuites but those modules will never be build > since they are commented out in the poms.
When I did 2.2 I tried to deal with this by including all these projects in the "all-submodules" profile and configuring the deploy plugin with "skip" so they would have their versions upgraded by the release plugin, and get built, but not deployed. ( I built the release with -Papache-release,all-submodules) I don't have an opinion yet on whether we should fix this for M1. If we re-roll M1 for other reasons I would definitely want it fixed. thanks david jencks > > Jarek > > On Fri, Jun 4, 2010 at 4:35 PM, Rick McGuire <[email protected]> wrote: >> I've managed to come up with a 3.0-M1 release candidate built using the >> maven-release-plugin. >> >> See the jira issues here: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315090&styleName=Text&projectId=10220 >> >> Staged to >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-038/ >> >> The main artifacts up for vote are the source release archives >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-038/org/apache/geronimo/geronimo/3.0-M1/geronimo-3.0-M1-source-release.zip >> https://repository.apache.org/content/repositories/orgapachegeronimo-038/org/apache/geronimo/geronimo/3.0-M1/geronimo-3.0-M1-source-release.tar.gz >> >> If you vote you should at least examine these and make sure something >> plausible builds from them. >> >> The voting will be open a minimum of 72 hours. >> >> [ ] +1 about time to push this out the door >> [ ] 0 no opinion >> [ ] -1 not this one (please explain why) >> >> Rick >>
