Maven and the -all.jars

[hubaer]

Hi all,

we are starting to run the embedded JBoss for our tests. Our project is a maven2 project, so we can use the artifact from the JBoss repository to add the dependencies from the embedded libraries.

So far so good.
The problem of using the embedded JBoss effiently are the all-jars. Because they contains all neccessary classes to run the embedded JBoss you running easily into duplicated classes problems, if you have other dependencies which contains the original implementations, which you need for the deployment of your application in an productive environment.

Are there any plans to split the -all.jar into their corresponding jar-dependencies and only refer to them in the -all.poms? It would make it much easier to work with the emebbed in JBoss in a maven project.

Regards
Marco

[spalazzi]

Hi Marco, i have the same problem.

Stefano

[hamtho2]

Same here! Would be great, if there will be a solution to this problem soon.

Thomas

[hubaer]

As I saw Stefanos and Thomas replies I think it is important to split this jars.
Therefore I am planing to split them (or try to split them), but it would be good it some of the JBoss guys could give me some advice to that.

First off all: Is there a reason, why the jboss embedded have this all-jars in the maven envirnoment? If not than ...

1. Is there a documentation which libraries (with their version) are included in the all-jars? It would be easier as to unpack the jar and discover the manifest etc...

2. How could I commit/contribute the modified pom into the repository? If there are important dependencies to the current pom it would also be good if we could create a subproject or so.

Thanks for your answers,

Marco

[hubaer]

Found today the following JIRA entry
http://jira.jboss.com/jira/browse/EMB-12

Hope the mavenized process is finished soon.

[skajotde]

"hubaer" wrote:
Found today the following JIRA entry
http://jira.jboss.com/jira/browse/EMB-12

Hope the mavenized process is finished soon.

+1 ;)

[skajotde]

Mavenize is really important. In my project is 150 pom.xml and I'm trying run test in Jboss Embedded but it is realy hard with jboss-embedded*-all style packing and maven Unflexible transitive depednencies. Will I must exclude 15 jars from 10 projects, it's ends with 200 entries in pom file ;/

[skajotde]

"skajotde" wrote:
Mavenize is really important. In my project is 150 pom.xml and I'm trying run test in Jboss Embedded but it is realy hard with jboss-embedded*-all style packing and maven Unflexible transitive depednencies. Will I must exclude 15 jars from 10 projects, it's ends with 200 entries in pom file ;/

Maven 2.0.9 correct order classpath and I simply put jboss embedded dependencies first without that many excludes and compilation is ok.

[johanmicoud]

Have the same problem.
I found a trick by isolating main embedded project and putting jboss-client in other project's classpath.
But we still have some CL problems...

+1

[skajotde]

"johanmicoud" wrote:
Have the same problem.
I found a trick by isolating main embedded project and putting jboss-client in other project's classpath.
But we still have some CL problems...

+1

When execute maven with debug you can see classpath ;) all embedded jar should be on first. Look that *direct* dependenciec are first in maven classparh order and dependiences from parent module or profile depencies can disturb that order.

[rickcr]

I'm sort of new to Maven2... what dependencies do I want to use the embedded JBoss? I'm confused what to even include. There are a lot of jboss entries in the repo:

http://www.mvnrepository.com/search.html?query=jboss

I'm not sure which ones I should declare poms for.

I'm actually deploying to JBoss5 and it's working correctly right now without declaring any jboss dependencies for the build, so shouldn't I just need a couple of JBoss dependencies for testing with the scope 'test' and everything should be fine? Why would I run into classpath issues in that case using scope test?