Right, see one of my earlier posts on this.
m-r-p seems to trigger a bug in Java 5, making it impossible to build
it using Java 5.
Having the correct source/target versions set and checking it with
animal sniffer should be enough.
On Sat, Feb 22, 2014 at 11:40 PM, Benson Margulies
wrote:
> I can'
cool! I'm grand. I cut m-gpg-p 1.5 using Java 1.7.0_51 and look at my class
versions!
java -jar
~/codehaus/animal-sniffer/animal-sniffer/target/animal-sniffer-1.10.jar
~/apache/maven-gpg-plugin/target/checkout/target/maven-gpg-plugin-1.5.jar
49.0
/Users/stephenc/apache/maven-gpg-plugin/target/ch
AFAIK yes we do... but if we don't then I'll need to cancel gpg 1.5
On 22 February 2014 22:40, Benson Margulies wrote:
> I can't built the m-r-p with Java 1.5. The compiler plugin fails.
> Don't we have source and target set so that I can leave JAVA_HOME at
> 1.6 and still cut a release?
>
>
>
I can't built the m-r-p with Java 1.5. The compiler plugin fails.
Don't we have source and target set so that I can leave JAVA_HOME at
1.6 and still cut a release?
On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies wrote:
> That's my plan. Cut a release with things as they are today, though
> Rob
That's my plan. Cut a release with things as they are today, though
Robert's discovery suggests at least a brief delay.
On Sat, Feb 22, 2014 at 3:00 PM, Jason van Zyl wrote:
> If you're going to try and cut a release that works with 2.x then I wouldn't
> worry about updating scm. I think users o
Found the cause:
SCM 1.8 has the following components.xml
org.apache.maven.scm.manager.ScmManager
org.apache.maven.scm.manager.plexus.DefaultScmManager
false
org.apache.maven.scm.provider.ScmProvider
scmProviders
If you're going to try and cut a release that works with 2.x then I wouldn't
worry about updating scm. I think users on Git are also more likely to be on m3
which is where the scm issues are yes? If you want to cut a quick release for
2.x users I would try and leave as many of the existing deps
Jason, I can't help suspecting that the first step in housecleaning
here will be a new-tech SCM release, do you think so?
On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies wrote:
> Seems to me we might as well make one last release with what's there
> now, just in case it helps someone. Then clea
Seems to me we might as well make one last release with what's there
now, just in case it helps someone. Then clean the closet.
On Sat, Feb 22, 2014 at 1:47 PM, Jason van Zyl wrote:
> I'l try it before you release it. But I suggest you modernize it and by that
> I mean forget Maven 2.x and up
I'l try it before you release it. But I suggest you modernize it and by that I
mean forget Maven 2.x and update it to the sisu-plexus, remove all the old
crap. If you want to use the new stuff then move to a relatively modern version
of Maven. If users need new capabilities then they move forwar
On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte wrote:
> I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on 1.9,
> such as the maven-scm-providers-standard.
> This brings me to the next question: Are you convinced that 1.9 will solve
> all the problems of the GIT users?
> I'm
I am willing to do the work of RM'ing what we have here, since no one
out there will test anything before it's released.
On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies wrote:
> On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte wrote:
>> I've only changed maven-scm-manager-plexus to 1.8, and ke
I've only changed maven-scm-manager-plexus to 1.8, and kept the rest on
1.9, such as the maven-scm-providers-standard.
This brings me to the next question: Are you convinced that 1.9 will solve
all the problems of the GIT users?
I'm not, and I wouldn't prepare a "git special"-release without kn
This, of course, does not help the people pining for the git support in 1.9.
On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholte wrote:
> http://svn.apache.org/r1570870 fixes the unittests on my machine.
> I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's a
> serious issue he
https://jira.codehaus.org/browse/SCM-698 seems to be the cause
Op Sat, 22 Feb 2014 19:10:06 +0100 schreef Robert Scholte
:
http://svn.apache.org/r1570870 fixes the unittests on my machine.
I'll have to check was has changed between SCM 1.8 and 1.8.1, but
there's a serious issue here.
Rob
http://svn.apache.org/r1570870 fixes the unittests on my machine.
I'll have to check was has changed between SCM 1.8 and 1.8.1, but there's
a serious issue here.
Robert
Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies
:
Still 2.2.1.
So, in version 2.2.1,
org.apache.maven.arti
Still 2.2.1.
So, in version 2.2.1,
org.apache.maven.artifact.transform.DefaultArtifactTransformationManager
tries to patch a list that is injected, and gets into trouble because
Plexus has made the list unmodifiable. Presumably, that
unmodifiability was some improvement to plexus.
I guess that ta
What version of Maven does release plugin depend on? I think
DefaultArtifactTransformationManager.initialize was removed in 3.x, at
least it's not present in 3.2.1 and 3.1.1.
--
Regards,
Igor
On 2/22/2014, 12:35, Benson Margulies wrote:
I'm sorry, I did mislead you. Not surprisingly, adding mav
I'm sorry, I did mislead you. Not surprisingly, adding maven-compat
did not fix the problem with the apparently unmodifiable list.
On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies
wrote:
> I may have misled you, but I'll try it.
>
> Caused by:
> org.codehaus.plexus.component.repository.excepti
I may have misled you, but I'll try it.
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
Error constructing component role:
'org.apache.maven.artifact.resolver.ArtifactResolver', implementation:
'org.apache.maven.artifact.resolver.DefaultArtifactResolver'
You need to add maven-compat as a dependency.
--
Regards,
Igor
On 2/22/2014, 12:27, Benson Margulies wrote:
Further down the message, this boils down to a failure to find an
ArtifactResolver.
On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies
wrote:
Plexus-container-default 1.5.5 changes som
Further down the message, this boils down to a failure to find an
ArtifactResolver.
On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies
wrote:
> Plexus-container-default 1.5.5 changes some issues.
>
> This seems to make some things better.
>
> The first failure is:
>
> testNoSnapshotDependencies(o
Plexus-container-default 1.5.5 changes some issues.
This seems to make some things better.
The first failure is:
testNoSnapshotDependencies(org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhaseTest)
Time elapsed: 0.07 sec <<< ERROR!
org.codehaus.plexus.component.repository.except
On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte wrote:
> src/test/resources/org/apache/maven/shared/release/phase
I'm trying to use a less ancient version of plexus-container-default,
it requires some test changes, I'll let you know what happens.
-
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentRepositoryException:
Component descriptor role: 'org.apache.maven.scm.manager.ScmManager',
implementation: 'org.apache.maven.scm.manager.plexus.DefaultScmManager',
role hint: 'default' has a hint, but there are other imp
Hi Benson,
is that with Maven 3.2.1?
I'm having random test failures with 3.2.1 on some projects.
Switching back to 3.1.1, everything's fine.
Regards,
Patrick.
--
View this message in context:
http://maven.40175.n5.nabble.com/Releasing-the-release-plugin-tp5785682p5785697.html
Sen
The CI job on Jenkins actually failed right after the upgrade of SCM to 1.9.
See job #226 at
https://builds.apache.org/view/M-R/view/Maven/job/maven-release/
On Fri, Feb 21, 2014 at 9:29 PM, Benson Margulies wrote:
> I just got an it failure email, apparently it has been in the tank for some
> t
I just got an it failure email, apparently it has been in the tank for some
time. What changed since the person who upgraded scm tested that change?
On February 21, 2014 2:44:10 PM EST, Robert Scholte
wrote:
>Ok, I found the cause and you're not gonna to like it.
>put scmVersion 1.9 back to 1.7
Ok, I found the cause and you're not gonna to like it.
put scmVersion 1.9 back to 1.7 and see the magic.
Seems like I missed something here, but why?
Robert
Op Fri, 21 Feb 2014 20:24:39 +0100 schreef Dennis Lundberg
:
I see those errors as well.
Also I have found that I cannot build maven
>
>--
>View this message in context:
>http://maven.40175.n5.nabble.com/Releasing-the-release-plugin-tp5785682p5785704.html
>Sent from the Maven Developers mailing list archive at Nabble.com.
>
>-
>To unsubscribe
I see those errors as well.
Also I have found that I cannot build maven-release using Java 5. Have
tried on Win 7 and Ubuntu - same problem. After downgrading to
maven-compiler-plugin:2.5.1 I was able to get the real error message
(3.0 seems to swallow it):
org.apache.maven.lifecycle.LifecycleEx
I see some small difference between 2.4.2 and current trunk which could be
part of the cause:
- different parent pom
- different version of surefire
I'll investigate
Robert
Op Fri, 21 Feb 2014 16:56:06 +0100 schreef Benson Margulies
:
I checked out the trunk and tried a simple 'mvn test
Hi Benson,
is that with Maven 3.2.1?
I'm having random test failures with 3.2.1 on some projects.
Switching back to 3.1.1, everything's fine.
Regards,
Patrick.
--
View this message in context:
http://maven.40175.n5.nabble.com/Releasing-the-release-plugin-tp5785682p5785704.html
I checked out the trunk and tried a simple 'mvn test', and I'm
drowning in test failures. Anyone have a hint?
---
Test set: org.apache.maven.shared.release.DefaultReleaseManagerTest
Yes this is annoying because not having interactive mode for PGP requires
either to put the password in our settings (without encryption) or to have to
use an agent (not always easy to setup for a wide team)
Arnaud
On Aug 1, 2010, at 4:59 PM, Marshall Schor wrote:
>
>
> On 7/30/2010 8:34 PM
On 7/30/2010 8:34 PM, Brian Fox wrote:
> A lot of people seem to have the gpg plugin hang during release
> perform.
It used to hang for me because I didn't want to put my gpg passphrase into a
file. I fixed it by installing (on Windows, where I'm running maven), a version
of the GPG client tha
A lot of people seem to have the gpg plugin hang during release
perform. It's never happened to me so I haven't dug into the root
cause, if it's release or gpg...but that's the only thing that
immediately comes to mind.
On Thu, Jul 29, 2010 at 7:01 PM, Brett Porter wrote:
> Several folks seem int
yup.
I have this fix locally I will commit it.
2010/7/30 Benjamin Bentmann :
> Brett Porter wrote:
>
>> That's one on the list - it's already committed on trunk, and Olivier has
>> volunteered to help get the SCM release out :)
>
> It seems r952813 should be reverted for the SCM 1.4 release. The
Brett Porter wrote:
That's one on the list - it's already committed on trunk, and Olivier has
volunteered to help get the SCM release out :)
It seems r952813 should be reverted for the SCM 1.4 release. The updated
plexus plugin generates non-empty role hints for the components which
causes
I have 2 annoying issues with 2.0 version of the release plugin :
* http://jira.codehaus.org/browse/MRELEASE-263 : Annoying to use GPG signature.
The easier solution for now is to store the password in our settings and this
one isn't encrypted.
* http://jira.codehaus.org/browse/MRELEASE-536 : Th
MRELEASE-128 SCM element properties replacement has been there for
long time. That would be nice to be fixed.
Rgds,
Markku
On 30.7.2010 2:01, Brett Porter wrote:
Several folks seem interested in a small handful of release plugin issues, so I
hoped to work on them next week and push towards g
That's one on the list - it's already committed on trunk, and Olivier has
volunteered to help get the SCM release out :)
On 30/07/2010, at 7:39 AM, Mark Derricutt wrote:
> While not release plugin specific, there's a few Maven SCM issues which
> effect the release process when using git.
>
> On
+1 to release Maven SCM too
See http://jira.codehaus.org/browse/MRELEASE-497 and
http://jira.codehaus.org/browse/SCM-562
On Fri, Jul 30, 2010 at 3:39 AM, Mark Derricutt wrote:
> While not release plugin specific, there's a few Maven SCM issues which
> effect the release process when using git.
>
While not release plugin specific, there's a few Maven SCM issues which
effect the release process when using git.
One of the mains ones being http://jira.codehaus.org/browse/SCM-444 - which
provides functionality to disable a git push during release:prepare.
If we're doing a release of the relea
Several folks seem interested in a small handful of release plugin issues, so I
hoped to work on them next week and push towards getting another release out.
Are there any issues that folks here would like to work on and see included
that aren't already?
Cheers,
Brett
--
45 matches
Mail list logo
