beyond Properies and Resource Filtering
I have read chapter 13 of Maven: The Definitive Guide and did not find my question answered there. Here is what I need to do. I have two subdirectories as follows: src/main/resources/foo src/main/resources/bar I have the same file in each of those two directories: src/main/resources/foo/mySpringBean.xml src/main/recourse/bar/mySpringBean.xml What I need to do is specify on the command line (or in a Profile or in settings.xml) which of those two directories should have it's contents copied to target/classes. The other directory should not have its contents copied into target/classes. Thank you in advance! (hope hope). Robert - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.0-RC3
I appreciate the advice and support I've received here. Today I was finally able to work further on the issue via gmail chat with a maven developer. Under his tutelage I created a JIRA for this issue: http://jira.codehaus.org/browse/MNG-4211 Your question on whether I tried 2.0.10 is a very good hunch. It turned out as I worked with the maven developer that in fact the proxy works fine with 2.0.10. The difference between 2.0.10 and 2.1, the developer told me, is that 2.1 was the first to use wagon 1.0-beta-4+. In summary, I can upgrade to 2.0.10 while waiting, patiently, for the stellar maven developers to find the problem and incorporate it into the next release after 2.2. And so, the story appears to be headed towards a happy ending. - Original Message From: Zac Thompson zac.thomp...@gmail.com To: Maven Users List users@maven.apache.org Sent: Thursday, June 18, 2009 6:36:07 PM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 Robert, this is just a guess: is the proxy defined in your user-specific (~/.m2/) settings.xml, but the proxy credentials are only supplied in your 2.0.9 install's $M2_HOME/conf/settings.xml? I don't even know if this is possible, so pardon me if you've already looked into this. You may want to post both settings.xml (please obscure any sensitive info). Have you tried 2.0.10 (different from 2.1.0)? Does it have the same problem? Is there a difference in the help:effective-pom between 2.0.9 and 2.2.0-RC3? Zac From: Robert Glover robertglove...@yahoo.com mailto:robertglove...@yahoo.com To: Maven Users List users@maven.apache.org mailto:users@maven.apache.org Sent: Thursday, June 11, 2009 6:44:06 PM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 I downloaded apache-maven-2.2.0-RC3 and tried it out but sadly, I get the same proxy problem I have been getting in all versions of maven subsequent to 2.0.9. Maven 2.0.9 continues to work fine, but if I change to 2.2.0.RC3 and use the same pom.xml file and the same settings.xml file (where the proxy config is) it causes a proxy error and I cannot do a mvn package Wayne has patiently explained to me that there is nothing to be done about this, I'm simply stuck using maven 2.0.9 forever or until by luck a subsequent release of Maven mysteriously starts letting my corporate proxy work again. Sigh. Below is the console log of my unsuccessful attempt to use 2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_aset m2 M2=C:\JavaLibs\apache-maven-2.2.0-RC3\bin M2_HOME=C:\JavaLibs\apache-maven-2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_acd simple C:\JavaLibs\aTestMaven220_rc3_a\simpledir Volume in drive C is COEv2_0 Volume Serial Number is 1428-1262 Directory of C:\JavaLibs\aTestMaven220_rc3_a\simple 06/11/2009 06:31 PM DIR . 06/11/2009 06:31 PM DIR .. 06/09/2009 12:33 PM 636 pom.xml 06/11/2009 06:29 PM DIR src 1 File(s) 636 bytes 3 Dir(s) 5,835,960,320 bytes free C:\JavaLibs\aTestMaven220_rc3_a\simplemvn -X package + Error stacktraces are turned on. Apache Maven 2.2.0-RC3 (r783569; 2009-06-10 19:26:18-0400) Java version: 1.5.0_12 Java home: C:\progfile\Java\jdk1.5.0_12\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\B1RXGC0\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\JavaLibs\apache-maven-2.2.0-RC3\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Wagons could not be registered as the extension container was never created [INFO] [INFO] Building simple [INFO]task-segment: [package] [INFO] [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:12 for project: null:maven-resources-plugin:maven-plugin:2.3 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:9 for project: org.apache.maven.plugins:maven-plugins:pom:12 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org.apache.maven:maven-parent:pom:9 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8 for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Trying repository central [DEBUG
Re: [PLEASE TEST] Maven 2.2.0-RC3
I'm feeling like a poor relation watching all the happy maven users at the banquet while I stand outside, hungry, peering in. The company I work for is pretty big. My department has started using maven and a following of developers is emerging who are asking us for advice on how to use maven in their projects as well. But maven totally stopped working at this entire company for any version higher than 2.0.9. Wayne and JDCasey have tried to be helpful, but I have not been able to actually interface with JDCasy because of the firewall at work that prevents IRC and the chat tag that is going on for days on google chat.. Can it really be that maven is so brittle that a total failure of the proxy for an entire company occurs for the mere reason that developers upgrade from maven 2.0.9 to a higher version? How can it be that the total failure of the maven proxying happens at this pretty big company and yet no one else is reporting this? This is very disheartening. Robert - Original Message From: Robert Glover robertglove...@yahoo.com To: Maven Users List users@maven.apache.org Sent: Monday, June 15, 2009 9:44:43 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 I had Friday off, so I logged onto the maven IRC channel at home via ChatZilla, but unfortunately JDCASEY was not logged on when I tried several times. I tried again on Saturday, but again JDCASEY was not online. Today, Monday, I tried from work and found that the corporate firewell blocks IRC. I've been able to use Google IM in the past through the firewall. So, I've opened up gmail and have it on the chat page. JDCASEY, if you see this please consider sending a chat message to my gmail account. My email address there is robertglove...@gmail.com Meanwhile, I'll see I I can build the source code of maven 2.2 RC3 to have log messages to pinpoint the exact line of code causing the proxy problem. --- On Fri, 6/12/09, John Casey jdca...@commonjava.org wrote: From: John Casey jdca...@commonjava.org Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 To: Maven Users List users@maven.apache.org Date: Friday, June 12, 2009, 4:18 PM Do you have the ability to join our IRC channel at irc.codehaus.org (#maven) to talk more about this? If you have a firewall/proxy in the way of an IRC connection, you might also be able to use the CGI client at http://irc.codehaus.org. From looking at your output in the original message on this thread, it seems like Maven doesn't think you're supplying any authentication information... Maybe if we could talk more about this, I could help you look for the reason behind it all. I'm on IRC most days; my nickname is 'jdcasey'. Please come find me if you have the ability, and maybe we can figure this out. Thanks, -john Robert Glover wrote: Below is the message from Wayne I was referring to. Now that I have downloaded and built maven 2.2-RC3, I guess I could put log messages into it to pin-point the exact line of code where the proxy fails. But already as it is, in running maven 2.2-RC3 it already has debug level logging turned on and is showing a lot more information than was being shown when this problem started occuring when I upgraded from maven 2.0.9 to maven 2.1. The sad thing is I have been keeping this maven proxy problem to myself because we have only been using maven for a few months. If I make it be known that it won't work and there is no solution if we upgrade to any version higher than maven 2.0.9, it is likely the managers will ban maven from being used. -- Proxy issues are, by their very nature, almost impossible for an outsider to investigate and resolve. There are literally hundreds (or more) of proxy server software packages in the world, and while they all more or less work for basic web browsing, most have issues with various pieces of software like Maven. I won't claim to know all the changes made to the Maven codebase from 2.0.9 to 2.1.0 (much less the changes in supporting utility libraries) but it would seem that some change has caused your proxy to stop working. If you seriously want to see this resolved, it will probably take some effort on your part to get Maven and all its libraries running in a debugger to try to track down what is different. Unless a ton of people start complaining about similar problems or the issue can be tracked to a specific change made in Maven (or a util library), I don't see this being resolved in any well-defined timeframe. So, I'd stick with 2.0.9 for now. Have you tried 2.0.10 yet? Wayne - Original Message From: John Casey jdca...@commonjava.org To: Maven Users List users@maven.apache.org Sent: Friday, June 12, 2009 10:38:30 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 Can you tell me what Wayne's explanation was for your
Re: [PLEASE TEST] Maven 2.2.0-RC3
Ok, I located a DSL line that does not go through the proxy. Tomorrow I'll bring in my personal laptop to work and use it to connect to the maven IRC channel at irc.codehaus.org Meanwhile, wouldn't it be nice if everyone was a good maven citizen and downloaded the maven 2.2 RC3 and tried it out-- which by the way would also be a help to see if anybody currently using maven 2.0.9 behind a firewall will discover their proxy is not being recognized any longer when they upgrade. - Original Message From: Robert Glover robertglove...@yahoo.com To: Maven Users List users@maven.apache.org Sent: Tuesday, June 16, 2009 12:05:53 PM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 I'm feeling like a poor relation watching all the happy maven users at the banquet while I stand outside, hungry, peering in. The company I work for is pretty big. My department has started using maven and a following of developers is emerging who are asking us for advice on how to use maven in their projects as well. But maven totally stopped working at this entire company for any version higher than 2.0.9. Wayne and JDCasey have tried to be helpful, but I have not been able to actually interface with JDCasy because of the firewall at work that prevents IRC and the chat tag that is going on for days on google chat.. Can it really be that maven is so brittle that a total failure of the proxy for an entire company occurs for the mere reason that developers upgrade from maven 2.0.9 to a higher version? How can it be that the total failure of the maven proxying happens at this pretty big company and yet no one else is reporting this? This is very disheartening. Robert - Original Message From: Robert Glover robertglove...@yahoo.com To: Maven Users List users@maven.apache.org Sent: Monday, June 15, 2009 9:44:43 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 I had Friday off, so I logged onto the maven IRC channel at home via ChatZilla, but unfortunately JDCASEY was not logged on when I tried several times. I tried again on Saturday, but again JDCASEY was not online. Today, Monday, I tried from work and found that the corporate firewell blocks IRC. I've been able to use Google IM in the past through the firewall. So, I've opened up gmail and have it on the chat page. JDCASEY, if you see this please consider sending a chat message to my gmail account. My email address there is robertglove...@gmail.com Meanwhile, I'll see I I can build the source code of maven 2.2 RC3 to have log messages to pinpoint the exact line of code causing the proxy problem. --- On Fri, 6/12/09, John Casey jdca...@commonjava.org wrote: From: John Casey jdca...@commonjava.org Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 To: Maven Users List users@maven.apache.org Date: Friday, June 12, 2009, 4:18 PM Do you have the ability to join our IRC channel at irc.codehaus.org (#maven) to talk more about this? If you have a firewall/proxy in the way of an IRC connection, you might also be able to use the CGI client at http://irc.codehaus.org. From looking at your output in the original message on this thread, it seems like Maven doesn't think you're supplying any authentication information... Maybe if we could talk more about this, I could help you look for the reason behind it all. I'm on IRC most days; my nickname is 'jdcasey'. Please come find me if you have the ability, and maybe we can figure this out. Thanks, -john Robert Glover wrote: Below is the message from Wayne I was referring to. Now that I have downloaded and built maven 2.2-RC3, I guess I could put log messages into it to pin-point the exact line of code where the proxy fails. But already as it is, in running maven 2.2-RC3 it already has debug level logging turned on and is showing a lot more information than was being shown when this problem started occuring when I upgraded from maven 2.0.9 to maven 2.1. The sad thing is I have been keeping this maven proxy problem to myself because we have only been using maven for a few months. If I make it be known that it won't work and there is no solution if we upgrade to any version higher than maven 2.0.9, it is likely the managers will ban maven from being used. -- Proxy issues are, by their very nature, almost impossible for an outsider to investigate and resolve. There are literally hundreds (or more) of proxy server software packages in the world, and while they all more or less work for basic web browsing, most have issues with various pieces of software like Maven. I won't claim to know all the changes made to the Maven codebase from 2.0.9 to 2.1.0 (much less the changes in supporting utility libraries) but it would seem that some change has caused your proxy to stop working. If you seriously want to see this resolved, it will probably take
Re: [PLEASE TEST] Maven 2.2.0-RC3
I had Friday off, so I logged onto the maven IRC channel at home via ChatZilla, but unfortunately JDCASEY was not logged on when I tried several times. I tried again on Saturday, but again JDCASEY was not online. Today, Monday, I tried from work and found that the corporate firewell blocks IRC. I've been able to use Google IM in the past through the firewall. So, I've opened up gmail and have it on the chat page. JDCASEY, if you see this please consider sending a chat message to my gmail account. My email address there is robertglove...@gmail.com Meanwhile, I'll see I I can build the source code of maven 2.2 RC3 to have log messages to pinpoint the exact line of code causing the proxy problem. --- On Fri, 6/12/09, John Casey jdca...@commonjava.org wrote: From: John Casey jdca...@commonjava.org Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 To: Maven Users List users@maven.apache.org Date: Friday, June 12, 2009, 4:18 PM Do you have the ability to join our IRC channel at irc.codehaus.org (#maven) to talk more about this? If you have a firewall/proxy in the way of an IRC connection, you might also be able to use the CGI client at http://irc.codehaus.org. From looking at your output in the original message on this thread, it seems like Maven doesn't think you're supplying any authentication information... Maybe if we could talk more about this, I could help you look for the reason behind it all. I'm on IRC most days; my nickname is 'jdcasey'. Please come find me if you have the ability, and maybe we can figure this out. Thanks, -john Robert Glover wrote: Below is the message from Wayne I was referring to. Now that I have downloaded and built maven 2.2-RC3, I guess I could put log messages into it to pin-point the exact line of code where the proxy fails. But already as it is, in running maven 2.2-RC3 it already has debug level logging turned on and is showing a lot more information than was being shown when this problem started occuring when I upgraded from maven 2.0.9 to maven 2.1. The sad thing is I have been keeping this maven proxy problem to myself because we have only been using maven for a few months. If I make it be known that it won't work and there is no solution if we upgrade to any version higher than maven 2.0.9, it is likely the managers will ban maven from being used. -- Proxy issues are, by their very nature, almost impossible for an outsider to investigate and resolve. There are literally hundreds (or more) of proxy server software packages in the world, and while they all more or less work for basic web browsing, most have issues with various pieces of software like Maven. I won't claim to know all the changes made to the Maven codebase from 2.0.9 to 2.1.0 (much less the changes in supporting utility libraries) but it would seem that some change has caused your proxy to stop working. If you seriously want to see this resolved, it will probably take some effort on your part to get Maven and all its libraries running in a debugger to try to track down what is different. Unless a ton of people start complaining about similar problems or the issue can be tracked to a specific change made in Maven (or a util library), I don't see this being resolved in any well-defined timeframe. So, I'd stick with 2.0.9 for now. Have you tried 2.0.10 yet? Wayne - Original Message From: John Casey jdca...@commonjava.org To: Maven Users List users@maven.apache.org Sent: Friday, June 12, 2009 10:38:30 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 Can you tell me what Wayne's explanation was for your proxy problem? Or, if Wayne's around, maybe he can chime in. I'm not familiar with this particular discussion, so I'm not sure how to help. Proxies can be incredibly hard to debug remotely, when I don't have access to probe the running system and find out where things are coming apart. -john Robert Glover wrote: The proxy error using 2.2.0-RC3 (see email below) was using the binary download. Since then, I've built 2.2.0-RC3 from source and am looking at it in Eclipse. It builds cleanly if I set it to not test; however I don't know how to run it (with it pointed to a pom.xml to build), so I'm just looking at the source code). The proxy problem I am having (see email below) is from org.apache.maven.artifact.manager.DefaultWagonManage; I can't pinpoint the exact line of source code. I cannot really take this further myself, with my level of expertise (or lack there-of), other than to have noticed that something similar to my problem is reported in a Jira that was opened around roughly the same time my problem first started happening. That Jira is: https://issues.sonatype.org/browse/NEXUS-515 I sure would be a happy camper if my
Re: [PLEASE TEST] Maven 2.2.0-RC3
Below is the message from Wayne I was referring to. Now that I have downloaded and built maven 2.2-RC3, I guess I could put log messages into it to pin-point the exact line of code where the proxy fails. But already as it is, in running maven 2.2-RC3 it already has debug level logging turned on and is showing a lot more information than was being shown when this problem started occuring when I upgraded from maven 2.0.9 to maven 2.1. The sad thing is I have been keeping this maven proxy problem to myself because we have only been using maven for a few months. If I make it be known that it won't work and there is no solution if we upgrade to any version higher than maven 2.0.9, it is likely the managers will ban maven from being used. -- Proxy issues are, by their very nature, almost impossible for an outsider to investigate and resolve. There are literally hundreds (or more) of proxy server software packages in the world, and while they all more or less work for basic web browsing, most have issues with various pieces of software like Maven. I won't claim to know all the changes made to the Maven codebase from 2.0.9 to 2.1.0 (much less the changes in supporting utility libraries) but it would seem that some change has caused your proxy to stop working. If you seriously want to see this resolved, it will probably take some effort on your part to get Maven and all its libraries running in a debugger to try to track down what is different. Unless a ton of people start complaining about similar problems or the issue can be tracked to a specific change made in Maven (or a util library), I don't see this being resolved in any well-defined timeframe. So, I'd stick with 2.0.9 for now. Have you tried 2.0.10 yet? Wayne - Original Message From: John Casey jdca...@commonjava.org To: Maven Users List users@maven.apache.org Sent: Friday, June 12, 2009 10:38:30 AM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 Can you tell me what Wayne's explanation was for your proxy problem? Or, if Wayne's around, maybe he can chime in. I'm not familiar with this particular discussion, so I'm not sure how to help. Proxies can be incredibly hard to debug remotely, when I don't have access to probe the running system and find out where things are coming apart. -john Robert Glover wrote: The proxy error using 2.2.0-RC3 (see email below) was using the binary download. Since then, I've built 2.2.0-RC3 from source and am looking at it in Eclipse. It builds cleanly if I set it to not test; however I don't know how to run it (with it pointed to a pom.xml to build), so I'm just looking at the source code). The proxy problem I am having (see email below) is from org.apache.maven.artifact.manager.DefaultWagonManage; I can't pinpoint the exact line of source code. I cannot really take this further myself, with my level of expertise (or lack there-of), other than to have noticed that something similar to my problem is reported in a Jira that was opened around roughly the same time my problem first started happening. That Jira is: https://issues.sonatype.org/browse/NEXUS-515 I sure would be a happy camper if my meager contribution here could motivate someone to figure out how to get my proxy to work. A solution seems so tantalizingly close. For example, if I could compare the source code of the 2.0.9 version of DefaultWagManager to the source code version of it in later versions. From: Robert Glover robertglove...@yahoo.com mailto:robertglove...@yahoo.com To: Maven Users List users@maven.apache.org mailto:users@maven.apache.org Sent: Thursday, June 11, 2009 6:44:06 PM Subject: Re: [PLEASE TEST] Maven 2.2.0-RC3 I downloaded apache-maven-2.2.0-RC3 and tried it out but sadly, I get the same proxy problem I have been getting in all versions of maven subsequent to 2.0.9. Maven 2.0.9 continues to work fine, but if I change to 2.2.0.RC3 and use the same pom.xml file and the same settings.xml file (where the proxy config is) it causes a proxy error and I cannot do a mvn package Wayne has patiently explained to me that there is nothing to be done about this, I'm simply stuck using maven 2.0.9 forever or until by luck a subsequent release of Maven mysteriously starts letting my corporate proxy work again. Sigh. Below is the console log of my unsuccessful attempt to use 2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_aset m2 M2=C:\JavaLibs\apache-maven-2.2.0-RC3\bin M2_HOME=C:\JavaLibs\apache-maven-2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_acd simple C:\JavaLibs\aTestMaven220_rc3_a\simpledir Volume in drive C is COEv2_0 Volume Serial Number is 1428-1262 Directory of C:\JavaLibs\aTestMaven220_rc3_a\simple 06/11/2009 06:31 PMDIR . 06/11/2009 06:31 PMDIR .. 06/09/2009 12:33 PM 636 pom.xml 06/11/2009
Re: dependency management in sub-sub-module
I'm new to Maven so take this with a grain of salt, but I don't see why you can't just do: ...snip... modules modulemodule1/module modulemodule2/module moduleclient1/module moduleclient2/module /modules ...snip... From: Markus Jostock markus.jost...@softwareag.com To: Maven Users List users@maven.apache.org Sent: Thursday, June 11, 2009 8:17:01 AM Subject: dependency management in sub-sub-module Dear all I have module structure with two levels of sub-modules. The root level pom defines a dependency managment section which is working fine for sub-modules. But for a deeper level, the dependency management section of the root pom apparently is not available any more ... root +- module1 -- working fine +- module2 -- working fine +- clients +- client1 -- compile errors ... +- client2 -- compile errors ... During build, the system does not complain about unsatisfied dependencies, but in the compile phase the compiler cannot find the symbols. Would anyone have an idea what I could be doing wrong here? Any advice would be gratefully appreciated ... Many, many thanks! Markus root-pom: === project modelVersion4.0.0/modelVersion groupIdmy.groupid/groupId artifactIdroot/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameMy Project/name modules modulemodule1/module modulemodule2/module moduleclients/module /modules dependencyManagement dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId version1.8.0/version scopecompile/scope /dependency ... /dependencyManagement /project clients-pom: project modelVersion4.0.0/modelVersion parent artifactIdroot/artifactId groupIdmy.groupid/groupId version1.0-SNAPSHOT/version /parent artifactIdclients/artifactId nameMy Clients/name packagingpom/packaging modules moduleclient1/module moduleclient2/module /modules /project client1-pom: project modelVersion4.0.0/modelVersion parent artifactIdclients/artifactId groupIdmy.groupId/groupId version1.0-SNAPSHOT/version /parent artifactIdclient1/artifactId nameMy Client 1/name dependencies dependency groupIdcommons-beanutils/groupId artifactIdcommons-beanutils/artifactId scopecompile/scope /dependency ... /dependencies /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: About resource folder in Maven structure
I have to respond from the perspective of a maven user, because that's me. When I do what you asked about, I manually add the resources directory and manually put into it what I think should be there. The key lesson I learned the hard way is that the java directory can only contain .java files. If you put xml files or property files or velocity template files into the java directory, they will not become part of the target or the jar file in the target. They MUST be placed in the resources directory or else maven will not put them into target. I have no experience with META-INF so your guess is as good as Mine. (My guess is you should manually add it). From: dr_pompeii dr_pomp...@yahoo.com To: users@maven.apache.org Sent: Thursday, June 11, 2009 5:13:55 PM Subject: About resource folder in Maven structure Dear Members I know how to create a default project according to maven structure like mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app and work without problem, but in this link http://maven.apache.org/guides/getting-started/index.html I see this structure, specially the bold part (I need these folders) my-app |-- pom.xml `-- src |-- main | |-- java | | `-- com | | `-- mycompany | | `-- app | | `-- App.java | `-- resources | `-- META-INF | `-- application.properties `-- test `-- java `-- com `-- mycompany `-- app `-- AppTest.java The comand mvn archetype:create (already written above) doesnt create neither resources nor META-INF folders Therefore Must I do this by hand? or is there a special command to have these folders in the structure? Thanks in advanced -- View this message in context: http://www.nabble.com/About-resource-folder-in-Maven-structure-tp23989113p23989113.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
Re: [PLEASE TEST] Maven 2.2.0-RC3
I downloaded apache-maven-2.2.0-RC3 and tried it out but sadly, I get the same proxy problem I have been getting in all versions of maven subsequent to 2.0.9. Maven 2.0.9 continues to work fine, but if I change to 2.2.0.RC3 and use the same pom.xml file and the same settings.xml file (where the proxy config is) it causes a proxy error and I cannot do a mvn package Wayne has patiently explained to me that there is nothing to be done about this, I'm simply stuck using maven 2.0.9 forever or until by luck a subsequent release of Maven mysteriously starts letting my corporate proxy work again. Sigh. Below is the console log of my unsuccessful attempt to use 2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_aset m2 M2=C:\JavaLibs\apache-maven-2.2.0-RC3\bin M2_HOME=C:\JavaLibs\apache-maven-2.2.0-RC3 C:\JavaLibs\aTestMaven220_rc3_acd simple C:\JavaLibs\aTestMaven220_rc3_a\simpledir Volume in drive C is COEv2_0 Volume Serial Number is 1428-1262 Directory of C:\JavaLibs\aTestMaven220_rc3_a\simple 06/11/2009 06:31 PMDIR . 06/11/2009 06:31 PMDIR .. 06/09/2009 12:33 PM 636 pom.xml 06/11/2009 06:29 PMDIR src 1 File(s)636 bytes 3 Dir(s) 5,835,960,320 bytes free C:\JavaLibs\aTestMaven220_rc3_a\simplemvn -X package + Error stacktraces are turned on. Apache Maven 2.2.0-RC3 (r783569; 2009-06-10 19:26:18-0400) Java version: 1.5.0_12 Java home: C:\progfile\Java\jdk1.5.0_12\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\B1RXGC0\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\JavaLibs\apache-maven-2.2.0-RC3\conf\plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Wagons could not be registered as the extension container was never created [INFO] [INFO] Building simple [INFO]task-segment: [package] [INFO] [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:12 for project: null:maven-resources-plugin:maven-plugin:2.3 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:9 for project: org.apache.maven.plugins:maven-plugins:pom:12 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org.apache.maven:maven-parent:pom:9 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:8 for project: null:maven-compiler-plugin:maven-plugin:2.0.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:5 for project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Trying repository central [DEBUG] Checking for pre-existing User-Agent configuration. [DEBUG] Adding User-Agent configuration. [DEBUG] Connecting to repository: 'central' with url: 'http://repo1.maven.org/maven2'. [DEBUG] Using Proxy: b1web1.frb.org Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom Jun 11, 2009 6:35:12 PM hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost WARNING: Required credentials not available for BASIC any realm@repo1.maven.org:80 Jun 11, 2009 6:35:12 PM hidden.org.apache.commons.httpclient.HttpMethodDirector authenticateHost WARNING: Preemptive authentication requested but no default credentials available [DEBUG] http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom - Status code: 403 [DEBUG] Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:510) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:327) at
Re: mvn test -DproxyHost=... -DproxyPort=...
I'm having the same problem. Below I paste the error message I get. (I posted this a few days earlier as well). Is this similar to the error you receive? (Note you need to use the -X option on the mvn command you are using to make the expanded console output appear so that you can see if you too get this error message). ...snip... [DEBUG] Connecting to repository: 'central' with url: 'http://repo1.maven.org/maven2'. [DEBUG] Using Proxy: b1web1.obfuscated.org Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom [DEBUG] Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:119) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372) ...snip... - Original Message From: Paolo Castagna paolo.casta...@hplb.hpl.hp.com To: users@maven.apache.org users@maven.apache.org Sent: Wednesday, June 10, 2009 4:33:20 AM Subject: mvn test -DproxyHost=... -DproxyPort=... Hi, I need to run a test suite which needs to connect to public web servers and I am behind a web proxy. I use: mvn test -DproxyHost=... -DproxyPort=... mvn test -DproxySet=true -DproxyHost=... -DproxyPort=... Everything works fine with Maven v2.0.9 but with Maven v2.0.10 or v2.1.0 seems to me that the proxy does not get used. I am probably missing something obvious... Any help? Paolo - 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: mvn test -DproxyHost=... -DproxyPort=...
Hi Paolo, Thanks for the reply back. Actually, the group had told me earlier that unless a number of people experienced the same problem I was having, it is unrealistic to expect a resolution because proxy issues are so difficult to figure out. But to answer your question, I use the same proxy config within settings.xml. When I use maven 2.0.9 the proxy works fine. However when I change to maven 2.1.0 (or also, I think but it's been a while so I'm not 100% sure, also with 2.0.10) the proxy fails. The only solution for me is to stick with maven 2.0.9. When each new version of maven comes out (I think maven 3 may be the next one to come out?), I'll give it a try. When a future version works for me, I'll upgrade then. My guess is that m2eclipse (the maven eclipse plugin) uses an embedded version of maven and so maybe is not affected by what version of maven I use. that is just a guess. m2eclipse continues to work fine even when I upgrade to maven 2.1.0. I wonder if that is significant or not? Robert - Original Message From: Paolo Castagna paolo.casta...@hplb.hpl.hp.com To: Maven Users List users@maven.apache.org Sent: Wednesday, June 10, 2009 9:52:52 AM Subject: Re: mvn test -DproxyHost=... -DproxyPort=... Hi Robert, thank you for your reply. But, no... I do not see any access denied problem when I run Maven in debug mode. It definitely downloaded the surefire plugin v2.4.3 and the plugin is used to run the tests. However, it seems to me that the plugin is ignoring the -DproxyHost=... and -DproxyPort=... options. Are you sure you have properly configured your web proxy in $MAVEN_HOME/conf/settings.xml ? Your problem is different: Maven is not able to download the surefire plugin using your web proxy. Paolo Robert Glover wrote: I'm having the same problem. Below I paste the error message I get. (I posted this a few days earlier as well). Is this similar to the error you receive? (Note you need to use the -X option on the mvn command you are using to make the expanded console output appear so that you can see if you too get this error message). ...snip... [DEBUG] Connecting to repository: 'central' with url: 'http://repo1.maven.org/maven2'. [DEBUG] Using Proxy: b1web1.obfuscated.org Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom [DEBUG] Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:119) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:491) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372) ...snip... - Original Message From: Paolo Castagna paolo.casta...@hplb.hpl.hp.com To: users@maven.apache.org users@maven.apache.org Sent: Wednesday, June 10, 2009 4:33:20 AM Subject: mvn test -DproxyHost=... -DproxyPort=... Hi, I need to run a test suite which needs to connect to public web servers and I am behind a web proxy. I use: mvn test -DproxyHost=... -DproxyPort=... mvn test -DproxySet=true -DproxyHost=... -DproxyPort=... Everything works fine with Maven v2.0.9 but with Maven v2.0.10 or v2.1.0 seems to me that the proxy does not get used. I am probably missing something obvious... Any help? Paolo - 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: How to skip install of war in multi-module project?
I'm a new to maven which may be why I think I know the answer. For a while in the beginning of my maven usage in the same situation as yours I was doing mvn install like you are. Then I discovered that mvn package was sufficient since all I wanted was for the war file to be in the target directory, not copied to the local repository. From: Jesfre jesfre...@gmail.com To: users@maven.apache.org Sent: Wednesday, June 10, 2009 6:17:42 PM Subject: How to skip install of war in multi-module project? Hi everybody... I have a multi-module project wich contains modules wich generates jar files and war files, but when I run mvn install on the parent pom.xml, this installs the war files in the local repository. So, how can I skip the installation of the war files in the parent pom.xml? Thanks in advance... -- View this message in context: http://www.nabble.com/How-to-skip-install-of-war-in-multi-module-project--tp23972182p23972182.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
Re: follow to: problem upgrading from maven 2.0.9 to 2.1
) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:518) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build project for plugin 'org.apache.maven.plugins:maven-surefire-plugin': POM 'org.apache.maven.plugins:maven-surefire-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.apache.maven.plugins:maven-surefire-plugin at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:286) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1517) ... 18 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven.plugins:maven-surefire-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.apache.maven.plugins:maven-surefire-plugin at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:270) ... 21 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558) ... 23 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:349) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216) ... 25 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue Jun 09 12:46:44 EDT 2009 [INFO] Final Memory: 2M/4M [INFO] From: Baptiste MATHUS m...@batmat.net To: Maven Users List users@maven.apache.org Sent: Monday, June 8, 2009 2:31:41 PM Subject: Re: follow to: problem upgrading from maven 2.0.9 to 2.1 Maybe unrelated, but your java_home seems to point to a jre, not a jdk. It seems abnormal to me, although I don't see how it could be related to your authentication problem. Are you sure you're using the very same Java_home between both maven installations? And btw, I guess diff'ing mvn help:effective-settings and help:effective-pom between the two installs could also provide you with some hints. Cheers. 2009/6/8 Robert Glover robertglove...@yahoo.com Try again with mvn -X package and see what that says. Paste the output to www.pastebin.org and send us the link I can't connect to www.pastebin.org, so
Re: follow to: problem upgrading from maven 2.0.9 to 2.1
I believe your problem must lie within your proxy: I was overly glib in wrongly implying this problem is recreate-able in shops where maven 2.1.0 is working okay. I simply meant it always happens to me at work, even when the pom file is the simplest possible. I agree with you that the proxy is the key to this. However the only control I am aware of that I have over the proxy is in settings.xml. Below is what I have in settings.xml. It's the same settings.xml I use with maven 2.0.9, where it works fine. The proxy does not use or need a username/password, even though I specify dummies for it in settings.xml. I was thinking maybe that maven 2.1.0 fails because of the dummy username/password below in settings.xml, even though with maven 2.0.9 it does not care that there are a dummy username/password. I've been stumped by this for going on a month. There was something in the release notes of 2.1.0 about the active tag in settings.xml being misleading, but it did not explain if anything was actually changed. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | -- proxy idoptional/id activetrue/active protocolhttp/protocol usernameproxyuser/username passwordproxypass/password hostb1web1.obfuscated.org/host port8080/port nonProxyHostsb1bsdzv03/nonProxyHosts /proxy /proxies - Original Message From: Wayne Fay wayne...@gmail.com To: Maven Users List users@maven.apache.org Sent: Tuesday, June 9, 2009 2:58:58 PM Subject: Re: follow to: problem upgrading from maven 2.0.9 to 2.1 I followed your directions exactly and got the following results: [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 26 seconds [INFO] Finished at: Tue Jun 09 11:56:19 PDT 2009 [INFO] Final Memory: 8M/22M [INFO] I believe your problem must lie within your proxy: [DEBUG] Using Proxy: b1web1.obfuscated.org Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom [DEBUG] Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.4.3/maven-surefire-plugin-2.4.3.pom Wayne On Tue, Jun 9, 2009 at 9:53 AM, Robert Gloverrobertglove...@yahoo.com wrote: I've reduced the problem of why I can't upgrade from maven 2.0.9 to to 2.1.0 to it's barest essentials. For my recreatable test, I am using the instructions in chapter 3 of Maven: The Definitive Guide from the section Creating a Simple Project. Note as I detail the steps below that these exact same steps work perfectly when I point M2, M2_Home, and PATH to maven 2.0.9. They fail however when I point to 2.1.0.Please also note that this problem is total, by which I mean that there are no situations in which maven 2.1.0 is working, yet in all these same situations maven 2.0.9 is working okay. I even tried this on another developer machine which had never had maven installed on it before, and maven 2.1.0 failed there too. Step one of six: create new directory. Step two of six: open Dos window, make that directory current. Step three of six: invoke this bat file: set M2_HOME=C:\JavaLibs\apache-maven-2.1.0 set M2=C:\JavaLibs\apache-maven-2.1.0\bin set PATH=C:\JavaLibs\apache-maven-2.1.0\bin;%PATH% step four of six) issue this command (note: because I already did this test with maven 2.0.9, it does not need to get anything from local repository). mvn archetype:create -DgroupId=org.foo.bar -DartifactId=simple -DpackageName=org.foo.bar (output is shown below) C:\JavaLibs\aTestMaven210bXmvn archetype:create -DgroupId=org.foo.bar -DartifactId=simple -DpackageName=org.foo.bar - 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: $JAVA_HOME ignored?
I'm a new maven user starting the journey up the maven learning curve. I recall reading in the free Maven book that by default Maven sets itself to java 1.3. But I'm not sure if I'm recalling that correctly. If it's not 1.3 then it is certainly 1.4. It is definately not 1.5. From: Elliot Huntington elliot.hunting...@gmail.com To: users@maven.apache.org Sent: Tuesday, June 9, 2009 5:49:28 PM Subject: $JAVA_HOME ignored? Hi everyone, Following the installation instructions for Maven, I set my JAVA_HOME environment variable to point to my Java 5 directory. Why is it then that in order to have maven compile my project for 1.5 I need to use the following? build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /pluginManagement /build Thanks, Elliot - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
follow to: problem upgrading from maven 2.0.9 to 2.1
by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.maven.plugins:maven-surefire-plugin' not found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), TSS-snapshots (http://b1bsdzv03:8080/artifactory/repo), TSS-central (http://b1bsdzv03:8080/artifactory/repo) for project org.apache.maven.plugins:maven-surefire-plugin at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251) at org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:270) ... 21 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.4.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), TSS-snapshots (http://b1bsdzv03:8080/artifactory/repo), TSS-central (http://b1bsdzv03:8080/artifactory/repo) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558) ... 23 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:349) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216) ... 25 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Mon Jun 08 13:20:04 EDT 2009 [INFO] Final Memory: 2M/4M [INFO] But if I execute the identical mvn package but with m2, m2_home, and path all pointing to maven 2.1, I get a quick build failure that says there is an authentication problem trying to access the maven repo1 repository. Try again with mvn -X package and see what that says. Paste the output to www.pastebin.org and send us the link if you can't sort it out from the debug output. Wayne - Forwarded Message From: Robert Glover robertglove...@yahoo.com To: Maven Users List users@maven.apache.org Sent: Thursday, June 4, 2009 6:50:35 PM Subject: problem upgrading from maven 2.0.9 to 2.1 I'm at my wits end over this. Working behind a corporate firewall, my mvn package command works perfectly when m2 and m2_home and path all point to maven 2.0.9. But if I execute the identical mvn package but with m2, m2_home, and path all pointing to maven 2.1, I get a quick build failure that says there is an authentication problem trying to access the maven repo1 repository. I'm at home and so can't paste the exact error message.
problem upgrading from maven 2.0.9 to 2.1
I'm at my wits end over this. Working behind a corporate firewall, my mvn package command works perfectly when m2 and m2_home and path all point to maven 2.0.9. But if I execute the identical mvn package but with m2, m2_home, and path all pointing to maven 2.1, I get a quick build failure that says there is an authentication problem trying to access the maven repo1 repository. I'm at home and so can't paste the exact error message.
