Hi,
In preparation to Apache parent pom version 18, we need a little bugfix on
Apache Source Release Assembly Descriptor to fix MPOM-106
We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621&version=12329542&styleName=Text
Staging repo:
https://repositor
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/9#issuecomment-216382925
@wangxf1030 this way `mvn test -Dconfigfailurepolicy=continue` would work
```
configfailurepolicy
I don't really understand
yes, http://www.mojohaus.org/development/performing-a-release.html is heavy
But if you look at the content, you'll see that:
1. the 3 first sections are about quality expectations, not release,
2. the next 2 are about preparing your environment,
3. then releasing is only
+1 to Jorg's comments ;)
I believe what Jorg says is that process is _manual_:
- do something NOW (merge PR, write email for vote, ...)
- come back after 3 days (and do something more...) (what if you get a baby
in between?)
Ideally, all you'd need is to start a small snowball: merge the PR, and
Hi,
Package binding together with m-manifest-p sound like a bit of packaging,
it could be m-shade-p then there as well.
But I understand that you want to provide a bigger comfort to the users.
Having m-manifest-p would force creation of Manifest and the other like BND
plugins to merge the content
