the site plugin itself works
but the site plugin launches a lot of other plugins, like remote resources
plugin
which is apparently failing here
did you try to update remote resources to 1.5, like Dennis proposed?
Regards,
Hervé
Le samedi 22 février 2014 10:03:14 Jason van Zyl a écrit :
> That
wondering where nexus is looking to resolve dependencies?
I'll try provided for nexus-core
(re)posted to nexus-...@sonatype.org
Thanks Stewart
Martin
> Subject: Re: Sonatype plugin question?
> From: mccu...@gmail.com
> Date: Sun, 23 Feb 2014 00:37:17 +
> To: dev@maven.apache.org
>
Hi,
it does appear, but is listed as "app-client" instead of "acr"
perhaps name in the list should be updated because it's not easy to figure out
that app-client == acr
Regards,
Hervé
Le jeudi 20 février 2014 00:01:39 Karl Heinz Marbaise a écrit :
> Hi,
>
> so after taken a look into SVN it
On 23 Feb 2014, at 00:08, Martin Gainty wrote:
> I *think* the sonatype folk went home for weekend so I'll ask maven gurus
Odd assumption, why didn’t you at least try asking this question on nexus-user
or nexus-dev?
> Close to getting a plugin working but when i start wrapper.exe the
> wrapper
I wrote and installed a quick and dirty sonatype plugin
My Nexus OpenSource distro that Im testing against is 2.8.0-SNAPSHOT
my plugin examples came from 2.7.0
If Monday am comes and Im calling no joy... i'll revert nexus back to 2.7.0 and
test on that
I guess Sonatype folk are is in Russia or wa
I think this message comes from a Nexus server, and the "plugin" refers
to Nexus plugin running on the server. Almost looks like a broken Nexus
installation, but it's been some time since I last looked at Nexus.
--
Regards,
Igor
On 2/22/2014, 19:08, Martin Gainty wrote:
I *think* the sonatype
It's not political correctness (I've never been accused of that before), it's
just self interest in protecting myself against unintended imagery...
On Feb 22, 2014, at 3:31 PM, Jason van Zyl wrote:
> Ok, I promise never to poke fun if you promise never to never again use the
> word "hump" in a
I *think* the sonatype folk went home for weekend so I'll ask maven gurus
Close to getting a plugin working but when i start wrapper.exe the wrapper.log
displays this error:
"The following plugins were processed:
jvm 1| ...
org.sonatype.nexus.plugins:stagingrules-nexus-plugin:1.0-SNAPSHOT
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'
You are overly politically correct. I should take offence!
On 22 February 2014 23:31, Jason van Zyl wrote:
> Ok, I promise never to poke fun if you promise never to never again use
> the word "hump" in an email to this list.
>
> On Feb 22, 2014, at 12:24 PM, Stephen Connolly <
> stephen.alan.co
Ok, I promise never to poke fun if you promise never to never again use the
word "hump" in an email to this list.
On Feb 22, 2014, at 12:24 PM, Stephen Connolly
wrote:
> Somehow with my brief emails you find some misinterpretation to take a hump
> at! Verbose or misunderstood... You decide ;-
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?
>
>
>
Am 2014-02-22 00:58, schrieb Dennis Lundberg:
Hi,
If anyone wants to add something to the next release of the Checkstyle
plugin, now would be a good time to do it, as I intend to make a
release next week. If you need more time to squeeze something in, just
let me know.
Thanks for that notifica
On 22 February 2014 22:00, Baptiste Mathus wrote:
> +1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become
> old. We're already using Java 1.7 at our shop, and plan to migrate to 1.8
> asap. And we're really not a startup kind of company ;-). And I'm sure the
> features in 1.
+1 to dump Java 5.
Gary
Original message
From: Baptiste Mathus
Date:02/22/2014 17:00 (GMT-05:00)
To: Maven Developers List
Subject: Re: Java 1.5
+1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become
old. We're already using Java 1.7 at our shop, an
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
+1 to dump Java5 compat. In about 2 months, even Java 6 will rapidly become
old. We're already using Java 1.7 at our shop, and plan to migrate to 1.8
asap. And we're really not a startup kind of company ;-). And I'm sure the
features in 1.8 (compared to the ones in the previous version) is gonna
ac
+1
- can be built and tested from source-release.zip
- rat: only approved licenses
- sha11: correct
- site: ok
Robert
Op Fri, 21 Feb 2014 15:13:14 +0100 schreef Stephen Connolly
:
Hi,
We solved 4
issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431&styleName=Html&vers
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 a plugin depends on Maven 2.2.1 through 3.1.1 then we are stuck with Java 1.5
Hence my version policy that you lot are all ignoring commenting on... No
comments means I'll just put it up for a vote ;-)
Sent from my iPhone
> On 22 Feb 2014, at 20:10, "Arnaud Héritier" wrote:
>
> ;) AFAIR fo
Somehow with my brief emails you find some misinterpretation to take a hump at!
Verbose or misunderstood... You decide ;-)
Sent from my iPhone
> On 22 Feb 2014, at 20:03, Jason van Zyl wrote:
>
> Didn't we decide that everything can be 1.6? I remember because it was one of
> Stephen's overly
Yeah need to update site plugin to 3.3 and it should work on mvn 2.x and
3.x (yes 2.x is EOL already but anyways)
On Saturday, 22 February 2014, Jason van Zyl wrote:
> I had build of master I was using.
>
> jvz
>
> > On Feb 22, 2014, at 11:25 AM, Dennis Lundberg
> > >
> wrote:
> >
> > Which ver
;) AFAIR for core yes. New releases (thus 3.2) should be certified 1.6+
For plugins it's another story I suppose depending of the version of maven core
they are supposed to support..
—
Sent from Mailbox for iPhone
On Sat, Feb 22, 2014 at 9:04 PM, Jason van Zyl wrote:
> Didn't we decide that e
Didn't we decide that everything can be 1.6? I remember because it was one of
Stephen's overly long emails :-)
jvz
> On Feb 22, 2014, at 11:02 AM, Benson Margulies wrote:
>
> How much longer with this Java 1.5 business? It' a giant pain.
>
> ---
I had build of master I was using.
jvz
> On Feb 22, 2014, at 11:25 AM, Dennis Lundberg
> wrote:
>
> Which versions of Maven failed for you?
>
>> On Sat, Feb 22, 2014 at 7:03 PM, Jason van Zyl wrote:
>> That version of the site plugin we have configured just doesn't work with
>> newer versio
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
I think we might just use animal sniffer to check such compatibility if we want
to keep it. Not 100% safe but enought to cover a respectable compatibility
My 2 cents
—
Sent from Mailbox for iPhone
On Sat, Feb 22, 2014 at 8:44 PM, Benson Margulies
wrote:
> The business of being required to us
The business of being required to use it in all Maven releases, which
adds a layer of VM complexity to my process.
On Sat, Feb 22, 2014 at 2:31 PM, Dennis Lundberg wrote:
> Which business are you referring to?
>
> On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies
> wrote:
>> How much longer wi
Which business are you referring to?
On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies wrote:
> How much longer with this Java 1.5 business? It' a giant pain.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For
Which versions of Maven failed for you?
On Sat, Feb 22, 2014 at 7:03 PM, Jason van Zyl wrote:
> That version of the site plugin we have configured just doesn't work with
> newer versions of Maven. I ran the command with Maven 3.0.4 and it works.
>
> We are a long, long, long way from push button
How much longer with this Java 1.5 business? It' a giant pain.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
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
That version of the site plugin we have configured just doesn't work with newer
versions of Maven. I ran the command with Maven 3.0.4 and it works.
We are a long, long, long way from push button releases.
On Feb 22, 2014, at 1:54 AM, Dennis Lundberg wrote:
> Hi Jason,
>
> Looking at the stack
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.
-
Artifacts have been pushed to Maven Central. I'll wait for them to arrive
before announcing and publishing the main site.
On Feb 20, 2014, at 3:22 AM, Olivier Lamy wrote:
> +1
> finally it's agile @apache :P
>
>
> On 20 February 2014 13:30, Igor Fedorenko wrote:
>> Jason, Stephen, other PMC
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 Jason,
Looking at the stack trace it seems to be the remote resources plugin that
is throwing an NPE. Didn't you release 1.5 of that plugin because of issues
with core? Your build is using 1.4...
--
Dennis Lundberg
Den 22 feb 2014 05:30 skrev "Jason van Zyl" :
> Not sure who looks after the s
54 matches
Mail list logo
