RE: dependencies problem
you can run the dependency plugin http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Fri, 6 Nov 2009 10:13:00 +0800 Subject: dependencies problem From: apachemav...@gmail.com To: users@maven.apache.org Hi:1>I want to know can there be more than one dependency declaration in a pom file? Since I got the error in the eclipse console: dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique... 2> I want to know the project organization in eclipse:If I create a maven project and add some modules the parent project and module projects are separate(see annex s.jpg) however I have down another maven project from svn and the modules are included in the parent project(see svn.jpg)? I wonder why? _ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/
dependencies problem
Hi: 1>I want to know can there be more than one dependency declaration in a pom file? Since I got the error in the eclipse console: *dependencies*.*dependency*.(groupId:artifactId:type:classifier)' *must be unique...* 2> I want to know the project organization in eclipse: If I create a maven project and add some modules the parent project and module projects are separate(see annex s.jpg) however I have down another maven project from svn and the modules are included in the parent project(see svn.jpg)? I wonder why? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: unpack-dependencies problem
Actually the problem seemed to be related to my repository. Not sure what was messed up, but I started fresh and I didn't specify a maven-dependency-plugin version (i.e. 2.0). Instead it got 2.0-alpha-4. All works better now, not sure what the changes are though. -- View this message in context: http://www.nabble.com/unpack-dependencies-problem-tp18891876p18894401.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]
Re: unpack-dependencies problem
If you are using m2eclipse, you may want to try to install Maven 2.0.9 and set Maven runtime in Eclipse to use external Maven pointing to 2.0.9 installation. regards, Eugene anoweb wrote: > > If I run this from eclipse (i.e. Run As -> Maven test) I get the following > output: > > Maven encountered an error while looking up the following Mojo: > Group-Id: org.apache.maven.plugins > Artifact-Id: maven-dependency-plugin > Version: 2.0 > Mojo: unpack-dependencies > brought in via: POM > > Referenced from project: > Group-Id: com.acme > Artifact-Id: web > Version: 1.0 > From file: C:\dev\web\pom.xml > Reason: Unable to lookup component 'org.apache.maven.plugin.Mojo', it > could not be created. > role: org.apache.maven.plugin.Mojo > roleHint: > org.apache.maven.plugins:maven-dependency-plugin:2.0:unpack-dependencies > classRealm: > /plugins/org.apache.maven.plugins:maven-dependency-plugin:[EMAIL > PROTECTED]/thread:main > > Root cause: org.codehaus.plexus.archiver.ArchiverException > -- View this message in context: http://www.nabble.com/unpack-dependencies-problem-tp18891876p18894332.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]
Re: unpack-dependencies problem
If I run this from eclipse (i.e. Run As -> Maven test) I get the following output: Maven encountered an error while looking up the following Mojo: Group-Id: org.apache.maven.plugins Artifact-Id: maven-dependency-plugin Version: 2.0 Mojo: unpack-dependencies brought in via: POM Referenced from project: Group-Id: com.acme Artifact-Id: web Version: 1.0 >From file: C:\dev\web\pom.xml Reason: Unable to lookup component 'org.apache.maven.plugin.Mojo', it could not be created. role: org.apache.maven.plugin.Mojo roleHint: org.apache.maven.plugins:maven-dependency-plugin:2.0:unpack-dependencies classRealm: /plugins/org.apache.maven.plugins:maven-dependency-plugin:[EMAIL PROTECTED]/thread:main Root cause: org.codehaus.plexus.archiver.ArchiverException -- View this message in context: http://www.nabble.com/unpack-dependencies-problem-tp18891876p18892175.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]
Re: unpack-dependencies problem
sorry the XML got messaged up during posting, here it is again (the snippet
from my pom.xml):
org.apache.maven.plugins
maven-dependency-plugin
unpack-config
unpack-dependencies
generate-resources
${project.build.directory}/${project.build.finalName}/WEB-INF/flex
config
${project.groupId}
resources
true
jar
copy-swf
process-classes
copy-dependencies
${project.build.directory}/${project.build.finalName}
swf
...
...
${project.groupId}
ria
1.0
swf
${project.groupId}
config
1.0
resources
zip
provided
--
View this message in context:
http://www.nabble.com/unpack-dependencies-problem-tp18891876p18891898.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]
unpack-dependencies problem
maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:m aven-dependency-plugin:2.0:unpack-dependencies' in the plugin 'org.apache.maven.plugins:maven-dependency-plugi n' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup compo nent 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-dependency-plugin:2.0:unpack-dependencies', i t could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609) ... 18 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate compon ent: role: 'null', implementation: 'org.apache.maven.plugin.dependency.UnpackDependenciesMojo' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory. java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.ja va:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464 ) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComp onentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentMana ger.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) ... 20 more Caused by: java.lang.NoClassDefFoundError: org/codehaus/plexus/archiver/ArchiverException at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) at java.lang.Class.newInstance(Class.java:308) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.ja va:44) ... 24 more Caused by: java.lang.ClassNotFoundException: org.codehaus.plexus.archiver.ArchiverException at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 30 more I do have C:\...\.m2\repository\org\apache\maven\plugins\maven-dependency-plugin\2.0. This is using maven 2.0.9 (if that matters). -- View this message in context: http://www.nabble.com/unpack-dependencies-problem-tp18891876p18891876.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Inherit dependencies problem
Hi, Maybe this is just a "copy and paste" error but the end tag is missing. Julien Simon.
Inherit dependencies problem
Hi, We have been using maven 2 ( 2.0.8 )for a while with love and hate :-) And now we want to make our child pom.xml:s a bit cleaner in terms of dependencies. We have the following structure in Eclipse 3.3.0: src | |---services | | | |---alarm | | | |pom.xml (child) | |--pom.xml (master) In my master POM I have the following: junit junit 4.4 test org.jmock jmock-junit4 2.4.0 test sailfin javaee 0.22 provided services/alarm In my child POM I have the following: com.mycompany.project dtx 1 ../../pom.xml When I run 'mvn clean install' from the command line maven complains that it cannot find the dependencies in my master pom. Any ideas what I am doing wrong. By the way everything has been working fine until I tried this. cheers, //mike
Re: can maven solve circle dependencies problem in multiple module projects
You should program against interfaces and then you can create a module containing the interfaces and one containing the classes. The dependencies will be from a class module to several source modules. On Jan 24, 2008 5:02 PM, Guillaume Lederrey <[EMAIL PROTECTED]> wrote: > Usually, if you have circular dependencies only at the module level, > you either have classes packaged in the wrong module or you need to > create one more module. If you have class level circular dependency > (class A depends on class B which depends on class C which depends on > class A), then you'll have to do some heavy refactoring ... > > It's hard to give you a generic answer without knowing exactly why you > have circular dep, and what's their meaning ... > > Good luck ! I'm in the same hell as you for the moment ... > > On 24/01/2008, Rex Huang <[EMAIL PROTECTED]> wrote: > > I see, but some times circle dependence is not easy to cut. > > so we had to find out how to solve this problem. > > Is there any ideas to do it? > > > > Rex > > > > On Jan 24, 2008 3:48 PM, Rémy Sanlaville <[EMAIL PROTECTED]> > wrote: > > > > > Hi, > > > > > > Cyclic dependence is not allowed with maven (it's a good practice). > > > You have to cut your cyclic dependence. > > > > > > Rémy > > > > > > > > -- > Jabber : [EMAIL PROTECTED] > Skype : Guillaume.Lederrey > Projects : > * http://rwanda.wordpress.com/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: can maven solve circle dependencies problem in multiple module projects
Usually, if you have circular dependencies only at the module level, you either have classes packaged in the wrong module or you need to create one more module. If you have class level circular dependency (class A depends on class B which depends on class C which depends on class A), then you'll have to do some heavy refactoring ... It's hard to give you a generic answer without knowing exactly why you have circular dep, and what's their meaning ... Good luck ! I'm in the same hell as you for the moment ... On 24/01/2008, Rex Huang <[EMAIL PROTECTED]> wrote: > I see, but some times circle dependence is not easy to cut. > so we had to find out how to solve this problem. > Is there any ideas to do it? > > Rex > > On Jan 24, 2008 3:48 PM, Rémy Sanlaville <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Cyclic dependence is not allowed with maven (it's a good practice). > > You have to cut your cyclic dependence. > > > > Rémy > > > -- Jabber : [EMAIL PROTECTED] Skype : Guillaume.Lederrey Projects : * http://rwanda.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: can maven solve circle dependencies problem in multiple module projects
I see, but some times circle dependence is not easy to cut. so we had to find out how to solve this problem. Is there any ideas to do it? Rex On Jan 24, 2008 3:48 PM, Rémy Sanlaville <[EMAIL PROTECTED]> wrote: > Hi, > > Cyclic dependence is not allowed with maven (it's a good practice). > You have to cut your cyclic dependence. > > Rémy >
Re: can maven solve circle dependencies problem in multiple module projects
Hi, Cyclic dependence is not allowed with maven (it's a good practice). You have to cut your cyclic dependence. Rémy
can maven solve circle dependencies problem in multiple module projects
there are three modules A, B, C A depends on B, B depends on C, C depends on A To solve this problem, we can make one module use the old version build. In maven, even I make one module dependency in old version build, it still cause error. [ERROR] BUILD FAILURE [INFO] The projects in the reactor contain a cyclic reference Can we solve this problem? BR//Rex
can maven solve circle dependencies problem in multiple module projects
there are three modules A, B, C A depends on B, B depends on C, C depends on A To solve this problem, we can make one module use the old version build. In maven, even I make one module dependency in old version build, it still cause error. [ERROR] BUILD FAILURE [INFO] The projects in the reactor contain a cyclic reference Can we solve this problem? BR//Rex
Re: [M2] EJB JAR + client JAR + EAR transitive dependencies problem
Hi, Indeed I use Xdoclet to generate EJB interfaces and hibernate mapping files. thanks for your time -- View this message in context: http://www.nabble.com/-M2--EJB-JAR-%2B-client-JAR-%2B-EAR-transitive-dependencies-problem-t1760618.html#a4789953 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] EJB JAR + client JAR + EAR transitive dependencies problem
Hi, I have a setup similar to yours. I have split the ejb project in two projects my_ejb_client (jar) and my_ejb_impl (ejb) And then just declare the ejb_client as a dependency in both, ejb_impl and the client project. So the client is totaly decoupled from the ejb implementation. That said. This is with EJB 3.0. If you use EJB < 3.0 and generate a lot of code with xdoclet this setup probably won't work for you. -Tim ozeebee schrieb: Hi, Once again I need your advices and support for a problem I'm locked in :) This time it relates to transtitive dependencies in an EJB+CLIENT+EAR context. I have 3 projects: - Project A --> EJB JAR project which generates 2 artifacts : the ejb JAR and the ejb-client JAR - Project B --> EAR project which depends on ProjectA : it simply creates the EAR for Project A - Project C --> simple JAR client which depends on Project A's ejb-client JAR Ok, pretty classical case. Now, my EJB project (A) has many dependencies: on the spring, hibernate and other libs. I don't want my client (C) to depend on these libraries because of transitive dependencies. Thus I have put these dependencies as in my EJB project (A). The problem is: because of that, my EAR project (B) does not bundle these libraries in my ear artifcat anymore which results in an incomplete EAR file !! What are the solution(s) for such a problem ? I can 'duplicate' my dependencies in the EAR project (B) ==> heavy to maintain: each time I add a library I have to add the dependency in A and B. Is there any 'clean' solution to this issue ? (I want the libs in my EJB project, in my EAR but not in my client) Thanks in advance. Greets, Ozeebee. -- View this message in context: http://www.nabble.com/-M2--EJB-JAR-%2B-client-JAR-%2B-EAR-transitive-dependencies-problem-t1760618.html#a4789568 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] EJB JAR + client JAR + EAR transitive dependencies problem
Hi, Once again I need your advices and support for a problem I'm locked in :) This time it relates to transtitive dependencies in an EJB+CLIENT+EAR context. I have 3 projects: - Project A --> EJB JAR project which generates 2 artifacts : the ejb JAR and the ejb-client JAR - Project B --> EAR project which depends on ProjectA : it simply creates the EAR for Project A - Project C --> simple JAR client which depends on Project A's ejb-client JAR Ok, pretty classical case. Now, my EJB project (A) has many dependencies: on the spring, hibernate and other libs. I don't want my client (C) to depend on these libraries because of transitive dependencies. Thus I have put these dependencies as in my EJB project (A). The problem is: because of that, my EAR project (B) does not bundle these libraries in my ear artifcat anymore which results in an incomplete EAR file !! What are the solution(s) for such a problem ? I can 'duplicate' my dependencies in the EAR project (B) ==> heavy to maintain: each time I add a library I have to add the dependency in A and B. Is there any 'clean' solution to this issue ? (I want the libs in my EJB project, in my EAR but not in my client) Thanks in advance. Greets, Ozeebee. -- View this message in context: http://www.nabble.com/-M2--EJB-JAR-%2B-client-JAR-%2B-EAR-transitive-dependencies-problem-t1760618.html#a4789568 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependencies problem
It is the role of the ejb.bundle property in the pom : jarid jarversion false Look at : http://maven.apache.org/reference/plugins/ejb/properties.html Nicolas, On Fri, 7 Jan 2005 02:04:24 -0800 (PST), Ravi Hegde <[EMAIL PROTECTED]> wrote: > I am building EJB component using Maven. Some xdoclet > related jars have to be added as dependencies for > building the EJB project. Strictly speaking, my EJB's > don't directly depend on these xdoclet jars - they are > needed just for code generation and nothing else. > Therefore, my strong feeling is that it is not a good > idea to add such jars as dependencies in POM. Is there > any other way to specify such dependencies ? (through > some classpath or property setting ?) > > Cheers :) > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependencies problem
I am building EJB component using Maven. Some xdoclet related jars have to be added as dependencies for building the EJB project. Strictly speaking, my EJB's don't directly depend on these xdoclet jars - they are needed just for code generation and nothing else. Therefore, my strong feeling is that it is not a good idea to add such jars as dependencies in POM. Is there any other way to specify such dependencies ? (through some classpath or property setting ?) Cheers :) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download dependencies problem...
On Wed, 2003-04-09 at 14:54, Cyriaque Dupoirieux wrote: > DO you know why maven cannot download the xsdlib-20020414.jar ? I had a similar problem a few days ago. www.ibiblio.com/maven/ seems to be broken for this jar! It's now gone magically, maybe some could check the RePo anyway please? Tnx -- Martin Skopp Riege Software International GmbH Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com This email is intended to be viewed with a nonproportional font. Public Key on http://www.keyserver.net, Key-ID: 3D4027B5 Fingerprint: 1970 C78D 9A1D 99FA 5CE4 5C0D 29E6 6A95 3D40 27B5 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
