Yes on both accounts. The clirr plugin was failing with the patch, but
was obviously hitting a too wide pattern.
,gitignore is because of git-svn users.
Kristian
Den 9. apr. 2013 kl. 03:58 skrev "Hervé BOUTEMY" :
> thank you for reviewing
>
>> Added:
>>maven/doxia/doxia/trunk/.gitignore
> w
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?
Regards,
Hervé
[1] https://github.com/hboutemy/maven
Le mard
thank you for reviewing
> Added:
> maven/doxia/doxia/trunk/.gitignore
was this intentional?
> Modified: maven/doxia/doxia/trunk/pom.xml
> URL:
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/pom.xml?rev=1465675&r1
> =1465674&r2=1465675&view=diff
> =
uh, really interesting case
this gives me more interest in reimporting maven-aether-provider unit tests to
reproduce and track the issue :)
I just tried the example, but the beta spring artifact isn't in Spring: I
can't simply reproduce, will need to work more on it.
BTW, did you try with Mave
Le dimanche 7 avril 2013 22:29:29 Jason van Zyl a écrit :
> On Apr 7, 2013, at 7:32 PM, Hervé BOUTEMY wrote:
> > while working on site publication, I found that all my work on
> > maven-aether- provider unit tests had simply been pruned when merging
> > Aether. I will need to re-do the work, step
I'd love to see this happening. We would be a big step closer to allow more
user-defined providers or extensions, which could easily be added as
plugin-dependencies, without having to worry too much on when to load what.
2013/4/8 Brett Porter
> I looked at something similar some time back and s
I looked at something similar some time back and struggled with it - but that
was pre-shading of providers and still having to deal with the forking to the
old booter. I suspect the combination of both will make this more feasible, but
it's long enough ago that I can't remember anything more spe
2013/4/8 John Casey :
> On 4/8/13 1:13 PM, Kristian Rosenvold wrote:
>> Surefire currently uses this classloader architecture :
>>
>> Boot
On 4/8/13 1:13 PM, Kristian Rosenvold wrote:
Surefire currently uses this classloader architecture :
Boot
Surefire currently uses this classloader architecture :
Boot
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 :
> Hi,
>
> maven-shared-utils 0.4
> --
> We sol
On the subject of forgetting things;
2.14.1 will be the last version to support ANY version of java prior to 1.5.
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
Hi all (and especially Herve, Jason and those who are working on Aether),
We are several to hit what we consider to be a bug but myself I don't
understand how we did to not see it before.
To be short the problem resides in depMgt usage. It is useful only in the
project you are building to enfo
The Apache Maven team is pleased to announce the release of the Maven
Compiler Plugin, version 3.1
The Compiler Plugin is used to compile the sources of your project.
The default compiler is javac and is used to compile Java sources.
Also note that at present the default source setting is 1.5 and
14 matches
Mail list logo