Well actually I'd say force people to use 2.2.2 after rolling a 2.2.2
that does not barf on the 3.0.3 metadata in local repo... such a 2.2.2
does not need to understand the extra metadata, just not barf on it
(i.e. copy the 2.2.1 tag, make the metadata forgiving, release 2.2.2
so that the changes a
So what you're actually saying:
Let's force people to NOT use Maven-2.1.0 of 2.2.0 by setting the
prerequisite for maven to 2.2.1
And hence, we get the Doxia verison we want.
That would solve two problems at once.
-Robert
On Mon, 16 Jan 2012 16:47:39 +0100, Stephen Connolly
wrote:
On 16
On 16 January 2012 15:45, Stephen Connolly
wrote:
> On 15 January 2012 11:11, Hervé BOUTEMY wrote:
>> Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
>>> personally i think we need to draw a line in the sand for all plugins...
>>> 2.2.1 is the best line at the moment imho...
>> +1
>
On 15 January 2012 11:11, Hervé BOUTEMY wrote:
> Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
>> personally i think we need to draw a line in the sand for all plugins...
>> 2.2.1 is the best line at the moment imho...
> +1
>
>>
>> 2.1.0 and 2.2.0 are not recommended versions, and
Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
> personally i think we need to draw a line in the sand for all plugins...
> 2.2.1 is the best line at the moment imho...
+1
>
> 2.1.0 and 2.2.0 are not recommended versions, and drawing a line above them
> makes our message to users t
personally i think we need to draw a line in the sand for all plugins...
2.2.1 is the best line at the moment imho...
2.1.0 and 2.2.0 are not recommended versions, and drawing a line above them
makes our message to users that much cleaner.
the only other thing we maybe should do is roll a 2.2.2 t
I've fixed MCHECKSTYLE-170 and tried to apply some shading.
The separation of api/interfaces versus implementation is not done well in
Doxia.
This would mean, that the shade-plugin will need a lot of configuration,
which also needs to be maintained if there are new Doxia-classes.
So for plugin
+1 Now that Java 1.5 has already seen EOL for some years it is funny that
most plugins even are still working with 1.4.
Regards Mirko
--
Sent from my phone
http://illegalstateexception.blogspot.com
http://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Jan 12, 2012 12:22 AM, "Be
On 2012-01-13 20:43, Robert Scholte wrote:
> My guess would be that with relocation it wouldn't matter.[1]
> I'd like to confirm this with the maven-checkstyle-plugin project, but
> unfortunately a lot of unit-tests are failing on my machine (win7 + jdk6
> + any M2/M3)
I can confirm these test err
+1
Le mercredi 11 janvier 2012 18:22:29 Benson Margulies a écrit :
> I tend to feel that this community is a bit whelmed, and that we'd do
> better service to the world at large if we drew a line in the sand at
> 2.2.1. Anyone who really wants new functionality with older core maven
> can step up
My guess would be that with relocation it wouldn't matter.[1]
I'd like to confirm this with the maven-checkstyle-plugin project, but
unfortunately a lot of unit-tests are failing on my machine (win7 + jdk6 +
any M2/M3)
-Robert
[1]
http://maven.apache.org/plugins/maven-shade-plugin/example
Hi
Can it work? I haven't had much experience with shading, but I was under
the impression that it is a way to hide classes from Maven's class
loader. What we really want in this case is a way to *insert* newer
versions of classes into Maven's class loader. Don't know if that can be
done...
On 20
+1
--
Olivier
Le 11 janv. 2012 23:23, "Dennis Lundberg" a écrit :
> Hi
>
> I've had a look at this issue in the Checkstyle Plugin
> http://jira.codehaus.org/browse/MCHECKSTYLE-146
>
> The issue is not unique to the Checkstyle Plugin, but rather any plugin
> that uses Doxia 1.1.x or newer. That m
+1
Den 11. jan. 2012 kl. 23:23 skrev Dennis Lundberg :
> Hi
>
> I've had a look at this issue in the Checkstyle Plugin
> http://jira.codehaus.org/browse/MCHECKSTYLE-146
>
> The issue is not unique to the Checkstyle Plugin, but rather any plugin
> that uses Doxia 1.1.x or newer. That means at leas
we should maybe roll a 2.3 where the fix is being aware of the new snapshot
metadata so that people who have projects not ready for 3.0.4 can have them
coexist.
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of u
+1
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 11 Jan 2012 23:22, "Benson Margulies" wrote:
> I tend to feel that this community is a bit whelmed, and that we'd do
> b
I tend to feel that this community is a bit whelmed, and that we'd do
better service to the world at large if we drew a line in the sand at
2.2.1. Anyone who really wants new functionality with older core maven
can step up and volunteer to maintain branches of plugins.
On Wed, Jan 11, 2012 at 6:1
On Thu, Jan 12, 2012 at 9:42 AM, Robert Scholte
wrote:
> What about plugins containing both build and report goals?
> If the suggested shading of Doxia will work, I'd prefer that option.
Can you elaborate on the problem?
-
To un
What about plugins containing both build and report goals?
If the suggested shading of Doxia will work, I'd prefer that option.
-Robert
On Wed, 11 Jan 2012 23:53:57 +0100, Barrie Treloar
wrote:
On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly
wrote:
+1
+1
On Thu, Jan 12, 2012 at 9:15 AM, Stephen Connolly
wrote:
> +1
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 11 Jan 2012 22:23, "Dennis Lundberg" wrote:
> Hi
>
> I've had a look at this issue in the Checkstyle Plugin
> http://jir
Hi
Some background on Maven and Doxia versions and compatibility can be
found here:
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
On 2012-01-11 23:22, Dennis Lundberg wrote:
> Hi
>
> I've had a look at this issue in the Checkstyle Plugin
> http://jira.codehaus.org/browse/MCHECKSTYL
Hi
I've had a look at this issue in the Checkstyle Plugin
http://jira.codehaus.org/browse/MCHECKSTYLE-146
The issue is not unique to the Checkstyle Plugin, but rather any plugin
that uses Doxia 1.1.x or newer. That means at least all reporting
plugins. I've verified it on the PMD Plugin that I am
23 matches
Mail list logo
