[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Checking in Eclipse project files into Remoting 3 reposi

[trustin]

In Maven 2, there's only one artifact for one module.  Actually having an artifact assembled from more than one module causes some complication in dependency reolution.

For example, let's assume that module A produces artifact A, module B produces artifact B and artifact C is assembled from the artifact A and B.  In this case, if project X depends on artifact C, project Y depends on artifact A and project Z depends on artifact X and Y, there's no easy way for Maven to figure out artifact C includes artifact A.  If project X depended on artifact A & B, dependency resolution will be easier.  (Uh... poor English, eh? ;)

I was obnoxious about this restriction at the first time Maven 2 was released, but I found it is pretty good restriction that reduces the confusion about the relationship between artifacts and modules.

Anyway, it doesn't mean that you cannot create an artifact of artifacts (e.g. artifact C) with Maven assembly plugin, which is often used to generate a tarball distribution and all-in-one JAR.

I believe I can mavenize Remoting 3 within a couple days.  Then you can simply type 'mvn package' to build all artifacts and the build shouldn't break at all, hopefully not slowing us down very much.   WDYT?  ;)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142827#4142827

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142827