I moved the "fix" to 2.11.
Kristian
2014-09-29 8:50 GMT+02:00 Mikolaj Izdebski :
> On 09/27/2014 04:34 PM, Michael Osipov wrote:
>> We solved 3 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&version=20644
>
> MJAVADOC-415 is not fixed. POM still seems to declare vers
On 09/27/2014 04:34 PM, Michael Osipov wrote:
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&version=20644
MJAVADOC-415 is not fixed. POM still seems to declare versions 2.5 of
both maven-archiver and plexus-archiver. Plexus-utils is at 3.0.15, not
3.0.18.
Using java 7 or better:
git clone https://github.com/sonatype/plexus-io.git
git clone https://github.com/sonatype/plexus-archiver.git
On maven-war-plugin (trunk), update plexus-io to 2.1.2-SNAPSHOT and
plexus-archiver to 2.6.2-SNAPSHOT.
Run mvn -Prun-its clean install
If it works now, my patc
Hi Kristian,
Let me know if you need any help. I have Jenkins set up locally on my
windows box with most versions of Java and Maven available. What needs
testing?
--
Dennis Lundberg
Den 28 sep 2014 21:27 skrev "Kristian Rosenvold" <
kristian.rosenv...@gmail.com>:
> I have fixed it, but I'll see
Github user miyajan closed the pull request at:
https://github.com/apache/maven-surefire/pull/48
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/50
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/50
The module surefire-setup-integration-tests fails with Maven 3.2.3
The module surefire-setup-integration-tests which fails with Maven 3.2.3
due to https://jira.codehaus.org/i#browse/MPH-101
+2
On 28 Sep 2014, at 21:36, Robert Scholte wrote:
I would go one step further: make the toolchains.xml part of the Maven
distribution, aside the settings.xml with the same amount of
documentation.
That should make it clear how to divide the Maven Runtime JDK from the
Compile JDK.
Robert
I have fixed it, but I'll see if I can dig up a windows box tomorrow
to actually test it before releasing more.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.a
You should be able to follow the repositories on github and get
notifications. Commits with maven-release plugin are a giveaway :)
I don't think the nexus instance posts staging mails to plexus-dev,
but the overall mode of operations in plexus is 1 fix = 1 release. So
jira traffic generally means
Well why I recall we said last time was that we'd only support the jdk
supported by the supported versions of maven
So *if* one of the core plugins chooses - for technical reasons (such as
try with resources or the diamond operator making the code nicer) to bump
its dependency to maven 4.0 then th
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/49
[SUREFIRE-1098] Fix runOrder=balanced is not working
Fix for #48 with IT.
Updated documentation for runOrder parameter.
Added ststem property for runOrder.
You can merge this pull req
Hi,
On 9/28/14 3:10 PM, sebb wrote:
On 28 September 2014 12:17, Benson Margulies wrote:
The Apache Maven team is pleased to announce the release of the Apache
Common POM, version 15.
This POM (org.apache:apache) configures common Maven settings for
projects to use ASF infrastructure.
Documen
On 28 September 2014 12:17, Benson Margulies wrote:
> The Apache Maven team is pleased to announce the release of the Apache
> Common POM, version 15.
>
> This POM (org.apache:apache) configures common Maven settings for
> projects to use ASF infrastructure.
>
> Documentation live at: http://maven
Hi Mirko,
On 9/28/14 1:23 PM, Mirko Friedenhagen wrote:
Hello Karl,
sorry about forgetting the Cc to private :-(. I follow the steps but
especially site creation/upload/promotion has loads of details :-)
Yes...it's really so...i have mistaken this also in my first
releases...so no problem..
The Maven team is pleased to announce the release of the Apache Maven
Changes Plugin, version 2.11
Creates a release history for inclusion into the site and assists in
generating an announcement mail.
http://maven.apache.org/plugins/maven-changes-plugin/
You should specify the version in your pr
Hello Karl,
sorry about forgetting the Cc to private :-(. I follow the steps but
especially site creation/upload/promotion has loads of details :-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org
The Apache Maven team is pleased to announce the release of the Apache
Common POM, version 15.
This POM (org.apache:apache) configures common Maven settings for
projects to use ASF infrastructure.
Documentation live at: http://maven.apache.org/poms/asf.
To use this parent, you should specify the
This vote passes, with me, Robert Scholte, Hervé Boutemy, Stephen Connolly.
On Fri, Sep 26, 2014 at 2:33 PM, Robert Scholte wrote:
> in that case, +1
>
> thanks,
> Robert
>
> Op Fri, 26 Sep 2014 19:06:34 +0200 schreef Benson Margulies
> :
>
>
>> I apparently pasted the wrong sum. apache-15-source
Hi,
i have a suggestioncurrently there are changes on going in plexus
parts (really good Thanks Kristian...)...but it's hard to know when a
new release is out...
It would be great having a small mail here on the dev list to be
informed about new releases of the plexus components cause ma
Hi Mirko,
please make a CC of this mail to
"Maven Project Management Committee List"
best is to follow the steps described on this page:
http://maven.apache.org/developers/release/maven-project-release-procedure.html
Kind regards
Karl-Heinz Marbaise
On 9/27/14 10:19 PM, Mirko Friedenhagen
+1 for making toolchains part of the distribution.
Regards
Mirko
--
Sent from my mobile
On Sep 28, 2014 10:36 AM, "Robert Scholte" wrote:
> I would go one step further: make the toolchains.xml part of the Maven
> distribution, aside the settings.xml with the same amount of documentation.
> That
+1
Op Sat, 27 Sep 2014 16:34:00 +0200 schreef Michael Osipov
:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138&version=20644
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MJAVADOC%20AND%20resol
+1
Checked SHA1 OK
Ran javadoc:javadoc with Maven 3.0.5, 3.1.1 and 3.2.3 in a
multi-module project where version 2.10 spat out loads of warnings and
errors,
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbu
Hi Karl-Heinz,
Prerequisites are only used for plugins at runtime, specifying with which
Maven version it should at least be executed.
When Maven builds the dependency-tree, the prerequisites are ignored.
So your latest change has no effect.
It's very rare when I use version ranges, but this
I would go one step further: make the toolchains.xml part of the Maven
distribution, aside the settings.xml with the same amount of documentation.
That should make it clear how to divide the Maven Runtime JDK from the
Compile JDK.
Robert
Op Sun, 28 Sep 2014 05:02:04 +0200 schreef Mark Derric
Hi Robert,
> I wonder if this does what we want to achieve: forcing projects using
maven-shared-utils to be executed with at least Maven 2.2.1.
Right now it is just the preferred version, no problem if the project
itself redefines it to 2.0.9 for instance.
Is that a problem or should we say [2.2
27 matches
Mail list logo
