Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11695&version=14343
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MSTAGE%20AND%20status%20%3D%20Reopened%20ORDER%20BY%20priority%20DESC
Staging repo:
https:
The Apache Maven team is pleased to announce the release of the
Apache Maven Repository Plugin, version 2.4
This plugin is used to create bundles of artifacts that can be uploaded to the
central repository.
http://maven.apache.org/plugins/maven-repository-plugin/
org.apache.maven.plugins
m
I noticed 3.2.6 is becoming filled with lots of interesting enhancements:
* MNG-5771 user-configurable core extensions mechanism
* MNG-5767 project-specific default jvm options and command line parameters
* MNG-3891 Modify maven-toolchain to look in
${maven.home}/conf/toolchains.xml and in ${user.
GitHub user trenchguinea opened a pull request:
https://github.com/apache/maven-surefire/pull/85
[SUREFIRE-1140] Add anchors to test case names in Surefire reports.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trenchguinea/mav
ok, done:
https://github.com/takari/takari-lifecycle/issues/11
regards,
Cristiano
On 22-02-2015 00:22, Igor Fedorenko wrote:
Looks like takari plugin test harness can't talk to one of your
project's repositories. Can you please open issue at github so we don't
spam this mailing list?
--
Rega
On 23 February 2015 at 13:45, Lennart Jörelid
wrote:
> Hello all again,
>
> This is exactly my experience with large reactors; while semver would be
> the desired way to go it is impractical bordering on impossible to combine
> semver for a large number of projects. (In fact, it boils down to man
Hello all again,
This is exactly my experience with large reactors; while semver would be
the desired way to go it is impractical bordering on impossible to combine
semver for a large number of projects. (In fact, it boils down to manually
correctly managing all versions within a release.propertie
On Sun, Feb 22, 2015 at 10:42 PM, Fred Cooke wrote:
> I'd also love to hear that no one is trying to release 200 artifacts in a
> single reactor.
At Wicket Stuff (https://github.com/wicketstuff) we do just that. It
is a pain, but
it is quite a lot less pain than trying to release each project by
That makes some sense, but a more generic big project where the life cycle
of each component is distinct and meaingfully distinct, it does not. I can
think of another good case, albeit with a much lower number of moving
parts: Parent sets. It's nice to have only one current version number to
rememb