this will work as well, thank you for the idea.
Original Message
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Nigel Magnay
To: Maven Developers List
Date: Tue 09 Apr 2013 03:47:21 AM CDT
> This keeps coming up, over and over and over.
>
> e.g:
> http://maven.40175.n5.nabble.c
+1
Regards,
Hervé
Le lundi 8 avril 2013 18:42:08 Kristian Rosenvold a écrit :
> And, to increase my winning chance in "messiest vote thread of the
> year", here's the correct link
> for surefire 2.14.1 solved issues ;)
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&versio
that's it, it works
thank you Stuart: I knew I was missing something like this = few code but
major structure :)
Regards,
Hervé
Le mardi 9 avril 2013 12:30:31 Stuart McCulloch a écrit :
> On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
> > I just did the reimport and changed API to let the code
If this would help with MRELEASE-564 and other equivalent issues I'm all
ears.
The issue I'm facing is that the maven-release-plugin can't detect
dependencies/artifacts specified within the configuration. These are files
you can't just add to the dependencies of the plugin, because they have
Doesnt each plugin needs its own handling?
Maybe some event base siluyion with just a spi yo register listeners is
better (like in arquillian)
Le 9 avr. 2013 21:49, "Baptiste MATHUS" a écrit :
> +1. Would be great.
> I was recently thinking about this when designing an enforcer rule about
> nam
+1. Would be great.
I was recently thinking about this when designing an enforcer rule about
naming & dependency rule. I want to define some simple config through XML,
but also considered being able to inject some kind of
DependencyNamingRulesStrategy by anyone who would not have enough with the
st
+1 :)
2013/4/9 Olivier Lamy
> +1
>
>
> 2013/4/9 Kristian Rosenvold :
> > And, to increase my winning chance in "messiest vote thread of the
> > year", here's the correct link
> > for surefire 2.14.1 solved issues ;)
> >
> >
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&ver
How does the wicket-style approach look like?
I think we should end up with something that allows to have:
* multiple implementations of the same interface, e.g. different test
filters, different test run listeners
* configurable extensions, e.g. configure details for the filters or run
listener
Yes when I analyzed the behavior, seeing it was here for long long time I
understood that it was probably done by design.
I had a look at our doc (
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management)
and we should probably detail more this be
On 9 Apr 2013, at 03:33, Hervé BOUTEMY wrote:
> I just did the reimport and changed API to let the code compile [1]
>
> but I get Guice provisioning exceptions during tests: probably something
> stupid in initialization, but I don't know what to do
> Can you help me at this step, please?
You ne
surefire (and quite a few other plugins) seem to be screaming for a
simple way to add user-defined extension points for easy ability to
modify/extend capabilities without forking the plugin or further
bloating it for yet more marginal use cases.
Conceptually I'm thinking somewhere along these line
This is how is was designed to work. Aether can do anything but the original
implementation is simply a map of GAs with a version preference. If the GA is
encountered then its version is overridden. This effectively gives you a target
platform like mechanism but is intended to be controlled from
+1
2013/4/9 Kristian Rosenvold :
> And, to increase my winning chance in "messiest vote thread of the
> year", here's the correct link
> for surefire 2.14.1 solved issues ;)
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19135
>
>
>
> 2013/4/7 Kristian Rosenvold :
>
This keeps coming up, over and over and over.
e.g:
http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html
The maven 'answer' seems to amount to 'hard cheese, you must re-specify
each and every one of your dependencies again in your plugin config'. And
then po
On Tue, Apr 9, 2013 at 3:44 AM, Hervé BOUTEMY wrote:
> uh, really interesting case
>
I was sure you'll like it ;-)
>
> this gives me more interest in reimporting maven-aether-provider unit
> tests to
> reproduce and track the issue :)
>
>
+1
> I just tried the example, but the beta spring ar
15 matches
Mail list logo