RE: Reproducing a former build with exact dependencies but version ranges in the POM
Hi Stephen, thanks - I'll investigate here. Kind regards Andreas -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Mittwoch, 16. Dezember 2009 11:34 To: Maven Users List Subject: Re: Reproducing a former build with exact dependencies but version ranges in the POM have a look at versions-maven-plugin it has some goals which might help you -Stephen 2009/12/16 Heix, Andreas andreas.h...@sap.com Hi Anders, thanks - that's also the only thing I found. I just hoped for a more flexible way to do it. So I'll have to dig deeper... Kind regards Andreas -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Mittwoch, 16. Dezember 2009 08:09 To: Maven Users List Subject: Re: Reproducing a former build with exact dependencies but version ranges in the POM The only way (that I know of) to ensure a reproducable build is to lock down all versions in your pom. This includes plugins as well as dependencies. /Anders On Tue, Dec 15, 2009 at 10:48, Heix, Andreas andreas.h...@sap.com wrote: Hi, for development we want to use dependency version ranges within our poms. As soon as we release a project for each artifact a certain version is used in this build. At a later point in time we want to reproduce exactly the same build result without changing the poms which still contain version ranges. But very likely the content of our repositories will have changed: meanwhile e.g. newer versions of certain artifacts are available. We can retrieve the list of used dependencies and plugins via mvn dependency:resolve mvn dependency:resolve-plugins. Is there a chance to use this list as kind of 'whitelist'? It would specify the exact versions of the dependencies instead of letting maven resolve the best fit in future builds? Kind regards - 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: enforce dependency to be set to provided
This doesn't work. Scope cannot be specified yet. Please see http://jira.codehaus.org/browse/MENFORCER-72 Cheers. 2009/12/17 Marco Beelen mbee...@iprofs.nl Hello, For my portal I'm going to write various web-application and I want them to reuse various libraries provided by my portal server. All the webapp project have the same parent. In order to prevent the webapps to include the dependency in the WEB-INF\lib, I wan't to configure a rule in the parent pom, where I ban some library (log4j:log4j). The webapp are allowed to use the dependency, but only when the scope is set to provided. I tried the bannedDependency configuration like this: bannedDependencies searchTransitivetrue/searchTransitive excludes excludelog4j:log4j/exclude /excludes includes includelog4j:log4j:*:provided/include /includes /bannedDependencies That doesn't work, because when I build a webapp with the log4j dependency on compile scope, the enforcer plugin doesn't cause my build to fail, which I would like it to. Any suggestions how to handle this? With kind regards, Marco Marco Beelen Software-architect +31(0)6 55 145 554 IPROFS Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nlhttp://www.iprofs.nl/ +31 (0)23 547 6369 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Mojo configuration question--share object?
I have a Mojo I'm developing. As part of its configuration it takes two objects. I'd like to use the same instance of an object for the value of both parameters. How do I do this? For example, suppose I have an object, C, that implements both A and B. And suppose my mojo has a private A a field, and a private B b field. I'd like, somehow, to create a C, configure it, and pass it in as the value of both the a and the b field. I suspect that I need to use the @component annotation somehow--this sounds like depending on a Plexus component--but I'm not sure how to get C registered as a Plexus component from a Mojo's configuration. Thanks, Laird
Re: Batch releasing many projects in Maven. Is it possible?
Hi Paul, had a similar situation which I temporarily this week +) all variable version are expressed as properties in the M2 pom +) wrote a little ANT script based on regexp task to replace the variable with the expanded values if this helps I can send you the script as a starting point Cheers, Siegfried Goeschl Paul Benedict wrote: Thanks Stephen. It looks like this feature isn't handled by Maven yet. These aren't parent-child projects, so it appears I have to remain doing it manually. Paul On Thu, Dec 17, 2009 at 12:28 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#commitByProject might be a property that could help 2009/12/17 Stephen Connolly stephen.alan.conno...@gmail.com depends on how your scm's are organised... 2009/12/17 Paul Benedict pbened...@apache.org My work situation is similar to what I learned about Eclipse. There's a release train in which 10-20 projects -- with dependencies on each other -- have to be versioned, built, and deployed. It's extremely tedious manually do this in the console. Can Maven provide any alleviation? Ideally, I would write a project (type pom) with all the projects as dependencies that I want to batch release, and let the Maven Release Plugin take care of things. Possible or a dream? Paul - 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
[SURVEY] Which plugins would you like us to release?
Hello everyone This is the second time I'm sending out this survey. Based on feedback from last time, you can now select multiple answers. The survey is to get a feel for what you, our users, want us to do next when it comes to plugin releases. This is *not* about fixing issues - it's about getting already fixed issues released. Please help us help you, by answering this survey at http://www.surveymonkey.com/s/QHYJV9P On the page below you can find links to JIRA (our issue tracker) for all of the plugins that are in the survey. http://maven.apache.org/plugins/index.html -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
release plugin: version change not only in POMs ?
Hello. Recently I've got acquainted with the release plugin. I started using it, it works great but I am missing one feature. The problem is the following: the version that is specified in a POM is used not only in this POM but also in another place in a plain-text format. Actually it is used in the MANIFEST.MF in the special header. So when I perform a release the release version have the new version, the trunk version gets the new y-SNAPSHOT version but that MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both in trunk and in the release. What I want is two steps to be executed while release:perform (phrases in quotes are taken from here http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html ): - The first is after the step Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use): the same transformation must be done with the text file that I specify. - The second is after the step Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for): the same transformation must be done with text file that I specify. How can I achieve this? Thank you. -- С уважением, Григорий Пташко +7 (916) 1489766 gptas...@cmmt.ru http://www.cmmt.ru
Re: [SURVEY] Which plugins would you like us to release?
Hi It is great to see that there are already 13 responses to the survey. However I see the need to clarify thing further. The plugin with most votes at this time is the Assembly Plugin. The only problem is that the Assembly Plugin has 0 (zero) issues that are solved, that has not been released yet. So voting for that plugin is pointless. A new release isn't going to happen if there are no issues solved. Please have a look in JIRA before taking the survey. Look at the Road Map tab for each plugin and look at the issues solved for the next release. If you see *solved* issues there that you need to have released, then do vote for that plugin. If you have an issue that has *not* been solved, the best way to let us know that is to go and vote for that *issue* in JIRA. Thanks Dennis Lundberg wrote: Hello everyone This is the second time I'm sending out this survey. Based on feedback from last time, you can now select multiple answers. The survey is to get a feel for what you, our users, want us to do next when it comes to plugin releases. This is *not* about fixing issues - it's about getting already fixed issues released. Please help us help you, by answering this survey at http://www.surveymonkey.com/s/QHYJV9P On the page below you can find links to JIRA (our issue tracker) for all of the plugins that are in the survey. http://maven.apache.org/plugins/index.html -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Sharing files between modules within the same project, for use by sql-maven-plugin
Hi I'm facing a problem sharing files between modules. We have a multi module build where several of the modules have database tests that use the sql-maven-plugin to set up a test database. These modules needs to share two files: a DDL file that creates the tables and an SQL file that populates the tables. We don't want to have multiple copies of these files in different modules, for obvious reasons. After browsing the web for examples of sharing resources between modules, I tried one where you put the files to be shared in a new module. They go into the directory src/main/resources. Then each module that needs the files just adds a dependency on the new module. The problem with that approach is that the files are then class path resources, which the sql-maven-plugin is not able to see. It seems to only be able use files within the current module. Is there another way we can do this? Would it be possible to patch the sql-maven-plugin to be able to read class path resources as files? Are there any examples of other plugins that do this? -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sharing files between modules within the same project, for use by sql-maven-plugin
Hi, I guess you could patch the sql-plugin, but maybe you should use the maven-dependency-plugin[1] to unpack your new module for the tests. Then the sql-plugin can just read the unpacked file and you don't need to patch anything. [1] http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html Roland Hi I'm facing a problem sharing files between modules. We have a multi module build where several of the modules have database tests that use the sql-maven-plugin to set up a test database. These modules needs to share two files: a DDL file that creates the tables and an SQL file that populates the tables. We don't want to have multiple copies of these files in different modules, for obvious reasons. After browsing the web for examples of sharing resources between modules, I tried one where you put the files to be shared in a new module. They go into the directory src/main/resources. Then each module that needs the files just adds a dependency on the new module. The problem with that approach is that the files are then class path resources, which the sql-maven-plugin is not able to see. It seems to only be able use files within the current module. Is there another way we can do this? Would it be possible to patch the sql-maven-plugin to be able to read class path resources as files? Are there any examples of other plugins that do this? -- Dennis Lundberg - 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: release plugin: version change not only in POMs ?
You should try to go about this in another way. Instead of having the version explicitly in text files, you should filter these files using the Resources Plugin. See http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html As for the example of the manifest file, you should let the JAR Plugin handle the version in there instead of managing it yourself. See http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html and http://maven.apache.org/shared/maven-archiver/index.html Grigory Ptashko wrote: Hello. Recently I've got acquainted with the release plugin. I started using it, it works great but I am missing one feature. The problem is the following: the version that is specified in a POM is used not only in this POM but also in another place in a plain-text format. Actually it is used in the MANIFEST.MF in the special header. So when I perform a release the release version have the new version, the trunk version gets the new y-SNAPSHOT version but that MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both in trunk and in the release. What I want is two steps to be executed while release:perform (phrases in quotes are taken from here http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html ): - The first is after the step Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use): the same transformation must be done with the text file that I specify. - The second is after the step Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for): the same transformation must be done with text file that I specify. How can I achieve this? Thank you. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: version change not only in POMs ?
Sorry for the mess but actually this is not directly the MANIFEST file. It is a file used by other plugin to create the MANIFEST file. I am talking about the pax plugin and osgi.bnd file which must reside in the root of the maven project along with the pom.xml. This file is a not resource, it is not going to the jar at all. It is like a config file for the pax plugin. And it is a text file. I read the info in the link about the resources plugin - it is exactly what I need but without packing this file to the resulting jar and it must not go to the target directory during the build process. 19 декабря 2009 г. 0:45 пользователь Dennis Lundberg denn...@apache.orgнаписал: You should try to go about this in another way. Instead of having the version explicitly in text files, you should filter these files using the Resources Plugin. See http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html As for the example of the manifest file, you should let the JAR Plugin handle the version in there instead of managing it yourself. See http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html and http://maven.apache.org/shared/maven-archiver/index.html Grigory Ptashko wrote: Hello. Recently I've got acquainted with the release plugin. I started using it, it works great but I am missing one feature. The problem is the following: the version that is specified in a POM is used not only in this POM but also in another place in a plain-text format. Actually it is used in the MANIFEST.MF in the special header. So when I perform a release the release version have the new version, the trunk version gets the new y-SNAPSHOT version but that MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both in trunk and in the release. What I want is two steps to be executed while release:perform (phrases in quotes are taken from here http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html ): - The first is after the step Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use): the same transformation must be done with the text file that I specify. - The second is after the step Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for): the same transformation must be done with text file that I specify. How can I achieve this? Thank you. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- С уважением, Григорий Пташко +7 (916) 1489766 gptas...@cmmt.ru http://www.cmmt.ru
Re: [SURVEY] Which plugins would you like us to release?
On Fri, Dec 18, 2009 at 2:15 PM, Dennis Lundberg denn...@apache.org wrote: Please have a look in JIRA before taking the survey. Look at the Road Map tab for each plugin and look at the issues solved for the next release. If you see *solved* issues there that you need to have released, then do vote for that plugin. At one point we had a report that sorted the plugins by the total number of votes for resolved-but-unreleased issues. It was a Swizzle/JIRA thing, I remember working on it... anyone know where it is and whether it's being published? -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: version change not only in POMs ?
Hi, Sorry, didn't read the mail good enough and made some errors in my previous reply! - Put your files in src/main/config with the variables configured - Have the resource-plugin copyfilter them to the root of the project (make sure this is done before the pax-plugin runs) If you use the clean-plugin, it would be a good idea to put the 2 files in the root of the project in the list of files to delete as well! Roland Sorry for the mess but actually this is not directly the MANIFEST file. It is a file used by other plugin to create the MANIFEST file. I am talking about the pax plugin and osgi.bnd file which must reside in the root of the maven project along with the pom.xml. This file is a not resource, it is not going to the jar at all. It is like a config file for the pax plugin. And it is a text file. I read the info in the link about the resources plugin - it is exactly what I need but without packing this file to the resulting jar and it must not go to the target directory during the build process. 19 ÄÅËÁÂÒÑ 2009 Ç. 0:45 ÐÏÌØÚÏ×ÁÔÅÌØ Dennis Lundberg denn...@apache.orgÎÁÐÉÓÁÌ: You should try to go about this in another way. Instead of having the version explicitly in text files, you should filter these files using the Resources Plugin. See http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html As for the example of the manifest file, you should let the JAR Plugin handle the version in there instead of managing it yourself. See http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html and http://maven.apache.org/shared/maven-archiver/index.html Grigory Ptashko wrote: Hello. Recently I've got acquainted with the release plugin. I started using it, it works great but I am missing one feature. The problem is the following: the version that is specified in a POM is used not only in this POM but also in another place in a plain-text format. Actually it is used in the MANIFEST.MF in the special header. So when I perform a release the release version have the new version, the trunk version gets the new y-SNAPSHOT version but that MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both in trunk and in the release. What I want is two steps to be executed while release:perform (phrases in quotes are taken from here http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html ): - The first is after the step Change the version in the poms from x-SNAPSHOT to a new version (you will be prompted for the versions to use): the same transformation must be done with the text file that I specify. - The second is after the step Bump the version in the POMs to a new value y-SNAPSHOT (these values will also be prompted for): the same transformation must be done with text file that I specify. How can I achieve this? Thank you. -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- ó Õ×ÁÖÅÎÉÅÍ, çÒÉÇÏÒÉÊ ðÔÁÛËÏ +7 (916) 1489766 gptas...@cmmt.ru http://www.cmmt.ru - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [SURVEY] Which plugins would you like us to release?
Wendy Smoak wrote: On Fri, Dec 18, 2009 at 2:15 PM, Dennis Lundberg denn...@apache.org wrote: Please have a look in JIRA before taking the survey. Look at the Road Map tab for each plugin and look at the issues solved for the next release. If you see *solved* issues there that you need to have released, then do vote for that plugin. At one point we had a report that sorted the plugins by the total number of votes for resolved-but-unreleased issues. It was a Swizzle/JIRA thing, I remember working on it... anyone know where it is and whether it's being published? Someone set it up on the grid, but it doesn't seem to build any more. https://grid.sonatype.org/ci/job/Plugins%20Fixed%20Report/ -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 deprecated properties
Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo.
Re: Maven 3 deprecated properties
Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How can I automate the testing of my archetype? Maven Build from TestNG?
Hello All, Does anyone have advice on automating the testing of an archetype? I am a community volunteer helping out the JBoss folks with their Weld Java EE 6 archetypes. I currently have a bash script I use to test it, but it requires *NIX and presently requires manually running a selenium test. I'd like to automate it so Hudson can catch my mistakes. Surely I am not the first guy who built an archetype and wanted to test it from Continuous Integration, has someone already solved this problem? I would guess the ideal would be to have a TestNG/JUnit test that does the following: 1. Create new project from archetype in memory or a temp directory somewhere. It won't be needed once the test has finished running. 2. Run maven commands on the new project (mvn test jetty:run) to confirm the unit tests pass. 3. Trigger an HttpUnit test to confirm the JSF code renders correctly. If there's no pre-canned solution to this problem, how difficult would it be to have one project run maven from TestNG to trigger the archetype:generate and then a maven build from JUnit or TestNG? Thanks in advance, Steven -- View this message in context: http://old.nabble.com/How-can-I-automate-the-testing-of-my-archetype---Maven-Build-from-TestNG--tp26850764p26850764.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
java 1.4 versus the maven-eclipse-plugin
The eclipse plugin forces the compiler source version to 1.4 for maven plugins. I'm building a maven plugin that I want to require 1.5. Is there a way to tell the eclipse plugin to stop harassing me? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mojo with a default execution
So, I have a Mojo class with this comment block: /** * @description Generate java code with Velocity. * @goal generate * @phase generate-sources * @requiresProject true */ I put this plugin in buildplugins in a pom, and I run 'mvn generate-sources'. I get ... [INFO] [INFO] No goals needed for project - skipping [INFO] [INFO] BUILD SUCCESSFUL - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo with a default execution
I put this plugin in buildplugins in a pom, and I run 'mvn generate-sources'. What's the pom entry look like? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo with a default execution
When it didn't work, just plugin groupId/ artifactId/ version/ plugin No executions, since I thought the @goal + @phase in the comment would produce a default execution. If I add an execution with my goal in it, it indeed binds to the correct phase. On Fri, Dec 18, 2009 at 9:22 PM, Wayne Fay wayne...@gmail.com wrote: I put this plugin in buildplugins in a pom, and I run 'mvn generate-sources'. What's the pom entry look like? 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
archetype appfuse-modular-jsf-archetype
Can anyone help me? When I try to run this project on the server, in eclipse, I get a 404 and the page the project tries to load is index.html, the welcome file is index.jsp and there is a index.jsp in the webapps directory. Anyhow, I get a 404. Thanks, Sonia - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 deprecated properties
Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - 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: authentication problem to nexus repository with non-anonymous user
Could you try using the admin user instead of the deployment user? If that works then we know maven is getting the credentials through to Nexus. If not, then there's still some problem on the maven side. 2009/12/8 irfan irfango...@gmail.com: Hi; I build my project with maven 2.1.0, which has some dependencies on nexus(1.4.0) repository. When I enable anonymous user in nexus, maven can download necessary artifacts as expected but if i disable anonymous user maven cannot download the artifacts. I mailed to nexus forums but they decided that somehow maven cannot send user credentials to nexus to authenticate. My mails can be followed from http://old.nabble.com/settings.xml-for-non-anonymous-user-td22150250.html here is my settings.xml and maven debug logs: thanks. *settings.xml * settings localRepositoryc:/dev/tools_data/maven_local_repo/localRepository proxies /proxies pluginGroups pluginGrouporg.sonatype.plugins/pluginGroup /pluginGroups servers server idrepo/id usernamedeployment/username passworddeployment123/password /server /servers mirrors mirror idrepo/id mirrorOf*/mirrorOf nameHuman Readable Name for this Mirror./name urlhttp://myserver:8082/nexus/content/groups/repo/url /mirror /mirrors profiles profile iddeveloper/id activation activeByDefaulttrue/activeByDefault /activation repositories repository idrepo/id nameMirror of Maven repositories on the internet/name urlhttp://myserver:8082/nexus/content/groups/repo/url snapshots enabledtrue/enabled /snapshots releases enabledtrue/enabled /releases /repository /repositories pluginRepositories pluginRepository idrepo/id nameMaven Plugin Repository/name urlhttp://myserver:8082/nexus/content/groups/repo/url layoutdefault/layout snapshots enabledtrue/enabled /snapshots releases enabledtrue/enabled /releases /pluginRepository /pluginRepositories /profile /profiles activeProfiles activeProfiledeveloper/activeProfile /activeProfiles /settings *maven debug logs:* [DEBUG] Connecting to repository: 'repo' with url: ' http://myserver:8082/nexus/content/groups/repo'. [DEBUG] Downloading: http://myserver:8082/nexus/content/groups/repo/myproject/faces/faces-core/0.2.37/faces-core-0.2.37.jar Connecting to repository: 'repo' with url: ' http://myserver:8082/nexus/content/groups/repo'. Downloading: http://myserver:8082/nexus/content/groups/repo/myproject/runtime/myproject-base/0.5.8/myproject-base-0.5.8.jar [DEBUG] Error transferring file: Connection refused: connect org.apache.maven.wagon.TransferFailedException: Error transferring file: Connection refused: connect at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:143) 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 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:455) at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:433) at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:619) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at
