On 5/5/10 15:41, Guo Du wrote:
On Wed, May 5, 2010 at 7:19 PM, Richard S. Hall<he...@ungoverned.org> wrote:
artifactId to "groupId.subproject", which means our JARs names are fully
qualified. So for us, artifactId (or JAR name) is all you need to know.
Didn't know this. It's very good practice in the world of OSGi bundles.
For this case, the sub project has it's own groupId make sense:
org.apache.felix.gogo.foo.X.Y.Z.jar is better than
org.apache.felix.foo.X.Y.Z.jar IMO.
Perhaps I didn't explain it very well. Our groupId has always been
org.apache.felix, which is our package root. Our subprojects all get a
package name under this root. All artifactIds are their fully qualified
root.
So, for example, iPOJO's groupId is org.apache.felix, but the iPOJO arch
module's artifactId is org.apache.felix.ipojo.arch. Likewise, all iPOJO
modules start with org.apache.felix.ipojo, even though their groupId is
org.apache.felix.
-> richard
-Guo
