Re: maven download the dependency of a error version?
2010/1/29 Anders Hammar and...@hammar.net Well, this is the good thing about m2eclipse. It uses the pom as master. A repo manager (Nexus for example) will solve your network problems. Nexus is to be used for building private maven repository, and I just make some mirrors (for example ,create a proxy repo for the central) in the setting.xml. So I wonder if I have to create proxy repo for each repo defined in the project using nexus? And then config the releated mirror in the setting.xml? However in a maven project, there always too many repo defined, is it necessary ? /Anders On Fri, Jan 29, 2010 at 02:28, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You should use m2eclipse. You want to have one dev environment setup, not having to manage two separate ones - the POM should be the master. And you would get many nice features like dep graphs and easier management of your deps. Yes, it is true,I can check the dependency more clearly, However there is a rather unbearable problem, m2eclipse will update the maven dependency as soon as I modify the pom(most time I just config some plugins rather add or remove the dependency),and if the web connecttion is bad or some artifact is not available, it will take too long. And eventuelly you'll also get much fast builds (incremental builds, already partly in place in 0.9.9-dev). And, maybe most importantly, the maven configuration and eclipse configuration will be synced. We're not there yet though, but I believe we will be for the major plugins in v1.0 of m2e. But make sure you use the latest 0.9.9-dev build, not v0.9.8 of m2e. /Anders On Thu, Jan 28, 2010 at 10:22, maven apache apachemav...@gmail.com wrote: BTW, do you think it is a good idea to use m2eclipse? or other IDE integrate with maven? Beacuse I found if I work without m2eclipse, each I edit the pom, I should use mvn eclipse:eclipse to update the .classpath ,however the m2eclipse work rather slowly :(. How about your? 2010/1/28 Anders Hammar and...@hammar.net I also see that they add other repositories in their pom. A total mess... /A On Thu, Jan 28, 2010 at 10:05, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Correct, based on their pom this is one of those examples of why it is a bad plan to add dependencies in a profile that is activated based on the build JDK and/or OS 2010/1/28 maven apache apachemav...@gmail.com 2010/1/28 Anders Hammar and...@hammar.net Here you go: http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom I didn't look closely enough. The JDK1.4 profile is active by default, do as you're NOT using JDK 1.5 that profile is not going to kick in. Oh, my fault, I did not check it clearly enouth. You mean not matter which jdk I use( configed in the compile version?), as long as the version is not 1.5(for my case , it is 1.6), the jdk14 profile will be actived? /Anders On Thu, Jan 28, 2010 at 09:30, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You're building with JDK 1.4, not JDK 1.5. How? I did not sepcify 1.4 or .1.5. In the parent pom of my project I config the compile version to 1.6, and my eclipse are using jdk1.6_18 There are profiles in the pom of org.apache.rampart:rampart-policy:jar:1.4 (Actually, the profiles are in the parent of that project). Yes, I know this, I have check the pom. The homepage which you refer to isn't telling the complete truth... /Anders On Thu, Jan 28, 2010 at 09:15, maven apache apachemav...@gmail.com wrote: Hi: I found a strange problem, it seems that maven may download a wrong version for a transitive dependency. Details can be found here : http://dpaste.com/151511/
Re: maven download the dependency of a error version?
The Nexus book talks about all these questions: http://www.sonatype.com/books/nexus-book/reference/ /Anders On Fri, Jan 29, 2010 at 09:17, maven apache apachemav...@gmail.com wrote: 2010/1/29 Anders Hammar and...@hammar.net Well, this is the good thing about m2eclipse. It uses the pom as master. A repo manager (Nexus for example) will solve your network problems. Nexus is to be used for building private maven repository, and I just make some mirrors (for example ,create a proxy repo for the central) in the setting.xml. So I wonder if I have to create proxy repo for each repo defined in the project using nexus? And then config the releated mirror in the setting.xml? However in a maven project, there always too many repo defined, is it necessary ? /Anders On Fri, Jan 29, 2010 at 02:28, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You should use m2eclipse. You want to have one dev environment setup, not having to manage two separate ones - the POM should be the master. And you would get many nice features like dep graphs and easier management of your deps. Yes, it is true,I can check the dependency more clearly, However there is a rather unbearable problem, m2eclipse will update the maven dependency as soon as I modify the pom(most time I just config some plugins rather add or remove the dependency),and if the web connecttion is bad or some artifact is not available, it will take too long. And eventuelly you'll also get much fast builds (incremental builds, already partly in place in 0.9.9-dev). And, maybe most importantly, the maven configuration and eclipse configuration will be synced. We're not there yet though, but I believe we will be for the major plugins in v1.0 of m2e. But make sure you use the latest 0.9.9-dev build, not v0.9.8 of m2e. /Anders On Thu, Jan 28, 2010 at 10:22, maven apache apachemav...@gmail.com wrote: BTW, do you think it is a good idea to use m2eclipse? or other IDE integrate with maven? Beacuse I found if I work without m2eclipse, each I edit the pom, I should use mvn eclipse:eclipse to update the .classpath ,however the m2eclipse work rather slowly :(. How about your? 2010/1/28 Anders Hammar and...@hammar.net I also see that they add other repositories in their pom. A total mess... /A On Thu, Jan 28, 2010 at 10:05, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Correct, based on their pom this is one of those examples of why it is a bad plan to add dependencies in a profile that is activated based on the build JDK and/or OS 2010/1/28 maven apache apachemav...@gmail.com 2010/1/28 Anders Hammar and...@hammar.net Here you go: http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom I didn't look closely enough. The JDK1.4 profile is active by default, do as you're NOT using JDK 1.5 that profile is not going to kick in. Oh, my fault, I did not check it clearly enouth. You mean not matter which jdk I use( configed in the compile version?), as long as the version is not 1.5(for my case , it is 1.6), the jdk14 profile will be actived? /Anders On Thu, Jan 28, 2010 at 09:30, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You're building with JDK 1.4, not JDK 1.5. How? I did not sepcify 1.4 or .1.5. In the parent pom of my project I config the compile version to 1.6, and my eclipse are using jdk1.6_18 There are profiles in the pom of org.apache.rampart:rampart-policy:jar:1.4 (Actually, the profiles are in the parent of that project). Yes, I know this, I have check the pom. The homepage which you refer to isn't telling the complete truth... /Anders On Thu, Jan 28, 2010 at 09:15, maven apache apachemav...@gmail.com wrote: Hi: I found a strange problem, it seems that maven may download a wrong version for a transitive dependency. Details can be found here : http://dpaste.com/151511/
Maven execution element and dependencies
Hi List, I would like to generate two artifacts within one maven project (one with a classifier). I can do this by executing the compiler plugin (flexmojos in my case) twice, once with the classifier. The only problem is that the compilations should have different scopes on some dependencies. Is it possible to specify dependencies for plugin execution elements? If so, how? For the time being, I am using profiles as a workaround. However, this requires that I execute maven twice in sequence in order to create a pair of artifacts. I have several projects which require double compilation, and one which depends on all of these and creates a deployment package (including all artifacts) This results in double deployment of the main packaging project to our local repository, which is somewhat inconvenient for our continuous integration environment. Thanks, Rade -- View this message in context: http://old.nabble.com/Maven-execution-element-and-dependencies-tp27367114p27367114.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Non-plexus Components in maven
Hi, I'm new to maven plugin(mojo). I know there are some shared plexus components in maven. Besides them,I also found there are some other components in maven, such as MavenFileFilter in maven-filtering, MavenProjectHelper in maven-project, etc. I hope to know how to use these components in maven, but only found API docs just containing method signature. Is there anyone can provide any information on the usage of these components? Or is the source code the only way to know how to use them? Thanks in advance! -- View this message in context: http://old.nabble.com/Non-plexus-Components-in-maven-tp27367121p27367121.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Compile what can be compiled, ignore sources with errors
Is there a way to configure Maven to ignore source files that present errors during compilation, and compile everything that is possible (that is, has no error)? I've set maven-compiler-plugin's failOnError option to false, and the build is considered successful despite the errors. However, no classes are generated. Our jar file is even created, but it has nothing except the META-INF directory. I believe the problem happens because it's a big project (229 source files as of now). I created a simple project with two sources, and even without failOnError=true the source with no errors was compiled. But when I created a lot more sources with errors, nothing was generated. Apparently after some number of errors Maven gives up and does not try to compile anything else. Is that assumption correct? I couldn't find any information on that. One possible way to solve the problem would be to manually list the files to be excluded, and remove them from the list as they get fixed. But this is tedious and error-prone, so I wonder if there is a better way. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Compile what can be compiled, ignore sources with errors
The obvious counter question is: Why do you want to do this? Why not just fix the compile errors? Eduardo M KALINOWSKI schrieb: Is there a way to configure Maven to ignore source files that present errors during compilation, and compile everything that is possible (that is, has no error)? I've set maven-compiler-plugin's failOnError option to false, and the build is considered successful despite the errors. However, no classes are generated. Our jar file is even created, but it has nothing except the META-INF directory. I believe the problem happens because it's a big project (229 source files as of now). I created a simple project with two sources, and even without failOnError=true the source with no errors was compiled. But when I created a lot more sources with errors, nothing was generated. Apparently after some number of errors Maven gives up and does not try to compile anything else. Is that assumption correct? I couldn't find any information on that. One possible way to solve the problem would be to manually list the files to be excluded, and remove them from the list as they get fixed. But this is tedious and error-prone, so I wonder if there is a better way. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Compile what can be compiled, ignore sources with errors
Hi Eduardo, a solution would be +) create a project in the IDE of your choice +) fix the errors incrementally Cheers, Siegfried Goeschl Eduardo M KALINOWSKI wrote: Is there a way to configure Maven to ignore source files that present errors during compilation, and compile everything that is possible (that is, has no error)? I've set maven-compiler-plugin's failOnError option to false, and the build is considered successful despite the errors. However, no classes are generated. Our jar file is even created, but it has nothing except the META-INF directory. I believe the problem happens because it's a big project (229 source files as of now). I created a simple project with two sources, and even without failOnError=true the source with no errors was compiled. But when I created a lot more sources with errors, nothing was generated. Apparently after some number of errors Maven gives up and does not try to compile anything else. Is that assumption correct? I couldn't find any information on that. One possible way to solve the problem would be to manually list the files to be excluded, and remove them from the list as they get fixed. But this is tedious and error-prone, so I wonder if there is a better way. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Compile what can be compiled, ignore sources with errors
2010/1/29 Eduardo M KALINOWSKI edua...@kalinowski.com.br: One possible way to solve the problem would be to manually list the files to be excluded, and remove them from the list as they get fixed. But this is tedious and error-prone, so I wonder if there is a better way. Sure, complain with your team. Having a project that does not compile is simply incorrect, not to mention the sarcasm that it may cause, such as the famous Every build you break song on YouTube :-D Or the sheep of shame (usually a toy) that is given to the one who breaks the build. Have fun :-D Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven download the dependency of a error version?
2010/1/29 Anders Hammar and...@hammar.net The Nexus book talks about all these questions: http://www.sonatype.com/books/nexus-book/reference/ Thanks, I have tried the nexus, in fact I have heard it before, and I use it this afternoon. You said it can solve the speed problem in the IDE for updating dependency,however I found the nexus just acted as a bridge between the proxy repo and the remote repo, when updating dependency, it also connect to the remote repo which is a time-cousuming work. So,it is my configration or something else? /Anders On Fri, Jan 29, 2010 at 09:17, maven apache apachemav...@gmail.com wrote: 2010/1/29 Anders Hammar and...@hammar.net Well, this is the good thing about m2eclipse. It uses the pom as master. A repo manager (Nexus for example) will solve your network problems. Nexus is to be used for building private maven repository, and I just make some mirrors (for example ,create a proxy repo for the central) in the setting.xml. So I wonder if I have to create proxy repo for each repo defined in the project using nexus? And then config the releated mirror in the setting.xml? However in a maven project, there always too many repo defined, is it necessary ? /Anders On Fri, Jan 29, 2010 at 02:28, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You should use m2eclipse. You want to have one dev environment setup, not having to manage two separate ones - the POM should be the master. And you would get many nice features like dep graphs and easier management of your deps. Yes, it is true,I can check the dependency more clearly, However there is a rather unbearable problem, m2eclipse will update the maven dependency as soon as I modify the pom(most time I just config some plugins rather add or remove the dependency),and if the web connecttion is bad or some artifact is not available, it will take too long. And eventuelly you'll also get much fast builds (incremental builds, already partly in place in 0.9.9-dev). And, maybe most importantly, the maven configuration and eclipse configuration will be synced. We're not there yet though, but I believe we will be for the major plugins in v1.0 of m2e. But make sure you use the latest 0.9.9-dev build, not v0.9.8 of m2e. /Anders On Thu, Jan 28, 2010 at 10:22, maven apache apachemav...@gmail.com wrote: BTW, do you think it is a good idea to use m2eclipse? or other IDE integrate with maven? Beacuse I found if I work without m2eclipse, each I edit the pom, I should use mvn eclipse:eclipse to update the .classpath ,however the m2eclipse work rather slowly :(. How about your? 2010/1/28 Anders Hammar and...@hammar.net I also see that they add other repositories in their pom. A total mess... /A On Thu, Jan 28, 2010 at 10:05, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Correct, based on their pom this is one of those examples of why it is a bad plan to add dependencies in a profile that is activated based on the build JDK and/or OS 2010/1/28 maven apache apachemav...@gmail.com 2010/1/28 Anders Hammar and...@hammar.net Here you go: http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom I didn't look closely enough. The JDK1.4 profile is active by default, do as you're NOT using JDK 1.5 that profile is not going to kick in. Oh, my fault, I did not check it clearly enouth. You mean not matter which jdk I use( configed in the compile version?), as long as the version is not 1.5(for my case , it is 1.6), the jdk14 profile will be actived? /Anders On Thu, Jan 28, 2010 at 09:30, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You're building with JDK 1.4, not JDK 1.5. How? I did not sepcify 1.4 or .1.5. In the parent pom of my project I config the compile version to 1.6, and my eclipse are using jdk1.6_18 There are profiles in the pom of org.apache.rampart:rampart-policy:jar:1.4 (Actually, the profiles are in the parent of that project). Yes, I know this, I have check
Re: Compile what can be compiled, ignore sources with errors
On Sex, 29 Jan 2010, Christoph Kutzinski wrote: The obvious counter question is: Why do you want to do this? Why not just fix the compile errors? To make a long story short: we received this project from another company, and we have to fix it and complete the parts that are missing. We are doing this in incremental steps, naturally. Sometimes we make changes that break other parts of the project. For example, a method name may be changed. This will break everywhere that calls the method. This gets fixed in the parts that we are currently working on, but in other parts, we ignore them for now. When work is started on those parts, they'll have to get fixed. It's true that in the end everything will have to compile without errors. But at this moment, we need the parts that are OK to be compiled, so that the application (it's a web application) can be run and those parts be tested. As for what's still with errors, they at the moment aren't being called. Naturally, if they were called, a run-time error would show up. That's OK by now. I hope this clears up the reasons. I know it's a weird request, but this situation is not permanent. As the project progresses, this will simply not be necessary anymore. -- You're being followed. Cut out the hanky-panky for a few days. Eduardo M KALINOWSKI edua...@kalinowski.com.br - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Compile what can be compiled, ignore sources with errors
Sounds to me like you should modularize the application, make a multi-module project of it (if not already) and then add only those modules on which you're working currently to the modules section of the parent POM and leave out all the others for the moment. Just a quick idea from the top of my head. The alternative you mentioned - try to compile everything and just hope at runtime that all currently needed functionality is working - sounds inherently dangerous to me. Eduardo M KALINOWSKI schrieb: On Sex, 29 Jan 2010, Christoph Kutzinski wrote: The obvious counter question is: Why do you want to do this? Why not just fix the compile errors? To make a long story short: we received this project from another company, and we have to fix it and complete the parts that are missing. We are doing this in incremental steps, naturally. Sometimes we make changes that break other parts of the project. For example, a method name may be changed. This will break everywhere that calls the method. This gets fixed in the parts that we are currently working on, but in other parts, we ignore them for now. When work is started on those parts, they'll have to get fixed. It's true that in the end everything will have to compile without errors. But at this moment, we need the parts that are OK to be compiled, so that the application (it's a web application) can be run and those parts be tested. As for what's still with errors, they at the moment aren't being called. Naturally, if they were called, a run-time error would show up. That's OK by now. I hope this clears up the reasons. I know it's a weird request, but this situation is not permanent. As the project progresses, this will simply not be necessary anymore. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven download the dependency of a error version?
Nexus has to connect for the first download of a specific artifact. But it's going to be much faster for the second access (for that artifact). A Maven repo manager is a normal part of a maven infrastructure nowadays. Or at least should be. /Anders On Fri, Jan 29, 2010 at 13:27, maven apache apachemav...@gmail.com wrote: 2010/1/29 Anders Hammar and...@hammar.net The Nexus book talks about all these questions: http://www.sonatype.com/books/nexus-book/reference/ Thanks, I have tried the nexus, in fact I have heard it before, and I use it this afternoon. You said it can solve the speed problem in the IDE for updating dependency,however I found the nexus just acted as a bridge between the proxy repo and the remote repo, when updating dependency, it also connect to the remote repo which is a time-cousuming work. So,it is my configration or something else? /Anders On Fri, Jan 29, 2010 at 09:17, maven apache apachemav...@gmail.com wrote: 2010/1/29 Anders Hammar and...@hammar.net Well, this is the good thing about m2eclipse. It uses the pom as master. A repo manager (Nexus for example) will solve your network problems. Nexus is to be used for building private maven repository, and I just make some mirrors (for example ,create a proxy repo for the central) in the setting.xml. So I wonder if I have to create proxy repo for each repo defined in the project using nexus? And then config the releated mirror in the setting.xml? However in a maven project, there always too many repo defined, is it necessary ? /Anders On Fri, Jan 29, 2010 at 02:28, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You should use m2eclipse. You want to have one dev environment setup, not having to manage two separate ones - the POM should be the master. And you would get many nice features like dep graphs and easier management of your deps. Yes, it is true,I can check the dependency more clearly, However there is a rather unbearable problem, m2eclipse will update the maven dependency as soon as I modify the pom(most time I just config some plugins rather add or remove the dependency),and if the web connecttion is bad or some artifact is not available, it will take too long. And eventuelly you'll also get much fast builds (incremental builds, already partly in place in 0.9.9-dev). And, maybe most importantly, the maven configuration and eclipse configuration will be synced. We're not there yet though, but I believe we will be for the major plugins in v1.0 of m2e. But make sure you use the latest 0.9.9-dev build, not v0.9.8 of m2e. /Anders On Thu, Jan 28, 2010 at 10:22, maven apache apachemav...@gmail.com wrote: BTW, do you think it is a good idea to use m2eclipse? or other IDE integrate with maven? Beacuse I found if I work without m2eclipse, each I edit the pom, I should use mvn eclipse:eclipse to update the .classpath ,however the m2eclipse work rather slowly :(. How about your? 2010/1/28 Anders Hammar and...@hammar.net I also see that they add other repositories in their pom. A total mess... /A On Thu, Jan 28, 2010 at 10:05, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Correct, based on their pom this is one of those examples of why it is a bad plan to add dependencies in a profile that is activated based on the build JDK and/or OS 2010/1/28 maven apache apachemav...@gmail.com 2010/1/28 Anders Hammar and...@hammar.net Here you go: http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom I didn't look closely enough. The JDK1.4 profile is active by default, do as you're NOT using JDK 1.5 that profile is not going to kick in. Oh, my fault, I did not check it clearly enouth. You mean not matter which jdk I use( configed in the compile version?), as long as the version is not 1.5(for my case , it is 1.6), the jdk14 profile will be actived? /Anders On Thu, Jan 28, 2010 at 09:30, maven apache apachemav...@gmail.com wrote: 2010/1/28 Anders Hammar and...@hammar.net You're building with JDK
Re: Maven execution element and dependencies
The obvious question is why you don't make it two projects? The problem you're running into is because there is just one pom. Even if you solve your compilation problem, you're going to cause problems for anyone consuming the artifact (as the pom will list the wrong deps). /Anders On Fri, Jan 29, 2010 at 09:32, radomirz radom...@gmail.com wrote: Hi List, I would like to generate two artifacts within one maven project (one with a classifier). I can do this by executing the compiler plugin (flexmojos in my case) twice, once with the classifier. The only problem is that the compilations should have different scopes on some dependencies. Is it possible to specify dependencies for plugin execution elements? If so, how? For the time being, I am using profiles as a workaround. However, this requires that I execute maven twice in sequence in order to create a pair of artifacts. I have several projects which require double compilation, and one which depends on all of these and creates a deployment package (including all artifacts) This results in double deployment of the main packaging project to our local repository, which is somewhat inconvenient for our continuous integration environment. Thanks, Rade -- View this message in context: http://old.nabble.com/Maven-execution-element-and-dependencies-tp27367114p27367114.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Access to server settings from settings.xml
Hi,
Is it possible to access a server username/password (even/especially when
encrypted) from an Ant Mojo and/or antrun script?
If you know how to do it from a Java Mojo, I would take that too.
I would like to be able to use it to ssh to other servers where we have some
cross-compilers installed, etc, and currently we are forcing our developers to
set our own properties in settings.xml, which does not support encryption.
I have tried things like this (following the pattern from
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide) , but of
course, the server id must get in there somehow, I assume.
${settings.servers.id.username} ${settings.server.id.username} etc etc to no
avail.
Thanks,
Ben
Re: Compile what can be compiled, ignore sources with errors
On Sex, 29 Jan 2010, Christoph Kutzinski wrote: Sounds to me like you should modularize the application, make a multi-module project of it (if not already) and then add only those modules on which you're working currently to the modules section of the parent POM and leave out all the others for the moment. Just a quick idea from the top of my head. It is already a multi-module application. Some modules are OK, but the problems I'm referring to happen in only one of the modules (well, two actually). The alternative you mentioned - try to compile everything and just hope at runtime that all currently needed functionality is working - sounds inherently dangerous to me. Yes, it is dangerous. But it works fine when building with Eclipse. Apparently Eclipse does just that, compiling what can be compiled and including that in the final war (or whatever else is being generated). -- Your mileage may vary. Eduardo M KALINOWSKI edua...@kalinowski.com.br - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Access to server settings from settings.xml
To answer my own question for groovy, I found this:
http://weblogs.java.net/blog/2009/08/10/getting-most-out-maven-settingsxml-file
which explains doing this:
def server = settings.servers.find{ it.id.equals('dbserver') }
But does anyone know how to do it in ant?
Thanks,
Ben
- Ben Tatham bentat...@nanometrics.ca wrote:
Hi,
Is it possible to access a server username/password (even/especially when
encrypted) from an Ant Mojo and/or antrun script?
If you know how to do it from a Java Mojo, I would take that too.
I would like to be able to use it to ssh to other servers where we have some
cross-compilers installed, etc, and currently we are forcing our developers
to set our own properties in settings.xml, which does not support encryption.
I have tried things like this (following the pattern from
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide) , but of
course, the server id must get in there somehow, I assume.
${settings.servers.id.username} ${settings.server.id.username} etc etc to no
avail.
Thanks,
Ben
Re: Compile what can be compiled, ignore sources with errors
2010/1/29 Eduardo M KALINOWSKI edua...@kalinowski.com.br: For example, a method name may be changed. This will break everywhere that calls the method. Refactoring anyone? Or deprecations? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Upload snapshot on nexus
Http didn't work for me in the past so I didn't try that, I just did, providing it with the 'deployment' user credentials and it worked and I was able to upload the snapshot Thanks Anders Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, January 29, 2010 1:47 AM To: Maven Users List Subject: Re: Upload snapshot on nexus Why are you using scp and not http? /Anders On Fri, Jan 29, 2010 at 03:47, Qureshi,Shahzad [Ontario] shahzad.qure...@ec.gc.ca wrote: Ahh, forgot that it should be snapshotRepository and not repository below So it should be distributionManagement snapshotRepository idnexus/id urlscp://serveraddress/usr/local/sonatype-work/nexus/storage/snapshots/url /snapshotRepository /distributionManagement Its working now, well not entirely since the account I am usng doesn't write permission on the directory I am trying to write this snapshot to but that's a different issue and will be solved by tmrw. I will report back when I do successfully write the snapshot to the snapshot repo Thanks for your help Ron Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -Original Message- From: Qureshi,Shahzad [Ontario] [mailto:shahzad.qure...@ec.gc.ca] Sent: Thursday, January 28, 2010 9:30 PM To: Maven Users List Subject: *SPAM* RE: Upload snapshot on nexus Did that, also added a distributionManagement section in the pom like the following distributionManagement repository idnexus/id urlscp://serveraddress/usr/local/sonatype-work/nexus/storage/snapshots/url /repository /distributionManagement And I still get the exact same error Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: Thursday, January 28, 2010 8:50 PM To: Maven Users List Subject: Re: Upload snapshot on nexus http://www.sonatype.com/books/nexus-book/reference/ch14s04.html Qureshi,Shahzad [Ontario] wrote: Hi all, I am having problem uploading a snapshot of my project to our internal nexus repository. Everything else is working fine, I can download plugins/dependencies, I am able to upload releases using the browser but when I try to do mvn deploy for a snapshot of my project, I get [INFO] Error retrieving previous build number for artifact 'test:Archive:jar': repository metadata for: 'snapshot test:Archive:1.0-SNAPSHOT' could not be retrieved from repository: central due to an error: Authentication failed: Cannot connect. Reason: connection is closed by foreign host I've done what this link mentioned here: http://www.sonatype.com/books/nexus-book/reference/maven-sect-single -g ro up.html i.e. included snapshot repository to the public group and created the settings.xml and everything is working except deploying of the snapshot I don't have distributionManagement section in my pom file though, does that matter? If so, what should go in there? Because I don't seem to need it when deploying releases It seems to me that the reason its failing is because I need to proivde login and password for the server where I am trying to upload the snapshot(Authentication failed), where do I specify that? Any help will be great Thanks Shahzad Qureshi - 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 - 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: Compile what can be compiled, ignore sources with errors
Eduardo- AFAIK, the behavior you are seeing is the behavior of javac, not Maven. As you note, the Eclipse compiler does something different, so if that's the behavior you want, use the Eclipse compiler. Justin On Fri, Jan 29, 2010 at 8:21 AM, Eduardo M KALINOWSKI edua...@kalinowski.com.br wrote: On Sex, 29 Jan 2010, Christoph Kutzinski wrote: Sounds to me like you should modularize the application, make a multi-module project of it (if not already) and then add only those modules on which you're working currently to the modules section of the parent POM and leave out all the others for the moment. Just a quick idea from the top of my head. It is already a multi-module application. Some modules are OK, but the problems I'm referring to happen in only one of the modules (well, two actually). The alternative you mentioned - try to compile everything and just hope at runtime that all currently needed functionality is working - sounds inherently dangerous to me. Yes, it is dangerous. But it works fine when building with Eclipse. Apparently Eclipse does just that, compiling what can be compiled and including that in the final war (or whatever else is being generated). -- Your mileage may vary. Eduardo M KALINOWSKI edua...@kalinowski.com.br - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Eear libraries classpath
Hi All We are creatign an ear as a result artifact of a maven project. In the ear file we package all libraries with the final names without verison numbers. Maven creates classpaths for those libraries with the names+versions. Example: We have an EAR package contains Module A and B Module A depends on Module B ModuleA's manifest-mf: Implementation-Title: Module A Implementation-Version: 1.5.2-SNAPSHOT Implementation-Vendor-Id: vendor id Class-Path: ModuleB-1.5.2-SNAPSHOT.jar ModuleB's manifets mf: Implementation-Title: Module B Implementation-Version: 1.5.2-SNAPSHOT Implementation-Vendor-Id: vendor id EAR PAckage: ModuleA.jar ModuleB.jar Is this a problem; having ModuleB as ModuleB.jar in ear package? Can ModuleA fsee ModuleB on the classpath? If the answer is no, how do I addd dependencies to the manifest.mf classpath without version numbers only with the finalNames? Many thanks for your help. Regards Maruf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Eear libraries classpath
Is this a problem; having ModuleB as ModuleB.jar in ear package? Can ModuleA fsee ModuleB on the classpath? When you tested this EAR with your target Java EE app server, what happened? Did things deploy and work properly, or no? If the answer is no, how do I addd dependencies to the manifest.mf classpath without version numbers only with the finalNames? I'd just keep the version numbers everywhere in the first place, and avoid this entire discussion. What possible reason do you have for removing them from some of your dependencies? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Compile what can be compiled, ignore sources with errors
On Fri, Jan 29, 2010 at 12:31:06PM +0100, Christoph Kutzinski wrote: Why do you want to do this? Why not just fix the compile errors? Likely the same reason that compiler writers have spent so much time studying error recovery in parsers: to discover as many errors as possible in one iteration. Fewer iterations, each one more productive. You also get a better feel for just how buggy the code is, and for patterns of problems, by seeing everything that *doesn't* fail to compile. It's useful to be able to answer questions like, this is happening all over the place -- is there a deeper problem? Of course that has to be balanced against the fact that, when compiling X against broken Y, you may not get a true picture of the status of X. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents. pgpCFXpy2ucDp.pgp Description: PGP signature
Re: Plugin executions vs. POM inheritance
If this is the way it should work, is there a way to achieve what I want? I.e. define some utility executions in parent that can be called in child modules, but independent of other executions. Did you consider profiles for this purpose? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
automating maven release plugin tag label
Hi maven people,
We have projects we want to release using the maven-release-plugin. Moreover,
we want to perform our releases in Hudson, with the help of the M2release
(hudson) plugin. This is a dream come true: perform a release on a single
push of a button (actually, more of a link).
Now, to do this without fiddling with the version number, I need to be able to
rely on conventions:
- releaseVersion is OK (defaults to ex. 1.0.0)
- developmentVersion is OK (defaults to ex. 1.0.1-SNAPSHOT)
- tagBase is OK (I can specify it directly in the POM)
The value causing me trouble is the release tag label. I would have liked to
have it this way:
project ...
version1.0.0-SNAPSHOT/version
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
tagrelease-${pom.version}/tag
...
/project
But, this gives me a SCM tag with the '-SNAPSHOT' suffix. Not good. And I
don't want to explicitly mention the version in the Hudson job configuration.
Is there a way I can get the tag label to use the correct release version?
Thank you for your answers.
--
JS.
FW: Errors after upgrade to 2.2.1
I also found this JIRA ticket entered against a project named Maven Evangelism. Nice project name. :) http://jira.codehaus.org/browse/MEV-649 However, switching down to log4j 1.2.14 changed nothing as far as these errors go. Perhaps some other library(s) also have this issue? If so, is there some simple way to tell Maven not to use this bogus repo? Previously... Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-pm-if:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pro j-pm-if\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-pm-if:1.0.6-SNAPSHOT @
RE: Errors after upgrade to 2.2.1
I put this into my settings.xml: mirrors mirror idexternal-redirect/id nameRedirect of external refs to local/name urlhttp://our.local.server.host/repository/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Same errors occur in the log regardless of this change. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:37 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Thats fine too. Just try the mirror of external everything setting. I would really recommend looking at nexus on that server though. The repository is still just a filesystem but you have a lot of tooling around it via the webapp and you just run jetty/nexus instead of apache.. manfred -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource com.abc.xyz.etp:proj-edoms-lib:jar:1.0.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact =
Re: automating maven release plugin tag label
Are you not using standard SVN directory layout or no SVN at all? We
do fully automated releases with mvn -B release:prepare
release:perform and it gets the tagname etc. right without any special
configuration. As a sidenote, pom.version is deprecated, use
project.version instead.
Kalle
On Fri, Jan 29, 2010 at 1:06 PM, JS Bournival j...@jipiju.com wrote:
Hi maven people,
We have projects we want to release using the maven-release-plugin.
Moreover, we want to perform our releases in Hudson, with the help of the
M2release (hudson) plugin. This is a dream come true: perform a release on
a single push of a button (actually, more of a link).
Now, to do this without fiddling with the version number, I need to be able
to rely on conventions:
- releaseVersion is OK (defaults to ex. 1.0.0)
- developmentVersion is OK (defaults to ex. 1.0.1-SNAPSHOT)
- tagBase is OK (I can specify it directly in the POM)
The value causing me trouble is the release tag label. I would have liked to
have it this way:
project ...
version1.0.0-SNAPSHOT/version
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
tagrelease-${pom.version}/tag
...
/project
But, this gives me a SCM tag with the '-SNAPSHOT' suffix. Not good. And I
don't want to explicitly mention the version in the Hudson job configuration.
Is there a way I can get the tag label to use the correct release version?
Thank you for your answers.
--
JS.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Errors after upgrade to 2.2.1
I think I may know what's happening: http://n2.nabble.com/Suck-cannot-build-repository-down-td3432724.html#a3432724 Since I'm using the maven-project-info-reports-plugin:dependencies report, it does completely bypass the normal repository mechanism and thus Nexus. This sounds like a defect in the dependencies report portion of the codehaus mojo maven-project-info-reports-plugin. Does anyone know a workaround for this? I've spent a lot of time already on integrating Maven into our development process, and the deeper I go, the more problems crop up. Tom -Original Message- From: Thomas Harris Sent: Friday, January 29, 2010 4:58 PM To: manf...@mosabuam.com; mo...@yahoo-inc.com; users@maven.apache.org Subject: RE: Errors after upgrade to 2.2.1 I put this into my settings.xml: mirrors mirror idexternal-redirect/id nameRedirect of external refs to local/name urlhttp://our.local.server.host/repository/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Same errors occur in the log regardless of this change. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:37 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Thats fine too. Just try the mirror of external everything setting. I would really recommend looking at nexus on that server though. The repository is still just a filesystem but you have a lot of tooling around it via the webapp and you just run jetty/nexus instead of apache.. manfred -- Manfred Moser http://www.mosabuam.com skype mosabua, twitter.com/mosabua http://www.linkedin.com/in/manfredmoser On Friday January 29 2010, Thomas Harris wrote: Manfred: What if we aren't running Nexus locally? I set up a VM on our network with Apache, and we're using that to host a repository folder and a place to deploy the site. But, we haven't even begun to look into installing Nexus locally. Tom -Original Message- From: Manfred Moser [mailto:manf...@mosabuam.com] Sent: Friday, January 29, 2010 4:30 PM To: Thomas Harris Cc: mo...@yahoo-inc.com Subject: Re: Errors after upgrade to 2.2.1 Try mirrorOfexternal:*/mirrorOf with a local nexus instance to speed things up and then something like mirrors mirror idcentral/id nameLocalhost Nexus/name urlhttp://localhost:9081/nexus/content/groups/all/url mirrorOfexternal:*/mirrorOf /mirror /mirrors Muser, Manfred: I'm getting these same errors, but many many more of them. I did not have any reference to this oddball repository anywhere in my projects' pom.xml files, yet it seems Maven wants desperately to pull these jars from the ancient and deleted Maven 1 repository. I added this to my settings.xml, to no avail: mirrors mirror idjava.net2/id nameMirror of https://maven-repository.dev.java.net/nonav/repository//name urlhttp://download.java.net/maven/2//url mirrorOfjava.net/mirrorOf /mirror /mirrors Were you able to resolve this issue, Muser? How? Manfred, any ideas? Even though the build EVENTUALLY succeeds, these bogus lookups make our build like 20 times slower. Tom Harris Axispoint, Inc. Maven log output in question: [ERROR] Unable to determine if resource aopalliance:aopalliance:jar:1.0:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource apache-log4j:log4j:jar:1.2.14:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource asm:asm:jar:3.1:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib:jar:2.2:compile exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource cglib:cglib-nodep:jar:2.1_3:test exists in https://maven-repository.dev.java.net/nonav/repository [ERROR] Unable to determine if resource active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = active project artifact: artifact = com.abc.xyz.etp:proj-commons:jar:1.0.6-SNAPSHOT:compile; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @ C:\eclipse-workspaces\project-workspace\proj-pm-parent\modules\pr o j-commons\pom.xml; project: MavenProject: com.abc.xyz.etp:proj-commons:1.0.6-SNAPSHOT @
Re: Errors after upgrade to 2.2.1
and thus Nexus. This sounds like a defect in the dependencies report portion of the codehaus mojo maven-project-info-reports-plugin. I agree. Check Jira to see if it is already filed. Does anyone know a workaround for this? Stop using this report for now, until it is fixed. If you have the time and interest, patch the report and contribute your fixes back to mojo for inclusion in a future release of the report. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin executions vs. POM inheritance
How could this be achieved with profiles? Lóránt On Fri, Jan 29, 2010 at 21:13, Wayne Fay wayne...@gmail.com wrote: If this is the way it should work, is there a way to achieve what I want? I.e. define some utility executions in parent that can be called in child modules, but independent of other executions. Did you consider profiles for this purpose? Wayne - 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: Plugin executions vs. POM inheritance
You could insert this utility executions in profile. e.g. profiles profile idwhatever/id build plugins plugin ... /plugin /plugins /build /profile /profiles And this plugin will be executed only when this profile is activated. 2010/1/30 Lóránt Pintér lorant.pin...@gmail.com How could this be achieved with profiles? Lóránt On Fri, Jan 29, 2010 at 21:13, Wayne Fay wayne...@gmail.com wrote: If this is the way it should work, is there a way to achieve what I want? I.e. define some utility executions in parent that can be called in child modules, but independent of other executions. Did you consider profiles for this purpose? Wayne - 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 -- Regards, Alexander
Re: automating maven release plugin tag label
ok but what if you want to override the default tag label? The
default one is ${project.artifactId}-release version.
is there a way in the pom to retrieve the release version as set by
the maven-release-plugin?
--
JS.
--
Le 2010-01-29 à 17:05, Kalle Korhonen kalle.o.korho...@gmail.com a
écrit :
Are you not using standard SVN directory layout or no SVN at all? We
do fully automated releases with mvn -B release:prepare
release:perform and it gets the tagname etc. right without any special
configuration. As a sidenote, pom.version is deprecated, use
project.version instead.
Kalle
On Fri, Jan 29, 2010 at 1:06 PM, JS Bournival j...@jipiju.com wrote:
Hi maven people,
We have projects we want to release using the maven-release-
plugin. Moreover, we want to perform our releases in Hudson, with
the help of the M2release (hudson) plugin. This is a dream come
true: perform a release on a single push of a button (actually,
more of a link).
Now, to do this without fiddling with the version number, I need to
be able to rely on conventions:
- releaseVersion is OK (defaults to ex. 1.0.0)
- developmentVersion is OK (defaults to ex. 1.0.1-SNAPSHOT)
- tagBase is OK (I can specify it directly in the POM)
The value causing me trouble is the release tag label. I would
have liked to have it this way:
project ...
version1.0.0-SNAPSHOT/version
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
tagrelease-${pom.version}/tag
...
/project
But, this gives me a SCM tag with the '-SNAPSHOT' suffix. Not
good. And I don't want to explicitly mention the version in the
Hudson job configuration.
Is there a way I can get the tag label to use the correct release
version?
Thank you for your answers.
--
JS.
-
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
pom without artifacts?
I have uploaded a swing look-and-feel to our internal repository. The LaF contains a main jar plus a separate jar for each skin. In order to minimize the end result, each skin is uploaded separately with its own pom referring to the main jar. But sometimes I want it all skins, so I figured I create a pom with refers to all skins (which in turn refer to the main), but does not contain any artifacts itself. I can upload the pom without problems, leaving out the packaging. But when refering to it, it tries to download xxx-all.jar, so it assumes a default packaging. Is there any way to create such a artifact-less pom? -- View this message in context: http://old.nabble.com/pom-without-artifacts--tp27381618p27381618.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
