Just a few remarks and questions on the Release Process Wiki page:
http://team.ops4j.org/wiki/display/ops4j/Releasing
- The process is based on Sonatype OSS and requires a Sonatype account.
I think this should be mentioned first of all.
- The current parent POM is org.ops4j:master:2.0.0 for all projects, PAX
or not.
- Are there any pros and cons for using mvn release:prepare and mvn
release:perform in two separate invocations, compared to calling
mvn release:prepare release:perform in one go?
- Usually you'll want to add -DautoVersionSubmodules=true.
- You'll have to make sure that the Maven Release plugin is able to tag
and push to Github. Or do you push manually? I don't even remember how I
did it last time... But I had to do some fumbling with ssh-agent and so
on...
- Is the repos.ops4j profile still used?
- AFAIK, pushing to Maven Central _only_ works via a Staging repository
(i.e. profile repos.sonatype.staging), so why should anyone use the
repos.sonatype profile for a release?
Maybe for a milestone release, but in general, we do want to promote our
artifacts to Maven Central, don't we?
- Change log: the Pax Runner example is a manual list. I think the
Confluence JIRA macros are way smarter :-) See Pax Exam.
- Sonatype Nexus authentication: The "jira task" link refers to OPS4J
INFRA. This should be Sonatype OSSRH.
- gpg --gen-key took ages on my machine for lack of entropy. I had to
use rngd to speed this up.
- Is it still required to upload the keys to http://www.ops4j.org/keys?
Best regards,
Harald
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
