Sun, 26 Jun 2011 16:00:35 +0300, /Stanimir Stamenkov/:
O.k. I've tried with my own EJB module and I've found I have to
specify <type>ejb</type> for the dependency to get automatically
included as EJB module in the EAR. So the attached "pom.xml" appears
to build as expected.
However I seem to get problem when "jboss-seam" is declared in
<dependencyManagement> in a parent POM.
[...]
Specifying the "jboss-seam" version additionally in the EAR POM
seems to fix the things, but why one has to do it given the version
is specified in the parent POM?
So, as far as I've been able to find out, I have to declare
<type>ejb</type> in the <dependencyManagement> of the parent POM and
in every child POM I refer to the given dependency. This appears
mentioned in "Introduction to the Dependency Mechanism - Dependency
Management"
<http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Management>:
NOTE: In two of these dependency references, we had to specify the
<type/> element. This is because the minimal set of information for
matching a dependency reference against a dependencyManagement
section is actually {groupId, artifactId, type, classifier}...
This makes me wonder how Maven distinguish between "ejb" and "jar"
types (they are both packaged as JARs)?
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
