Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-beta-10
-
Fix Version/s: 1.0-beta-10
-
Component/s: core
-
Labels:None
Description
Hi Folks,
I'm using beta-9 sucessfully. A minor problem leads me to a new question:
How does maven assebles maven.depedency.classpath?
For instance the following dependencies won't work with java:compile:
<dependency>
<id>jPortal-ejb</id>
<version/>
<type>ejb</type>
<jar>jPortal-ejb-0.6.1.jar</jar>
</dependency>
<dependency>
<id>jPortal-security</id>
<version/>
<type>ejb</type>
<jar>jPortal-security-0.1.5.jar</jar>
</dependency>
It seems that java:compile will take care only on assemblies under jar/ and
not under the type you mave configure.
This coulde be very usefull if you try to assemble a modular enterprise
application. Or is this against a strategy the maven.dependecy.classpath
follows?
Thx
Toby
Issue Links
- is depended upon by
-
MAVEN-401
Release maven-b10
-
jar and ejb types are added to the dependency classpath now