I am working on a basic Tuscany SCA app and as such have 3 separate
components dependent on each other.

The main webapp: qmAppSCA has a dependency on qmController.
qmController has a dependency on domainBCA - all of them versioned on:
1.0-SNAPSHOT.

So accordingly I have 3 separate project directories and such and when I do
a clean install everything works fine.
This is quite a basic app and I have been building it to learn Tuscany SCA.

It has been working fine in loading up and connecting to Oracle and ll and
there has been no issues in the last 2 months I have been working on it.

Now suddenly (and I mean it just started a week ago) when I build  - in the
webapp: qmAppSCA.war there are two jars of the qmController. One is just
qmController.jar and the other: qmController-1.0-SNAPSHOT.jar.

There is only one version of the domainBCA - which is the SNAPSHOT version:
domainBCA-1.0-SNAPSHOT.jar.

The two versions of the qmController is causing conflicts on loading in
Jetty.

But I am perplexed as to why suddenly I have 2 versions of the qmController
as there has been no changes to the maven file and the dependencies are
quite simple and I do not find any problem.

I am running in Ubuntu 11.04 in:
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1)
OpenJDK Client VM (build 20.0-b11, mixed mode, sharing)
and have also been on AIX 64 - same issues.

As a result of the two qmControllers I get a duplicate component exception
when loading up in Jetty.

I would really appreciate your help in resolving this - again I had not made
any changes to the maven files and it seems this has suddenly started.

If you need to see the 3 maven files for the 3 apps (components) I am happy
to attach them.

Thanks.


--
View this message in context: 
http://maven.40175.n5.nabble.com/Multiple-versions-of-jars-in-war-tp4504999p4504999.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to