How to model dependency from Unit Test Source to a another Projects Source
Hello, I try to execute our unit tests with maven. The problem that I know get is a compilation failure (Cannot find class), when maven tries to compile the Unit Test souces in these sources we import a Class from another sub projects normal src Directory. So what I have is the following situation: Subproject project_a: I have Class name a1.java on the file System it looks like a/src/a1.java In Subproject project_b: I have another Classes and the Unit Tests: b/src/b1.java and also b/test/src.c1 In the class c1 I have a import to a1.java. When the test sources being compiled I get the compilation failure in Class c1 cannot filnd symbol a1. The dependency in the pom file in project b is modeled like this: dependencies dependency groupIdcom.xxx/groupId artifactIdaartifactId /ependency /dependencies So my question Is how do I have to model theses dependency in the pom. file so that the class a1 can be found ?? Must model the dependency additionaly in another Scope ? Thanks for your help. I really try to solve this problem since a while and I'm quite new to maven. Regards Richard Sailer
Re: How to model dependency from Unit Test Source to a another Projects Source
It should work as it is I believe (if the coordinates of project a are correct). Possible you just need to build the a project so that it is copied to the local repo by mvn install /Anders On Mon, Apr 18, 2011 at 09:02, Sailer, Richard richard.sai...@cassidian.com wrote: Hello, I try to execute our unit tests with maven. The problem that I know get is a compilation failure (Cannot find class), when maven tries to compile the Unit Test souces in these sources we import a Class from another sub projects normal src Directory. So what I have is the following situation: Subproject project_a: I have Class name a1.java on the file System it looks like a/src/a1.java In Subproject project_b: I have another Classes and the Unit Tests: b/src/b1.java and also b/test/src.c1 In the class c1 I have a import to a1.java. When the test sources being compiled I get the compilation failure in Class c1 cannot filnd symbol a1. The dependency in the pom file in project b is modeled like this: dependencies dependency groupIdcom.xxx/groupId artifactIdaartifactId /ependency /dependencies So my question Is how do I have to model theses dependency in the pom. file so that the class a1 can be found ?? Must model the dependency additionaly in another Scope ? Thanks for your help. I really try to solve this problem since a while and I'm quite new to maven. Regards Richard Sailer
AW: How to model dependency from Unit Test Source to a another Projects Source
Thanks for your reply. The project a is already a maven project and is installed in the mvn repo correctly because all the other sources from project b compiles correctly. Therefore it seems really strange to me. Richard -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 18. April 2011 10:34 An: Maven Users List Betreff: Re: How to model dependency from Unit Test Source to a another Projects Source It should work as it is I believe (if the coordinates of project a are correct). Possible you just need to build the a project so that it is copied to the local repo by mvn install /Anders On Mon, Apr 18, 2011 at 09:02, Sailer, Richard richard.sai...@cassidian.com wrote: Hello, I try to execute our unit tests with maven. The problem that I know get is a compilation failure (Cannot find class), when maven tries to compile the Unit Test souces in these sources we import a Class from another sub projects normal src Directory. So what I have is the following situation: Subproject project_a: I have Class name a1.java on the file System it looks like a/src/a1.java In Subproject project_b: I have another Classes and the Unit Tests: b/src/b1.java and also b/test/src.c1 In the class c1 I have a import to a1.java. When the test sources being compiled I get the compilation failure in Class c1 cannot filnd symbol a1. The dependency in the pom file in project b is modeled like this: dependencies dependency groupIdcom.xxx/groupId artifactIdaartifactId /ependency /dependencies So my question Is how do I have to model theses dependency in the pom. file so that the class a1 can be found ?? Must model the dependency additionaly in another Scope ? Thanks for your help. I really try to solve this problem since a while and I'm quite new to maven. Regards Richard Sailer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to model dependency from Unit Test Source to a another Projects Source
OK, then I guess it must be either the coordinates that are incorrect or the scope set to runtime. The runtime scope sounds unlikely to me. /Anders On Mon, Apr 18, 2011 at 11:13, Sailer, Richard richard.sai...@cassidian.com wrote: Thanks for your reply. The project a is already a maven project and is installed in the mvn repo correctly because all the other sources from project b compiles correctly. Therefore it seems really strange to me. Richard -Ursprüngliche Nachricht- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Montag, 18. April 2011 10:34 An: Maven Users List Betreff: Re: How to model dependency from Unit Test Source to a another Projects Source It should work as it is I believe (if the coordinates of project a are correct). Possible you just need to build the a project so that it is copied to the local repo by mvn install /Anders On Mon, Apr 18, 2011 at 09:02, Sailer, Richard richard.sai...@cassidian.com wrote: Hello, I try to execute our unit tests with maven. The problem that I know get is a compilation failure (Cannot find class), when maven tries to compile the Unit Test souces in these sources we import a Class from another sub projects normal src Directory. So what I have is the following situation: Subproject project_a: I have Class name a1.java on the file System it looks like a/src/a1.java In Subproject project_b: I have another Classes and the Unit Tests: b/src/b1.java and also b/test/src.c1 In the class c1 I have a import to a1.java. When the test sources being compiled I get the compilation failure in Class c1 cannot filnd symbol a1. The dependency in the pom file in project b is modeled like this: dependencies dependency groupIdcom.xxx/groupId artifactIdaartifactId /ependency /dependencies So my question Is how do I have to model theses dependency in the pom. file so that the class a1 can be found ?? Must model the dependency additionaly in another Scope ? Thanks for your help. I really try to solve this problem since a while and I'm quite new to maven. Regards Richard Sailer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven with clearcase integration
Hi, I am new Maven; I have integrate Maven with Clearcase. Clearcase version: 7.1.1 UCM version. Ie creating dynamic view on shared location. Please let me know the steps to integrate Maven with Clearcase. Thanks Kasim DISCLAIMER http://www.belgacom.be/maildisclaimer
SVN can not revert - VISTA can not copy it
If I would be a maven developer I would make this path a bit more longer to really see others go into problems as well as I do on my Vista PC; Error restoring text for 'E:\asf\maven\maven-3\nb_trunk\maven-embedder\src\test\error-reporting-p rojects\ext-plugin-artifact-missing\local-repo\org\apache\maven\errortes t\ext-plugin-artifact-missing-maven-plugin\1\ext-plugin-artifact-missing -maven-plugin-1.pom' AIt looks to me as this was never said long ago by many other developers. :-( I toke maven down using SVN checkout to a trunk, then I tried to just copy it to a different directory and VISTA faild because the path is just too long. Josef :-(
Re: SVN can not revert - VISTA can not copy it
Hello, maybe try : svn revert E:\asf\maven\maven-3\nb_trunk HTH, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/4/18 Stadelmann Josef josef.stadelm...@axa-winterthur.ch: If I would be a maven developer I would make this path a bit more longer to really see others go into problems as well as I do on my Vista PC; Error restoring text for 'E:\asf\maven\maven-3\nb_trunk\maven-embedder\src\test\error-reporting-p rojects\ext-plugin-artifact-missing\local-repo\org\apache\maven\errortes t\ext-plugin-artifact-missing-maven-plugin\1\ext-plugin-artifact-missing -maven-plugin-1.pom' AIt looks to me as this was never said long ago by many other developers. :-( I toke maven down using SVN checkout to a trunk, then I tried to just copy it to a different directory and VISTA faild because the path is just too long. Josef :-( - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using classifiers, missing artifact
Hello to the Maven users,
I have an issue with Maven and a missing artifact, that in fact is on
our local Maven repository
$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-09 00:58:10+)
Java version: 1.6.0_21, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
$mvn dependency:analyze
[ERROR] Failed to execute goal on project corba-test-bench: Could not
resolve dependencies for project
uk.co.mycompany.corba.test.bench:corba-test-bench:jar:1.0.0-SNAPSHOT:
The following artifacts could not be resolved:
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT,
uk.co.mycompany.corba:igtypes:jar:jacorb:1.0.6-SNAPSHOT: Could not
find artifact
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-20110418.093031-6
in nexus.ig.snapshot.repo
(http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot)
- [Help 1]
At my company, we use the following repository:
Sonatype Nexus Open Source Edition, Version: 1.8.0
If I open my browser at the url
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot/uk/co/mycompany/corba/common-corba-v3/3.0.10-SNAPSHOT/
I can see these files:
common-corba-v3-3.0.10-20110418.084702-1.pom
common-corba-v3-3.0.10-20110418.084702-1.pom.md5
common-corba-v3-3.0.10-20110418.084702-1.pom.sha1
common-corba-v3-3.0.10-20110418.084731-2.pom
common-corba-v3-3.0.10-20110418.084731-2.pom.md5
common-corba-v3-3.0.10-20110418.084731-2.pom.sha1
common-corba-v3-3.0.10-20110418.090905-3.pom
common-corba-v3-3.0.10-20110418.090905-3.pom.md5
common-corba-v3-3.0.10-20110418.090905-3.pom.sha1
common-corba-v3-3.0.10-20110418.090951-4.pom
common-corba-v3-3.0.10-20110418.090951-4.pom.md5
common-corba-v3-3.0.10-20110418.090951-4.pom.sha1
common-corba-v3-3.0.10-20110418.092902-5.pom
common-corba-v3-3.0.10-20110418.092902-5.pom.md5
common-corba-v3-3.0.10-20110418.092902-5.pom.sha1
common-corba-v3-3.0.10-20110418.093031-6.pom
common-corba-v3-3.0.10-20110418.093031-6.pom.md5
common-corba-v3-3.0.10-20110418.093031-6.pom.sha1
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.sha1
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.sha1
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1
The metadata file is
metadata
groupIduk.co.mycompany.corba/groupId
artifactIdcommon-corba-v3/artifactId
version3.0.10-SNAPSHOT/version
versioning
snapshot
timestamp20110418.093031/timestamp
buildNumber6/buildNumber
/snapshot
lastUpdated20110418093046/lastUpdated
/versioning
style /
/metadata
The artifact common-corba-v3 is built and deployedusing the following
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
classifier${envClassifier}/classifier
/configuration
/plugin
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.5/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.3/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
/plugins
where ${envClassifier} can be sunorb or jacorb. The build fail also if
I uncomment the configuration in the install and deploy plugins.
This is not the only artfact that cannot be resolved, despite it's
there, on the repository. I can download it on my hard drive.
I have tried all Maven version from 2.2.0 to 3.0.2
The thing hat baffles me is that the build, sometimes succeeed, but
most of the time it fails.
I have tried to fix this since weeks, when it looks fine, suddenly the
problems re-arise. I cannot find much help googling.
Please, can you help me?
Many thanks
--
Claves do Amaral
Email: claves.doama...@gmail.com
LinkedIn: http://www.linkedin.com/pub/claves-do-amaral/a/b3b/1a9
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven eclipse plugin
Hi all, I am trying to set up code styles, work space and so on, but it doesn't work. Does anybody know if maven plug in eclipse is working for these kind of set up? I am using eclipse helios thanks in advance
Re: Using classifiers, missing artifact
The jar is not in your repo.
Only the POM
Ron
On 18/04/2011 9:20 AM, Claves do Amaral wrote:
Hello to the Maven users,
I have an issue with Maven and a missing artifact, that in fact is on
our local Maven repository
$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-09 00:58:10+)
Java version: 1.6.0_21, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
$mvn dependency:analyze
[ERROR] Failed to execute goal on project corba-test-bench: Could not
resolve dependencies for project
uk.co.mycompany.corba.test.bench:corba-test-bench:jar:1.0.0-SNAPSHOT:
The following artifacts could not be resolved:
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT,
uk.co.mycompany.corba:igtypes:jar:jacorb:1.0.6-SNAPSHOT: Could not
find artifact
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-20110418.093031-6
in nexus.ig.snapshot.repo
(http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot)
- [Help 1]
At my company, we use the following repository:
Sonatype Nexus Open Source Edition, Version: 1.8.0
If I open my browser at the url
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot/uk/co/mycompany/corba/common-corba-v3/3.0.10-SNAPSHOT/
I can see these files:
common-corba-v3-3.0.10-20110418.084702-1.pom
common-corba-v3-3.0.10-20110418.084702-1.pom.md5
common-corba-v3-3.0.10-20110418.084702-1.pom.sha1
common-corba-v3-3.0.10-20110418.084731-2.pom
common-corba-v3-3.0.10-20110418.084731-2.pom.md5
common-corba-v3-3.0.10-20110418.084731-2.pom.sha1
common-corba-v3-3.0.10-20110418.090905-3.pom
common-corba-v3-3.0.10-20110418.090905-3.pom.md5
common-corba-v3-3.0.10-20110418.090905-3.pom.sha1
common-corba-v3-3.0.10-20110418.090951-4.pom
common-corba-v3-3.0.10-20110418.090951-4.pom.md5
common-corba-v3-3.0.10-20110418.090951-4.pom.sha1
common-corba-v3-3.0.10-20110418.092902-5.pom
common-corba-v3-3.0.10-20110418.092902-5.pom.md5
common-corba-v3-3.0.10-20110418.092902-5.pom.sha1
common-corba-v3-3.0.10-20110418.093031-6.pom
common-corba-v3-3.0.10-20110418.093031-6.pom.md5
common-corba-v3-3.0.10-20110418.093031-6.pom.sha1
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.sha1
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.sha1
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1
The metadata file is
metadata
groupIduk.co.mycompany.corba/groupId
artifactIdcommon-corba-v3/artifactId
version3.0.10-SNAPSHOT/version
versioning
snapshot
timestamp20110418.093031/timestamp
buildNumber6/buildNumber
/snapshot
lastUpdated20110418093046/lastUpdated
/versioning
style /
/metadata
The artifact common-corba-v3 is built and deployedusing the following
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
classifier${envClassifier}/classifier
/configuration
/plugin
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.5/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.3/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
/plugins
where ${envClassifier} can be sunorb or jacorb. The build fail also if
I uncomment theconfiguration in the install and deploy plugins.
This is not the only artfact that cannot be resolved, despite it's
there, on the repository. I can download it on my hard drive.
I have tried all Maven version from 2.2.0 to 3.0.2
The thing hat baffles me is that the build, sometimes succeeed, but
most of the time it fails.
I have tried to fix this since weeks, when it looks fine, suddenly the
problems re-arise. I cannot find much help googling.
Please, can you help me?
Many thanks
--
Claves do Amaral
Email: claves.doama...@gmail.com
LinkedIn: http://www.linkedin.com/pub/claves-do-amaral/a/b3b/1a9
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Maven ate my hard drive !
Hi all, Maven can eat up a lot of disk space... I'm sharing those two Bash scripts I use for freeing some space: https://github.com/nicoulaj/dotfiles/blob/master/bin/mvn-clean-projects - Looks for Maven projects in $HOME and does a mvn clean https://github.com/nicoulaj/dotfiles/blob/master/bin/mvn-clean-repository - Deletes artifacts that have not been used within the last 3 months from the local repository. Hopefully this will be useful to someone ! Regards, Julien
maven in 5 min not working
Hi, I have downloaded latest maven 3.0.3, java version 1.6.0_18. mvn –version *Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)* *Maven home: C:\software\apache-maven-3.0.3* *Java version: 1.5.0_05, vendor: Sun Microsystems Inc.* *Java home: C:\software\jdk1.5.0.15\jre* *Default locale: en_GB, platform encoding: Cp1252* *OS name: windows xp, version: 5.1, arch: x86, family: windows* * * *My application located at: *C:\Temp\ecm_esv\app\ENT_APP\ESV. I am getting following error message: * * C:\Temp\ecm_esv\app\ENT_APP\ESVmvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.4.1: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:2.3.1: Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.5/maven-deploy-plugin-2.5.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-deploy-plugin:2.5: Plugin org.apache.maven.plugins:maven-deploy-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-deploy-plugin:jar:2.5 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0.1/maven-site-plugin-2.0.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:2.0.1: Plugin org.apache.maven.plugins:maven-site-plugin:2.0.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-site-plugin:jar:2.0.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/2.2-beta-5/maven-assembly-plugin-2.2-beta-5.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.1/maven-dependency-plugin-2.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-dependency-plugin:2.1: Plugin org.apache.maven.plugins:maven-dependency-plugin:2.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-dependency-plugin:jar:2.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.0/maven-release-plugin-2.0.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-release-plugin:2.0: Plugin org.apache.maven.plugins:maven-release-plugin:2.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-release-plugin:jar:2.0 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central ( http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org [WARNING] Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo1.maven.org/maven2): Error transferring file: repo1.maven.org Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central ( http://repo1.maven.org/maven2):
Re: maven eclipse plugin
On 18/04/2011 10:18 AM, Fernando Wermus wrote: Hi all, I am trying to set up code styles, work space and so on, but it doesn't work. Does anybody know if maven plug in eclipse is working for these kind of set up? I am using eclipse helios thanks in advance You might want to move to the STS version of Eclipse. All the required Java development plug-ins are preloaded and the Maven integration works very well since M2 is built-in. We have used it for almost 2 years and is much easier to get started with STS than an out-of-the-box Eclipse since you just install and go (still need to add Subversion for licensing reasons but it is made easy) Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using classifiers, missing artifact
They are there, but with a non-unique snapshot version.
/Anders (mobile)
Den 18 apr 2011 16.25 skrev Ron Wheeler rwhee...@artifact-software.com:
The jar is not in your repo.
Only the POM
Ron
On 18/04/2011 9:20 AM, Claves do Amaral wrote:
Hello to the Maven users,
I have an issue with Maven and a missing artifact, that in fact is on
our local Maven repository
$ mvn -version
Apache Maven 3.0.2 (r1056850; 2011-01-09 00:58:10+)
Java version: 1.6.0_21, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_21\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
$mvn dependency:analyze
[ERROR] Failed to execute goal on project corba-test-bench: Could not
resolve dependencies for project
uk.co.mycompany.corba.test.bench:corba-test-bench:jar:1.0.0-SNAPSHOT:
The following artifacts could not be resolved:
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT,
uk.co.mycompany.corba:igtypes:jar:jacorb:1.0.6-SNAPSHOT: Could not
find artifact
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-20110418.093031-6
in nexus.ig.snapshot.repo
(
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot
)
- [Help 1]
At my company, we use the following repository:
Sonatype Nexus Open Source Edition, Version: 1.8.0
If I open my browser at the url
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot/uk/co/mycompany/corba/common-corba-v3/3.0.10-SNAPSHOT/
I can see these files:
common-corba-v3-3.0.10-20110418.084702-1.pom
common-corba-v3-3.0.10-20110418.084702-1.pom.md5
common-corba-v3-3.0.10-20110418.084702-1.pom.sha1
common-corba-v3-3.0.10-20110418.084731-2.pom
common-corba-v3-3.0.10-20110418.084731-2.pom.md5
common-corba-v3-3.0.10-20110418.084731-2.pom.sha1
common-corba-v3-3.0.10-20110418.090905-3.pom
common-corba-v3-3.0.10-20110418.090905-3.pom.md5
common-corba-v3-3.0.10-20110418.090905-3.pom.sha1
common-corba-v3-3.0.10-20110418.090951-4.pom
common-corba-v3-3.0.10-20110418.090951-4.pom.md5
common-corba-v3-3.0.10-20110418.090951-4.pom.sha1
common-corba-v3-3.0.10-20110418.092902-5.pom
common-corba-v3-3.0.10-20110418.092902-5.pom.md5
common-corba-v3-3.0.10-20110418.092902-5.pom.sha1
common-corba-v3-3.0.10-20110418.093031-6.pom
common-corba-v3-3.0.10-20110418.093031-6.pom.md5
common-corba-v3-3.0.10-20110418.093031-6.pom.sha1
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.sha1
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.sha1
maven-metadata.xml
maven-metadata.xml.md5
maven-metadata.xml.sha1
The metadata file is
metadata
groupIduk.co.mycompany.corba/groupId
artifactIdcommon-corba-v3/artifactId
version3.0.10-SNAPSHOT/version
versioning
snapshot
timestamp20110418.093031/timestamp
buildNumber6/buildNumber
/snapshot
lastUpdated20110418093046/lastUpdated
/versioning
style /
/metadata
The artifact common-corba-v3 is built and deployedusing the following
configuration
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
classifier${envClassifier}/classifier
/configuration
/plugin
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.5/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.3/version
!--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration --
/plugin
/plugins
where ${envClassifier} can be sunorb or jacorb. The build fail also if
I uncomment theconfiguration in the install and deploy plugins.
This is not the only artfact that cannot be resolved, despite it's
there, on the repository. I can download it on my hard drive.
I have tried all Maven version from 2.2.0 to 3.0.2
The thing hat baffles me is that the build, sometimes succeeed, but
most of the time it fails.
I have tried to fix this since weeks, when it looks fine, suddenly the
problems re-arise. I cannot find much help googling.
Please, can you help me?
Many thanks
--
Claves do Amaral
Email: claves.doama...@gmail.com
LinkedIn: http://www.linkedin.com/pub/claves-do-amaral/a/b3b/1a9
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven in 5 min not working
solved, it was my proxiy issue: new proxy setting is: proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. |-- proxy idoptional/id activetrue/active protocolhttp/protocol * hostwebproxy/host* port80/port nonProxyHostslocalhost|google.com/nonProxyHosts /proxy /proxies On Mon, Apr 18, 2011 at 4:31 PM, kasim ahmed mail2ka...@googlemail.comwrote: Hi, I have downloaded latest maven 3.0.3, java version 1.6.0_18. mvn –version *Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)* *Maven home: C:\software\apache-maven-3.0.3* *Java version: 1.5.0_05, vendor: Sun Microsystems Inc.* *Java home: C:\software\jdk1.5.0.15\jre* *Default locale: en_GB, platform encoding: Cp1252* *OS name: windows xp, version: 5.1, arch: x86, family: windows* * * *My application located at: *C:\Temp\ecm_esv\app\ENT_APP\ESV. I am getting following error message: * * C:\Temp\ecm_esv\app\ENT_APP\ESVmvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-clean-plugin:2.4.1: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-install-plugin:2.3.1: Plugin org.apache.maven.plugins:maven-install-plugin:2.3.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.3.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.5/maven-deploy-plugin-2.5.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-deploy-plugin:2.5: Plugin org.apache.maven.plugins:maven-deploy-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-deploy-plugin:jar:2.5 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0.1/maven-site-plugin-2.0.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:2.0.1: Plugin org.apache.maven.plugins:maven-site-plugin:2.0.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-site-plugin:jar:2.0.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-antrun-plugin:1.3: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-antrun-plugin:jar:1.3 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/2.2-beta-5/maven-assembly-plugin-2.2-beta-5.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5: Plugin org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-5 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.1/maven-dependency-plugin-2.1.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-dependency-plugin:2.1: Plugin org.apache.maven.plugins:maven-dependency-plugin:2.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-dependency-plugin:jar:2.1 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.0/maven-release-plugin-2.0.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-release-plugin:2.0: Plugin org.apache.maven.plugins:maven-release-plugin:2.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-release-plugin:jar:2.0 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml [WARNING] Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (
Enforcer banned dependencies... Not working ?
I was trying to centralize enforcer configuration to make use of banned dependencies, configured following in parent pom.xml: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0-beta-1/version executions execution idenforce-banned-dependencies-track-level/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludejunit/exclude /excludes includes includejunit:junit:3.8.1/include /includes /bannedDependencies Ànd inside the project which has above a parent, I did this: dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version /dependency /dependencies I would have expected that mvn validate will fail, as clearly version is among the banned ones But alas, it passes clean... trace below... Any ideas? Regards Pavel TRACE: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100) Java version: 1.5.0_16-rev Java home: /home/epasmir/bin/jdk/jre Default locale: en, platform encoding: ISO646-US OS name: sunos version: 5.10 arch: sparc Family: unix Skipped... [DEBUG] Configuring mojo org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1, parent: ClassRealm[maven.api, parent: null]] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce' with basic configurator -- [DEBUG] (s) fail = true [DEBUG] (s) failFast = false [DEBUG] (f) ignoreCache = false [DEBUG] (s) project = MavenProject: sample:item2:1.0-SNAPSHOT @ /home/epasmir/poc/reactor/item2/pom.xml [DEBUG] (s) searchTransitive = true [DEBUG] (s) excludes = [junit] [DEBUG] (s) includes = [junit:junit:3.8.1] [DEBUG] (f) message = Best Practice is to always define plugin versions! [DEBUG] (f) banLatest = true [DEBUG] (f) banRelease = true [DEBUG] (s) banSnapshots = true [DEBUG] (s) rules = [org.apache.maven.plugins.enforcer.BannedDependencies@110278e, org.apache.maven.plugins.enforcer.RequirePluginVersions@194e776] [DEBUG] (s) session = org.apache.maven.execution.MavenSession@1342545 [DEBUG] (s) skip = false [DEBUG] -- end configuration -- [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.BannedDependencies --- SHOULD HAVE failed here ?! [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.RequirePluginVersions (that's fine I guess) [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 9.203s [INFO] Finished at: Mon Apr 18 15:12:04 BST 2011 [INFO] Final Memory: 2M/5M [INFO]
Re: Enforcer banned dependencies... Not working ?
Did you read the output? The answer to why it doesn't check is stated there. /Anders (mobile) Den 18 apr 2011 16.56 skrev Pavel Smirnov D pavel.d.smir...@ericsson.com : I was trying to centralize enforcer configuration to make use of banned dependencies, configured following in parent pom.xml: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0-beta-1/version executions execution idenforce-banned-dependencies-track-level/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludejunit/exclude /excludes includes includejunit:junit:3.8.1/include /includes /bannedDependencies Ànd inside the project which has above a parent, I did this: dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version /dependency /dependencies I would have expected that mvn validate will fail, as clearly version is among the banned ones But alas, it passes clean... trace below... Any ideas? Regards Pavel TRACE: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100) Java version: 1.5.0_16-rev Java home: /home/epasmir/bin/jdk/jre Default locale: en, platform encoding: ISO646-US OS name: sunos version: 5.10 arch: sparc Family: unix Skipped... [DEBUG] Configuring mojo org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1, parent: ClassRealm[maven.api, parent: null]] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce' with basic configurator -- [DEBUG] (s) fail = true [DEBUG] (s) failFast = false [DEBUG] (f) ignoreCache = false [DEBUG] (s) project = MavenProject: sample:item2:1.0-SNAPSHOT @ /home/epasmir/poc/reactor/item2/pom.xml [DEBUG] (s) searchTransitive = true [DEBUG] (s) excludes = [junit] [DEBUG] (s) includes = [junit:junit:3.8.1] [DEBUG] (f) message = Best Practice is to always define plugin versions! [DEBUG] (f) banLatest = true [DEBUG] (f) banRelease = true [DEBUG] (s) banSnapshots = true [DEBUG] (s) rules = [org.apache.maven.plugins.enforcer.BannedDependencies@110278e, org.apache.maven.plugins.enforcer.RequirePluginVersions@194e776] [DEBUG] (s) session = org.apache.maven.execution.MavenSession@1342545 [DEBUG] (s) skip = false [DEBUG] -- end configuration -- [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.BannedDependencies --- SHOULD HAVE failed here ?! [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.RequirePluginVersions (that's fine I guess) [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 9.203s [INFO] Finished at: Mon Apr 18 15:12:04 BST 2011 [INFO] Final Memory: 2M/5M [INFO]
Re: Using classifiers, missing artifact
On 18 April 2011 15:44, Anders Hammar and...@hammar.net wrote: They are there, but with a non-unique snapshot version. /Anders (mobile) Den 18 apr 2011 16.25 skrev Ron Wheeler rwhee...@artifact-software.com: The jar is not in your repo. Only the POM Ron yes, the point is that his is a pattern that i noticed for all artifacts. The time-stamped version of the POM is produced at every build, and only one JAR is produced in each folder. I think that when an artifact is requested, the time stamp is used to return the correct jar version, even if I don't know the details. Anway, I have errors only for some artifacts Cheers, Claves - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using classifiers, missing artifact
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar is the same as
common-corba-v3-3.0.10-SNAPSHOT.jar???
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT is what
it wants.
common-corba-v3-3.0.10-20110418.xx-1.pom is just a POM
Ron
On 18/04/2011 10:44 AM, Anders Hammar wrote:
They are there, but with a non-unique snapshot version.
/Anders (mobile) Den 18 apr 2011 16.25 skrev Ron Wheeler
rwhee...@artifact-software.com:
The jar is not in your repo. Only the POM
Ron On 18/04/2011 9:20 AM, Claves do Amaral wrote:
Hello to the Maven users, I have an issue with Maven and a
missing artifact, that in fact is on our local Maven repository
$ mvn -version Apache Maven 3.0.2 (r1056850; 2011-01-09
00:58:10+) Java version: 1.6.0_21, vendor: Sun Microsystems
Inc. Java home: C:\Program Files\Java\jdk1.6.0_21\jre Default
locale: en_GB, platform encoding: Cp1252 OS name: windows 7,
version: 6.1, arch: amd64, family: windows
$mvn dependency:analyze
[ERROR] Failed to execute goal on project corba-test-bench: Could
not resolve dependencies for project
uk.co.mycompany.corba.test.bench:corba-test-bench:jar:1.0.0-SNAPSHOT:
The following artifacts could not be resolved:
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT,
uk.co.mycompany.corba:igtypes:jar:jacorb:1.0.6-SNAPSHOT: Could not
find artifact
uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-20110418.093031-6
in nexus.ig.snapshot.repo
(
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot
)
- [Help 1]
At my company, we use the following repository:
Sonatype Nexus Open Source Edition, Version: 1.8.0
If I open my browser at the url
http://maven-repo2.mygroup.local:8081/nexus/content/repositories/ig.snapshot/uk/co/mycompany/corba/common-corba-v3/3.0.10-SNAPSHOT/
I can see these files:
common-corba-v3-3.0.10-20110418.084702-1.pom
common-corba-v3-3.0.10-20110418.084702-1.pom.md5
common-corba-v3-3.0.10-20110418.084702-1.pom.sha1
common-corba-v3-3.0.10-20110418.084731-2.pom
common-corba-v3-3.0.10-20110418.084731-2.pom.md5
common-corba-v3-3.0.10-20110418.084731-2.pom.sha1
common-corba-v3-3.0.10-20110418.090905-3.pom
common-corba-v3-3.0.10-20110418.090905-3.pom.md5
common-corba-v3-3.0.10-20110418.090905-3.pom.sha1
common-corba-v3-3.0.10-20110418.090951-4.pom
common-corba-v3-3.0.10-20110418.090951-4.pom.md5
common-corba-v3-3.0.10-20110418.090951-4.pom.sha1
common-corba-v3-3.0.10-20110418.092902-5.pom
common-corba-v3-3.0.10-20110418.092902-5.pom.md5
common-corba-v3-3.0.10-20110418.092902-5.pom.sha1
common-corba-v3-3.0.10-20110418.093031-6.pom
common-corba-v3-3.0.10-20110418.093031-6.pom.md5
common-corba-v3-3.0.10-20110418.093031-6.pom.sha1
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar.sha1
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.md5
common-corba-v3-3.0.10-SNAPSHOT-sunorb.jar.sha1
maven-metadata.xml maven-metadata.xml.md5
maven-metadata.xml.sha1
The metadata file is
metadata groupIduk.co.mycompany.corba/groupId
artifactIdcommon-corba-v3/artifactId
version3.0.10-SNAPSHOT/version versioning snapshot
timestamp20110418.093031/timestamp
buildNumber6/buildNumber /snapshot
lastUpdated20110418093046/lastUpdated /versioning style
/ /metadata
The artifact common-corba-v3 is built and deployedusing the
following configuration
plugin groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId configuration
classifier${envClassifier}/classifier /configuration
/plugin
plugins plugin groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
version2.5/version !--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration -- /plugin plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-install-plugin/artifactId
version2.3/version !--configuration --
!--classifier${envClassifier}/classifier --
!--/configuration -- /plugin /plugins
where ${envClassifier} can be sunorb or jacorb. The build fail
also if I uncomment theconfiguration in the install and deploy
plugins. This is not the only artfact that cannot be resolved,
despite it's there, on the repository. I can download it on my
hard drive.
I have tried all Maven version from 2.2.0 to 3.0.2
The thing hat baffles me is that the build, sometimes succeeed,
but most of the time it fails.
I have tried to fix this since weeks, when it looks fine,
suddenly the problems re-arise. I cannot find much help
googling.
Please, can you help me?
Many thanks
-- Claves do Amaral
Email: claves.doama...@gmail.com LinkedIn:
http://www.linkedin.com/pub/claves-do-amaral/a/b3b/1a9
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
Re: Enforcer banned dependencies... Not working ?
The warning is talking about the plugin versions rule. Off hand nothing jumps out as being wrong with the config to me. It's been too long since I wrote this rule to recall off the top of my head how it's processed. Take a look at the code and see how includes, excludes are handled. There may be some short-circuit that is causing this. On Mon, Apr 18, 2011 at 11:00 AM, Anders Hammar and...@hammar.net wrote: Did you read the output? The answer to why it doesn't check is stated there. /Anders (mobile) Den 18 apr 2011 16.56 skrev Pavel Smirnov D pavel.d.smir...@ericsson.com : I was trying to centralize enforcer configuration to make use of banned dependencies, configured following in parent pom.xml: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0-beta-1/version executions execution idenforce-banned-dependencies-track-level/id goals goalenforce/goal /goals configuration rules bannedDependencies searchTransitivetrue/searchTransitive excludes excludejunit/exclude /excludes includes includejunit:junit:3.8.1/include /includes /bannedDependencies Ànd inside the project which has above a parent, I did this: dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.3.1/version /dependency /dependencies I would have expected that mvn validate will fail, as clearly version is among the banned ones But alas, it passes clean... trace below... Any ideas? Regards Pavel TRACE: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100) Java version: 1.5.0_16-rev Java home: /home/epasmir/bin/jdk/jre Default locale: en, platform encoding: ISO646-US OS name: sunos version: 5.10 arch: sparc Family: unix Skipped... [DEBUG] Configuring mojo org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce from plugin realm ClassRealm[pluginorg.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1, parent: ClassRealm[maven.api, parent: null]] [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce' with basic configurator -- [DEBUG] (s) fail = true [DEBUG] (s) failFast = false [DEBUG] (f) ignoreCache = false [DEBUG] (s) project = MavenProject: sample:item2:1.0-SNAPSHOT @ /home/epasmir/poc/reactor/item2/pom.xml [DEBUG] (s) searchTransitive = true [DEBUG] (s) excludes = [junit] [DEBUG] (s) includes = [junit:junit:3.8.1] [DEBUG] (f) message = Best Practice is to always define plugin versions! [DEBUG] (f) banLatest = true [DEBUG] (f) banRelease = true [DEBUG] (s) banSnapshots = true [DEBUG] (s) rules = [org.apache.maven.plugins.enforcer.BannedDependencies@110278e, org.apache.maven.plugins.enforcer.RequirePluginVersions@194e776] [DEBUG] (s) session = org.apache.maven.execution.MavenSession@1342545 [DEBUG] (s) skip = false [DEBUG] -- end configuration -- [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.BannedDependencies --- SHOULD HAVE failed here ?! [DEBUG] Executing rule: org.apache.maven.plugins.enforcer.RequirePluginVersions (that's fine I guess) [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 9.203s [INFO] Finished at: Mon Apr 18 15:12:04 BST 2011 [INFO] Final Memory: 2M/5M [INFO] - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using classifiers, missing artifact
On 18 April 2011 16:07, Ron Wheeler rwhee...@artifact-software.com wrote: common-corba-v3-3.0.10-SNAPSHOT-jacorb.jar is the same as common-corba-v3-3.0.10-SNAPSHOT.jar??? uk.co.mycompany.corba:common-corba-v3:jar:jacorb:3.0.10-SNAPSHOT is what it wants. common-corba-v3-3.0.10-20110418.xx-1.pom is just a POM Ron I am not sure how does the repository works. I am not managing it and the team who is managing it is not easily reachable, therefore, I cannot ask for help. I am trying to deploy an artifact that has only classifiers (jacorb and sunorb). There is not a principal artifact (only attached artifacts). I don't know about the internals of the repository, how the timestamp is generated, if it is generated only for the poms or for the jars also. I am looking for someone who can help me to get the answet. Cheers, Claves - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Arranging Modules on the File System
I apologize if this is a newbie question, but I'm looking for a quick answer... I'm using Sonatype Maven plug-in for Eclipse and I have set up a project with several modules. The way the plug-in arranged them on the file system is: eclipse-workspace/parent-project/.project eclipse-workspace/parent-project/pom.xml eclipse-workspace/parent-project/sub-project-1/.project eclipse-workspace/parent-project/sub-project-1/pom.xml eclipse-workspace/parent-project/sub-project-2/.project eclipse-workspace/parent-project/sub-project-2/pom.xml eclipse-workspace/parent-project/sub-project-3/.project eclipse-workspace/parent-project/sub-project-3/pom.xml The problem is that the IBM Rational Team Concert source control I am using chokes when I try to share and check in the parent-project because of the nesting. The sub-projects are fine. Can I just rearrange the file system so it looks like: eclipse-workspace/parent-project/.project eclipse-workspace/parent-project/pom.xml eclipse-workspace/sub-project-1/.project eclipse-workspace/sub-project-1/pom.xml eclipse-workspace/sub-project-2/.project eclipse-workspace/sub-project-2/pom.xml eclipse-workspace/sub-project-3/.project eclipse-workspace/sub-project-3/pom.xml It was not immediately apparent to me looking at the pom.xml or the Sonatype UI how to do this. The POM looks like modules modulesub-project-1/module modulesub-project-2/module modulesub-project-3/module /modules Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven eclipse plugin
On Mon, Apr 18, 2011 at 11:48 PM, Fernando Wermus fwer...@odeasrl.com.ar wrote: Hi all, I am trying to set up code styles, work space and so on, but it doesn't work. Does anybody know if maven plug in eclipse is working for these kind of set up? I am using eclipse helios If you are talking about m2e, this isn't the correct mailing list. If you are talking about maven-eclipse-plugin then: * Coding Styles: http://maven.apache.org/plugins/maven-eclipse-plugin/examples/load-code-styles.html * Checkstyle: http://maven.apache.org/plugins/maven-eclipse-plugin/examples/configure-checkstyle.html I put all this guff into your parent project's pom in build/pluginManagement so you dont have to specify it per project. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Arranging Modules on the File System
On Tue, Apr 19, 2011 at 8:17 AM, Eric Kolotyluk eric.koloty...@gmail.com wrote: I apologize if this is a newbie question, but I'm looking for a quick answer... I'm using Sonatype Maven plug-in for Eclipse and I have set up a project with several modules. The way the plug-in arranged them on the file system is: You may have better luck on the m2e mailing list, or ask the Team Concert lists how a hierarchical layout is supported. You may be able to use the guidance at http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html *Read this carefully* Especially Note, you have to delete the .project-file of your parent project before. You need to do this as the import step will produce a blank list of projects to import, but if you delete the .project file and try the sub-projects are now available in the list. Eclipse doesn't really support projects within projects so your mileage may vary, however a lot of us have this working ok. You can also try turning off Team support for the sub-projects and only uses the main project for checkin/checkout. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: SVN can not revert - VISTA can not copy it
On Mon, Apr 18, 2011 at 9:23 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: If I would be a maven developer I would make this path a bit more longer to really see others go into problems as well as I do on my Vista PC; Error restoring text for 'E:\asf\maven\maven-3\nb_trunk\maven-embedder\src\test\error-reporting-p rojects\ext-plugin-artifact-missing\local-repo\org\apache\maven\errortes t\ext-plugin-artifact-missing-maven-plugin\1\ext-plugin-artifact-missing -maven-plugin-1.pom' AIt looks to me as this was never said long ago by many other developers. :-( I toke maven down using SVN checkout to a trunk, then I tried to just copy it to a different directory and VISTA faild because the path is just too long. Yeah, sucks to use Microsoft. Recommend shortening the path. E:\m3 We have to do this with our eclipse development projects - they are a lot longer. Unfortunately at some point you run out of stuff that can be shortened and you are stuffed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: SVN can not revert - VISTA can not copy it
dir /AD /X 04/18/2011 08:49 PMDIR INSANE~1 Insane Long Folder Name to do anything useful with this folder you'll need reference either the full name e.g. rmdir Insane Long Folder Name or reference the shortened name e.g. rmdir INSANE~1 (or run maven in cygwin) Martin __ 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: Tue, 19 Apr 2011 10:11:11 +0930 Subject: Re: SVN can not revert - VISTA can not copy it From: baerr...@gmail.com To: users@maven.apache.org On Mon, Apr 18, 2011 at 9:23 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: If I would be a maven developer I would make this path a bit more longer to really see others go into problems as well as I do on my Vista PC; Error restoring text for 'E:\asf\maven\maven-3\nb_trunk\maven-embedder\src\test\error-reporting-p rojects\ext-plugin-artifact-missing\local-repo\org\apache\maven\errortes t\ext-plugin-artifact-missing-maven-plugin\1\ext-plugin-artifact-missing -maven-plugin-1.pom' AIt looks to me as this was never said long ago by many other developers. :-( I toke maven down using SVN checkout to a trunk, then I tried to just copy it to a different directory and VISTA faild because the path is just too long. Yeah, sucks to use Microsoft. Recommend shortening the path. E:\m3 We have to do this with our eclipse development projects - they are a lot longer. Unfortunately at some point you run out of stuff that can be shortened and you are stuffed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
