Hi Florian,
since testing your problem I've some trouble with my workspace ;-)
I'm not understanding the behavior (of my ws) yet!
I'm using m3, there your problem seems to be fixed.
So it looks more like a bug than a feature!
Fredy
What happens, if you use mvn install?
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 10:51
An: users@maven.apache.org
Betreff: Dependency on pom-project not resolved in reactor on multi-module build
Hello,
I
How is the reactor solving the order of your modules?
How is the order in your parent pom?
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp [mailto:florian.ra...@jambit.com]
Gesendet: Freitag, 17. Dezember 2010 10:51
An: users@maven.apache.org
Betreff: Dependency on pom-project not
Hello Freddy,
Thanks for your quick reply. I should have mentioned that mvn installs solves
the problem. So Maven resolves the dependency from the local repository. But
this is just a workaround since I expect the dependency to be resolved from the
reactor.
I think the order in which the
Hello Florian,
have you defined the typepom/type ??
dependencies
dependency
groupIdmygroup/groupId
artifactIdA/artifactId
version${parent.version}/version
typepom/type
/dependency
Fredy
-Ursprüngliche Nachricht-
Von: Florian Rampp
Yes, I have. See my first mail for the content of A/pom.xml and B/pom.xml
Florian
--
Florian Rampp, Software Architect
Phone: +49.89.45 23 47-64
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Freitag, 17. Dezember 2010 13:12
So I can't see a difference to my test, expecting
version${project.version}/version
I've used
version${parent.version}/version
Can't imagine, that that is a difference, but who knows!
Fredy
project xmlns=http://maven.apache.org/POM/4.0.0;