Re: [VOTE] Retire Maven One Plugin
+1 Thanks Dennis! - Brett On 20/07/2013, at 7:13 PM, Dennis Lundberg wrote: > Hi, > > Now that we have Maven 1 at End-Of-Life, I think it's time to retire > Maven One Plugin as well. It has been almost six years since the last > release. I therefor propose that we retire maven-one-plugin. > > http://maven.apache.org/plugins/maven-one-plugin/ > > If this vote is successful I will make one final release of the > plugin, making it clear on the plugin site that it has been retired. > After that the source code will be moved into the "retired" area in > Subversion. > > The process for retiring a plugin is described here, and is being improved: > http://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Seeking Maven Way advice: repos in project profile?
On 23/10/2012, at 9:09 AM, Laird Nelson wrote: > A user of my jpa-maven-plugin (http://github.com/ljnelson/jpa-maven-plugin) > was complaining that he didn't know what repos to proxy (EclipseLink in > particular staunchly refuses to migrate their stuff to Central; their repo > is broken; we've tried to get them to fix it for years). We had an email > exchange about it during which I was sending him XML snippets for his > settings.xml. I was wondering if there was some way to indicate in a > slightly more rigorous manner than just "here, copy and paste this hunk of > XML" to public consumers such as this what repositories to proxy in their > own Nexus setups, or, as in his case, in his own settings.xml (I have no > control over whether he sets up a repository manager or not). > > I was looking for a semi-structured solution that would: > > (a) Do The Right Thing (i.e. nothing) for those of us running repository > managers, > (b) provide information for those of us running repository managers on what > repositories to proxy, and > (c) provide a simple switch to let other users get what they need > (-PnameOfTheProfileContainingNonCentralRepositoriesForLazyPeopleWhoDoNotSetUpNexus) Repositories in the POM are always a trade-off between making your build work "out of the box", and the problems they cause. They are almost always the wrong choice, but I believe your use case is the one exception (a public plugin) where it makes sense to just add them. The way I've approached this in another project is to add them to the plugin's POM, but also document for users how to set up a repository manager: http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/guide/devinfra/artifact-repository.html. Others here will likely disagree :) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven on a Terminal Server
Hi Terry, On 28/09/2012, at 9:41 AM, "Sposato, Terry" wrote: > Hi, > > We currently use Nexus as our project’s local repository server which works > well. > We also have a Terminal server which offshore developers access to do their > development/testing/building etc. > I want to know if there is a way of having all these users access the same > .m2 local repository which maven3 is using in a safe way? > I have currently set the path in settings.xml to use a local path, which at a > high level works, I am just not sure if this will cause issues moving forward? > > Please reply all as I am currently not subscribed to the list. Sharing the local repository is not advised. There's no external locking on files written there. Given you have a repository manager, as long as you have one geographically close to that terminal server (or on the machine), you typically give each user a local repository and are free to clean it out frequently if needed. Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter
Re: Executing a goal *after* install
Binding the mojo in the install phase will run it after anything already executed in the install phase, which should be sufficient for your use case (you can probably even run it in the package phase since everything attaching artifacts will happen there). - Brett On 25/07/2012, at 7:08 AM, Mirko Friedenhagen wrote: > Hello, > > in a multi-module project, I want to create a sha1 list of all > artifacts created. For that I created a Mojo which collects all > artifacts as well as attachedArtifacts from the executionRoot as well > as the invoking parent. Now I probably need a way to execute a plugin > *after* install ran in all projects. Is there a way to define that I > want to run the mojo "post-install"? > > Regards Mirko > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ClassNotFoundException: org.codehaus.classworlds.Launcher
On 24/07/2012, at 6:42 PM, Rui wrote: > Hi. I'm trying to use maven to make a version of some software I'm working on. > > Everything works fine (I can do 'mvn clean', 'mvn release:clean', and 'mvn > install' without problems) until I try to do 'mvn -Dmaven.test.skip=true > release:prepare), at which point I get the following error midway through the > process: > >[INFO] Not generating release POMs >[INFO] Executing goals 'clean verify install assembly:assembly'... >[WARNING] Maven will be executed in interactive mode, but no input stream > has been configured for this MavenInvoker instance. >[INFO] Exception in thread "main" java.lang.NoClassDefFoundError: > org/codehaus/classworlds /Launcher >[INFO] Caused by: java.lang.ClassNotFoundException: > org.codehaus.classworlds.Launcher >[INFO] at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >[INFO] at java.security.AccessController.doPrivileged(Native Method) >[INFO] at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >[INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) >[INFO] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >[INFO] at java.lang.ClassLoader.loadClass(ClassLoader.java:247) >[INFO] Could not find the main class: org.codehaus.classworlds.Launcher. > Program will exit. >[INFO] > >[ERROR] BUILD ERROR >[INFO] > >[INFO] Maven execution failed, exit code: '1' > > Help solving this issue would be greatly appreciated. This usually happens when M2_HOME does not match the path of the mvn executable. You should check they both match up (including whatever version is forked in this instance). Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 'mvn deploy' complaining that it cannot find what it is deploying
On 18/07/2012, at 6:05 AM, Benson Margulies wrote: > (http://maven.basistech.net/nexus/content/repositories/thirdpary/) I think you have mis-spelt "thirdparty". - Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Migrating from Maestro to Apache Maven - Archiva
Hi Alex, For Maven, you're essentially using Maven 2.0.4. The transition to Maven 3 should not be too painful from there. You should double-check your dependency resolution is still what you expect (that underwent some changes in Maven 2.0.6, but was largely unchanged after that). You should also look at https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes. For Archiva, you can get more help on the us...@archiva.apache.org list as that's now a separate project. You're using an incredibly old version there, so the configuration file will not be upgraded. You should start up the latest release of Archiva from http://archiva.apache.org/, create the repositories that you want, and then copy the repository data from your old installation into the locations you specified. It will automatically re-scan and index them for you. Hope that helps, Brett On 08/12/2011, at 2:17 AM, Alex. wrote: > Hi , > > We would to migrate from Maetro 1.1 to Apache Maven 3.0 -Archiva. > Any one have a good installation - configuration - integration guide? > > Best regards, > > Alex. -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Managing Different Java Versions
On 09/10/2011, at 11:25 AM, Eric Kolotyluk wrote: > I've been using Maven for about 6 months now so I am still a big green. > > Recently I discovered that my project needs to be compatible with client code > that requires Java 5, because it needs to run on OS 10.5 32-bit Intel. > Unfortunately I have been doing all my development with Java 6. I am almost > complete reworking things to run on a Java 5 run-time, and while everything > compiles, things are dying in hibernate somewhere because there are Java 6 > class files in some of the artifacts. Unfortunately from the diaganosics I > cannot tell which artifact I am importing that has the Java 6 class files. It should give you the name of the class itself, which you can search for in your repository manager or on one of the public instances of repository search to find out which JAR it is coming from. You might also try the animal sniffer plugin: http://mojo.codehaus.org/animal-sniffer-maven-plugin/examples/generating-other-api-signatures.html > > Is there some common wisdom or best practices on how to determine which Java > versions were used to build an artifact. I know you can specify a java > version in the classifier, but is there a way to search for specific > coordinates based on the classifier, or some way to tell Maven to only use > artifacts with a specific version of Java class files? Maven can't do dependency resolution based on this, because there is no global flag for a JAR that's applicable (each class in it can be different). - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Looking for free wrapper_windows_x86_64_exe version 3.2.3
As far as I recall, the x86_64 Windows wrapper has only been available since 3.3.0, and has always been commercial. You will have to contact Tanuki Software. - Brett On 29/09/2011, at 1:03 PM, Dan Tran wrote: > Hi > > the opensource version of java service wrapper ( JSW ) used by > appassembler-maven-plugin does not come with windows_x86_64 bit, > > and Sonatype's nexus community distribution has a copy of > wrapper_windows_x86_64_exe, and I believe is from version 3.2.3. > > Can we use this with appassembler-plugin and freely distribute it? > > Would Sonatype donate this bit to OS ? > > Thanks > > -Dan > > I queried Sonatype on the same question, but still waiting for an > official answer. > > http://getsatisfaction.com/sonatype/topics/free_wrapper_windows_x86_64_exe > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release from Git branch
On 17/09/2011, at 12:37 AM, Stuart Sierra wrote: > Hello list! > > I use Git, maven-release-plugin, Hudson, and the Hudson M2 Release > Plugin. Can I perform a release from a Git branch other than "master"? > > Right now, to do a release, Hudson checks out the "master" branch and > calls "mvn release:prepare release:perform". If the release succeeds, > the M2 Extra Steps Plugin runs "git push origin master `git tag | grep > -v ^hudson`" to update Git tags. > > If I change my Hudson config to build a different branch, like > "1.2.x", will the maven-release-plugin still do the right thing? I believe so. You may need to set the element in the section of the POM on the branch. In my experience, the release plugin correctly releases in that situation (I'm not using Hudson for that, however). - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can I run my class file(abc.java).
http://mojo.codehaus.org/exec-maven-plugin/usage.html (under "Java goal") On 01/08/2011, at 5:28 PM, kalnsh wrote: > I have Java, Eclipse, and Maven all installed. Please someone sent me a POM > file, and I need to call my.java file using pom file. > > Any help would be appreciated. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/How-can-I-run-my-class-file-abc-java-tp4654234p4654234.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Issue with building .net project through maven
You will need to provide more information about what you tried. What plugins are you using to build the .NET project? For example, is it http://incubator.apache.org/npanday/ ? - Brett On 11/05/2011, at 6:59 PM, sadaf2dec wrote: > I am getting below error while compiling my project with Maven. > "The project 'MyProject' is not a visual studio project" even it is a .net > project. > > Please help me on this. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Issue-with-building-net-project-through-maven-tp4386842p4386842.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
On 02/05/2011, at 8:11 PM, Andreas Sewe wrote: > Hi Brett, > >> I think in the Maven 3 version of the site plugin, you need to add >> the wagon as a dependency of the site plugin, instead of as an >> extension (which only applies to the core deployment components). > > thanks for your suggestion. I am afraid, it didn't help: When declaring a > plugin dependency, the maven-site-plugin now has both > org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and > org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it still > insists on using the latter for sftp URIs. :-( > > Any other suggestions? > Apologies for not noticing that detail sooner. The external wagon doesn't have a handler for sftp - only scpexe. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
I think in the Maven 3 version of the site plugin, you need to add the wagon as a dependency of the site plugin, instead of as an extension (which only applies to the core deployment components). On 02/05/2011, at 1:05 AM, Andreas Sewe wrote: > Hi, > > I am facing some problems deploying my project's site using sftp. For > testing purposes I thus want to switch wagons, namely from > org.apache.maven.wagon:wagon-ssh:1.0-beta-7 to > org.apache.maven.wagon:wagon-ssh-external:1.0-beta-7. However, even > adding the appropriate extension to my POM doesn't convince the > maven-site-plugin:3.0-beta-4-SNAPSHOT to pick a different wagon for the > sftp URI scheme. > > > org.apache.maven.wagon > wagon-ssh-external > 1.0-beta-6 > > > At least, I still get the same exception, which clearly says that I am > using the JSch-based Wagon and not an external ssh process: > > Caused by: 3: Permission denied >at > com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) >at com.jcraft.jsch.ChannelSftp.mkdir(ChannelSftp.java:1701) >at > org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdir(SftpWagon.java:204) >at > org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdirs(SftpWagon.java:184) >at > org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.putDirectory(SftpWagon.java:271) >... 25 more > [ERROR] > > Any suggestions? How does the maven-site-plugin map URI schemes to wagons? > > Also, is there any configuration option / system property to make the > wagon more chatty? Just running "mvn site-deploy -X" doesn't produce > enough information to track down what's actually going over the wire. :-( > > Best wishes, > > Andreas Sewe > > --------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configuring repositories
On 26/02/2011, at 1:41 PM, Mark wrote: > How can I configure maven to first check all the default repositories and if > a jar is not found THEN check our corporate repo (Archiva)? > > I've added the following to settings.xml however It tries to connect to this > repo first, not last. > > Foo > http://my.company.com:8080/archiva/repository/internal/ > > true > > > true > It depends where you've declared this, but generally due to inheritance rules this is going to take precedence over the built in ones. The only solution is to redeclare the default repository above the declaration you've given: central http://repo1.maven.org/maven2 ... Foo http://my.company.com:8080/archiva/repository/internal/ ... A better solution is to run a copy of Archiva on your own machine, and point your builds there for everything. You can then use proxy rules to direct only requests for corporate artifacts to the corporate repository, and take that connector offline when you're not on the VPN (as well as controlling timeouts). > > This repo will also only be available if I am connected to our VPN. Is there > also a way to configure a connect timeout so it doesn't hang for minutes when > Im not connected to the VPN? https://brettporter.wordpress.com/2009/06/16/configuring-maven-http-connections/ Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copying dependencies' binaries (dlls) for runtime
Resources are for things packaged and to be used at runtime - that doesn't sound like what you want here. This is typically done with a combination of the dependecy & assembly plugin. You might also be interested in NPanday (http://incubator.apache.org/npanday/) which provides several .NET specific plugins if that's the flavour of DLL you are dealing with. - Brett On 06/01/2011, at 11:22 AM, Phillip Hellewell wrote: > On Wed, Jan 5, 2011 at 4:32 PM, Phillip Hellewell wrote: >> >> My question now is, if I want to define the in a separate >> stand-alone xml file (actually there will be more than one), rather >> than in the pom.xml, what code/class do I use to read an xml file into >> a java.util.List of org.apache.maven.model.Resource? > > Would it work to take read the tag from my XML, surround > it with or whatever to make it a > valid pom, and then use the MavenXpp3Reader to parse that? > > I think I found the code where it parses a Resource, and obviously I > don't want to duplicate that code in my own plugin: > > http://maven.apache.org/ref/2.0.11/xref/org/apache/maven/model/io/xpp3/MavenXpp3Reader.html#4474 > > Phillip > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: The master password
I believe if you regenerated another settings-security.xml file with the same master password, while the hash would be different it would effectively decrypt the passwords. However, you make a good point - automatically generating it would be a nice additional feature. - Brett On 04/01/2011, at 7:40 PM, Anders Hammar wrote: > Is there any reason why I would need to remember my master password (used > for encrypting my server passwords in settings.xml)? I haven't found any and > I'm thinking that it could be auto-generated (by some tool) when creating > settings-security.xml, instead of specified by the user. > > /Anders -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Archiva 1.3.3 released
The Apache Archiva team would like to announce the release of Archiva 1.3.3. All users are advised to upgrade. Archiva is available for download from: * http://archiva.apache.org/download.html Archiva is an application for managing one or more remote artifact repositories, including administration, artifact handling, browsing and searching. If you have any questions, please consult: * the web site: http://archiva.apache.org/ * the archiva-user mailing list: http://archiva.apache.org/mail-lists.html ** Release Notes for Archiva 1.3.3 ** This release brings significant performance and memory improvements to large or frequent scanning and indexing operations, as well as diagnostic tools for reviewing the current server performance. [MRM-1097] - Error 500 "too many open files" [MRM-1369] - Editing user roles in archiva clobbers continuum redback roles [MRM-1396] - Purge task problem : Not enough parts to the path [MRM-1421] - Archiva repository purge incorrectly purges based on file timestamps even when the snapshot timestamp is known [MRM-1443] - repository statistics collection can cause server to hang [MRM-1416] - upgrade to Redback 1.2.5 [MRM-1439] - improve indexing performance [MRM-1440] - system status page [MRM-1441] - monitor repository scanning progress [MRM-1442] - track time spent in each consumer during a scan, to help diagnose poor scanning performance [MRM-1445] - disable referrer check by default -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deployment Advice?
On 16/12/2010, at 6:19 PM, Martin Höller wrote: > Hi Ron! > > Am Mittwoch 15 Dezember 2010, 23:04:49 schrieb Ron Wheeler: >> Use JNDI to manage the site specific aspects of your configuration. This >> will make deploying to test machines and production less painful. > > I saw you mentioning this a few times now. However, I don't get it what you > are actually doing here. Would you mind explaining this approach in more > detail. It's not strictly related to automated deployment (though it might help)... the basic idea is to ensure that a single WAR can be used in any environment without being rebuilt. So anything specific to a target environment is "externalised" - typically database connections or a set of properties. These can all be specified through JNDI, or other similar techniques. More information can be found at slide 31: http://brettporter.files.wordpress.com/2007/11/ac-us-07-maven-best-practices.pdf. Or for those that have it, chapter 7 of "Apache Maven 2: Effective Implementation". Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mvn3 book and documentation
All of the books covering Maven 2 are still relevant. There are several posts & the release notes around detailing the differences between the two, such as this one I wrote: https://brettporter.wordpress.com/2010/10/09/apache-maven-3-0-released-a-few-important-tips/ On 16/12/2010, at 5:26 AM, Michael Szalay wrote: > Hi all > > I've looking for a good book and/or other documentation which covers > the new features of mvn3. > Is there anything on the roadmap? > > Regards > Michael > > -- > Michael Szalay Senior Software Engineer > > basis06 AG, Birkenweg 61, CH-3013 Bern - Fon +41 31 311 32 22 > http://www.basis06.ch - source of smart business > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 doesn't download sources
There's a couple of potential things in the way you've described it: - Maven 3.0 does not support non-unique snapshots - you would need to use timestamps and rely on the repo manager to purge old versions - if I've misunderstood the above, the difference on timestamps is that Maven 3.0 will actually store separate metadata per classifier. They should be the same in the scenario you describe, but maybe Artifactory doesn't support the new metadata format and affects it in some way. HTH, Brett On 24/11/2010, at 3:21 AM, Stephen Connolly wrote: > Don't know what it should be but I think we may have found a possible > culpret. > > Check with Benjamin Bentmann, he'd know what m3 is supposed to do > > -Stephen > > On 23 November 2010 14:30, Moser, Christian wrote: > >> They are from snapshot artifacts. We use non-unique snapshots in >> artifactory. >> The sources are deployed on the same time like the compiled artifacts. So >> the timestamp should be equals, shouldn't it? >> If not, how could I archieve it? >> >> -Chris >> >> -Ursprüngliche Nachricht- >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> Gesendet: Dienstag, 23. November 2010 14:39 >> An: Maven Users List >> Betreff: Re: Maven 3.0 doesn't download sources >> >> Are these sources of snapshots or releases? >> >> If snapshots it may be that the sources were deployed with a different >> timestamp, in which case the maven metadata my not be letting maven 3 find >> the artifacts. >> >> IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might not >> trust it as much (but I could be wrong, my recollection is fuzzy) >> >> -Stephen >> >> On 23 November 2010 12:13, Moser, Christian wrote: >> >>> I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1 >>> with following command. >>> >>> >>> >>> Sources classifier is: -sources (default) >>> >>> >>> >>> "mvn -U validate dependency:sources -DoverWriteSnapshots=true >>> -DoverWriteReleases=true" >>> >>> >>> >>> >>> >>> the artifacts with classifier -sources are available in the locale >>> remote-repository manager (artifactory). >>> >>> >>> >>> Is there another call to force maven to download sources? >>> >>> >>> >>> Greez Chris >>> >>> >>> >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with release plugin versions
On 18/11/2010, at 10:10 AM, Todd Nine wrote: > Hi Brett, > There wasn't any version in my pom. I believe I've found the issue. > I had a repository that connected to github, which is issuing 301 > redirects. This bug is the underlying issue > > http://jira.codehaus.org/browse/WAGON-314 > > > Maven is downloading the http response as the pom.xml, which in turn > fails on the run because it is not a valid pom. Is there any progress > on this issue? > We discussed this on dev@ the other day, and are likely to push for another wagon release. On that issue specifically - we're looking for someone to update the patch that has fallen out of date. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: New version of Eclipse from Springsource
On 18/11/2010, at 4:51 PM, Ron Wheeler wrote: > On 17/11/2010 6:42 PM, Wayne Fay wrote: >>>> This seems off-topic for the Maven list? >>> Perhaps not. I like the fact that STS comes bundled with Maven >>> 2.2.1 and m2e. If you're a Maven developer then this is a good IDE bundle. >> I personally don't particularly mind the occasional Maven-related >> announcement like this, and believe there are a number of Maven >> users/developers who are using STS and appreciate it. I actually just >> pulled STS down for another machine just last week and got the old >> version, so this will cause me to go update several installs. >> >> Perhaps next time it should be tagged [OT] or even [ANN] in the >> subject to avoid any complaints? > I will do this if I have any news of this nature. > > I do feel that the ecosystem around Maven such as Nexus and Eclipse/STS are > very helpful in improving the role that Maven plays in development. > > I do not have any vested interest or participation in either of these > projects but I really encourage developers who are using Maven to get a Repo > going. I only know Nexus but I know that others here do use other repo > packages. > I used plain Eclipse for a couple of years before finding the STS version and > the integration of the Maven and all the other Java and Web tools into a > single download has been a great relief for our team. The Maven tools in > Eclipse/STS have really helped us understand and use Maven better. Sharing something like you just said, with the context of why you find it is helpful for Maven users, is totally appropriate. I post semi-OT stuff here all the time. I just couldn't make the connection from your brief email - and if we start talking about anything tangentially related to Maven, we could easily end up with threads about anything Java related :) Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: New version of Eclipse from Springsource
This seems off-topic for the Maven list? On 18/11/2010, at 2:31 AM, Ron Wheeler wrote: > I know that everyone thinks that I must have shares in Springsource/VMWare > but I just find that it is the best way to run Eclipse and build web > applications. > > There is a new version available. > Look at the datasheet at the bottom of the page on this link. > > http://www.springsource.com/landing/best-development-tool-enterprise-java?mkt_tok=3RkMMJWWfF9wsRokuqrKZKXonjHpfsX87u8rX7Hr08Yy0EZ5VunJEUWy2oAJT9QhcOuuEwcWGog80xxKE%2B6Sb49V6PZY > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with release plugin versions
Try mvn help:effective-pom to see if you've locked in the version. Otherwise, we would need to know if you were using a repository manager. - Brett On 18/11/2010, at 7:38 AM, Todd Nine wrote: > Hi all, > This morning I attempted to perform a release using maven v 2.2.1 > (r801777; 2009-08-07 07:16:01+1200). Maven downloaded new versions of > all my plugins, and now I receive the following error when trying to > perform a mvn release:prepare mvn release:perform > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Internal error in the plugin manager executing goal > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-8:prepare': > Unable to load the mojo > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-8:prepare' in > the plugin 'org.apache.maven.plugins:maven-release-plugin'. A required > class is missing: org/jdom/filter/Filter > org.jdom.filter.Filter > > > 2.1 is the current version for the "release" plugin. I haven't touched > my pom nor any of my settings.xml files. Any idea why maven now things > that 2.0-beta8 is the latest? > > Thanks, > > > todd > SENIOR SOFTWARE ENGINEER > > > > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[OT] BarCamp Apache Sydney - December 11, 2010
Hi, I figure there may be a few Sydneysiders on this list, so I thought you might be interested in attending a BarCamp at the University of Sydney next month. Please help us to spread the word. WHEN: Saturday 11 December. Registration is at 9:30am, for a 10:00am start. WHERE: The Darlington Centre, University of Sydney, at 174 City Road, Darlington. The event is free, but you need to sign up: http://barcamp.org/BarCampApacheSydney We will use the discussion group for updates and plans closer to the date: http://groups.google.com/group/barcamp-sydney The BarCamp is being run in conjunction with the Apache Software Foundation, and several Apache committers will be there proposing talks. However it is still run like a normal BarCamp, and given we haven't had one in Sydney in the last year we're expecting a diverse turn out. If you're interested in BarCamps and particularly Apache projects, please come along! There'll almost certainly be a chance to talk about Maven and related projects. We've ensured that wifi, snacks and some other goodies will be provided on the day. Lunch may also be provided, depending on available sponsorship. There will also be a dinner & drinks event the night before for those who are interested. See you there! Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maybe bug in release plugin for computing next dev release?
This was a known bug, fixed in maven-release-plugin 2.1. Are you using that release? On 01/11/2010, at 12:26 PM, Marshall Schor wrote: > I have a pom which has a property which has as a value "2.3.1-SNAPSHOT". > > The property is used to factor into one spot the version level for > dependencies, > where the dependencies are for other modules in a multi-module build (most of > which have the same > version level). > > When I do mvn release:prepare -DdryRun on a POM which includes this as a > module, > the release:prepare successfully updates the property, first, to "2.3.1" for > the > "tag", and then, for the next development version, to "2.3.2-SNAPSHOT". I > think > it figures out that this property is being used as a dependency version value, > and matches it to version levels of things in the "Reactor", to figure out it > needs updating. > > So far everything seems to be correct. > > But, if I do exactly the same thing, but leave off the "-DdryRun", it updates > the property, first (as before), to "2.3.1" for the tag, but then does *not* > update it for the next development version. > > Any idea why? Is this a (known) bug? I can, of course, work around this by > manually updating this property to the right level and committing that change > to > the trunk. > > -Marshall Schor > > > > ----- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release Plugin 2.1 : invalid label perforce scm provider 1.4
This was to avoid case-comparison issues where c:\something looked different to C:\something (MRELEASE-536). It seems like it shouldn't be persisting that change then. Can you file a new issue? On 12/10/2010, at 9:11 AM, Thiebaud, Christophe wrote: > Hi all, > > I just tested the brand new Release Plugin 2.1 and I found that the label > created by the perforce scm provider has an empty file set. > > Looking at the generated perforce label, I can see that the perforce view > specification is wrongly all lowercase. > > I then found that the ReleaseUtil.java getCommonBaseDir function produces a > lowercased result when running under Windows (which is the case for me). > > I guess that this is common base dir is then used then by the scm provider to > create the wrong perforce label. > > It looks it is rather a Release Plugin issue than a scm perforce provider > issue. > > My question is : why does getCommonBaseDir lowercase the common base dir ? > > Christophe > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to change the commit message when publishing a site to Subversion?
It's currently hardcoded in line 282 of org/apache/maven/wagon/providers/scm/ScmWagon.java in wagon-scm. It would be possible to move that up to wagon-level configuration, which would allow it to be set in settings.xml in the servers section - but that only gives you one value to replace it with. It isn't possible to use properties. For the site plugin specifically, it might be able to take some configuration to apply to the wagon which would allow greater flexibility, since I believe it's configuring it's own ones rather than using them from the core. - Brett On 12/10/2010, at 7:07 AM, Wendy Smoak wrote: > I'm using the site plugin with distributionManagement set to a > scm:svn:https://... url. This commits the generated site files to a > special place in Subversion where they are then visible as part of the > project's website. > > But... there is a pre-commit hook that requires every commit to be > associated with an issue tracker item. When this is enabled, I can't > publish the website anymore. > > Does anyone know if there is a way to change the commit message that > the Site Plugin (or is it Maven SCM?) sends when it commits the files? > > This would be similar to the scmCommentPrefix parameter in the Release > Plugin, which is what we use to insert an issue tracker key in those > commit messages. > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 3.0 Arftifact changes
Ok sorry, I wasn't looking closely enough at the error message. ArtifactTransformation has been hidden to avoid it being used going forward. So the options are to seek an alternative higher level API to obtain the information, or file a bug request to restore the interface. What's the reason that the plugin needs the transformation directly? To achieve what you were doing, normally you'd use the resolver, then read the metadata file through the artifact APIs to get the values rather than hooking into the transformation. Also, is this something that could be covered by the org.codehaus.mojo:versions-maven-plugin ? On 11/10/2010, at 7:22 PM, Jason Chaffee wrote: > Looks the maven dependencies are being excluded in the class realm. I am > noticing this for all the plugins executed. All of the org.apache.maven jars > are Excluded. > > [INFO] --- maven-version-plugin:1.0.0:version (default) @ cbsp --- > [DEBUG] com.ebates.maven.plugins:maven-version-plugin:jar:1.0.0: > [DEBUG]log4j:log4j:jar:1.2.16:compile > [DEBUG]org.apache.maven:maven-model:jar:2.2.1:compile > [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.15:compile > [DEBUG]org.apache.maven:maven-plugin-api:jar:2.2.1:compile > [DEBUG]org.apache.maven:maven-project:jar:2.2.1:compile > [DEBUG] org.apache.maven:maven-settings:jar:2.2.1:compile > [DEBUG] org.apache.maven:maven-profile:jar:2.2.1:compile > [DEBUG] org.apache.maven:maven-plugin-registry:jar:2.2.1:compile > [DEBUG] org.codehaus.plexus:plexus-interpolation:jar:1.11:compile > [DEBUG] > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile > [DEBUG] junit:junit:jar:4.8.1:test (scope managed from compile) > (version managed from 3.8.1) > [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:compile > [DEBUG]org.apache.maven:maven-artifact-manager:jar:2.2.1:compile > [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.2.1:compile > [DEBUG] > backport-util-concurrent:backport-util-concurrent:jar:3.1:compile > [DEBUG]org.apache.maven:maven-artifact:jar:2.2.1:compile > [DEBUG]com.svnkit:svnkit:jar:1.3.3:compile > [DEBUG] Created new class realm > plugin>com.ebates.maven.plugins:maven-version-plugin:1.0.0 > [DEBUG] Populating class realm > plugin>com.ebates.maven.plugins:maven-version-plugin:1.0.0 > [DEBUG] Included: com.ebates.maven.plugins:maven-version-plugin:jar:1.0.0 > [DEBUG] Included: log4j:log4j:jar:1.2.16 > [DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.15 > [DEBUG] Included: org.codehaus.plexus:plexus-interpolation:jar:1.11 > [DEBUG] Included: backport-util-concurrent:backport-util-concurrent:jar:3.1 > [DEBUG] Included: com.svnkit:svnkit:jar:1.3.3 > [DEBUG] Excluded: org.apache.maven:maven-model:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-project:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.2.1 > [DEBUG] Excluded: > org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 > [DEBUG] Excluded: junit:junit:jar:4.8.1 > [DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2 > [DEBUG] Excluded: org.apache.maven:maven-artifact-manager:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.2.1 > [DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.2.1 > > > > -Original Message- > From: Brett Porter on behalf of Brett Porter > Sent: Mon 10/11/2010 12:44 AM > To: Maven Users List > Subject: Re: 3.0 Arftifact changes > > > On 11/10/2010, at 5:42 PM, Jason Chaffee wrote: > >> Yes. >> >> The 2.2.1 is configured in the parent pom dependencyMangement. >> >> I remember Jason saying talking about the Artifact refactoring about a year >> ago and saying it would not be backwards compatible with 2.0 and that if you >> had plugins using Artifact resolution you would need to rewrite them in 3.0. >> That is why I thought this particular plugin is failing. I tagged it as >> something I would need to refactor with 3.0. >> >> Is this no longer the case with 3.0? > > Nope, that was never the case on trunk. For example, the Compiler plugin > depends on 2.0.6 APIs for maven-artifact and maven-core. > > Something is wrong in the way that it is loading your libraries - maybe > running with -X will show how it constructs the plugin's dependencies and > point to the issue. > > You could also try re-compiling the plugin with Maven 3, see if it builds
Re: 3.0 Arftifact changes
On 11/10/2010, at 5:42 PM, Jason Chaffee wrote: > Yes. > > The 2.2.1 is configured in the parent pom dependencyMangement. > > I remember Jason saying talking about the Artifact refactoring about a year > ago and saying it would not be backwards compatible with 2.0 and that if you > had plugins using Artifact resolution you would need to rewrite them in 3.0. > That is why I thought this particular plugin is failing. I tagged it as > something I would need to refactor with 3.0. > > Is this no longer the case with 3.0? Nope, that was never the case on trunk. For example, the Compiler plugin depends on 2.0.6 APIs for maven-artifact and maven-core. Something is wrong in the way that it is loading your libraries - maybe running with -X will show how it constructs the plugin's dependencies and point to the issue. You could also try re-compiling the plugin with Maven 3, see if it builds, then try using that snapshot and see if it works. That would eliminate a complete incompatibility. > > Even so, it is perplexing as to why a class would not be found in 3.0 but was > found properly in 2.0 with the same plugin jar. This is usually a difference in the way the POM is loaded, and as such the way the the dependency JARs are included in the classloader. The fact that it's Maven ones missing does make it suspicious to the core differences, but it also clearly works in other POMs. Another thing to check is if the dependency POM is more strictly validated and failing (you should see something in the build for that), or if there are some other potential changes like an for one of those libraries in the tree, or a flag. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 3.0 Arftifact changes
They should be fine. Just to be clear, they are in the maven-version-plugin-1.0.0.pom, in the local repository? On 11/10/2010, at 4:07 PM, Jason Chaffee wrote: > I should add that the version on all of these is 2.2.1 > > > -Original Message- > From: Jason Chaffee [mailto:jchaf...@ebates.com] > Sent: Sun 10/10/2010 9:54 PM > To: Maven Users List; Maven Users List > Subject: RE: 3.0 Arftifact changes > > I have these dependencies in my pom: > > > org.apache.maven > maven-model > > > org.apache.maven > maven-plugin-api > > > org.apache.maven > maven-project > > > org.apache.maven > maven-artifact-manager > > > org.apache.maven > maven-artifact > > > > -Original Message- > From: Brett Porter on behalf of Brett Porter > Sent: Sun 10/10/2010 7:36 PM > To: Maven Users List > Subject: Re: 3.0 Arftifact changes > > It looks like you were missing a dependency before - there's no dep on > maven-artifact or maven-model. Do you have them in your POM? > > I can see why it would have run in 2.0, but not sure how it ever compiled :) > > - Brett > > On 11/10/2010, at 12:56 PM, Jason Chaffee wrote: > >> Yes, I meant does not work. >> >> Here are the errors: >> >> There are several Error messages: >> >> >> [ERROR] Failed to execute goal >> com.ebates.maven.plugins:maven-version-plugin:1.0.0:version (default) on >> project domain-api: Execution default of goal >> com.ebates.maven.plugins:maven-version-plugin:1.0.0:version failed: Unable >> to load the mojo 'version' in the plugin >> 'com.ebates.maven.plugins:maven-version-plugin:1.0.0'. A required class is >> missing: Lorg/apache/maven/artifact/transform/ArtifactTransformation; >> [ERROR] - >> [ERROR] realm =plugin>com.ebates.maven.plugins:maven-version-plugin:1.0.0 >> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy >> [ERROR] urls[0] = >> file:/Users/jasonchaffee/.m2/repository/com/ebates/maven/plugins/maven-version-plugin/1.0.0/maven-version-plugin-1.0.0.jar >> [ERROR] urls[1] = >> file:/Users/jasonchaffee/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar >> [ERROR] urls[2] = >> file:/Users/jasonchaffee/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar >> [ERROR] urls[3] = >> file:/Users/jasonchaffee/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar >> [ERROR] urls[4] = >> file:/Users/jasonchaffee/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar >> [ERROR] urls[5] = >> file:/Users/jasonchaffee/.m2/repository/com/svnkit/svnkit/1.3.3/svnkit-1.3.3.jar >> [ERROR] Number of foreign imports: 4 >> [ERROR] import: Entry[import org.codehaus.plexus.util.xml.pull.XmlSerializer >> from realm ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import >> org.codehaus.plexus.util.xml.pull.XmlPullParserException from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParser >> from realm ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.util.xml.Xpp3Dom from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] >> [ERROR] realm =maven.api >> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy >> [ERROR] Number of foreign imports: 21 >> [ERROR] import: Entry[import org.sonatype.aether from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.personality from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.logging from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.lifecycle from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.context from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.container from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.configuration from realm >> ClassRealm[plexus.core, parent: null]] >> [ERROR] import: Entry[import org.codehaus.plexus.component from realm >> ClassRealm[plexus.core, parent: null]
Re: 3.0 Arftifact changes
t: Entry[import org.codehaus.plexus.ComponentRegistry from realm > ClassRealm[plexus.core, parent: null]] > [ERROR] import: Entry[import org.codehaus.classworlds from realm > ClassRealm[plexus.core, parent: null]] > [ERROR] import: Entry[import org.apache.maven from realm > ClassRealm[plexus.core, parent: null]] > [ERROR] > [ERROR] -: > org.apache.maven.artifact.transform.ArtifactTransformation > > > > > > > -Original Message- > From: Brett Porter on behalf of Brett Porter > Sent: Sun 10/10/2010 6:40 PM > To: Maven Users List > Subject: Re: 3.0 Arftifact changes > > I assume you mean "does not work". These APIs should continue to work without > modification, as it's commonly used in other plugins. > > What's the problem you're seeing? > > - Brett > > On 11/10/2010, at 11:35 AM, Jason Chaffee wrote: > >> I have a custom plugin that is using the following classes from maven 2.x. >> >> import org.apache.maven.artifact.Artifact; >> import org.apache.maven.artifact.repository.ArtifactRepository; >> import org.apache.maven.artifact.repository.DefaultArtifactRepository; >> import org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout; >> import >> org.apache.maven.artifact.repository.metadata.RepositoryMetadataResolutionException; >> import org.apache.maven.artifact.transform.ArtifactTransformation; >> import org.apache.maven.model.DeploymentRepository; >> import org.apache.maven.model.DistributionManagement; >> >> In particular, this plugin will fetch the maven-metadata.xml for a given >> artifact to fetch the previous build number and some other info for storing >> in a metadata file that bundled with the build and to use in the artifact >> manifest. >> >> This plugin does now work with 3.0 because of the refactoring. Is there any >> documentation or a plugin I can look at for an example? Or, is there an >> easier way to get this info in 3.0? >> >> thanks, >> >> Jason >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > > > > > > - > 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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 3.0 Arftifact changes
I assume you mean "does not work". These APIs should continue to work without modification, as it's commonly used in other plugins. What's the problem you're seeing? - Brett On 11/10/2010, at 11:35 AM, Jason Chaffee wrote: > I have a custom plugin that is using the following classes from maven 2.x. > > import org.apache.maven.artifact.Artifact; > import org.apache.maven.artifact.repository.ArtifactRepository; > import org.apache.maven.artifact.repository.DefaultArtifactRepository; > import org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout; > import > org.apache.maven.artifact.repository.metadata.RepositoryMetadataResolutionException; > import org.apache.maven.artifact.transform.ArtifactTransformation; > import org.apache.maven.model.DeploymentRepository; > import org.apache.maven.model.DistributionManagement; > > In particular, this plugin will fetch the maven-metadata.xml for a given > artifact to fetch the previous build number and some other info for storing > in a metadata file that bundled with the build and to use in the artifact > manifest. > > This plugin does now work with 3.0 because of the refactoring. Is there any > documentation or a plugin I can look at for an example? Or, is there an > easier way to get this info in 3.0? > > thanks, > > Jason > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ${version} in 3.0
It sounds like the warning in Maven needs to be updated to show the location.
Did you check your local repository as well?
On 11/10/2010, at 8:15 AM, Jason Chaffee wrote:
> I do have properties like this though:
>
>
>
> that I then use ${spring.version}
>
>
> -Original Message-
> From: Jason Chaffee [mailto:jchaf...@ebates.com]
> Sent: Sun 10/10/2010 2:12 PM
> To: Maven Users List; Maven Users List
> Subject: RE: ${version} in 3.0
>
> checked every file. It does no exist anywhere.
>
>
> -Original Message-
> From: Marshall Schor [mailto:m...@schor.com]
> Sent: Sat 10/9/2010 7:18 PM
> To: Maven Users List
> Subject: Re: ${version} in 3.0
>
> also check parent poms.
>
> -Marshall Schor
>
> On 10/9/2010 8:35 PM, Niall Pemberton wrote:
>> On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee wrote:
>>> I am getting this warning for every module, yet I am not using this
>>> variable any of the poms. Some poms do have ${project.version} but some of
>>> them don't have any variable expressions at all and it is still outputting
>>> this warning.
>>>
>>> Does this warning just get output regardless of what is the the pom?
>>>
>>> [WARNING] The expression ${version} is deprecated. Please use
>>> ${project.version} instead.
>> What about other places like assembly plugin config files?
>>
>> Niall
>>
>> -
>> 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
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Release Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven Release Plugin,
version 2.1
This plugin is used to release a project with Maven, saving a lot of
repetitive, manual work. Releasing a project is made in two steps: prepare and
perform.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-release-plugin
2.1
Release Notes - Maven Release Plugin - Version 2.1
** Bug
* [MRELEASE-128] - SCM properties being replaced during release:perform
* [MRELEASE-317] - release:prepare should fail if any pom depends on
SNAPSHOT parent
* [MRELEASE-318] - Release plugin throws NullPointerException when using
version range for dependency
* [MRELEASE-350] - Option '0' for "specify the selection number ( 0:All
1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ):" is broken
* [MRELEASE-370] - release:prepare is not updating inter-modules
dependencies to the next version snapshot identifier correctly (-DdryRun=true).
* [MRELEASE-458] - Branch Does Not Honor updateWorkingCopyVersions Setting
* [MRELEASE-524] - command line versions don't seem to work on
release:branch for specific format
* [MRELEASE-536] - CommonBasedir Calculation fails on windows
* [MRELEASE-546] - regression introduced in MRELEASE-261
* [MRELEASE-551] - Unable to release with maven 3 when having no
$HOME/.m2/settings.xml
* [MRELEASE-563] - help strings need help, they are not helpful out of
context
* [MRELEASE-586] - release:perform - The temporary file "pom.xml.branch"
should be ignored as "pom.xml.next" and "pom.xml.tag" are ignored
* [MRELEASE-589] - Resolved dependencies overwritten when multiple
subprojects with SNAPSHOT dependencies are released
** Improvement
* [MRELEASE-497] - Don't overwrite SVN auth cache
* [MRELEASE-530] - Git provider does 'git push' during 'mvn
release:prepare' which causes unwanted problems (scm 1.4 upgrade)
* [MRELEASE-554] - Allow custom files to be modified before doing a prepare
or branch...
* [MRELEASE-583] - Better Snapshot Dependency Handling
Enjoy,
-The Maven team
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
Are you using Safari? There's a long standing issue that it would download a HTML page instead for the .gz when you go via the mirror script. - Brett On 09/10/2010, at 12:09 AM, Nayan Hajratwala wrote: > The ZIP appears to be working fine, but the tar.gz is only downloading a > 12.3K file > --- > Nayan Hajratwala > http://agileshrugged.com > http://twitter.com/nhajratw > 734.658.6032 > > On Oct 8, 2010, at 8:06 AM, Jason van Zyl wrote: > >> The day has finally come, Maven 3.0 is here: >> >> http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ >> >> Big thanks to Benjamin Bentmann!! >> >> Come and get it! >> >> http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip >> >> http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> What matters is not ideas, but the people who have them. Good people can fix >> bad ideas, but good ideas can't save bad people. >> >> -- Paul Graham >> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven generated MANIFEST.MF: Commit or ignore?
Aren't they generated into target usually, and rebuilt on each build? Doesn't sound like something to check in. On 08/10/2010, at 11:31 AM, Paul Benedict wrote: > Can anyone recommend whether to SCM commit the generated MANIFEST.MF > files? Or should they just be ignored? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Difference between archetype:create and archetype:generate?
create doesn't do any prompting for missing arguments or utilise newer features like the catalog. It's deprecated, and I think actually delegates to generate internally. On 06/10/2010, at 11:28 PM, benxs wrote: > > What is the difference between these two goals? > > From my point of view both generate a project (directory structure). > > Ben > -- > View this message in context: > http://maven.40175.n5.nabble.com/Difference-between-archetype-create-and-archetype-generate-tp3201300p3201300.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Early Bird ends this Friday: Maven Training @ ApacheCon Atlanta
Hi all, A brief reminder that ApacheCon is coming up fast (Nov 1 - 5)! There's still time to register for the early bird rates. Of interest to this group, the following 1-day Maven training is scheduled: Apache Maven: Effective Implementation (http://na.apachecon.com/c/acna2010/sessions/628) Registration: http://guest.cvent.com/d/sdqfjv There is usually also a Maven Meetup scheduled on one of the nights, with several Maven developers in attendance. In addition to the training and BarCamp, the conference has tracks that include NoSQL, Content Technology, Hadoop, Tomcat, Lucene, OSGi, Java Enterprise Development, Business & Community. Hope to see you there! Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Failing a build with maven-failsafe-plugin
Add: verify and make sure you run up until that phase. Cheers, Brett On 05/10/2010, at 10:46 PM, Thomas Sundberg wrote: > integration-test -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploy large files
apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) > at > hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) > at > hidden.org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) > at > org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:446) > at > org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:330) > ... 24 more > [INFO] > > [INFO] Total time: 3 minutes 21 seconds > [INFO] Finished at: Wed Sep 29 10:43:14 CEST 2010 > [INFO] Final Memory: 36M/65M > [INFO] > > Finished: FAILURE > > > On Wed, Sep 29, 2010 at 1:47 PM, Brett Porter wrote: >> >> >> On 29/09/2010, at 7:51 PM, Em DauPhu wrote: >> >>> It doesn't seem related to the MRM as I get the same error with >>> Archiva or Nexus. >>> Btw I already set that property and the upload via the webapp works >>> fine but I don't want to do it manually. >>> I could submit the form automatically as well but that's not the point. ;) >> >> It sounds related to the double upload issue. Are you using dav:http:// or >> just http:// ? Do you have any of the other configuration options set >> somewhere? >> >> - Brett >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> >> >> >> >> >> - >> 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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Does Maven support this workflow?
Yes, though native support for (8) isn't particularly strong or easy. Different Maven plugins tend to help with that support in specific domains. You might be interested in looking at NPanday (http://incubator.apache.org/npanday/), which already provides some integration with VS, .sln files and msbuild - though it is focused at .NET C# and VB and may need some changes to support C++. You might also be interested in the "NAR" plugin, though I'm not sure what it's latest home is. - Brett On 01/10/2010, at 7:07 AM, Phillip Hellewell wrote: > Hi all, > > I'm investigating Maven for use at my company and would like to know if it > will support our desired workflow. Mainly I need to know if there are any > major issues that could not be solved with plugins. > > 1. Manage C++ and C# projects. > 2. Manage artifacts at the .sln level, not the .vcproj level. > 3. Append SVN tag name automatically to the artifact version. > 4. Compile phase simply invokes MSBuild.exe on the .sln using the > exec-maven-plugin. > 5. Create separate packages for headers, static libs, and dlls produced by a > build. > 6. For dependencies, specify which packages are needed (e.g., only dlls). > 7. Ability to obtain not only a packaged dependency from a remote to a local > repository, but also the ability to check out the source code for that > dependency from SVN, build it, and install it to the local repository. > 8. Use profiles to indicate the type of build a developer cares about (e.g., > Release|x64), and have this profile apply to every stage (fetching > dependencies, compile, install). > > Thanks, > Phillip -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploy large files
On 29/09/2010, at 7:51 PM, Em DauPhu wrote: > It doesn't seem related to the MRM as I get the same error with > Archiva or Nexus. > Btw I already set that property and the upload via the webapp works > fine but I don't want to do it manually. > I could submit the form automatically as well but that's not the point. ;) It sounds related to the double upload issue. Are you using dav:http:// or just http:// ? Do you have any of the other configuration options set somewhere? - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why? Maven 2.2.1 defaults to maven-surefire-plugin 2.4.3
The Surefire releases are more recent than the Maven 2.2.1 release. On 29/09/2010, at 12:40 AM, Chris Audley wrote: > I spent some time banging my head this morning because I couldn't get > the systemPropertyVariables element in the maven-surefire-plugin > configuration to work. After a while I realized that Maven was > defaulting to maven-surefire-plugin 2.4.3 and I was trying to use a > feature introduced in 2.5. > > OK, so I can update pluginManagement to pull in surefire 2.6, or I can > fall back to the older systemProperties element. > > My question is, why is Maven still using 2.4.3? Is it just that maven > hasn't been updated recently, or is there some kind of issue with > using 2.5 or above? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin to check SCM location
It sounds like you're on the right track - you're correct, that it would need to go into the validation logic of maven-scm (though not necessarily the maven-scm-plugin). 2010/9/28 Lóránt Pintér > I'd be willing to do this, but I have no clue what to change. > > Should this check be part of the SCM plugin itself, like part of the > validate goal, or maybe a new goal? In this case, I'd need to add something > like ScmProvider.getUrl(ScmRepository repository, String rootPath); That > means that all SCM providers would need to be updated. > > Or shall I add this only for the Subversion provider(s)? In that case, > there > is an ScmProvider.validateScmUrl() method, but it doesn't know about the > location of the working copy. So, again, another method should be added > like > ScmProvider.validateScmUrlAgainstWorkingCopy(String scmUrl, ScmRepository > repository, String rootPath);, and it would require a change in all SCM > providers again. > > Lóránt > > On Tue, Sep 28, 2010 at 09:04, Brett Porter wrote: > > > > > On 28/09/2010, at 4:01 PM, Lóránt Pintér wrote: > > > > > My problem with both these options is that they'd only check the syntax > > of > > > the URLs. My problem is more like > > > "MRELEASE-494<http://jira.codehaus.org/browse/MRELEASE-494>: > > > Should fail during release:prepare if scm:url doesn't match working > > copy". > > > > Ok, they should be part of one check, but I can see why they might be > > implemented separately. > > > > > Is there a plugin/goal/way to check this, at least before the release? > > > > None that I know of - I'm sure it's not too hard to implement though if > > you'd like to take a shot at a patch! > > > > Cheers, > > Brett > > > > -- > > Brett Porter > > br...@apache.org > > http://brettporter.wordpress.com/ > > > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > -- Brett Porter http://brettporter.wordpress.com/
Re: Release plugin to check SCM location
On 28/09/2010, at 4:01 PM, Lóránt Pintér wrote: > My problem with both these options is that they'd only check the syntax of > the URLs. My problem is more like > "MRELEASE-494<http://jira.codehaus.org/browse/MRELEASE-494>: > Should fail during release:prepare if scm:url doesn't match working copy". Ok, they should be part of one check, but I can see why they might be implemented separately. > Is there a plugin/goal/way to check this, at least before the release? None that I know of - I'm sure it's not too hard to implement though if you'd like to take a shot at a patch! Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin to check SCM location
You can also vote for http://jira.codehaus.org/browse/MRELEASE-512 On 28/09/2010, at 4:36 AM, Anders Hammar wrote: > The validate mojo does what you're asking for ( > http://maven.apache.org/scm/plugins/validate-mojo.html). So if you get that > executed early in the release process you would do that. > I guess there are several ways of doing that. One having a release profile > with this binding. Another specifying scm:validate as a preparationGoal for > the release:prepare process. > > /Anders > > 2010/9/27 Lóránt Pintér > >> Hi, >> >> The release plugin checks a lot of things, like local modifications >> and such, but the contents of the tag is not among them. I'm not >> sure if it is possible to check with every SCM provider, but with SVN >> it would be nice if it threw an error (preferably in the beginning) if >> the connection points to a wrong location. We have just managed to >> release the wrong branch for the umpteenth time. :) Is this possible >> to solve? >> >> Thanks, >> Lóránt >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plans to release Maven 3.0
Most are seeing it in the other direction. Are you able to reproduce it on a sample project you can post? Or is there anything distinctive about the build that is slower? Do you notice where it spends most of its time? - Brett On 10/09/2010, at 11:49 PM, Tim wrote: > I've been using m3 for a while now but just switched over to beta 3. > This version is vastly more stable than the previous versions > (seemingly obvious statement :)) > But it is definitely slower than version 2x. > I'm seeing a consistent ~10-20% increase in build times (a 50 second > build increased to a minute etc) > When I run it with -T 2 or -T 1c (on 2 core MBP) I am able to get back > that build time increase but not gain any. > I have not tried it with maven shell in this version. > Anyone else seeing the same thing? > > On Wed, Sep 8, 2010 at 8:49 AM, Brian Fox wrote: >> On the dev list we've been discussing more formal plans to drive to >> the Maven 3.0 final release. The plan is to release weekly release >> candidate releases with the goal of having 3.0 final by the beginning >> of October. So far Maven 3.0 beta 3 is pretty stable with only a >> couple of regressions identified. We need your help to determine what >> else needs to be fixed before the final release. So if you haven't >> yet, we would like you to grab the latest 3.x build and give us your >> feedback. You can find the download link here: >> http://maven.apache.org/download.html >> >> >> --Brian >> Apache Maven PMC Chair >> >> - >> 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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: SFTP wagon host key requires user input
On 09/09/2010, at 10:46 PM, fhomasp wrote: > > Thanks for the answer, > > a quick question about that though before I try. Won't this deny access to > my buildserver? No... you're on the build server, modifying known_hosts which is outgoing. On 09/09/2010, at 11:06 PM, fhomasp wrote: > > Hmm.. So I set this to yes, how do I record the key? 'Yes' was the default, so no need to set it if you still want to check the known hosts. You can record the key by performing a command line sftp operation on the build host to the target host and accepting the prompt so that it is recorded in ~/.ssh/known_hosts for the build server user. Then Maven will find it in future. But if you trust the connection, you can safely set the option to 'no' as described and Maven won't ask regardless. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: wagon-users-unsubscr...@maven.apache.org For additional commands, e-mail: wagon-users-h...@maven.apache.org
Re: Why my OpenQA repository is not used..?
er what to do.. > > I have the following content in the file .m2/.settings.xml > > > http://maven.apache.org/SETTINGS/1.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 > http://maven.apache.org/xsd/settings-1.0.0.xsd";> > >org.grails >org.mortbay.jetty > > > > >true > > > > OpenQA > OpenQA repository > >true > > >false > > http://nexus.openqa.org/content/repositories/releases/ > > > maven2 > Maven2 repository > >true > > >false > > http://repo2.maven.org/maven2/ > > > ibiblio > ibiblio repository > >true > > >false > > http://www.ibiblio.org/maven/ > > > maven > Maven repository > >true > > >false > > http://mvnrepository.com/ > > > > > > > And in my pom.xml I have the following content > > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > com.thalasoft.webtest > thalasoft-webtest > jar > 1.0-SNAPSHOT > thalasoft-webtest > http://maven.apache.org > > > selenium > > > selenium > > > > > > > org.codehaus.mojo > selenium-maven-plugin > 1.0.1 > > > > > >org.codehaus.mojo >selenium-maven-plugin > > >start >pre-integration-test > > start-server > > > true > true > true > > > >stop >post-integration-test > > stop-server > > > > > > > >/path/to/dev/appserver > > > > > > junit > junit > 4.1 > test > > > org.openqa.selenium.server > selenium-server > 1.0-beta-1 > > > org.openqa.selenium.client-drivers > selenium-java-client-driver > 1.0-beta-1 > > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Why-my-OpenQA-repository-is-not-used-tp2800226p2800226.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin rollback and subversion
Yes, it's a known issue that rollback doesn't remove any created tags. You should remove it manually. - Brett On 27/08/2010, at 11:56 PM, Timothy Mcginnis wrote: > Hello, > > I am trying to use Subversion with Maven for the first time. For the past > two years I have been using CVS. > > My situation is that I run a "release:prepare" successfully. Then I need > to run a "release:rollback" to fix something. When I try to run the > "release:prepare" again I get an error saying the path already exists in > my subversion repository. And if I go check in there is definitely a tag > in subversion for the release. Do I have to manually tell subversion to > remove the tag? Or am I doing something wrong? > > Tim McGinnis > 717 720-1962 > Web Development > AES/PHEAA > == > This message contains privileged and confidential information intended for > the above addressees only. If you > receive this message in error please delete or destroy this message and/or > attachments. > > The sender of this message will fully cooperate in the civil and criminal > prosecution of any individual engaging > in the unauthorized use of this message. > == -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting Error - Couldn't find a version in [11.0] to match range [9.0,11.0)
Seems the weblogic plugin doesn't support version 11.0 (it is looking for 9.0
<= version < 11.0)
On 13/08/2010, at 1:26 AM, Arunkumar wrote:
>
> Hi,
>
> I am trying to automate the Weblogic deployment using Maven. I am using
> Weblogic 11g.
> Here is my pom.xml
>
> org.codehaus.mojo
> weblogic-maven-plugin
> 2.9.1
>
>
> deploy
>
> deploy
> start
>
>
>
>
> dataselector-web
>
> localhost
> 7001
> t3
> admin
> Password1234$
> true
> true
> false
> false
> myserver
> true
>
>
>
> weblogic
> wlfullclient
> ${weblogic.version}
>
>
> weblogic
>
> com.bea.core.descriptor.wl
> 1.1.0.0
> provided
>
>
>
>
> I am using the following mvn istall cmds
> mvn install:install-file -DgroupId=weblogic
> -DartifactId=com.bea.core.descriptor.wl -Dversion=1.1.0.0 -Dpackaging=jar
> -Dfile=C:\Documents\wls1033_dev\modules\com.bea.core.descriptor.wl_1.3.2.0.jar
>
> mvn install:install-file -DgroupId=weblogic -DartifactId=wlfullclient
> -Dversion=11.0 -Dpackaging=jar
> -Dfile=C:\Documents\wls1033_dev\wlserver\server\lib\wlfullclient.jar
>
> mvn install:install-file -DgroupId=weblogic -DartifactId=weblogic
> -Dversion=11.0 -Dpackaging=jar
> -Dfile=C:\Documents\wls1033_dev\wlserver\server\lib\weblogic.jar
>
> The error msg is:
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Failed to resolve artifact.
>
> Couldn't find a version in [11.0] to match range [9.0,11.0)
> weblogic:weblogic:jar:null
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> codehaus.org (http://repository.codehaus.org),
> snapshots (http://snapshots.repository.codehaus.org)
>
> Path to dependency:
>1) org.codehaus.mojo:weblogic-maven-plugin:maven-plugin:2.9.1
>
>
>
> Pls let me know where am i going wrong.
>
> TIA
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Getting-Error-Couldn-t-find-a-version-in-11-0-to-match-range-9-0-11-0-tp2473346p2473346.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
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin: Accessing version numbers from custom mojos during a run goal
On 06/08/2010, at 9:12 PM, Mark Derricutt wrote:
> Hey all,
>
> I'm wanting to write a mojo to run as part of my release process ( by
> declaring it in the element of the release plugin, but I
> want to know the release version, and the next-release version as used by
> the release plugin.
The release version will be ${project.version} at that point.
>
> Are these values stored in any system parameters at all? It doesn't look
> like they're stored in the release.properties file and even if they were, I
> don't like the idea of just assuming this file will exist.
Not in sys properties, but I would have thought they were in release.properties
(probably several of them, per module). I'm not sure why you wouldn't be
comfortable reading that since it has to be there (it's certainly an
implementation leak, but not one that seems likely to change).
Other than that, I think you'd need to change the release plugin to pass them
to the preparation goals as a system property (though again there's the
difficulty of potentially not being the same for every module).
- Brett
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-shared-io gone from http://svn.apache.org/repos/asf/servicemix/m2-repo/
You'd have to ask the ServiceMix developers. It was probably not meant to be there in the first place, since if it's the same artifact, it's already on central: http://repo2.maven.org/maven2/org/apache/maven/shared/maven-shared-io/1.1/ - Brett On 03/08/2010, at 3:55 AM, Andrew Hamilton wrote: > I had a project pulling maven-shared-io 1.1 from > http://svn.apache.org/repos/asf/servicemix/m2-repo/ > Is there some background to that artifact not being there any more? > > Thanks, > Andrew -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to clear cache used in DefaultMavenProjectBuilder
If you're doing this in a mojo, you're stuck with the version Maven gives you. In that case, you can clear it like the following: http://archiva.apache.org/ref/1.1.2/xref/org/apache/archiva/consumers/dependencytree/DependencyTreeGeneratorConsumer.html#249 You'll want to ignore the exception in case it is running in Maven 3 where the field won't be present. If you're doing this outside of Maven, I recommend using the Maven 3 beta libraries. You can see an example here: http://archiva.apache.org/ref/1.4-SNAPSHOT/xref/org/apache/archiva/metadata/repository/storage/maven2/Maven2RepositoryMetadataResolver.html#166 Cheers, Brett On 03/08/2010, at 4:55 PM, amaresh mourya wrote: > Hi All, > > In DefaultMavenProjectBuilder.java, there is one private hash map called > rawProjectCache, which stores the last discovered projects. > But i want each time it to read the pom file and return me the current model > of pom.xml > > My Use case is: > I have a pom.xml (say Child), this has parent pom.xml (say Parent) > Now I want to build the Child and want the list of repositories (I want to > have all repositories referred by this Child, its own and of its ancestors) > First time it gives me the correct list of repositories(its and Parent's), > after this if I made some change in Parent(add in pom.xml), and > try to again get the list of repositories, I am not getting the latest list, > but the last one from the Parent, reason being before reading the Parent's > pom.xml it searches it in rawProjectCache(as mentioned above) and return > from there. > > So How can I clear this cache. I am using plexuscontainer to get the > instances of DefaultMavenProjectBuilder. > > Any Idea would be helpful. > Thanks, > Amaresh -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: wagon-webdav
This could be an incompatibility with Maven 3. Have you tried with Maven 2.2.1? On 31/07/2010, at 4:46 AM, Meeusen, Christopher W. wrote: > Hi, > > > > I'm trying to use maven-site-plugin and the wagon-webdav artifact. I > get this error when I do mvn site-deploy. But according to > http://maven.apache.org/wagon/wagon-providers/wagon-webdav/ it says it > does support directory copying... anyone know what could produce this > error? > > > > Thanks, > > Chris > > > > > > [INFO] --- maven-site-plugin:2.1.1:deploy (default-deploy) @ wsaxisM --- > > [INFO] > > > [INFO] BUILD FAILURE > > [INFO] > > > [INFO] Total time: 5.287s > > [INFO] Finished at: Fri Jul 30 13:41:59 CDT 2010 > > [INFO] Final Memory: 6M/15M > > [INFO] > > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:2.1.1:deploy (default-deploy) > on project wsaxisM: Wagon protocol 'dav' doesn't support directory > copying -> [Help 1] > > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > execute goal org.apache.maven.plugins:maven-site-plugin:2.1.1:deploy > (default-deploy) on project wsaxisM: Wagon protocol 'dav' doesn't > support directory copying > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:585) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:324) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104) > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427) > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:121) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a:39) > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Impl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:597) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche > r.java:290) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2 > 30) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc > her.java:409) > > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352 > ) > > Caused by: org.apache.maven.plugin.MojoExecutionException: Wagon > protocol 'dav' doesn't support directory copying > > at > org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java > :193) > > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui > ldPluginManager.java:105) > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec > ycleExecutor.java:577) > > ... 14 more > > [ERROR] > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven claims to try a repo, but doesn't
On 15/07/2010, at 11:58 PM, Charles Brown wrote: > That is, maven claims to have tried internal, but it didn't, really. It hit > external twice. > > My repository configuration is detailed below. What am I doing wrong? > > My maven is > > Apache Maven 2.2.1 (rdebian-1) > Java version: 1.6.0_20 > > My settings.xml has > > > > external > http://path/to/my/repository/external/ > external:* > > You've mapped all repositories to external here. Note that "external:*" doesn't have any correlation to your IDs, it just means "any that aren't file://...". try external:*,!internal instead, or set up a repository manager at the mirror location and have it manage requests between the two. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a way to stop mail delivery but not unsubscribe?
Send mail to users-allow-subscr...@maven.apache.org. Cheers, Brett On 15/07/2010, at 4:02 PM, benxs wrote: > > I prefer to read and write to this mailing-list through a browser frontend > like > > nabble.com > > I want to avoid delivery of all postings from this mailing list to my > mailbox but > be able to post questions. > Other mailing lists allow for such a scenario a mail delivery stop-only. > > I found no administration page for such a scenario for maven user mailing > list. > Did I miss something? > How else can I stop mail delivery without unsubscribe ? > > Ben > -- > View this message in context: > http://maven.40175.n5.nabble.com/Is-there-a-way-to-stop-mail-delivery-but-not-unsubscribe-tp1177296p1177296.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact in repo without an artifactId?
I removed them so they can put the right things in place. To Maven, POMs that don't validate are equivalent to no POMs anyway. I kept the JARs in place despite them being removed in the source repository. Yes, they should be using a system that checks for them instead of copying them blind. - Brett On 17/06/2010, at 6:26 AM, Wendy Smoak wrote: > On Wed, Jun 16, 2010 at 3:54 PM, Stopp, Bryan > wrote: >> I'm experiencing a strange issue and discrepancy with Maven 2.2.1 and >> the m2eclipse plugin. >> This artifact: >> org.hsqldb:hsqldb-j5:2.0.0:jar >> has a pom in repo1.maven.org which does not have a defined artifactId. > > I'm going to guess it's related to > http://jira.codehaus.org/browse/MAVENUPLOAD-2788 > > -- > Wendy > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: wagon-maven-plugin and wagon-scm
This would require that wagon-scm is in the build extensions, which is not possible without a POM file. An alternative is to use dav:http://, and turn on auto-versioning on your subversion server (though it creates a revision per-file...) On 11/06/2010, at 5:49 AM, Jim McCaskey wrote: > Hello all, > > I was wondering if anyone has gotten the wagon-maven-plugin working with > wagon-scm? Specifically, I am trying to issue a command like this: > > mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-3:merge-maven-repos > -Dwagon.source=file://E:\stage > -Dwagon.target=scm:svn:http://testserver/svn/test/trunk > -Djava.io.tmpdir=deploytemp > > Here is the error: > > [INFO] [wagon:merge-maven-repos] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error during performing repository copy > > Embedded error: Unable to create a Wagon instance for > scm:svn:http://testserver/svn/test/trunk > Component descriptor cannot be found in the component repository: > org.apache.maven.wagon.Wagonscm. > [INFO] > > > I'm sure that's telling me exactly what's wrong, I just don't speak that > language. > > If it matters, I'm using Maven 2.1.0. > > Disclaimer: Yes I know I should not use a Subversion server as a Maven repo > but this will solve a problem in the short term. > > Thanks! > > -Jim > > > > > --------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sign existing artifacts in repository
You can loop over them using shell and gpg. You can use an agent to store the password so it doesn't need to be typed in every time, or have it read from an argument. On 11/05/2010, at 10:51 AM, Mark Diggory wrote: > Hi, > > we have an existing repository which I want to batch sign all the > artifacts within. I do have file system access. Is there any tool > available that will go though our existing repository and allow me to > sign the artifacts (all of which have been created by me in the past)? > > thanks, > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven2 Shade vs Maven1 UberJar
No. On 05/05/2010, at 10:32 AM, hanasaki wrote: > Does Shade use the same "classworlds" as as UberJar did? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Compiler Plugin 2.3 Released
On 21/04/2010, at 11:13 PM, John Singleton wrote: > Thanks, Brett. > > FWIW, I also noticed this problem with the 2.2 version of Compiler plugin, > which was released a couple of weeks ago. Yes, they both use the same version of the shared component. It's being taken care of. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2.2.1 on Windows-64 bit
I have no direct experience, but there's no reason it shouldn't. It works just fine on my 64-bit Mac :) On 21/04/2010, at 2:53 PM, Vineeth Karkad (vkarkad) wrote: > Hi, > > We have our build hosts on Win 2K3 server Standard Edition 32-bit. > Because of memory related performance issues, we are planning to upgrade > to 64-bit Standard Edition/Enterprise Edition of Win 2K3 server. We have > Maven 2.2.1 on our build hosts that have latest releases and Maven 2.0.4 > on build hosts that are on maintenance. > > We need to upgrade JDK as well since we are moving to 64-bit, what about > Maven - Does it work on 64-bit Windows platform ? > > Please advise. Thank you. > > Regards, > Vineeth. -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Compiler Plugin 2.3 Released
Yes, the checksums seem to be incorrect on central. I'll forward this to the
dev list.
On 21/04/2010, at 5:48 AM, Raphael Ackermann wrote:
> I get the same/similar checksum errors with nexus 1.6.
> I deleted the plexus-compiler artefacts both from my local and the
> nexus repository but got the same error still.
>
> Raphael
>
> On Tue, Apr 20, 2010 at 21:09, John Singleton wrote:
>> I tried to upgrade to this version of the plugin, but am getting download
>> errors on some of its dependencies, namely:
>>
>> org.codehaus.plexus:plexus-compiler-api:jar:1.8
>> org.codehaus.plexus:plexus-compiler-manager:jar:1.8
>> org.codehaus.plexus:plexus-compiler-javac:jar:1.8
>>
>> sample error message from artifactory log:
>>
>> repo1: Downloaded '
>> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-compiler-javac/1.8/plexus-compiler-javac-1.8.jar'
>> with return code: 200.
>> 2010-04-20 14:24:17,955 [pool-1-thread-30] [WARN ]
>> (o.a.e.DownloadServiceImpl:194) - Sending HTTP error code 409: Checksum
>> policy 'GEN_IF_ABSENT' rejected the artifact
>> 'plexus-compiler-javac-1.8.jar'. Checksums info: [ChecksumInfo{type=SHA-1,
>> original='69203d97d835ff6851ed1e622ebde635a54ef681',
>> actual='8e8e1d4ef6c19ab4daaabe387218a74ea44b17c6'}, ChecksumInfo{type=MD5,
>> original='dde75ac45679d2a639d25f01da55663e',
>> actual='41a5a8bc0e92ace66d918c487b5fa345'}].
>>
>> Is there really an error in the posted checksums, or is this a problem on my
>> end?
>>
>> This error occurs with artifactory 2.2.2 runing on Ubuntu Linux 9.10 (Karmic
>> Koala), called from Maven 2.2.1
>>
>>
>> On Sat, Apr 17, 2010 at 6:43 AM, Benjamin Bentmann
>> wrote:
>>
>>> The Maven team is pleased to announce the release of the Maven Compiler
>>> Plugin, version 2.3.
>>>
>>> This plugin is used to compile the sources of your project. See the
>>> plugin's site for more details:
>>>
>>> http://maven.apache.org/plugins/maven-compiler-plugin/
>>>
>>> To use the updated plugin in your projects, you need to add the
>>> following snippet to the plugins or plugin management section of your POM:
>>>
>>>
>>>org.apache.maven.plugins
>>>maven-compiler-plugin
>>>2.3
>>>
>>>
>>> Release Notes - Maven 2.x Compiler Plugin - Version 2.3
>>>
>>> ** Improvement
>>>* [MCOMPILER-80] - Change default source level to 1.5
>>>
>>> Enjoy,
>>>
>>>
>>> -The Maven team
>>>
>>>
>>> -
>>> 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
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot find wagon... for ftp
On 16/04/2010, at 4:15 PM, Craig L Russell wrote:
> Hi Brett,
>
> I added the version number to the extension and now the symptom looks like
> this:
>
> clr% mvn install
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building ClusterJ Core
> [INFO]task-segment: [install]
> [INFO]
>
> [WARNING] Unable to get resource 'com.mysql.clusterj:clusterj-api:pom:7.1.3'
> from repository MySQL FTP (ftp://ftp.mysql.com/pub/mysql/maven-repo):
> Authentication failed: Password not specified for repository MySQL FTP
> Downloading:
> http://repo1.maven.org/maven2/com/mysql/clusterj/clusterj-api/7.1.3/clusterj-api-7.1.3.pom
> [INFO] Unable to find resource 'com.mysql.clusterj:clusterj-api:pom:7.1.3' in
> repository central (http://repo1.maven.org/maven2)
> [WARNING] Unable to get resource 'com.mysql.clusterj:clusterj-api:jar:7.1.3'
> from repository MySQL FTP (ftp://ftp.mysql.com/pub/mysql/maven-repo):
> Authentication failed: Password not specified for repository MySQL FTP
> Downloading:
> http://repo1.maven.org/maven2/com/mysql/clusterj/clusterj-api/7.1.3/clusterj-api-7.1.3.jar
> [INFO] Unable to find resource 'com.mysql.clusterj:clusterj-api:jar:7.1.3' in
> repository central (http://repo1.maven.org/maven2)
>
> If I type this into a browser window, the file downloads:
>
> ftp://ftp.mysql.com/pub/mysql/maven-repo/com/mysql/clusterj/clusterj-api/7.1.3/clusterj-api-7.1.3.jar
>
> Do I have the layout of the repository wrong, or do I need a special file in
> the repository?
This worked for me:
MySQL
anonymous
br...@apache.org
I'm guessing that is the configuration of the FTP server.
- Brett
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot find wagon... for ftp
On 16/04/2010, at 9:27 AM, Craig L Russell wrote: > > From the above, I downloaded the wagon-ftp which I guess is still in beta > release: > > repository metadata for: 'artifact org.apache.maven.wagon:wagon-ftp' could > not be retrieved from repository: MySQL FTP due to an error: Unsupported > Protocol: 'ftp': Cannot find wagon which supports the requested protocol: ftp > [INFO] Repository 'MySQL FTP' will be blacklisted I think there is a known JIRA issue for this, at least in 2.2.1. It's always going to look for the release metadata from that repository, fail because the wagon isn't set up yet, then blacklist it. Chicken and egg. > So two questions: > > 1. Is ftp support for repositories planned to be a standard feature (no > special wagons needed) at some point? I really don't want to have to explain > to every user out there how to configure an ftp wagon. No, demand has been very low for it as far as I can tell. > > 2. What did I do wrong? If you add the wagon version to the POM, the build will work fine. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: README.txt bundled with maven doesn't mention M2_HOME
Sounds like making them consistent makes sense. Note that the env var is not required - it is mostly for people that wish to run multiple versions of Maven. - Brett On 08/04/2010, at 1:03 PM, Matthew McCullough wrote: > Team, > > The download page for Maven mentions the M2_HOME variable and setting it up. > http://maven.apache.org/download.html > > However, the README.txt that ships with Maven binaries does not > mention it in the "setup" instructions. A student today was puzzled > at the disparity. Should we add it to the README.txt with the binary > distributions for the sake of the users? > > http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/apache-maven/README.txt?view=markup > and > http://svn.apache.org/viewvc/maven/maven-3/trunk/apache-maven/README.txt?view=markup > > > -Matthew > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating site.xml skin.version during a release, how?
That sounds bizarre. You said organization, which is generally a parent with no modules. If that's the case, why ever run the site goal on there? If you have modules and its actually the root of a multi-module build, then you can't change the type. This may well work for you, but it's bound to cause some confusion down the track. I'm not sure what your release patterns will look like. On 07/04/2010, at 2:57 PM, Andrew Hughes wrote: > Thanks Brett :) > > I got a workaround by making the "oganization" pom the skin, by: > > jar > then I moved all of the ./acme-maven-site-skin/src/main/resources into the > parent (../). This effectively makes the organization pom also the maven > site skin. > > In my case there might not be any draw backs > > > On Wed, Apr 7, 2010 at 11:21 AM, Brett Porter wrote: > >> >> On 07/04/2010, at 11:09 AM, Andrew Hughes wrote: >> >>> I tried that and it failed however I *think* there is another reason >> for >>> this not working... >>> >>> I have >>> ./pom.xml (organization pom, with site.xml skin== acme-maven-site-skin >>> e.t.a...) >>> ./acme-maven-site-skin/pom.xml (this is the actual jar skin module) >>> >>> The reactor build order "install site" *appears *to try and build >>> 1. parent (install) >>> 2. parent (site) >>> 3. acme-maven-site-skin (install) >>> 4. acme-maven-site-skin (site) >>> >>> This fails at #2 because "acme-maven-site-skin (install)" has not been >>> executed yet and the skin is not in the repository. >>> >>> Is it weird/wrong that I have a skin as a module under the organization >> pom? >> >> No, but it's weird to build the site for the org. POM and skin. Take a look >> at that sample project I pointed to and the structure - you'll see the skin >> is referenced from the documentation and the modules, but not the parent of >> the skin to avoid this conflict. That's where the site is run from, to >> ensure you don't build useless sites for things like the parent POM and >> skin. >> >> - Brett >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating site.xml skin.version during a release, how?
On 07/04/2010, at 11:09 AM, Andrew Hughes wrote: > I tried that and it failed however I *think* there is another reason for > this not working... > > I have > ./pom.xml (organization pom, with site.xml skin== acme-maven-site-skin > e.t.a...) > ./acme-maven-site-skin/pom.xml (this is the actual jar skin module) > > The reactor build order "install site" *appears *to try and build > 1. parent (install) > 2. parent (site) > 3. acme-maven-site-skin (install) > 4. acme-maven-site-skin (site) > > This fails at #2 because "acme-maven-site-skin (install)" has not been > executed yet and the skin is not in the repository. > > Is it weird/wrong that I have a skin as a module under the organization pom? No, but it's weird to build the site for the org. POM and skin. Take a look at that sample project I pointed to and the structure - you'll see the skin is referenced from the documentation and the modules, but not the parent of the skin to avoid this conflict. That's where the site is run from, to ensure you don't build useless sites for things like the parent POM and skin. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Updating site.xml skin.version during a release, how?
Use ${project.version} as the value for the skin:
http://github.com/brettporter/centrepoint/blob/master/centrepoint/documentation/src/site/site.xml
On 7 April 2010 09:53, Andrew Hughes wrote:
> Hi All,
>
> I've written a site skin (com.acme:acme-maven-site-skin-1.0.0-SNAPSHOT) and
> of course I want "the site skin project" to use the skin for its site :)
> so
>
> ./src/site/site.xml:
>
>
> com.acme
> acme-maven-site-skin
> 1.0.0-SNAPSHOT
>
>
> However, when I *release:prepare release:perform* the project the
> ${project.version} will become 1.0.0 but the site.xml's ${skin.version}
> will
> remain at 1.0.0-SNAPSHOT (unless I am wrong).
>
> How can I sync the ${project.version} and the skin.version when performing
> a
> release?
>
> CHEERS :)
>
--
Brett Porter
http://brettporter.wordpress.com/
Re: Does wagon-scm work with maven-scm-provider-gitexe?
I don't think wagon-scm has been tested with git - while most is generic there's a chance it won't work yet. You could file an issue in WAGON. You might also get help from more general git / scm users on us...@maven.apache.org. - Brett On 31/03/2010, at 3:47 AM, Kathryn Huxtable wrote: > On Mar 30, 2010, at 11:29 AM, Kathryn Huxtable wrote: > >> [INFO] Executing: /bin/sh -c cd >> /var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp- && git clone >> git+ssh//github.com/khuxtable/test-project.git/. >> /var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp-/wagon-scm472467110.checkout > > I especially like the "/." after the "test-project.git". Funny. > > I have just tried the url > > scm:git:g...@github.com:khuxtable/test-project.git > > and got > > [INFO] Executing: /bin/sh -c cd > /var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp- && git clone > 'g...@github.com:khuxtable/test-project.git gh-pages/.' > /var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp-/wagon-scm587989183.checkout > [INFO] Working directory: /var/folders/M+/M+95phY6GfOYTLYCJKW4Bk+++TI/-Tmp- > Transfer error: org.apache.maven.scm.ScmException: Unable to commit file. The > git-clone command failed. ERROR: Repository not found. Make sure you include > the .git, e.g. g...@github.com:defunkt/ambition.git > > Which is just as funny, if not funnier. It's a lot closer to what I want, > which is of course > >git clone 'g...@github.com:khuxtable/test-project.git' -b gh-pages > '/var/folders/blahblahblah' > > -K -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: wagon-users-unsubscr...@maven.apache.org For additional commands, e-mail: wagon-users-h...@maven.apache.org
Re: Does wagon-scm work with maven-scm-provider-gitexe?
On 29/03/2010, at 1:29 PM, Kathryn Huxtable wrote: > urls[1] = > file:/Users/huxtable/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar It looks like the project is using an older version of this library than is needed (at least 1.5.6). You should add the newer version to you extensions also. Re-ordering the extensions so that SCM is listed first may also help. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: wagon-users-unsubscr...@maven.apache.org For additional commands, e-mail: wagon-users-h...@maven.apache.org
Re: Does wagon-scm work with maven-scm-provider-gitexe?
ity/1.5/velocity-1.5.jar >> urls[18] = >> file:/Users/huxtable/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar >> urls[19] = file:/Users/huxtable/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar >> urls[20] = >> file:/Users/huxtable/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.2/maven-doxia-tools-1.2.jar >> urls[21] = >> file:/Users/huxtable/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar >> urls[22] = >> file:/Users/huxtable/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar >> urls[23] = >> file:/Users/huxtable/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar >> urls[24] = >> file:/Users/huxtable/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar >> urls[25] = >> file:/Users/huxtable/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar >> [FATAL ERROR] Container realm = plexus.core >> urls[0] = file:/usr/local/maven/lib/maven-2.2.1-uber.jar >> [INFO] >> >> [ERROR] FATAL ERROR >> [INFO] >> >> [INFO] >> org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/plexus/util/cli/Arg; >> [INFO] >> >> [INFO] Trace >> java.lang.NoSuchMethodError: >> org.codehaus.plexus.util.cli.Commandline.createArg()Lorg/codehaus/plexus/util/cli/Arg; >> at >> org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.getBaseGitCommandLine(GitCommandLineUtils.java:82) >> at >> org.apache.maven.scm.provider.git.gitexe.command.list.GitListCommand.createCommandLine(GitListCommand.java:81) >> at >> org.apache.maven.scm.provider.git.gitexe.command.list.GitListCommand.executeListCommand(GitListCommand.java:64) >> at >> org.apache.maven.scm.command.list.AbstractListCommand.executeCommand(AbstractListCommand.java:64) >> at >> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58) >> at >> org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:289) >> at >> org.apache.maven.scm.provider.git.AbstractGitScmProvider.list(AbstractGitScmProvider.java:300) >> at >> org.apache.maven.scm.provider.AbstractScmProvider.list(AbstractScmProvider.java:625) >> at >> org.apache.maven.wagon.providers.scm.ScmWagon.checkOut(ScmWagon.java:371) >> at >> org.apache.maven.wagon.providers.scm.ScmWagon.putInternal(ScmWagon.java:285) >> at >> org.apache.maven.wagon.providers.scm.ScmWagon.putDirectory(ScmWagon.java:510) >> at >> org.apache.maven.plugins.site.SiteDeployMojo.execute(SiteDeployMojo.java:215) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >> at >> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> [INFO] >> >> >> Any ideas? >> >> -K > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Help Plugin 2.1.1 Released
The Maven team is pleased to announce the release of the Maven Help Plugin, version 2.1.1. This plugin is used to get information about the working environment for the project. http://maven.apache.org/plugins/maven-help-plugin/ The release improves support for Maven 3 and removes the confusing incorrect deprecation warnings on plugin definitions. If Maven does not automatically update to this release for you, try running a help goal with the -U flag. Release Notes * [MPH-58] - effective pom file created with mixed newlines * [MPH-59] - Describe goal says everything is deprecated * [MPH-75] - help:describe crashes with NPE if -Dplugin=archetype is used with a non-existent mojo name * [MPH-57] - Hide server passphrase for effective-settings * [MPH-72] - Use ISO8601-format for date and time * [MPH-76] - use a fixed number of asterisks to mask passwords in effective-settings * [MPH-71] - call help:evaluate in batch mode Enjoy, -The Maven team -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2.2.1 and Release plugin 2.0 issue
Do you have any related to the SCM providers, or modified your install? On 24/03/2010, at 2:46 AM, Jonathan Ducharme wrote: > Hello, > > I'm trying to make a release using the maven-release-plugin. > > I'm doing a mvn release:clean release:prepare and I get this stack trace : > > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] > org.apache.maven.scm.providers.svn.settings.Settings.isUseNonInteractive()Z > [INFO] > > [INFO] Trace > java.lang.NoSuchMethodError: > org.apache.maven.scm.providers.svn.settings.Settings.isUseNonInteractive()Z >at > org.apache.maven.scm.provider.svn.svnexe.command.SvnCommandLineUtils.getBaseSvnCommandLine(SvnComma > ndLineUtils.java:121) >at > org.apache.maven.scm.provider.svn.svnexe.command.status.SvnStatusCommand.createCommandLine(SvnStatu > sCommand.java:83) >at > org.apache.maven.scm.provider.svn.svnexe.command.status.SvnStatusCommand.executeStatusCommand(SvnSt > atusCommand.java:46) >at > org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java > :44) >at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) >at > org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmProvider.java > :371) >at > org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.status(AbstractSvnScmProvider.java:340) >at > org.apache.maven.scm.provider.AbstractScmProvider.status(AbstractScmProvider.java:655) >at > org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase > .java:98) >at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203) >at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) >at > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) >at > org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211) >at > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) >at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor. > java:569) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx > ecutor.java:387) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja > va:284) >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:597) >at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Tue Mar 23 11:40:22 EDT 2010 > [INFO] Final Memory: 14M/508M > [INFO] > > > The code snipet in my poms are the same as the usage in the release plugin : > > >org.apache.maven.plugins >maven-release-plugin >2.0 > > https://my.repo/releases >
Re: How to add output statement in pom?
You can use the antrun plugin's task, though it'll only appear
underneath the project banner. At that time, there's usually a large number of
output lines already showing the absolute location of files being copied.
On 18/03/2010, at 8:29 AM, Jane Young wrote:
> Hi Maven experts,
>
> Is there a way to add logging or echo statement in pom file?
>
> For example in the "install" lifecycle, I want to be able to print out the
> directory where the sub-module resides:
> e.g.
> [INFO]
>
> [INFO] Building Deployment Object Library
> [INFO]task-segment: [install]
> [INFO]
>
>
> I can add ${project.basedir} in the element in the pom.
> (e.g. Admin CLI for v3 ${project.basedir})
> If the directory is very long the name will also be long.
>
> Is there a way that I can print the output:
> e.g.
> [INFO]
>
> [INFO] Building Deployment Object Library
> [INFO[ /export/GlassFish/v3/deploy/dol
> [INFO]task-segment: [install]
> [INFO]
>
>
> Thanks,
> Jane
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy large file to nexus requires huge memory
If that's working, you can try switching to the httpclient as discussed on the site: http://maven.apache.org/guides/mini/guide-wagon-providers.html You'll have to use the system property, as I've recently discovered the settings.xml variant is broken. - Brett On 08/03/2010, at 4:40 PM, Dan Tran wrote: > looks like Nexus does not support webdav > > http://www.sonatype.com/people/2009/01/contrasting-nexus-and-artifactory/ > > :( > > -Dan > > On Fri, Feb 19, 2010 at 6:20 AM, Dan Tran wrote: >> thanks Brett, >> >> I will give it a try >> >> -D >> >> On Thu, Feb 18, 2010 at 2:59 PM, Brett Porter wrote: >>> Yes, I've experienced the same. I'd need to check again, but my memory says >>> this was being done in the JDK so couldn't be worked around. >>> >>> does using 'dav:http://' (effectively using httpclient instead) help? >>> >>> - Brett >>> >>> On 19/02/2010, at 7:31 AM, Dan Tran wrote: >>> >>>> Hi >>>> >>>> I have to set my MAVEN_OPTS=-Xmx1024m in order to deploy 500M ISO file >>>> via http ( ie nexus ) >>>> >>>> Is it normal? >>>> >>>> I am using deploy-plugin 2.5 >>>> >>>> Thanks >>>> >>>> -Dan >>>> >>>> - >>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: users-h...@maven.apache.org >>>> >>> >>> -- >>> Brett Porter >>> br...@apache.org >>> http://brettporter.wordpress.com/ >>> >>> >>> >>> >>> >>> - >>> 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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: starting jetty during tests and stopping afterwards
On 04/03/2010, at 8:49 PM, Douglas Ferguson wrote: > Is there a clean way to start up jetty for the testing and then stopping git > afterwards? > > I'd like to include my integration tests for my code coverage. > > I'd like to set my code coverage profile to only start up jetty after > cobertura has instrumented the classes > then shut it down after the tests complete. > > Could I just start up the jetty in process-test-classes and shut it down in > prepare-package? Yep. http://github.com/brettporter/centrepoint/blob/master/centrepoint/modules/selenium-tests/pom.xml Bear in mind that if the tests fail, the "stop" won't be run, but normally they will shut down properly when Maven does anyway. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Configure Proxy based on location
Generally you have two options, you can have different settings files for the locations, or run an instance of nexus on your own machine that proxies from your work environment. That way you always use the one on your local machine, and when you need the other artifacts they'll be checked for on the work environment (if available). I do the latter with an instance of Archiva and it is quite useful anyway for being able to freely delete your local repository, and do other things like local search, etc. - Brett On 02/03/2010, at 12:22 AM, Nick Klauer wrote: > More or less i've asked this on StackOverflow, but I was totally unaware of > the users mailing list, so I'm reposting here since it's *probably* more > appropriate: > > http://stackoverflow.com/questions/2354001/make-maven-proxy-server-settings-configurable-based-on-location > > What my issue boils down to is that I have a corporate proxy and Nexus Repo > at work. When I'm at work, everything is great, works well. However, when > I walk out of the office, I don't have to go through a proxy, nor do I have > our corporate private Maven repo to look for artifacts against. How can I > configure my settings.xml file to work both in and out of the office based > on those two options? > > -Nick -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven 2.0.11 Released
The Apache Maven team would like to announce the release of Maven 2.0.11. http://maven.apache.org/download.html This release is intended for all current users of Maven 2.0.10 and below who are not able to upgrade to Maven 2.2.1, and contains 37 improvements and fixes. ** Note: the current stable release of Maven remains as Maven 2.2.1, and all users are recommended to upgrade to that version ** The full release notes can be obtained from: http://maven.apache.org/docs/2.0.11/release-notes.html Regards, - The Apache Maven team -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Get the effective pom to a program
On 26/02/2010, at 7:08 PM, pubudu gunawardena wrote:
> I want to to use the maven help plugin classes inside a program I'm writing
> to generate the effective pom. But since the variables are set by Mojo
> parameters ${reactorProjects} and ${project} I cannot accomplish this. Is
> there a way to get these parameters programmatically and pass them to the
> Mojo?
If you're doing it outside of Maven, you'll essentially need to reuse a number
of the libraries. This isn't strictly supported in the current version, and the
APIs may change.
That said, an example of how it can be done is shown here:
http://github.com/brettporter/centrepoint/blob/master/centrepoint/modules/maven-importer/src/main/java/com/effectivemaven/centrepoint/maven/repository/CentralRepositoryService.java
Bear in mind that the loaded projects are cached in memory in Maven 2 and that
will grow over time.
Depending on what you are trying to achieve, you may find it better to execute
mvn help:effective-pom externally and capture the output.
Cheers,
Brett
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Selenium Maven Plugin 1.0.1 Released
The team at the Codehaus Mojo project are pleased to announce the release of the Selenium Maven plugin 1.0.1. This corresponds to the recent release of Selenium RC 1.0.2. Documentation on the plugin can be found here: http://mojo.codehaus.org/selenium-maven-plugin/ RELEASE NOTES (since 1.0) * [MSELENIUM-59] - Selenium server could not be stopped from stop-server goal * [MSELENIUM-60] - Fails to run with Firefox 3.5 on OS X 10.6.2 * [MSELENIUM-58] - docu is outdated: there is no parameter multiWindow anymore Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
On 26/02/2010, at 2:02 AM, Marc Lustig wrote: > thanks for the swift response. > First I also thought it's an Archiva issue, but basically Maven is talking > to the Repo Manager, right? So Maven defines the contract, and Archiva can > only respond to the contract. > > We are still investigating the issue and try to reproduce different > scenarios. > > For now, the question for us is whether Maven has the concept of > artifact-verification by using hash-codes at all. > Any input on this matter? Maven can't really do anything without either having a specific relationship with a repository manager (requesting it send back the checksum of an actual file, not the checksum it just sent), or redownloading the entire file. It is better for the repository manager to deal with uploads that don't match their checksum and give Maven back an HTTP error at the conclusion of the upload. Currently, Archiva is only checking the content length matches on upload to prevent partial upload corruption, and filing problem reports for mismatches with checksums from misbehaving clients as Wendy said. Please let us know if we can help diagnose the issue if it's not as simple as avoiding the scenarios in the two issues I listed. Thanks, Brett > > > > 2010/2/25 Brett Porter > >> >> On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: >> >>> On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig wrote: >>>> we had a number of cases when the artifact in our central-repo >>>> (Archiva-based) was not consistent with the corresponding hash. >>> >>> You can configure the checksum policy to fail when Maven _downloads_ >>> an artifact if the checksum doesn't match. >>> >>> If you're having trouble with checksums when deploying to Archiva, it >>> would probably be best to ask on the Archiva users list. If artifacts >>> are getting added with the wrong checksum, that's probably a bug. >> >> Could it be one of these? >> http://jira.codehaus.org/browse/MNG-4301 >> http://jira.codehaus.org/browse/MNG-4235 >> >>> It >>> does have some 'repository health' reports that might help find the >>> problems after the fact. >> >> >> - Brett >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unexpected behavior in parsing element (mvn 2.2.x)
That would be a bug. Please file it at http://jira.codehaus.org/browse/MNG.
On 26/02/2010, at 5:13 AM, Jonathan Gold wrote:
> I'm using 2.2.x and was surprised to find that, while valid XML, the following
> are not valid in a pom.xml:
>
> 4.0.0
>
> or
>
>
>4.0.0
>
>
> I had expected that the maven xml parser would be normalizing the whitespace,
> but looked in
> maven-2.2.x/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
> and found this in readModel(), line 1609:
>
>if ( modelSource.indexOf( "" + MAVEN_MODEL_VERSION ) < 0
> )
>{
>throw new InvalidProjectModelException( projectId, pomLocation,
> "Not a v" + MAVEN_MODEL_VERSION + " POM." );
>}
>
> Why is the parser hand-parsing this piece of the XML instead of looking at the
> child content and normalizing/trimming whitespace? It's counterintuitive to me
> as a user, since the POM XSD decalres modelVersion to be xs:string and there
> is
> no mention anywhere that I'm not allowed to use whitespace.
>
> jon
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: > On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig wrote: >> we had a number of cases when the artifact in our central-repo >> (Archiva-based) was not consistent with the corresponding hash. > > You can configure the checksum policy to fail when Maven _downloads_ > an artifact if the checksum doesn't match. > > If you're having trouble with checksums when deploying to Archiva, it > would probably be best to ask on the Archiva users list. If artifacts > are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 > It > does have some 'repository health' reports that might help find the > problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin name abbreviated to 's'?
Seems like a slight bug in the default plugin prefix calculation, which is
supposed to recognise 'maven-*-plugin' and '*-maven-plugin'
You can correct this by passing the configuration to the
maven-plugin-plugin.
http://maven.apache.org/plugins/maven-plugin-plugin/examples/generate-descriptor.html
On 23/02/2010, at 12:10 AM, Benson Margulies wrote:
> [INFO] [s:endian-variable {execution: getEndianFlag}]
>
> Can anyone explain where the 's' comes from? The plugin's full name is
> a com.basistech:maven-plugins.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: learning about dependencies of a plugin
The dependency of the plugin will be in the classloader of the plugin already - you don't need to do anything else. You can use mvn -X ... to see the full construction of your plugin for more information. Or are you trying to dynamically use a dependency of the project the plugin is operating on? On 19/02/2010, at 3:26 PM, Kai Hackemesser wrote: > Hi there, > > I'm writing my first plugin. My plugin will have a dependency to another > library/artifact that needs to be added to the classpath when the plugin > executes its work. How can I find the artifact that the plugin is depending > to, when the plugin is running? The maven-dependency-plugin resolves the > dependencies of the current project, not of the current plugin. Or am I > wrong here? > > Cheers, > Kai -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy large file to nexus requires huge memory
Yes, I've experienced the same. I'd need to check again, but my memory says this was being done in the JDK so couldn't be worked around. does using 'dav:http://' (effectively using httpclient instead) help? - Brett On 19/02/2010, at 7:31 AM, Dan Tran wrote: > Hi > > I have to set my MAVEN_OPTS=-Xmx1024m in order to deploy 500M ISO file > via http ( ie nexus ) > > Is it normal? > > I am using deploy-plugin 2.5 > > Thanks > > -Dan > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: building, installing, using maven COMPLETELY OFFLINE (setting up local mini repository)
I run a repository manager (Archiva) on my local machine, allowing me to clean my local repository at any time without concern, and getting other advantages like less configuration, whitelist/blacklist, search, etc. What type of errors are you getting in offline mode? Is it missing artifacts that weren't obtained before you went offline, or attempts to get things that you should already have? BTW, for search, there are several alternative archives on the mailing lists page, but you can also google with "site:http://mail-archives/mod_mbox/maven-users/"; On 18/02/2010, at 5:26 AM, Edward Peschko wrote: > All, > > I need to support a project where I cannot access the internet, even > by proxy. And I'd like to use some tools that require maven support > for building (apache commons, for example). > > I see offline mode, and gave it a try, but it STILL seems to still > want to connect to the internet when both building maven, and when > building apache commons. This is as of 2.1.0. > > Anyways, what I was hoping to do was to trick maven to run from a sole > pre setup repository; ie: to build a cache on another machine, tar up > that complete cache and move that cache to the local directory to > build it from there. I would have thought this would be simple (in > fact it should work out of the box IMO) but I don't see any HOWTO > document offhand. > > Any help on this would be great and IMO this should be a FAQ. > > Thanks much, > > Ed > > (ps - BTW - I did try to do a search, but the mail archive at > > http://mail-archives.apache.org/mod_mbox/maven-users/ > > doesn't have a search feature for some odd reason. > ) > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Accessing Properties in site.xml?
Yes... just do it. You need to be using a version of the site plugin >= 2.0-beta-6. For example: http://svn.apache.org/repos/asf/maven/site/trunk/src/site/site.xml - Brett On 11/02/2010, at 4:59 PM, mfs wrote: > > Hi Guys, > > Is there a way to access the properties defined in pom.xml from within > site.xml ?. I am creating some custom menu items and would like the "href" > for each of the items to be constructed dynamically based on some properties > in pom or within some profiles. > > Is that possible ? > > Thanks in advance, > Farhan > -- > View this message in context: > http://old.nabble.com/Accessing-Properties-in-site.xml--tp27542692p27542692.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 > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Logging
On 11/02/2010, at 12:33 PM, mfs wrote: > > Hello Guys, > > I am using maven 2.2.1 and wondering if there has been any support added to > stream the build output to a file in addition to the console ?. Doesn't seem > to be the case taking a look at the JIRA issues, but just wanted to be sure. > > We would like to publish the build logs to a centralized location, as part > of our nightly build and thats why I ask the above question. Only currently available in the Maven 3.0 alphas, and in that it goes only to the file, not to both. You can alter your Maven installation to change log4j.xml in any version, but I'm not sure that is recommended :) Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: 2.0-beta-10 of release plugin
.. which has happened too. We'd love to hear your results of testing on d...@. http://mail-archives.apache.org/mod_mbox/maven-dev/201002.mbox/%3c4b6df774.8000...@apache.org%3e On 06/02/2010, at 2:27 AM, Stephen Connolly wrote: > it's being skipped and 2.0 is in the process of being released but there > are some issues which Benjamin may or may not have vetoed the release on... > as soon as Benjamin clarifies whether he was vetoing the release or not, the > release manager will be able to continue or re-roll the release of 2.0 > > On 5 February 2010 14:43, Todd Thiessen wrote: > >> It doesn't look like this version of the release plugin has been >> released yet. It has the useRemoteTagging fix or the branch goal in it >> which I am interested in. Could this plugin be released? >> >> --- >> Todd Thiessen >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Archetype 1.0 to 2.0 variations question on CLI interactive prompt
On 06/02/2010, at 2:44 PM, Matthew McCullough wrote: > Wendy noted: "It all changed with archetype 2.0 and I don't think all > the archetypes came back. now they get generated from samples or > something." > > Can anyone elaborate on the above statement? Any docs/wiki/nabble > links on the rewrite and new way to use 'samples'? I was never clear on the intention myself, since generating from the sample project gives you an archetype in target, but doesn't do any of the further steps for building, deploying or releasing the archetype. I would suggest the following: - generate a project from the old archetype - fix it up to how you would expect - submit it as a patch for the "samples" directory. To get it release, we should discuss what needs to happen with them on dev@, but the best thing is probably to build an /archetypes directory, similar to /plugins, and move forward from there. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: do I need to list the ssh wagon as an extension?
No. On 04/02/2010, at 11:19 PM, Benson Margulies wrote: > If I want to make the dependency plugin deliver over ssh, to I need to > list an extension? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: antrun plugin dependency disappearance
On 02/02/2010, at 1:46 PM, Benson Margulies wrote: > On Mon, Feb 1, 2010 at 9:06 PM, Brett Porter wrote: >> In Maven 2, only to ensure that the first plugin declaration encountered >> (usually by putting it in the root) contains all of the desired plugin >> dependencies. > > It was in the root. However, since modules run first, the instance in > a module won, so I had to put the dependencies there. Is the root not also the parent of the module? The only reason I said root was because it should be consistently inherited into the children (Which may have to be empty, I'm not sure if the dependencies lists are correctly merged in some versions either). It's definitely fickle - the best I've found is: - put it in build > plugins of the topmost parent that will use it (not plugin management) - don't add any dependency to modules that will use it, just the additional configuration / executions - make sure it is in build, not reporting for checkstyle, etc. type plugins Anyway, glad you got it sorted. Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: antrun plugin dependency disappearance
In Maven 2, only to ensure that the first plugin declaration encountered (usually by putting it in the root) contains all of the desired plugin dependencies. I believe that Maven 3 has already fixed the problem. - Brett On 02/02/2010, at 12:46 PM, Benson Margulies wrote: > I think I'm hitting an known issue, but I'm stumped in working around it. > > In an aggregate POM, I've got a use of the maven-antrun-plugin that > needs custom dependencies. > > They are disappearing. > > The reason, I suspect, is that several of the modules that the > aggregate POM aggregates are themselves using the antrun plugin, not > specifying these dependencies. I tried to get past this by hanging the > dependencies in a pluginManagment section of the profile that turns > all of this loose, but to no avail. Maven run with -X shows that they > are gone. > > Is there some more reliable workaround? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[2.0.11 RC] Please help us test
Hi, We've been planning a Maven 2.0.11 release for current 2.0.10 users that might want access to some fixes that were made but are not wanting to upgrade to 2.2.1. To get a wider range of feedback before publishing the release, we're looking for release candidate testers. Please note that the following are for testing purposes only and won't be retained past the next release - please post your results to d...@maven.apache.org. You can find binaries here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/apache-maven/2.0.11-RC1/, and source distributions here: https://repository.apache.org/content/repositories/maven-016/org/apache/maven/maven/2.0.11-RC1/ Here are the issues that have been fixed: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14118 in this version. Please test it out and let us know how it goes - particularly if you are currently using 2.0.9 or 2.0.10. Thanks, Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Archiva 1.3 Released
The Apache Archiva team would like to announce the release of Archiva 1.3. Archiva 1.3 is available for download from the web site and mirrors: http://archiva.apache.org/download.html Archiva is an application for managing one or more remote Maven repositories, including administration, proxying, artifact handling, browsing and searching. New in Archiva 1.3: - Ability to force a re-scan of a repository to recreate metadata and the index - Improved memory usage, particularly for long running scan operations - Audit logging of uploads from the user interface More information and a full list of changes can be found in the release notes online: http://archiva.apache.org/docs/1.3/release-notes.html If you have any questions, please consult: - the web site: http://archiva.apache.org/ - the archiva-user mailing list: http://archiva.apache.org/mail-lists.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
