Hi,
There are several MSITE/DOXIA and MRELEASE issues related to this subject.
For the SCM-section and the site-section of the distributionManagement we
need a more intelligent way to resolve this.
Right now this logic is hidden inside the maven-release-plugin and
maven-site-plugin, causing
*Stephen*
1) great. lets collaborate on your plugin.
in the end, I do not care how it works, 100% maven or maven + jenkins.
2) do you know about other initiatives to address this issue?
3) do you know of a way to relax maven-release-plugin so
it does not always release ch
The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.14
Please note the introduction of the "forkCount" parameter and check
the docs for this; a few of the settings relating to parallel forks
have changed slightly:
http://maven.apache.org/surefire/maven-surefi
My one comment would be to please just get this out and available to
everyone soon so we can move on.
manfred
> Any other comments?
>
> Unless I hear otherwise this week I'll start merging Eclipse Aether into
> master and start a discussion about what that means.
>
> On Mar 10, 2013, at 1:20 AM,
+1 to release.
Thanks,
Henning
On Mon, Mar 11, 2013 at 9:44 AM, John Casey wrote:
> Bump...
>
> Has this vote failed, then, or are we saying that all the +1's from the
> previous round of voting should be counted here? There is new code in this
> vote, so I'm not 100% sure that's a good
Hi guys,
I am heavily using maven in my company. We introduced doxia about 2 month ago.
During updating our documentation we discovered a bug in doxia-core 1.3. I
registered for JIRA at codehaus and filled a bug report.
Further I added a project to reproduce the bug and a patch against the
http
Github user Riduidel closed the pull request at:
https://github.com/apache/maven-plugins/pull/6
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Bump...
Has this vote failed, then, or are we saying that all the +1's from the
previous round of voting should be counted here? There is new code in
this vote, so I'm not 100% sure that's a good idea.
I can complete the release of the dependency analyzer, I guess, as that
code has not chang
GitHub user Riduidel opened a pull request:
https://github.com/apache/maven-plugins/pull/6
Updated shade mojo to use another artifactId
This pull request correspond to a mail i sent later on to maven-dev
concerning one issue with maven-shade-plugin.
Although there is a `shadedAr
Well with my Maven hat on, I don't like that it requires Jenkins nor that
it is (most likely from a quick look) using the (IMPO fundamentally broken)
Maven Project type for jobs
But in essence I envision a Maven plugin with a similar end-goal... just
not yet confident enough of my logic for detect
Any other comments?
Unless I hear otherwise this week I'll start merging Eclipse Aether into master
and start a discussion about what that means.
On Mar 10, 2013, at 1:20 AM, Anders Hammar wrote:
> Personally I would like us to stick with the initial discussion of shipping
> 3.1 with the slf4j
*Stephen**
*
I made this solution for the problem:
https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
Please let me know what you think?
Thank you,
Andrei
Original Message
Subject: Multi-project releases
From: Stephen Connolly
To: Ma
12 matches
Mail list logo
