Hi, I have created jira entry for this (https://issues.apache.org/jira/browse/ARIES-1101) and attached a patch. I put this to the Subsystem component because I couldn't find any component for the esa-maven-plugin.
Best regards Stephan From: Siano, Stephan [mailto:[email protected]] Sent: Mittwoch, 21. August 2013 10:48 To: [email protected] Subject: name of archived dependencies in esa-maven-plugin Hi, the esa-maven-plugin names artifacts bundled in an esa always [artifactId]-[version].[type], so a bundle with the maven corrdinates com.foo:bar:7.1.2:jar is named "bar-7.1.2.jar"in the bundle (see the coding below): zipArchiver.addFile(artifact.getFile(), artifact.getArtifactId() + "-" + artifact.getVersion() + "." + (artifact.getType() == null ? "jar" : artifact.getType())); Is there any reason for this? It might be better to use the bundle symbolic name or subsystem symbolic name or make this configurable. Just an example for the issue: Let us create two subsystems with the maven coordinates com.foo:baz:1.0.0:esa and com.bar:baz:1.0.0:esa. The esa-maven-plugin will generate the subsystem symbolic names com.foo.baz and com.bar.baz for it. If both are included (and stored) within a third subysystem with the same esa-maven-plugin, both are supposed to have the filename baz-1.0.0.esa. Best regards Stephan
