Re: If there any way to execute plugin conditionally?
No problem Dmitry, glad to share the knowledge :). On Wed, 2009-12-09 at 13:08 -0500, Dmitry Skavish wrote: Thanks a lot! Works perfectly! That's exactly what I was looking for. On Wed, Dec 9, 2009 at 12:28 PM, Adam Leggett (UPCO) adam.legg...@upco.co.uk wrote: Did you look at profiles for this - http://maven.apache.org/guides/introduction/introduction-to-profiles.html? They can be activated with an env var. Thanks Adam On Wed, 2009-12-09 at 12:24 -0500, Dmitry Skavish wrote: Hi, I need to run dependency-copy plugin only when some environment variable set. Is it possible? I could not find anything even remotely related to that. Thanks! - 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: Super pom / enforcer issues?
Comments inline. Regards, /James 2009/12/9 Nord, James jn...@nds.com: I'm having a really strange error in Maven 2.2.1 and the enforcer plugin. Basically it appears as though the super pom is missing version definitions for the following even though they should be present according to the web documentation (and performing a help:effective-pom shows them listed in the pluginManagement section): * maven-clean-plugin * maven-deploy-plugin * maven-install-plugin * maven-site-plugin Anyone any ideas what's happening? If I read your mail correctly then you're thinking the Enforcer plugin should not complain about missing versions if those versions are provided by the super pom. Correct. But think about it, if you upgrade to a newer Maven version then you could get a different super pom and as such your build is not reproducible. But the build is reproducible - you made an invalid assumption. In our builds we record the Maven version used to do the build so if we want to reproduce it we use exactly the same maven version on exactly the same platform with exactly the same JDK. I don't expect any maven version to give exactly the same results as a different version. You should explicitly list the versions of everything you use. Don't depend on the super pom to do it for you. The Enforcer plugin is just doing what you asked it to do. From the documentation: The Super POM is Maven's default POM. All POMs extend the Super POM unless explicitly set This rule enforces that all plugins have a version defined, either in the plugin or pluginManagement section of the pom or a parent pom. The combination of the two says to me that my POM implicitly has the Super POM as its parent, and hence *does* have the versions defined. My take on the Enforcer plugin is to make builds reproducible given the same environment at a latter date. Changing Maven version (or JDK!) changes the environment and is out of scope IMHO. This is especially the case if you explicitly limit the version of Maven and JDK (and OS!) used in the enforcer rules, and setting these does make sure your build is reproducible. ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. An NDS Group Limited company. www.nds.com
Plugin to start a jar?
Hi! I want to start a jar during the 'pre-integration-test' pretty much as starting a Tomcat with Cargo or similar. But this is a standalone jar that contains a server that i want to have available for integrationstests that I want to run later. I want the server jar to be shut down in the 'post-integration-test' phase I could live with it beeing shut down when Maven terminates so the post-integration-test phase isn't the most important part. Any tips on plugins I could use? /Thomas -- Thomas Sundberg M. Sc. in Computer Science Agical AB Västerlånggatan 79, 2 tr 111 29 Stockholm, SWEDEN Mobile: +46 70 767 33 15 E-mail: thomas.sundb...@agical.com Blog: http://thomassundberg.wordpress.com/ http://www.agical.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin to start a jar?
The exec plugin? Thomas Sundberg wrote: Hi! I want to start a jar during the 'pre-integration-test' pretty much as starting a Tomcat with Cargo or similar. But this is a standalone jar that contains a server that i want to have available for integrationstests that I want to run later. I want the server jar to be shut down in the 'post-integration-test' phase I could live with it beeing shut down when Maven terminates so the post-integration-test phase isn't the most important part. Any tips on plugins I could use? /Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin to start a jar?
2009/12/9 Thomas Sundberg thomas.sundb...@agical.com: I want to start a jar during the 'pre-integration-test' pretty much as starting a Tomcat with Cargo or similar. Take a look at the SHITTY maven plugin: http://mojo.codehaus.org/shitty-maven-plugin/ HTH Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin to start a jar?
2009/12/10 Antonio Petrelli antonio.petre...@gmail.com: 2009/12/9 Thomas Sundberg thomas.sundb...@agical.com: I want to start a jar during the 'pre-integration-test' pretty much as starting a Tomcat with Cargo or similar. Take a look at the SHITTY maven plugin: http://mojo.codehaus.org/shitty-maven-plugin/ Or the failsafe plugin: http://mojo.codehaus.org/failsafe-maven-plugin/ Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configuring the Site Descriptor
Hi Dennis The project is deployed at sourceforge. Sources: https://demoiselle-samp.svn.sourceforge.net/svnroot/demoiselle-samp/trunk/auction5/ The site I reffered to can be seen at http://demoiselle-samp.sourceforge.net/auction5/en/index.html Thanks. Dennis Lundberg-2 wrote: It's difficult to answer this without a sample project. Open an issue in JIRA and attach a sample project that we can test. strapa72 wrote: Hi all I have changed the site descriptor of a project to generate the english version of the site as well. In the POM.xml I include the en locale as follow: localespt_BR,en/locales Then I created the site_en.xml file setting the publishdate variable as follow: publishDate position=left format=MM/dd/ hh:mm:ss a/ It worked almost fine, apart from the header of the publish date at the english page, which is still being presented in portuguese (Ultima atualização) instead of in english (Last published). Does anyone know how to change this? Thanks! -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Configuring-the-Site-Descriptor-tp26714416p26725789.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: Configuring the Site Descriptor
strapa72 wrote: Hi Dennis The project is deployed at sourceforge. Sources: https://demoiselle-samp.svn.sourceforge.net/svnroot/demoiselle-samp/trunk/auction5 The site I reffered to can be seen at http://demoiselle-samp.sourceforge.net/auction5/en/index.html Thanks. Dennis Lundberg-2 wrote: It's difficult to answer this without a sample project. Open an issue in JIRA and attach a sample project that we can test. strapa72 wrote: Hi all I have changed the site descriptor of a project to generate the english version of the site as well. In the POM.xml I include the en locale as follow: localespt_BR,en/locales Then I created the site_en.xml file setting the publishdate variable as follow: publishDate position=left format=MM/dd/ hh:mm:ss a/ It worked almost fine, apart from the header of the publish date at the english page, which is still being presented in portuguese (Ultima atualização) instead of in english (Last published). Does anyone know how to change this? Thanks! -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Configuring-the-Site-Descriptor-tp26714416p26725799.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: Can't change packageName
The book is wrong. -DpackageName=org.XXX.mavenbook should be
-Dpackage=org.XXX.mavenbook.
Please help improving the book by creating a jira for this!
https://issues.sonatype.org/
/Anders
On Wed, Dec 9, 2009 at 19:24, nklein norman.kl...@gmail.com wrote:
I'm reading the Maven: Definitive Guide book to set up a project. In this
example from the book, I would like to change the packageName setting to
XXX as seen below:
mvn archetype:generate \
-DgroupId=org.sonatype.mavenbook \
-DartifactId=quickstart \
-Dversion=1.0-SNAPSHOT \
-DpackageName=org.XXX.mavenbook \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-quickstart \
-DarchetypeVersion=1.0 \
-DinteractiveMode=false
But mvn produces the following output:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:generate] (aggregator-style)
[INFO]
[INFO] Preparing archetype:generate
[INFO] No goals needed for project - skipping
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [archetype:generate {execution: default-cli}]
[INFO] Generating project in Batch mode
[INFO] Archetype repository missing. Using the one from
[org.apache.maven.archetypes:maven-archetype-quickstart:RELEASE] found in
catalog internal
[INFO]
[INFO] Using following parameters for creating OldArchetype:
maven-archetype-quickstart:1.0
[INFO]
[INFO] Parameter: groupId, Value: org.sonatype.mavenbook
[INFO] Parameter: packageName, Value: org.sonatype.mavenbook
[INFO] Parameter: package, Value: org.sonatype.mavenbook
[INFO] Parameter: artifactId, Value: quickstart
[INFO] Parameter: basedir, Value: c:\Temp
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] * End of debug info from resources from
generated
POM ***
[INFO] OldArchetype created in dir: c:\Temp\quickstart
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed Dec 09 10:22:44 PST 2009
[INFO] Final Memory: 8M/14M
[INFO]
The packageName doesn't conform to the overridden value supplied on the
command line. Do I understand the purpose of the packageName correctly? I
thought it allowed users to override the default value to supply a project
specific value.
Thanks.
--
View this message in context:
http://old.nabble.com/Can%27t-change-packageName-tp26715082p26715082.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: Pattern to setup common organization specific data in single pom?
I'd say the Maven way is to keep this info/data in a corp parent. For instance, have a look how this is done at Apache: http://repo1.maven.org/maven2/org/apache/apache/6/apache-6.pom As you can see, some values are handled by properties which make them customizable by projects using this parent. You should never, never change the info in a released artifact (a corp parent pom for instance). Instead, increment the version and do the necessary changes. I see this as an advantage and not a disadvantage. If you want to make sure that all projects are using the latest and greatest corp parent, that should be possible to enforce by an appropriate rule and the enforcer plugin. /Anders On Thu, Dec 10, 2009 at 08:34, Oskar Carlstedt oskar.carlst...@gmail.comwrote: Hello? I wonder if there is any pattern in Maven defining how to setup common organization specific data. What I mean is that I only want to define my distribution management in one place, I only want to setup specific deploy paths in one place etc., etc. One way is to define a lot of properties in a settings.xml - but then the user has to define all these properties himself. When properties are changing, then we have a mess. Even worse, there is no version tracking of properties using this solution. That is not good enough. One other way would be to use a global parent. Going that way it is possible to inherit all common data. But the disadvantage is that I cannot change the values without updating the same version of the parent in the repository (because Maven does not manage to resolve version ranges for the parent pom). So, is there any other suggestions? Can I import the data using version scopes. I like to be able to define exact versions of what I include in my builds but when it comes to build/deploy specific data, then I would like to be able to change this for all users in one place. Any advice to solve this problem is really appreciated! Cheers, Oskar -- View this message in context: http://old.nabble.com/Pattern-to-setup-common-organization-specific-data-in-single-pom--tp26723137p26723137.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
maven war plugin different webapp path
Hello I have following problem I have to adjust the maven war plugin to a different webapp source directory. I used webResources resource directorywebappDir/directory /resource /webResources to adjust it Now if I have a standalone project this works perfectly but if I have a parent pom.xml to the webapp I get the error that the parent pom tries to locate the webappDir relatively to its location instead of the child location and fails of course because the webappDir is relative to the childs pom.xml not the parents pom.xml. I use the version 2.0.2 of the war plugin. Is this a bug? Or is there another solution to the problem? Werner - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven war plugin different webapp path
Known issue: http://jira.codehaus.org/browse/MNG-2382 What version of Maven and what version of the war plugin are you using? /Anders On Thu, Dec 10, 2009 at 14:12, Werner Punz werner.p...@gmail.com wrote: Hello I have following problem I have to adjust the maven war plugin to a different webapp source directory. I used webResources resource directorywebappDir/directory /resource /webResources to adjust it Now if I have a standalone project this works perfectly but if I have a parent pom.xml to the webapp I get the error that the parent pom tries to locate the webappDir relatively to its location instead of the child location and fails of course because the webappDir is relative to the childs pom.xml not the parents pom.xml. I use the version 2.0.2 of the war plugin. Is this a bug? Or is there another solution to the problem? Werner - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Info report license LGPL
Hi, I have a maven project, where I specified LGPL as license. If the project site is generated (or the license goal is explicitly invoked) the resulting license.html says, that the Project License is GNU Lesser Public License, but all links and texts below (about the license) are about GPL and not LGPL. Is this a known bug or did I do something wrong? Thanks in advance. Cheers. Martin PS: Here is the link to the wrong project license site: http://www.enviromatics.net/charon/license.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to prevent deployment on release
The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
taglist report looking at/into xml files
It appears that the taglist report is trying to validate some hibernate config we have in our resources directory. One file in question is blowing up the report, is it possible to skip this single file? The problem lines look like this: join table=t_foo key column= id unique=true / many-to-one name=prop column=prop_id not-null=true lazy=false / /join The report dies with this error: Caused by: org.hibernate.MappingException: class someclass not found while looking for property: prop at org.hibernate.util.ReflectHelper.reflectedPropertyClass(ReflectHelper.java:97) at org.hibernate.mapping.ToOne.setTypeUsingReflection(ToOne.java:81) at org.hibernate.cfg.HbmBinder.createProperty(HbmBinder.java:2193) at org.hibernate.cfg.HbmBinder.bindJoin(HbmBinder.java:1014) at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2126) at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2060) at org.hibernate.cfg.HbmBinder.bindRootPersistentClassCommonValues(HbmBinder.java:381) at org.hibernate.cfg.HbmBinder.bindRootClass(HbmBinder.java:295) at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:166) at org.hibernate.cfg.Configuration.add(Configuration.java:702) at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:537) at org.hibernate.cfg.Configuration.addResource(Configuration.java:599) ... 30 more Caused by: java.lang.ClassNotFoundException: someclass at java.net.URLClassLoader$1.run(URLClassLoader.java:200) Any suggestions?
Re: How to prevent deployment on release
I believe its the default release profile that triggers the site deployment stuff. There is an option for setting custom ones on the perform mojo: http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles On Thu, 2009-12-10 at 09:25 -0500, Jim Collings wrote: The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - 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 prevent deployment on release
You can configure used goals with this : http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals 2009/12/10 Jim Collings jlistn...@gmail.com: The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to prevent deployment on release
I believe the only difference here is that this is a property and I am using xml but I imagine it is the same thing. On Thu, Dec 10, 2009 at 9:50 AM, Olivier Lamy ol...@apache.org wrote: You can configure used goals with this : http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals 2009/12/10 Jim Collings jlistn...@gmail.com: The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - 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 prevent deployment on release
How complicated is that to do? We don't generally use profiles around here so I've little experience with them. On Thu, Dec 10, 2009 at 9:48 AM, Adam Leggett (UPCO) adam.legg...@upco.co.uk wrote: I believe its the default release profile that triggers the site deployment stuff. There is an option for setting custom ones on the perform mojo: http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles On Thu, 2009-12-10 at 09:25 -0500, Jim Collings wrote: The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - 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 prevent deployment on release
Not massively complicated, have a look at the responses to this query about a similar issue. In this case a need to prevent deploying the sources jar as part of a release. http://stackoverflow.com/questions/437085/mvn-releaseperform-without-source-ending-up-in-artifactory On Thu, 2009-12-10 at 10:08 -0500, Jim Collings wrote: How complicated is that to do? We don't generally use profiles around here so I've little experience with them. On Thu, Dec 10, 2009 at 9:48 AM, Adam Leggett (UPCO) adam.legg...@upco.co.uk wrote: I believe its the default release profile that triggers the site deployment stuff. There is an option for setting custom ones on the perform mojo: http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles On Thu, 2009-12-10 at 09:25 -0500, Jim Collings wrote: The objective is to prevent maven's attempt at site deployment. Everything else, though, I want. Problem is that when I use the xml below, it ONLY installs. So I added goals with install: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version...someversion.../version configuration connectionUrl...appropriate connection stuff.../connectionUrl tagBase...appropriate connection stuff.../tagBase goals install /goals /configuration /plugin Clue? - 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: Generate + include list of resources included in jar
Just to give further details, here's what I've worked out as a (mostly)
general solution to this issue:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasecompile/phase
configuration
tasks
property name=rsrc.dir
value=${project.resources[0].directory}/
property name=excludes
value=${project.resources[0].excludes}/
property name=rsrc.list.out
value=${project.build.directory}/classes/${project.groupId}:${project.artifactId}:resourcelist.txt/
fileset id=resources.list dir=${rsrc.dir}
excludes=${excludes}/
pathconvert pathsep=${line.separator}
property=resources.str refid=resources.list
filtermapper
replacestring from=${rsrc.dir} to=/
/filtermapper
/pathconvert
echo file=${rsrc.list.out} append=false
message=${resources.str}/
echoIncluding resources found in ${rsrc.dir} in list
written to ${rsrc.list.out}/echo
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
The failings here being (a) it won't include resources in supplemental
resource directories in the outputted list (b) it writes files to
target/classes instead of a proper generated-sources directory
(http://jira.codehaus.org/browse/MANTRUN-54 would make that possible, I
believe), and (c) it's ant ;-)
Better options welcome.
- Chas
cemerick wrote:
I have a project that has a number of resources under src/main/resources.
The associated codebase needs to know what resources are available in
order to load them at runtime (new resources are added all the time, so
the list cannot be static). I've got an ant target (from an older
project) that scans the resources dir, and emits a list of the files under
that directory as a new file. The code can then always load that directly
listing at runtime, and do what it needs to.
This works fine, but I'm wondering if there's a native maven solution to
the problem. I see noticed a ${project.resources} property mentioned
elsewhere; I figured I'd drop that into the jar's manifest, and load it
back at runtime from there, but project.resources appears to be an
ArrayList, so can't be added as a manifest entry's value (or, at least,
not in a way obvious to me).
Thoughts?
Thanks,
- Chas
--
View this message in context:
http://old.nabble.com/Generate-%2B-include-list-of-resources-included-in-jar-tp26718010p26729085.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: assembly is deprecated. What to use?
Thanks for pointing out my version confusion. On Wed, Dec 09, 2009 at 04:12:29PM +0100, Jörg Schaible wrote: Mark H. Wood wrote at Mittwoch, 9. Dezember 2009 15:09: mw...@mhw ~ $ mvn --version CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_17 Java home: /opt/sun-jdk-1.6.0.17/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.30-gentoo-r5 arch: i386 Family: unix There seems something else fundamentally broken with your setup, looking at this strange CompilerOracle message. Oh, that is the result of this: mw...@mhw ~ $ cat .hotspot_compiler exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith mw...@mhw ~ $ which is required to work around a bug in the Sun compiler that is vigorously exercised by Eclipse, leading to Eclipse crashing on startup. It suppresses JIT compilation of that method IIRC, and I don't see that it would affect Maven at all. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents. pgp846FgbbrPx.pgp Description: PGP signature
release plugin: Why is allowTimestampedSnapshots being ignored?
Hi,
I'm using Maven 2 and trying to release a snapshot version of my Java web
app. Here is the command I'm running from my root project folder ...
mvn release:prepare -DdryRun=true -Dresume=false
-DallowTimestampedSnapshots=true
Eventually the build dies because of Can't release project due to non
released dependencies. I thought adding -DallowTimestampedSnapshots=true
was supposed to allow this. Could someone provide some clarity on how to
release a snapshot version of my project? Below is the last part of running
the above command.
Thanks, - Dave
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /Users/dalvarado/source/tours cvs -z3 -f
-d :pserver:dalvar...@localhost:/usr/local/cvs/nic -n -q update -d
[INFO] Working directory: /Users/dalvarado/source/tours
[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : 0
Resolve All Snapshots.: 'myco.galc.capitol.tours:myco-galc-capitol-tours'
set to release? (yes/no) yes: : yes
What is the next development version? (1.1-SNAPSHOT) 1.1-SNAPSHOT: :
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Can't release project due to non released dependencies :
myco.galc.capitol.tours:myco-galc-capitol-tours:pom:1.0-SNAPSHOT
in project 'myco GA Capitol Tours Webapp'
(myco.galc.capitol.tours:myco-galc-capitol-tours-webapp:war:1.0-SNAPSHOT)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 23 seconds
[INFO] Finished at: Thu Dec 10 08:28:55 MST 2009
[INFO] Final Memory: 12M/23M
[INFO]
--
View this message in context:
http://old.nabble.com/release-plugin%3A-Why-is-allowTimestampedSnapshots-being-ignored--tp26729314p26729314.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: Pattern to setup common organization specific data in single pom?
One way is to define a lot of properties in a settings.xml - but then the user has to define all these properties himself. When properties are changing, then we have a mess. Even worse, there is no version tracking of properties using this solution. That is not good enough. I've heard of many organizations who check in their settings.xml file into their SCM, making distributing and updating it pretty much dead simple. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to prevent deployment on release
Aw crud. Thanks for your help guys but this turned out to be a case of developer headspace and timing. ;-) I forgot that I had to call maven:prepare first. My assumption at the time was that it would be called by maven:perform if it was required. Not the case though. Works great now. Jim C. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: Why is allowTimestampedSnapshots being ignored?
You dont need to use the release plugin to deploy a snapshot.
A simple 'mvn deploy' will suffice.
Thanks
Adam
On Thu, 2009-12-10 at 07:35 -0800, laredotornado wrote:
Hi,
I'm using Maven 2 and trying to release a snapshot version of my Java web
app. Here is the command I'm running from my root project folder ...
mvn release:prepare -DdryRun=true -Dresume=false
-DallowTimestampedSnapshots=true
Eventually the build dies because of Can't release project due to non
released dependencies. I thought adding -DallowTimestampedSnapshots=true
was supposed to allow this. Could someone provide some clarity on how to
release a snapshot version of my project? Below is the last part of running
the above command.
Thanks, - Dave
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /Users/dalvarado/source/tours cvs -z3 -f
-d :pserver:dalvar...@localhost:/usr/local/cvs/nic -n -q update -d
[INFO] Working directory: /Users/dalvarado/source/tours
[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : 0
Resolve All Snapshots.: 'myco.galc.capitol.tours:myco-galc-capitol-tours'
set to release? (yes/no) yes: : yes
What is the next development version? (1.1-SNAPSHOT) 1.1-SNAPSHOT: :
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Can't release project due to non released dependencies :
myco.galc.capitol.tours:myco-galc-capitol-tours:pom:1.0-SNAPSHOT
in project 'myco GA Capitol Tours Webapp'
(myco.galc.capitol.tours:myco-galc-capitol-tours-webapp:war:1.0-SNAPSHOT)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 23 seconds
[INFO] Finished at: Thu Dec 10 08:28:55 MST 2009
[INFO] Final Memory: 12M/23M
[INFO]
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Super pom / enforcer issues?
My take on the Enforcer plugin is to make builds reproducible given the same environment at a latter date. Changing Maven version (or JDK!) changes the environment and is out of scope IMHO. This is especially the case if you explicitly limit the version of Maven and JDK (and OS!) used in the enforcer rules, and setting these does make sure your build is reproducible. Sounds like you want Enforcer to work like: if version of plugin not in this pom, or a parent etc and maven version locked down and jdk version is locked down and maven super pom specifies version of this plugin then do not fail You can certainly hack the code yourself or file a JIRA to make it work like you expect with a configurable flag to turn that feature on/off. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
ant-maven, dependency:? to recreate repo
Hey all, I'm checking out of source control several internal maven projects to put onto another medium (CD). I'm using ANT to to this task related to some other items that need to go on the CD. Question: I want to 'replicate' a mini-repository for each maven project, including all the artifacts, poms, and layout structure. Is there an easy way to accomplish this? I've tried using a command-line call from ant to mvn dependency:copy-dependencies, but this doesn't do the layout, and I can't figure out how to pass 'copyPom=true' through Ant (although, that doesn't help without the layout anyway). Thanks for any input, -D - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generate + include list of resources included in jar
Better options welcome. Write a plugin. Its super simple and will give you exactly what you need. I'd just knock something out in Groovy if I were you. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Changes Plugin 2.3 Released
The Maven team is pleased to announce the release of the Maven Changes Plugin, version 2.3 This plugin is used to inform your users of the changes that have occurred between different releases of your project. The plugin can extract these changes, either from a changes.xml file or from the JIRA issue management system, and present them as a report. You also have the option of creating a release announcement and even sending this via email to your users. http://maven.apache.org/plugins/maven-changes-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changes-plugin/artifactId version2.3/version /plugin Release Notes - Maven 2.x Changes Plugin - Version 2.3 ** Bug * [MCHANGES-135] - JIRA links on changes report are broken * [MCHANGES-138] - Exception thrown when issueManagement section of pom is missing * [MCHANGES-151] - A patch about the date parsing and html encoding for maven-changes-plugin-trac * [MCHANGES-186] - Issue links for JIRA are broken when using the %URL% token * [MCHANGES-187] - If jiraMerge=true then releases that are only in JIRA will not be included in the announcement * [MCHANGES-189] - There are presentation problems in the changes-report if an issue in changes.xml contains characters like and ** New Feature * [MCHANGES-145] - Make it possible to run the announcement goals only once for a multi-module project Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
building from parent a maven-j2ee-simple project
Hi all,
We have a modular project using maven-j2ee-simple archetype. This projects
has three modules: servlets, projects, and ear. Servlets contain one module,
a web application, projects contains some jar modules and the ear module
that generates our application ear. We use inside the ear, and servlet
modules some property files to do filtering depending on the environment we
are deploying the application. If we compile and package each module
separately, any problem, but, when we do compiling and packaging from the
root project, the property files cannot be found. Our build section of our
pom files is:
filters
filterpom.${env}.properties/filter
/filters
What we can do to able maven find our property files relative to root
project?
Thanks.
--
Everything should be made as simple as possible, but not simpler Albert
Einstein
Re: maven-plugin-api com.thoughtworks.qdox.parser.ParseException: syntax error
Hi
I m also facing the same issue . Where you able to solve your issue?
Binu
janszm wrote:
I am trying to write a maven plugin as per
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
When I compile my plugin I get the following error:
com.thoughtworks.qdox.parser.ParseException: syntax error @[38,33] in
file:/C:/work/schema-tools/src/main/java/org/w3/_2001/xmlschema/DerivationControl.java
The file is basically a JAXB generated file and the parser seems to
complain about the @XmlEnumValue(substitution) tag.
Anyone have any ideas why this occurs? I have tried various versions of
the maven-plugin-api
The full file contents (minus comments) are:
@XmlType(name = derivationControl)
@XmlEnum
public enum DerivationControl {
@XmlEnumValue(substitution)
SUBSTITUTION(substitution),
@XmlEnumValue(extension)
EXTENSION(extension),
@XmlEnumValue(restriction)
RESTRICTION(restriction),
@XmlEnumValue(list)
LIST(list),
@XmlEnumValue(union)
UNION(union);
private final String value;
DerivationControl(String v) {
value = v;
}
public String value() {
return value;
}
public static DerivationControl fromValue(String v) {
for (DerivationControl c: DerivationControl.values()) {
if (c.value.equals(v)) {
return c;
}
}
throw new IllegalArgumentException(v);
}
}
Help appreciated,
Menno
--
View this message in context:
http://old.nabble.com/maven-plugin-api-com.thoughtworks.qdox.parser.ParseException%3A-syntax-error-tp23874877p26731409.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: release plugin: Why is allowTimestampedSnapshots being ignored?
Thanks, I will definitely do this. But to satisfy my curiosity, is this not
the right syntax
-DallowTimestampedSnapshots=true
or is there a bug in the release plugin?
Thanks, - Dave
Adam Leggett (UPCO) wrote:
You dont need to use the release plugin to deploy a snapshot.
A simple 'mvn deploy' will suffice.
Thanks
Adam
On Thu, 2009-12-10 at 07:35 -0800, laredotornado wrote:
Hi,
I'm using Maven 2 and trying to release a snapshot version of my Java web
app. Here is the command I'm running from my root project folder ...
mvn release:prepare -DdryRun=true -Dresume=false
-DallowTimestampedSnapshots=true
Eventually the build dies because of Can't release project due to non
released dependencies. I thought adding
-DallowTimestampedSnapshots=true
was supposed to allow this. Could someone provide some clarity on how to
release a snapshot version of my project? Below is the last part of
running
the above command.
Thanks, - Dave
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /Users/dalvarado/source/tours cvs -z3
-f
-d :pserver:dalvar...@localhost:/usr/local/cvs/nic -n -q update -d
[INFO] Working directory: /Users/dalvarado/source/tours
[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.: Do you want to
resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All
1:Project
Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: : 0
Resolve All Snapshots.: 'myco.galc.capitol.tours:myco-galc-capitol-tours'
set to release? (yes/no) yes: : yes
What is the next development version? (1.1-SNAPSHOT) 1.1-SNAPSHOT: :
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Can't release project due to non released dependencies :
myco.galc.capitol.tours:myco-galc-capitol-tours:pom:1.0-SNAPSHOT
in project 'myco GA Capitol Tours Webapp'
(myco.galc.capitol.tours:myco-galc-capitol-tours-webapp:war:1.0-SNAPSHOT)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 23 seconds
[INFO] Finished at: Thu Dec 10 08:28:55 MST 2009
[INFO] Final Memory: 12M/23M
[INFO]
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
View this message in context:
http://old.nabble.com/release-plugin%3A-Why-is-allowTimestampedSnapshots-being-ignored--tp26729314p26731475.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
adding not-relocatable relative dir to classpath
Under development, for all run cases (exec:exec or surefire:test) I need a classpath be appended with a dir which has predefined location against project's basedir and *isn't* transitive (say, I can not use it as resources being copied to target/classes). How to append? Andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: Why is allowTimestampedSnapshots being ignored?
or is there a bug in the release plugin? There are many bugs in many plugins. Also see: http://jira.codehaus.org/browse/MRELEASE-452 What VERSION of the release plugin are you using? Just because there's a feature in a plugin doesn't mean you're using a recent enough version to get access to the feature. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can't change packageName
Anders Hammar wrote: The book is wrong. -DpackageName=org.XXX.mavenbook should be -Dpackage=org.XXX.mavenbook. Please help improving the book by creating a jira for this! https://issues.sonatype.org/ /Anders After updating this code to work with a Flex project (using org.sonatype.flexmojos), I still can't get the -Dpackage option to change the directory listing for ActionScript files. It seems to work fine with Java files. Is there any additional things that need to be performed to work with a Flex project? Thanks -- View this message in context: http://old.nabble.com/Can%27t-change-packageName-tp26715082p26731862.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
Problem with deploy (Error writing to server)
I have a very strange problem when I try to deploy artifacts. For
certain artifacts, the deployment fails with the message 'Error
deploying artifact: Error transferring file...Error writing to server'
(I included the stacktrace below). It appears to be related to the
size of the artifact, but here's the kicker -- the size restriction
isn't consistent acrosss artifact types. I can deploy an 11M WAR, but
can't deploy a 30M WAR. I can deploy a 96K JAR, but can't deploy a
128K JAR. (Sorry for the broad size range, I haven't had enough time
to narrow it down further).
I don't know if it's related, but I also noticed an oddity when I was
trying to narrow down the 'breaking point' for the size. I set up a
test project which deploys a jar and added images as resources to
build up the size. After passing the size threshold (which caused the
deploy to fail), I would remove the newest image and try to rebuild,
but now the deploy would fail with a 'connection reset' or 'connection
reset by peer: socket write error' message. Without making any
changes, I rerun 'mvn clean deploy' or 'mvn deploy. Most of the time
everything deploys fine; although sometimes it takes two tries before
it succeeds. For clarity, I outlined those steps below:
1.) Add image. Build and deploy fine. Size 96K.
2.) Add another image. Build fine, deploy breaks: Error writing to
server. Size 128K.
3.) Remove last image. Build fine, deploy breaks: Connection reset. Size 96K.
4.) No changes. Build and deploy fine. Size 96K.
Some additional information:
* I experience this problem using both Maven 2.0.9 and 2.2.1.
* Our repository is managed by Nexus (deployed to Tomcat with SSL from
apache). Nexus might be part of the problem, but I've checked some of
the logs, but I can't find any indication of errors on that side of
things.
* Our network uses a socks proxy (v5).
Lastly, here is the stack trace (and a bit of the Maven output):
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' --
[DEBUG] (f) artifact = com.cdmtech.icodes.ciw:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository =
Repository[snapshots|https://hudson149/nexus/content/repositories/snapshots]
[DEBUG] (s) localRepository = Repository[local|file://C:\Documents
and Settings\kj\.m2\repository]
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
C:\eclipse\eclipse-workspaces\eclipse-jee-ganymede-3.4.2\m2eclipse\ciw\test\pom.xml
[DEBUG] (f) skip = false
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapshots
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'snapshots' with url:
'https://hudson149/nexus/content/repositories/snapshots'.
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading:
https://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar
4/128K
...
128/128K
[DEBUG] Error writing to server
java.io.IOException: Error writing to server
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1002)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
at
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
RE: ant-maven, dependency:? to recreate repo
I haven't tried this but I think t may work. You could use mvn dependency:go-offline -Dmaven.repo.local=/some/archive/path This should cause all the required dependencies and plugins to be downloaded to the maven.repo.local path you specified. If you ran that on all of your projects you'd have a maven repo of what was needed to rebuild these. -Original Message- From: Darren Hartford [mailto:binarymon...@yahoo.com] Sent: Thursday, December 10, 2009 11:13 AM To: users@maven.apache.org Subject: ant-maven, dependency:? to recreate repo Hey all, I'm checking out of source control several internal maven projects to put onto another medium (CD). I'm using ANT to to this task related to some other items that need to go on the CD. Question: I want to 'replicate' a mini-repository for each maven project, including all the artifacts, poms, and layout structure. Is there an easy way to accomplish this? I've tried using a command-line call from ant to mvn dependency:copy-dependencies, but this doesn't do the layout, and I can't figure out how to pass 'copyPom=true' through Ant (although, that doesn't help without the layout anyway). Thanks for any input, -D - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --- CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configuring the Site Descriptor
Hi I gave your project a try and I can confirm the behavior you described. At first I thought it had something to do with your skin, but that wasn't it. Then I tried to build the site with Maven Site Plugin 2.1-SNAPSHOT and it worked as it should. The headings now says Last Published and Version for the English site. So there must be a bug in 2.0.1 that has been fixed in 2.1. The 2.1 release is in the works and we hope to have it out before Christmas. strapa72 wrote: Hi Dennis The project is deployed at sourceforge. Sources: https://demoiselle-samp.svn.sourceforge.net/svnroot/demoiselle-samp/trunk/auction5/ The site I reffered to can be seen at http://demoiselle-samp.sourceforge.net/auction5/en/index.html Thanks. Dennis Lundberg-2 wrote: It's difficult to answer this without a sample project. Open an issue in JIRA and attach a sample project that we can test. strapa72 wrote: Hi all I have changed the site descriptor of a project to generate the english version of the site as well. In the POM.xml I include the en locale as follow: localespt_BR,en/locales Then I created the site_en.xml file setting the publishdate variable as follow: publishDate position=left format=MM/dd/ hh:mm:ss a/ It worked almost fine, apart from the header of the publish date at the english page, which is still being presented in portuguese (Ultima atualização) instead of in english (Last published). Does anyone know how to change this? Thanks! -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Can't change packageName
I'm not sure, but I think that the package property is archetype specific. It's not listed on the archetype plugin doc site. If you specify what archetype you're using maybe someone knows. /Anders On Thu, Dec 10, 2009 at 19:01, nklein norman.kl...@gmail.com wrote: Anders Hammar wrote: The book is wrong. -DpackageName=org.XXX.mavenbook should be -Dpackage=org.XXX.mavenbook. Please help improving the book by creating a jira for this! https://issues.sonatype.org/ /Anders After updating this code to work with a Flex project (using org.sonatype.flexmojos), I still can't get the -Dpackage option to change the directory listing for ActionScript files. It seems to work fine with Java files. Is there any additional things that need to be performed to work with a Flex project? Thanks -- View this message in context: http://old.nabble.com/Can%27t-change-packageName-tp26715082p26731862.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: Pattern to setup common organization specific data in single pom?
There are also solutions with a maven plugin downloading and installing settings.xml. Such a plugin is included in Nexus Pro, but it shouldn't be too hard to write yourself (or is there an oss version already?). /Anders On Thu, Dec 10, 2009 at 16:35, Wayne Fay wayne...@gmail.com wrote: One way is to define a lot of properties in a settings.xml - but then the user has to define all these properties himself. When properties are changing, then we have a mess. Even worse, there is no version tracking of properties using this solution. That is not good enough. I've heard of many organizations who check in their settings.xml file into their SCM, making distributing and updating it pretty much dead simple. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
401 error with Maven Release Plugin
A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifact to the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problem having the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
Re: 401 error with Maven Release Plugin
are you using Archiva as your repo? On 11/12/2009 7:49 AM, Brendan Sibre wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifactto the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problemhaving the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 401 error with Maven Release Plugin
Actually, using Artifactory 2.1.0. And it is configured to mirror everything. So far I'm guessing that it's one of two problems: 1) I don't have things mapped properly between my ~/.m2/settings.xml and $MAVEN_HOME/conf/settings.xml where the shared configuration defines the distributionManagement and my settings defines server credentials. 2) I have some very vague recollection of there being a problem with Maven passing the MAVEN_HOME value to the forked maven when MAVEN_HOME points to a symlink. Although I've tried changing MAVEN_HOME to the actual directory as well as passing in the -DmavenHome parameter. On Thu, Dec 10, 2009 at 5:20 PM, Matt Milliss matt.mill...@gmail.comwrote: are you using Archiva as your repo? On 11/12/2009 7:49 AM, Brendan Sibre wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifactto the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problemhaving the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
Re: 401 error with Maven Release Plugin
We had the same problem with Archiva but it was fixed with the latest upgrade, which is why I asked. Sorry don't think I can help. Cheers Matt On 11/12/2009 10:47 AM, Brendan Sibre wrote: Actually, using Artifactory 2.1.0. And it is configured to mirror everything. So far I'm guessing that it's one of two problems: 1) I don't have things mapped properly between my ~/.m2/settings.xml and $MAVEN_HOME/conf/settings.xml where the shared configuration defines the distributionManagement and my settings defines server credentials. 2) I have some very vague recollection of there being a problem with Maven passing the MAVEN_HOME value to the forked maven when MAVEN_HOME points to a symlink. Although I've tried changing MAVEN_HOME to the actual directory as well as passing in the -DmavenHome parameter. On Thu, Dec 10, 2009 at 5:20 PM, Matt Milliss matt.mill...@gmail.com mailto:matt.mill...@gmail.com wrote: are you using Archiva as your repo? On 11/12/2009 7:49 AM, Brendan Sibre wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifactto the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problemhaving the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
Problem with Maven deploy (Error writing to server)
I have a very strange problem when I try to deploy artifacts. For
certain artifacts, the deployment fails with the message 'Error
deploying artifact: Error transferring file...Error writing to server'
(I included the stacktrace below). It appears to be related to the
size of the artifact, but here's the kicker -- the size restriction
isn't consistent acrosss artifact types. I can deploy an 11M WAR, but
can't deploy a 30M WAR. I can deploy a 96K JAR, but can't deploy a
128K JAR. (Sorry for the broad size range, I haven't had enough time
to narrow it down further).
I don't know if it's related, but I also noticed an oddity when I was
trying to narrow down the 'breaking point' for the size. I set up a
test project which deploys a jar and added images as resources to
build up the size. After passing the size threshold (which caused the
deploy to fail), I would remove the newest image and try to rebuild,
but now the deploy would fail with a 'connection reset' or 'connection
reset by peer: socket write error' message. Without making any
changes, I rerun 'mvn clean deploy' or 'mvn deploy. Most of the time
everything deploys fine; although sometimes it takes two tries before
it succeeds. For clarity, I outlined those steps below:
1.) Add image. Build and deploy fine. Size 96K.
2.) Add another image. Build fine, deploy breaks: Error writing to
server. Size 128K.
3.) Remove last image. Build fine, deploy breaks: Connection reset. Size 96K.
4.) No changes. Build and deploy fine. Size 96K.
Some additional information:
* I experience this problem using both Maven 2.0.9 and 2.2.1.
* Our repository is managed by Nexus (deployed to Tomcat with SSL from
apache). Nexus might be part of the problem, but I've checked some of
the logs, but I can't find any indication of errors on that side of
things.
* Our network uses a socks proxy (v5).
Lastly, here is the stack trace (and a bit of the Maven output):
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' --
[DEBUG] (f) artifact = com.cdmtech.icodes.ciw:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository =
Repository[snapshots|https://hudson149/nexus/content/repositories/snapshots]
[DEBUG] (s) localRepository = Repository[local|file://C:\Documents
and Settings\kj\.m2\repository]
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
C:\eclipse\eclipse-workspaces\eclipse-jee-ganymede-3.4.2\m2eclipse\ciw\test\pom.xml
[DEBUG] (f) skip = false
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapshots
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'snapshots' with url:
'https://hudson149/nexus/content/repositories/snapshots'.
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading:
https://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar
4/128K
...
128/128K
[DEBUG] Error writing to server
java.io.IOException: Error writing to server
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1002)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.finishPutTransfer(LightweightHttpWagon.java:185)
at
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:413)
at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:392)
at
org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:365)
at org.apache.maven.wagon.StreamWagon.put(StreamWagon.java:163)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:317)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:227)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
Re: Problem with Maven deploy (Error writing to server)
If you're running Apache 2.2, take a look at
http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslrenegbuffersize
Essentially, it might not really be the size, it might be the size in
combination with
opening a new connection. If there is already an active SSL connection it
won't need
to be renegotiated during the post of the file. If it needs to create a new
connection
then it might fail for larger files.
Tomcat has a similar setting, maxPostSize you can set on the connector so
you might need to
set both.
This has bitten me with other similar things and it's really frustrating.
I'm not quite sure why the
client can't wait for the renegotiation to complete before sending the file.
On Thu, Dec 10, 2009 at 8:17 PM, K J gomm...@gmail.com wrote:
I have a very strange problem when I try to deploy artifacts. For
certain artifacts, the deployment fails with the message 'Error
deploying artifact: Error transferring file...Error writing to server'
(I included the stacktrace below). It appears to be related to the
size of the artifact, but here's the kicker -- the size restriction
isn't consistent acrosss artifact types. I can deploy an 11M WAR, but
can't deploy a 30M WAR. I can deploy a 96K JAR, but can't deploy a
128K JAR. (Sorry for the broad size range, I haven't had enough time
to narrow it down further).
I don't know if it's related, but I also noticed an oddity when I was
trying to narrow down the 'breaking point' for the size. I set up a
test project which deploys a jar and added images as resources to
build up the size. After passing the size threshold (which caused the
deploy to fail), I would remove the newest image and try to rebuild,
but now the deploy would fail with a 'connection reset' or 'connection
reset by peer: socket write error' message. Without making any
changes, I rerun 'mvn clean deploy' or 'mvn deploy. Most of the time
everything deploys fine; although sometimes it takes two tries before
it succeeds. For clarity, I outlined those steps below:
1.) Add image. Build and deploy fine. Size 96K.
2.) Add another image. Build fine, deploy breaks: Error writing to
server. Size 128K.
3.) Remove last image. Build fine, deploy breaks: Connection reset. Size
96K.
4.) No changes. Build and deploy fine. Size 96K.
Some additional information:
* I experience this problem using both Maven 2.0.9 and 2.2.1.
* Our repository is managed by Nexus (deployed to Tomcat with SSL from
apache). Nexus might be part of the problem, but I've checked some of
the logs, but I can't find any indication of errors on that side of
things.
* Our network uses a socks proxy (v5).
Lastly, here is the stack trace (and a bit of the Maven output):
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy' --
[DEBUG] (f) artifact = com.cdmtech.icodes.ciw:test:jar:0.0.1-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository =
Repository[snapshots|
https://hudson149/nexus/content/repositories/snapshots]
[DEBUG] (s) localRepository = Repository[local|file://C:\Documents
and Settings\kj\.m2\repository]
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
C:\eclipse\eclipse-workspaces\eclipse-jee-ganymede-3.4.2\m2eclipse\ciw\test\pom.xml
[DEBUG] (f) skip = false
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapshots
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'snapshots' with url:
'https://hudson149/nexus/content/repositories/snapshots'.
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Using Wagon implementation lightweight from default mapping
for protocol https
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] not adding permissions to wagon connection
Uploading:
https://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar
4/128Khttps://hudson149/nexus/content/repositories/snapshots/ciw/test/0.0.1-SNAPSHOT/test-0.0.1-20091210.183044-14.jar%0A4/128K
...
128/128K
[DEBUG] Error writing to server
java.io.IOException: Error writing to server
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
at
sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1002)
at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at
Re: How to exclude a package from compile
I think this solution could be helpful: http://maven.apache.org/plugins/maven-compiler-plugin/howto.html -- View this message in context: http://old.nabble.com/How-to-exclude-a-package-from-compile-tp21476236p26738402.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
Deploying application in a tomcat
Hi All, I am planning to use maven to deploy my application in tomcat. My requirement is to deploy on a remote instance of tomcat. Can any one got some pointer/links to start with. Regards, Vijay Shanker Dubey
Re: Deploying application in a tomcat
http://cargo.codehaus.org/Maven2+plugin Kalle On Thu, Dec 10, 2009 at 8:53 PM, vijay shanker vijay.s...@gmail.com wrote: Hi All, I am planning to use maven to deploy my application in tomcat. My requirement is to deploy on a remote instance of tomcat. Can any one got some pointer/links to start with. Regards, Vijay Shanker Dubey - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: adding not-relocatable relative dir to classpath
Andrew Gaydenko wrote at Donnerstag, 10. Dezember 2009 18:49: Under development, for all run cases (exec:exec or surefire:test) I need a classpath be appended with a dir which has predefined location against project's basedir and *isn't* transitive (say, I can not use it as resources being copied to target/classes). How to append? The build-helper plugin should help. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Pattern to setup common organization specific data in single pom?
Hello all of you! Thank for your replies. I've tested all strategies told here, except for using a plugin generating the settings.xml, in earlier projects. I never had the feeling feeling of hitting the big success. Maybe the plugin way will work. I can understand all arguments for not being able to change the pom after a release, and therefore all arguments of not having a version scope on the parent pom. For me this applies to all build logic, but not for distribution management, deploy management etc., etc. This is the case where I want to be able to change some settings, not changing the build itself. Let say we change the url to our SCM, then we have to change all POMs configured using the old SCM. This mitgh be a network problem, but still such things happens. Let say I change the URL to the location of my globally published WSDL files or other resources. Then it is a must to walk through all POMs that are using that value. Ok, in booth cases above I can put expected data into the settings.xml file. I don't like this way because I think settings.xml is the user's personal file and it does not have the purpose of holding default values. Further, all settings had during a build is not checked in during a release because these vales are put in the settings.xml file. But it might be the only way to go. So having a plugin generating the most up to date settings.xml file might be a good way finding the path to the big success. Maybe we shall vote for a extra feature in the release plugin that makes it possible to checkin the current settings.xml and the full build log when doing a release. Just to get the full trace of a build. Thank you all again for your answers! Cheers, Oskar -- View this message in context: http://old.nabble.com/Pattern-to-setup-common-organization-specific-data-in-single-pom--tp26723137p26739437.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: adding not-relocatable relative dir to classpath
On Friday 11 December 2009 09:44:06 Jörg Schaible wrote: Andrew Gaydenko wrote at Donnerstag, 10. Dezember 2009 18:49: Under development, for all run cases (exec:exec or surefire:test) I need a classpath be appended with a dir which has predefined location against project's basedir and *isn't* transitive (say, I can not use it as resources being copied to target/classes). How to append? The build-helper plugin should help. - Jörg Have not found an appropriate build-helper's goal. I'd want to add a dir at runtime *only*, and this dir isn't relocatable: it must not be copied to target/ or packaged. I have filed new Improvement: http://jira.codehaus.org/browse/MEXEC-73 Andrew - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Pattern to setup common organization specific data in single pom?
Just to be clear, when you say version scope do you mean version range? What you could do is to use a property for some elements in your pom. The default value is defined in the pom through defining the property. It is then possible for each user to override this, either through their settings.xml or the command line. Have a look at the Apache parent pom I linked to earlier: http://repo2.maven.org/maven2/org/apache/apache/6/apache-6.pom In that pom this technique is used for the url of the snapshot repo of their distribution management. However, I agree that there are some elements of the pom that one could think shouldn't be locked down for a release. However, often there's a wider concept like with the scm part. The scm info in the pom of a release artifact can be used to retrieve that exact project. Very useful for open source projects where a lot of people are interested in quickly getting them. The benefit of not having to trying to find this info on the home page is not to ignore. So, do change them! :-) Or, at least make sure that the old url continue to work for released artifacts (the importance of this depends on the size of your audience). Regarding having to walk through all POMs that are using that value I'd argue that the benefit of having the value defined in a parent pom means you don't have to traverse every pom updating the old value. As you clearly understand the concepts I think I'm missing something to the story here... Regarding the settings.xml it would be very interesting to hear about some success story using the global settings.xml for corp wide stuff and the personal one just for passwords etc. How do you go about doing this in an agile, lightweight way? As the global settings.xml is part of the Maven installation, it will be replaced whenever a new Maven version is installed. This would either require a centrally re-package Maven bin or some tool for always keeping this file updated. I have always kept away from the global one for these reason. Any best-practice solution anyone can share? /Anders On Fri, Dec 11, 2009 at 07:46, Oskar Carlstedt oskar.carlst...@gmail.comwrote: Hello all of you! Thank for your replies. I've tested all strategies told here, except for using a plugin generating the settings.xml, in earlier projects. I never had the feeling feeling of hitting the big success. Maybe the plugin way will work. I can understand all arguments for not being able to change the pom after a release, and therefore all arguments of not having a version scope on the parent pom. For me this applies to all build logic, but not for distribution management, deploy management etc., etc. This is the case where I want to be able to change some settings, not changing the build itself. Let say we change the url to our SCM, then we have to change all POMs configured using the old SCM. This mitgh be a network problem, but still such things happens. Let say I change the URL to the location of my globally published WSDL files or other resources. Then it is a must to walk through all POMs that are using that value. Ok, in booth cases above I can put expected data into the settings.xml file. I don't like this way because I think settings.xml is the user's personal file and it does not have the purpose of holding default values. Further, all settings had during a build is not checked in during a release because these vales are put in the settings.xml file. But it might be the only way to go. So having a plugin generating the most up to date settings.xml file might be a good way finding the path to the big success. Maybe we shall vote for a extra feature in the release plugin that makes it possible to checkin the current settings.xml and the full build log when doing a release. Just to get the full trace of a build. Thank you all again for your answers! Cheers, Oskar -- View this message in context: http://old.nabble.com/Pattern-to-setup-common-organization-specific-data-in-single-pom--tp26723137p26739437.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: 401 error with Maven Release Plugin
You've tried different version of Maven? 2.2.1? 3.0-alpha-5? /Anders On Thu, Dec 10, 2009 at 21:49, Brendan Sibre bren...@sibre.net wrote: A previous poster wrote: Thanks for your response, this fixed the problem! However, another issue comes up - *release*:*perform* almost worked out except at the very end it failed to upload the artifact to the repo, and the error is [INFO] [INFO] Error deploying artifact: Failed to transfer file: .. Return code is: *401* I believe this is a permission related issue. But I've got the correct server username/password pairs in settings.xml and running the deploy goal in the lifecycle has no problem having the artifact deployed, it's just the *release*:*perform* that gets stuck with the permission problem. Anyone knows why this happens please? This is with an https url and, like the previous poster, I can do a maven deploy without any issues. Anyone have any ideas?
