Hi
Maybe I'm doing something wrong and maybe it's Maven bug.
Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
I have multi-module test project for my plugin:
https://maven-play-plugin.googlecode.com/svn/tags/test-projects-1.0.0-beta6/packagings/default/inter-app-dependency
There are two
On 11/04/2013 09:08 AM, Grzegorz Słowikowski wrote:
Maybe I'm doing something wrong and maybe it's Maven bug.
Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
I have multi-module test project for my plugin:
On 2013-11-04 10:03, Mikolaj Izdebski wrote:
On 11/04/2013 09:08 AM, Grzegorz Słowikowski wrote:
Maybe I'm doing something wrong and maybe it's Maven bug.
Failing with many Maven versions: 2.2.1, 3.0.x, 3.1.x
I have multi-module test project for my plugin:
If I checkout your test project it doesn't build. If you make a self contained
example that builds I'll take a look. It is most definitely a problem with the
WorkspaceReader which should be relatively easy to fix.
On Nov 4, 2013, at 3:08 AM, Grzegorz Słowikowski gslowikow...@gmail.com wrote:
Simplified version commited here:
http://maven-play-plugin.googlecode.com/svn/tmp/test-projects/reactor-problem/
Grzegorz
On 4 listopad 2013 15:12:45, Jason van Zyl wrote:
If I checkout your test project it doesn't build. If you make a self
contained example that builds I'll take a look. It
Danke.
On Nov 4, 2013, at 10:51 AM, Grzegorz Słowikowski gslowikow...@gmail.com
wrote:
Simplified version commited here:
http://maven-play-plugin.googlecode.com/svn/tmp/test-projects/reactor-problem/
Grzegorz
On 4 listopad 2013 15:12:45, Jason van Zyl wrote:
If I checkout your test
Hi Hervé
I'm not so happy with this solution, since it's abusing the xml namespace.
When we're going to do strict parsing with respect of the namespaces,
we're having serious issues.
Maybe in this case it is better to use properties:
sites
property
keyapache-maven:2.0.11/key
yes, I was surprised it even worked :)
I'll change the code tonight
thanks for your review
Hervé
Le lundi 4 novembre 2013 23:22:10 Robert Scholte a écrit :
Hi Hervé
I'm not so happy with this solution, since it's abusing the xml namespace.
When we're going to do strict parsing with
