Technically I'd get away with updating 2-3 artifacts, but I'd end up
writing a cookbook on how to add a crapload of dependencies to the
plugins in question and answering on the mailing list and irc, and in
the end we'd have a ton of poms lying around with 3 overridden
dependencies in 4-5 plugin
Kristian can describe in more detail what he's working on, but not all changes
take 8 artifact changes. In this case I think it's both that it's something
that affects multiple things (rather than dependencies), and also a couple of
things that have been broken down to one too separate many arti
Please make a new thread.
On Mon, Jun 20, 2011 at 5:51 PM, Mark Derricutt wrote:
> (Other) Mark,
>
> I'm not sure I see the connection here? Lukas had made comment that making
> one release would trigger cascading releases, which I assume is because
> downstream plugins have fixed version number
(Other) Mark,
I'm not sure I see the connection here? Lukas had made comment that making
one release would trigger cascading releases, which I assume is because
downstream plugins have fixed version number dependencies.
However if those dependencies were [1.0,2.0) then they would use the most
re
Mark,
maybe this is not so obvious, but Maven internally has ClassLoader isolation
between plugins. This is comparable to a servlet container where 1 webapp only
can see its own classes. This way it is no problem that there are more versions
of a plugin (or any other dependency) being used in t
Wow - that seems like a hell of a lot of releases having to be made...
This post is probably drifting off topic but the thing that strikes me here
is that this is the exact reason why maven supports version ranges - so that
you don't have to make a plethora of rolling releases just because one
cha
Hi,
Apologies for any inconvenience and thank you to those who have already
completed the survey. We will keep the survey open for another couple of
weeks. But, we do hope you will consider responding to the email request
below (sent 2 weeks ago).
Thanks,
Dr. Jeffrey Carver
Assistant Professor
U
actually I think javax.jstl NEVER have been on maven.central.
It originally was hosted on java.net, but they killed parts of their maven repo
while migrating from sun to oracle.
There is of course an ALv2 version of jstl:
http://repo1.maven.org/maven2/org/apache/geronimo/bundles/jstl/1.2_1/
Li
I though artifacts were supposed to never change at central... This could
break people's builds.
/Anders
On Mon, Jun 20, 2011 at 19:00, Paul Gier wrote:
> It seems that the artifacts were moved to a different location:
> https://issues.sonatype.org/browse/MVNCENTRAL-71
>
> On 06/20/2011 10:41 A
It seems that the artifacts were moved to a different location:
https://issues.sonatype.org/browse/MVNCENTRAL-71
On 06/20/2011 10:41 AM, Paul Gier wrote:
> The artifacts for javax.servlet:jstl:1.2 seem to have disappeared from
> central [1]. They still appear in the Sonatype search [2]. Does any
The artifacts for javax.servlet:jstl:1.2 seem to have disappeared from
central [1]. They still appear in the Sonatype search [2]. Does anyone
know what happened to these files? Were they removed because of a bad
license or something?
[1]http://repo1.maven.org/maven2/javax/servlet/jstl/
[2]http
Hi,
I'm no Maven PMC member, but please don't care about the kind of recent mail
that was recently received here.
This was only clueless flaming, not well-thought and constructive critics
that would have had a chance to improve something.
Having frequent releases is a good thing for people to see
Gavin McDonald wrote:
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Monday, 20 June 2011 9:00 PM
To: Maven Developers List
Cc: ga...@16degrees.com.au
Subject: Re: [VOTE]: release maven-changes-plugin 2.6
Gavin,
When you sent your message containing
Gavin,
Don't take it personal. I have expressed my opinion like you have
expressed yours, and we are both entitled to do so. But you have to
realize that your comments were taken with offence by some developers. I
have been with maven for several years now, I know we have taken
criticism for
Gavin,
Since I seem to have misread your tone, I apologize.
--benson
On Mon, Jun 20, 2011 at 7:53 AM, Gavin McDonald wrote:
>
>
>> -Original Message-
>> From: Benson Margulies [mailto:bimargul...@gmail.com]
>> Sent: Monday, 20 June 2011 9:00 PM
>> To: Maven Developers List
>> Cc: ga...
> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com]
> Sent: Monday, 20 June 2011 9:00 PM
> To: Maven Developers List
> Cc: ga...@16degrees.com.au
> Subject: Re: [VOTE]: release maven-changes-plugin 2.6
>
> Gavin,
>
> When you sent your message containing the wor
Gavin,
When you sent your message containing the words, "ignore me," I was
planning to take you at your word. But since you seem to have
continued to continue your campaign of sneer here I guess I'll
respond.
1: As it turned out, the vote that started all this concerned 10
issues. I was misled by
Recently a release vote received some criticism about whether the
release candidate contained sufficient changes to deserve a release.
Here is my position as a member of the Maven PMC.
If you are a Maven Committer and you think that a specific plugin /
component has a change which _you_ are prepa
On 20 June 2011 10:48, Gavin McDonald wrote:
>
>
>> -Original Message-
>> From: Lukas Theussl [mailto:ltheu...@gmail.com] On Behalf Of Lukas Theussl
>> Sent: Monday, 20 June 2011 7:25 PM
>> To: Maven Developers List
>> Subject: Re: [VOTE]: release maven-changes-plugin 2.6
>>
>>
>>
>> Gavin
> -Original Message-
> From: Lukas Theussl [mailto:ltheu...@gmail.com] On Behalf Of Lukas Theussl
> Sent: Monday, 20 June 2011 7:25 PM
> To: Maven Developers List
> Subject: Re: [VOTE]: release maven-changes-plugin 2.6
>
>
>
> Gavin McDonald wrote:
> >
> >
> >> -Original Message---
Gavin McDonald wrote:
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: Sunday, 19 June 2011 6:08 AM
To: Maven Developers List; Maven Project Management Committee List
Subject: [VOTE]: release maven-changes-plugin 2.6
Hi,
We solved 3 issues:
Really? Y
On Mon, Jun 20, 2011 at 11:41 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> I somehow think that if I was to do this integration I'd consider reversing
> the order; build maven3 from scratch
> and then use maven3 to build the older versions.
>
>
Kristian,
Thanks for the suggestio
22 matches
Mail list logo
