The pom looks good, but I think the maven assembly stuff should be moved into another pom or be optional. Maybe using another profile that would be activated by subprojects by default or something like that.
Does this mean that all subprojects like ConfigAdmin, PreferencesService and such will all have those four artifacts generated ? On Wed, Apr 22, 2009 at 19:22, Stuart McCulloch <[email protected]> wrote: > Hi, > > I've finally put together release 1.2.0 of the Felix parent pom - this uses > the new > Nexus repository infrastructure to stage releases. I've also changed the > artifactId > to be "felix-parent", which should be less confusing for people browsing the > repo. > > The release is staged at: > > https://repository.apache.org/content/repositories/felix-staging-015/ > > The new release process is documented on the wiki (based on the Maven > process): > > > http://cwiki.apache.org/confluence/display/FELIX/Release+Management+(Nexus) > > You can use this UNIX script to download the release and verify the > signatures: > > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > Usage: sh check_staged_release.sh 015 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours ... I'm off to get some sleep now, back > in ~8hrs. > > -- > Cheers, Stuart > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
