FWIW, I just completed /most/ of the conversion to commons-compress for the rest
of plexus-archiver; just so no-one else starts duplicating my work :)
K
2014-09-12 11:12 GMT+02:00 Stefan Bodewig bode...@apache.org:
On 2014-09-12, Kristian Rosenvold wrote:
The archivers in use are actually
On Linux, where i keep a very vanilla environment for this sort of thing,
running mvn test on the maven-release-plugin (using maven 3.0.5) yields:
Tests in error:
InvokerMavenExecutorTest.testEncryptSettings:132 » IllegalState Maven
applicat...
Help?
Is this us, or infra@?
[maven-scm-mvn-2.2x] $ /home/jenkins/tools/java/latest1.6/bin/java -cp
/home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar
hudson.maven.agent.Main /home/jenkins/tools/maven/apache-maven-2.2.1
/home/jenkins/jenkins-slave/slave.jar
http://mail.openjdk.java.net/pipermail/jdk7u-dev/2014-April/008910.html
Wondering if we should start thinking about upping to Java 7 as our minimum
next year ;-)
Sent from my iPad
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20535styleName=TextprojectId=10527Create=Createatl_token=ACIO-CAVI-QX7G-9IAS%7C6ec69413b98c8f7154244ebb8f5f495082468378%7Clin
Also listed below.
There are still a couple of issues left in
IIRC I'm getting this error when executed within the IDE, commandline
works fine.
Robert
Op Sat, 13 Sep 2014 13:49:52 +0200 schreef Benson Margulies
bimargul...@gmail.com:
On Linux, where i keep a very vanilla environment for this sort of thing,
running mvn test on the
I see it at command-line, with just 'mvn install'.
On Sat, Sep 13, 2014 at 10:02 AM, Robert Scholte rfscho...@apache.org
wrote:
IIRC I'm getting this error when executed within the IDE, commandline
works fine.
Robert
Op Sat, 13 Sep 2014 13:49:52 +0200 schreef Benson Margulies
I don't recall that something has changed here since you released 2.5...
Op Sat, 13 Sep 2014 16:03:18 +0200 schreef Benson Margulies
bimargul...@gmail.com:
I see it at command-line, with just 'mvn install'.
On Sat, Sep 13, 2014 at 10:02 AM, Robert Scholte rfscho...@apache.org
wrote:
I am completely failing to remember what I might have done differently.
On Sat, Sep 13, 2014 at 10:11 AM, Robert Scholte rfscho...@apache.org
wrote:
I don't recall that something has changed here since you released 2.5...
Op Sat, 13 Sep 2014 16:03:18 +0200 schreef Benson Margulies
Hi Benson,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20535styleName=TextprojectId=10527Create=Createatl_token=ACIO-CAVI-QX7G-9IAS%7C6ec69413b98c8f7154244ebb8f5f495082468378%7Clin
Also listed below.
There are still a couple of issues left in
Hi,
here my +1...
On 9/11/14 7:45 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=19151
Github user Tibor17 closed the pull request at:
https://github.com/apache/maven-surefire/pull/46
---
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
Since I'm planning a release, it occurs to me that this would be a
convenient moment to move this project. Did we decide to just migrate
things like this with no further discussion, or do we decide one by one?
Hi,
On 9/11/14 7:29 AM, Olivier Lamy wrote:
Hi,
I'd like to release Apache Wagon 2.7
We fixed 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20560styleName=TextprojectId=10335Create=Create
Staging repository:
https://repository.apache.org/content/repositories/maven-1054/
M2_HOME has to be set. I've added this to the site doc.
On Sat, Sep 13, 2014 at 10:33 AM, Benson Margulies bimargul...@gmail.com
wrote:
I am completely failing to remember what I might have done differently.
On Sat, Sep 13, 2014 at 10:11 AM, Robert Scholte rfscho...@apache.org
wrote:
I
All this will do is pick up SCM fixes. Still, that seems too big for 2.5.1
-- but definitely too small for 3.0. So I'm setting up for 2.6.0. If
someone disagrees I will change it again.
I agree that this is not a 3.0-release.
2.5 was mainly a Git release, and IMHO this release is an additional Git
bugfix release, so 2.5.1 would be fine for me.
Robert
Op Sat, 13 Sep 2014 18:51:03 +0200 schreef Benson Margulies
bimargul...@gmail.com:
All this will do is pick up SCM fixes.
That does probably explain why Eclipse has issues with it.
However, when executing from commandline, the M2_HOME should be set by the
mvn.bat/mvn.sh, right?
At least I know it works for Windows.
Robert
Op Sat, 13 Sep 2014 18:45:59 +0200 schreef Benson Margulies
bimargul...@gmail.com:
On Sat, Sep 13, 2014 at 1:09 PM, Robert Scholte rfscho...@apache.org
wrote:
That does probably explain why Eclipse has issues with it.
However, when executing from commandline, the M2_HOME should be set by the
mvn.bat/mvn.sh, right?
At least I know it works for Windows.
There's some complex
On Sat, Sep 13, 2014 at 1:06 PM, Robert Scholte rfscho...@apache.org
wrote:
I agree that this is not a 3.0-release.
2.5 was mainly a Git release, and IMHO this release is an additional Git
bugfix release, so 2.5.1 would be fine for me.
If no one else expresses an opinion I'll switch to that
Hi
I think that we have landed at this: whoever feel like moving
something to git announces it to the dev community and if no one
objects then goes ahead with the move.
That being said, maven-release is a vital component in this case. We
need to be absolutely certain that the release-plugin work
http://markmail.org/thread/owemhec7vfjdnvhc
IIRC the bottom line is that some parts are hard to migrate.
For instance: we prefer to keep the plugins together, but if it's 1 repo
per release-cycle project, we need a huge number of separate repo's.
For the maven-release project, as being one of
Hi
Maven Javadoc Plugin is one of our components that currently does not
work with Java 8. I have had a look at the issues in JIRA [1] and
there is now only one unresolved issue scheduled for 2.10:
MJAVADOC-393 [2]. As I have indicated in the issue I would like to
close it as Won't fix, but I
Hello,
yes I think if the fix is in a version specific handling, then it
should not be applied. (If the fix would be to always keep the slash
or not to alter the given link, then I would say add it).
BTW: wondering if lastIndexOf is really needed, in this context it can
only be the last char,
Benson,
If this release gets done before ASF-15 is released you might want to
revisit https://issues.apache.org/jira/browse/MPOM-55 and update to
the latest versions.
On Sat, Sep 13, 2014 at 6:51 PM, Benson Margulies bimargul...@gmail.com wrote:
All this will do is pick up SCM fixes. Still,
+1 for closing as won't fix. It was confirmed to be a JDK issue and they
fixed it.
Robert
Op Sat, 13 Sep 2014 21:25:47 +0200 schreef Dennis Lundberg
denn...@apache.org:
Hi
Maven Javadoc Plugin is one of our components that currently does not
work with Java 8. I have had a look at the
Hi,
+1 for closing as won't fix. It was confirmed to be a JDK issue and they
fixed it.
+1 from me too...for closing as won't fix.
Kind regards
Karl-Heinz
Robert
Op Sat, 13 Sep 2014 21:25:47 +0200 schreef Dennis Lundberg
denn...@apache.org:
Hi
Maven Javadoc Plugin is one of our
Le jeudi 11 septembre 2014 08:40:42 Kristian Rosenvold a écrit :
Excellent proposal Hervé, but how do we deal with jira-based
submissions ? I am probably @author of half my committs and @committer
of the rest ?
given we have the Submitted by stanza for svn, we should be able to count
these
Github user Tibor17 closed the pull request at:
https://github.com/apache/maven-surefire/pull/45
---
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
29 matches
Mail list logo
