Re: Welcome Mirko Friedenhagen to the Apache Maven Team
Good to have you with us, Mirko! Wayne On Mon, Mar 17, 2014 at 2:53 PM, Robert Scholte rfscho...@apache.org wrote: Hi, On behalf of the Apache Maven PMC I am pleased to announce that Mirko Friedenhagen (mfriedenhagen) has been voted in as a new Apache Maven committer. Mirko, welcome on board and have a lot of fun! thanks, Robert - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 2.x is end of life
On Thu, Feb 13, 2014 at 9:14 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: We have not made a release of Maven 2.x since 2.2.1 which was August 2009. +1: Maven 2.x is end of life, I am not willing to act as release manager for this line of releases Here's my +1. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: deploy:site unable to upload, status code = 403
I'm trying for the first time to upload my maven site on my nexus server. I configured my repository as recomanded on the official website. Please post this question on the Maven Users list instead. This list is for discussions related to the development of Maven itself. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven 3.1.1
+1 binding Finally gave it a shot last night after your reminder email, works well on various projects I tested it with. Wayne On Wed, Sep 25, 2013 at 5:22 PM, Jason van Zyl ja...@tesla.io wrote: Anyone else going to give the release a whirl? On Sep 17, 2013, at 8:39 AM, Jason van Zyl ja...@tesla.io wrote: Hi, Maven Core ITs are good, and the license/notice issue has been resolved so I'm rolling 3.1.1 again. Here is a link to Jira with 6 issues resolved: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18968 Staging repo: https://repository.apache.org/content/repositories/maven-065/ The distributable binaries and sources for testing can be found here: https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/ Specifically the zip, tarball, and source archives can be found here: https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.zip https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-bin.tar.gz https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.zip https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.1.1/apache-maven-3.1.1-src.tar.gz Source release checksum(s): apache-maven-3.1.1-src.zip sha1: 2251357aa47129674df578e787504b72cd57ed4d Staging site: http://people.apache.org/~jvanzyl/maven-3.1.1/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, The Maven Team Thanks, Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Can I create folder Dependency?
I am new for Maven; I have a question: Questions like this should go to the Maven Users list. This list is reserved for discussion of the development of Maven itself. Can I create folder Dependency in Maven? without installing the jar (dependency)? No. You will waste a lot of time going down this road. You only need to install all those jars one time (assuming you have a Repo Manager, you'll use mvn deploy:deploy-file otherwise you'll need to mvn install:install-file them on each developer's machine) and write the dependency stanzas once. Then you can reuse that work in your various projects. Bite the bullet and do it now. 100 jars is not too bad. If you do it the right way, I bet you'll find a lot of them are open source and already hosted in Central. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Should the Maven PMC be an example of how we want the Maven Community to behave (was Re: svn commit: r1506778 - /maven/site/trunk/content/markdown/project-roles.md)
AFAIK, merit at Apache is forever -- you can't have it undone. If someone loses their Apache first spirit and begins critical development elsewhere, what can be done about it? Are there any practical recourses? I don't think there is which is why Maven development has that problem today. Surely the PMC can vote to remove individuals from the PMC if necessary? They *can* but it rarely occurs for a whole host of reasons... Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven archetype plugin - issue # 409
First of all STFB. I just have to ask... what is STFB? :) I can think of a few things that might work but none seem appropriate. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] All new (non-patch) releases of Maven Core after 30th Sep 2013 to require Java 6+
+1 binding Wayne On Tue, Jul 23, 2013 at 8:59 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: This vote is to cover the minimum required version of Java for Maven Core. Maven Plugins produced by the Apache Maven Project that are flagged as compatible with older versions of Maven Core as their baseline will still require to stick to the minimum Java requirements of that Maven Core version. In other words, if for example maven-compiler-plugin advertises compatibility with Maven Core 2.0.11+ then that will still need to be compiled targeting Java 1.4 and only using dependencies that are aligned with that runtime requirement. Additionally patch releases to existing releases of Maven Core will not be subject to this requirement. For example [example]*if* this vote passes and *if* on Sep 29th we release Maven 3.2.0 and *if* on Oct 2nd we release Maven 2.0.12, Maven 2.2.2, Maven 3.0.6, Maven 3.1.1, Maven 3.2.1 and Maven 3.3.0 (due to say some security issue that affected all versions of Maven) then only Maven 3.3.0 would be require Java 6 as a minimum runtime requirement, the 2.0.12 release would still require Java 1.4 and the 2.2.2, 3.0.6, 3.1.1 and 3.2.1 versions would all still require Java 1.5.[/example] This is not a requirement that 3rd party plugins need use Java 6 as a minimum. Third party plugins are free to require any Java version = the corresponding Maven minimum requirement, though obviously from a users perspective it is best if plugins try to adhere to our contracts for corresponding versions of Maven Core. Justification for the cut-off date: * Oracle has gone end of life on Java 6 Feb 2013 (note that there is still extended and sustaining support for existing Oracle customers using Java 5) * IBM will go end of life for z/OS on 30th Sep 2013 (other platforms are still with support, but there are other Java vendors for other platforms) * Apple no longer supports any hardware that does not have at least an Apple Java 6 version available. * Red Hat is providing support for OpenJDK 6 * HP-UX, OpenVMS, and Tru64 all have a Java 6 implementation available. As I see it, that essentially ensures that for the vast majority of platforms there is a very strong likelihood of a Java 6 compatible version of Java available for that platform. Toolchains support or forking of the compiler and surefire can provide support for users who still need to build with older versions of Java (e.g., as was the case for Java 1.4.2 with Maven 2.2.1). Additionally users who are forced to use a java version older than Java 6 also are likely unable to upgrade their version of Maven, so this change will not affect them This vote is open for 72 hours. A minimum of three +1 binding votes (i.e. from the PMC) and the majority of votes cast from committers will be required to pass this vote. +1000: Yes, and when can we have the vote to go for Java 7 as a minimum? (This option is equivalent to +1 but provides people the ability to indicate an additional preference while not contributing to the inevitible noise) +1: Yes 0: No opinion -1: No -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven Model Converter
+1 thanks Dennis. Wayne On Sat, Jul 20, 2013 at 12:26 PM, Dennis Lundberg denn...@apache.org wrote: Hi, The only consumer of Maven Model Converter we have left at the Apache Maven project is Maven One Plugin. If the vote for the retirement of Maven One Plugin succeeds we should also retire Maven Model Converter. The last release was made almost six years ago. Last time I checked Maven Model Converter was also used by the Apache Archiva project. The retirement plan is to move the component to the Apache Archiva project, if they want it. http://maven.apache.org/shared/maven-model-converter/ I therefor propose that we retire maven-model-converter. If this vote is successful I will make one final release of the component (there are some issues that have been fixed) making it clear on the component site that it has been retired. After that the source code will be moved to the Apache Archiva project in Subversion, or if they do not want it to the retired area in Subversion. The process for retiring a plugin is described here: 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: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven-Compiler-Plugin Bug
I am currently using the compiler plugin and I am try to set filters to include and exclude subdirectories of files on my source path, to my chagrin the filtering is not working. I have documented the issues on stack overflow: http://stackoverflow.com/questions/17584719/groovy-eclipse-compiler-excludes-and-includes-not-working Did you see this on the groovy-eclipse-compiler page [1]? I suspect you will have better luck there. ### Where to find more information and ask questions Please ask all questions on the Groovy-Eclipse mailing list [2]. Any bugs or feature enhancements should go on Groovy-Eclipse's jira. ### [1] http://groovy.codehaus.org/Groovy-Eclipse+compiler+plugin+for+Maven#Groovy-EclipsecompilerpluginforMaven-Wheretofindmoreinformationandaskquestions [2] http://xircles.codehaus.org/lists/eclipse-plugin-u...@groovy.codehaus.org Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Help Needed on Crystal Report in Maven!
We would appreciate your help, solution and suggestions. If you need more information, please send me a post and I will send more details. If you received this email, and nothing more, would you be able to solve the problem? I think not. You provided merely the rough overview of the problem but failed to describe anything in detail. This list is not full of CR experts. It seems to me that you have some problem in the contents of your EAR which prevents CR from working properly. Go to a CR list, ask those experts for help, figure out what is not working there (and then fix it manually, outside of Maven) and THEN come back and we can talk about how to make it work properly with Maven via configuration etc. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: using multiple artifacts from a single group
I am a newbie to maven and I am still trying to get a grip of how maven First off, you're emailing the wrong list. This list is for discussion of Maven itself. You should send future emails to the Maven Users list. While uploading these jars I have given unique artifact id to each jar but I have given same groupid. I was curious if I have to use all the jars in this group do I have to create a separate dependency section for each jar or is there an easier way to use all artifacts in a group. There is no way to use all artifacts in a group. You must list each one. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
Another late +1 from me. Looks good. I'm on vacation this week in Florida but found some time last night to run it against a handful of projects and didn't run into any issues. :) Wayne On Sat, Jun 1, 2013 at 8:13 AM, Jason van Zyl ja...@tesla.io wrote: Here are the release bits for 3.1.0-alpha-1: Release notes: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=18967 Staging repository: https://repository.apache.org/content/repositories/maven-046/ Staged distribution: https://repository.apache.org/content/repositories/maven-046/org/apache/maven/apache-maven/3.1.0-alpha-1/ Staged Site: http://maven.apache.org/ref/3.1.0-alpha-1 Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
Re: [VOTE] Should we respin CANCELLED releases with the same version number?
On Thu, May 30, 2013 at 4:55 AM, Stephen Connolly ... wrote: And I am considering whether I want to change my vote ;-) I am as well. Fred's comments like: but I'm not confused by the absence of 2.7.3 in any way shape or form. and The concept of immutability is pretty core to Maven (at least in my mind). are making me rethink things a little bit. :) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Should we respin CANCELLED releases with the same version number?
Agree with Dan. +1 for qualified -1 for actual Wayne On Wed, May 29, 2013 at 8:20 AM, Daniel Kulp dk...@apache.org wrote: +1 for qualified releases (alpha, beta, RC, etc…) that are working toward the full blow release but aren't intended to be that. -1 for the actual releases. Dan On May 29, 2013, at 6:01 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: We have been using a policy of only making releases without skipping version numbers, e.g. 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, etc Whereby if there is something wrong with the artifacts staged for release, we drop the staging repo, delete the tag, roll back the version, and run again. This vote is to change the policy to: drop the staging repo, document the release as not released, and run with the next version. Under this new proposal, if the staged artifacts for 3.1.0 fail to meet the release criteria, then the artifacts would be dropped from the staging repository and never see the light of day. The tag would remain in SCM, and we would document (somewhere) that the release was cancelled. The respin would have version number 3.1.1 and there would never be a 3.1.0. This change could mean that the first actual release of 3.1.x might end up being 3.1.67 (though I personally view that as unlikely, and in the context of 3.1.x I think we are very nearly there) Please Note: http://maven.apache.org/developers/release/maven-project-release-procedure.html#Check_the_vote_resultsdoes not actually specify what it means by the process will need to be restarted so this vote will effect a change either outcome +1: Never respin with the same version number, always increment the version for a respin 0: Don't care -1: Always respin with the same version number until that version number gets released This vote will be open for 72 hours. A Majority of PMC votes greater that 3 will be deemed as decisive in either direction (i.e. if the sum is -3 or +3 then there is a documented result) For any releases in progress at this point in time, it is up to the release manager to decide what to do if they need to do a respin. -Stephen -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
what is missing from maven is the ability to communicate arbitrary custom attributes on per-dependency basis, such as: provide osgiStartLevel value, to specify to osgi runtime bundle start level: ... or provide karafBootInstall flag, to specify that karaf runtime should install this dependency at boot-time vs build-time: ... in lieu of these, karaf-maven-plugin is trying to encode this information via scope https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215 which contradicts the dependency resolution rules and really does not work. hence my request to relax. is there any other ways to address this need? IMO this can and should all be handled via configuration in the karaf-m-p and not via adding attributes in dependencies which are specific to one plugin. Otherwise the Assembly plugin could reasonably ask to put outputFileNameMapping as an (optional) attribute of the dependency, and the Ear plugin could ask to put bundleFileName as an (optional) attribute, etc. That way lies madness. Look at how Assembly and Ear plugins (and others) are doing similar things for guidance on how to implement these features in the karaf plugin itself. FWIW I agree that doing it via scope is the wrong way to do it. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
the way I understand your suggestions is essentially I must duplicate configuration: Yes, just like you do with the other plugins mentioned. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache 3.1.0-alpha-1
to be able to annotate dependency with user properties - the kind of constrains I would like maven to remove in 3.1.0. Doubtful to be removed in 3.1.0. So: can I please respectfully request a formal PMC vote on my change request or should I just go away and leave you all alone? :-) No need to go away but please appreciate this is an issue that we are aware of and will continue to discuss for enhancement/change in some future release of Maven. Calling for a formal vote of the PMC at this time is unlikely to provide the result you desire. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven checkstyle plugin. No html report when failOnError = true.
If it's not the right address to ask such questions please direct me to the right please and sorry for inconvenience. This list is for the discussion of the development of Maven itself. Please post questions like yours to the Maven Users list, thanks. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] formally end support for Maven 1
My +1. On Sat, Mar 2, 2013 at 9:18 AM, Benson Margulies bimargul...@gmail.com wrote: Based on the sentiment on the discussion thread, I call a formal vote to end support for Maven 1.x. This is a vote to: 1: Remove maven 1 release materials from the primary distribution area, leaving them only on the archive. 2: Make appropriate changes to the web site to state clearly that the community no longer provides support for Maven 1. This vote will be open for until Wed March 6, 00:00 GMT (we're not in a hurry here). Here is my +1. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven 3.0.5
We fixed 1 issue: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=19088 Staging repository: https://repository.apache.org/content/repositories/maven-270/ Staging distribution: https://dist.apache.org/repos/dist/dev/maven/maven-3/3.0.5/ Vote open for 72H [+1] [0] [-1] +1 tested with some smaller personal projects and a couple larger work projects, no issues encountered Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Pain with MNG-5181 (_maven.repositories)
1/ change the default behavior to deactivate this control which is difficult to understand 2/ change the error message when this control is activated to clearly explain that the problem comes from the unavailability of the artifact on its original remote repo. For me 1/ is mandatory and 2/ a nice to have I am in general agreement but I would say 2 is must-do and 1 is probably-must-do. I've had to help a bunch of people who ran into this problem in the last few months. If the error message was better (with a simple direction to follow to disable it), then I'm less sure about 1 being a must-do. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Antrun to maven plugin - file size
So my question was is there an existing plugin to do this kind of stuff? I guess no. I am unaware of a plugin to calculate and then display the length of a file/resource. Your antrun approach seems valid, why change it? Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
Changing my vote to +1 based on Kristian and Mark's recent exchanges. Wayne On Thu, Sep 6, 2012 at 11:28 AM, Wayne Fay wayne...@gmail.com wrote: [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) +0.5 Sorry but I will be no help, I have little git experience except as an end user. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
[+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) +0.5 Sorry but I will be no help, I have little git experience except as an end user. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: org.codehaus.mojo.jspc:jspc-compiler-tomcat6:2.0WHATEVER
Devs I found jspc-compiler-tomcat6 was missing plugin.xml when testing today here is the signature groupIdorg.codehaus.mojo.jspc/groupId artifactIdjspc-compiler-tomcat6/artifactId version2.0/version .. The jspc-tomcat6 source is missing plugin.xml and needs compile goal code in the Impl class..I need someone to review and get back to me hopefully by Tuesday As this is an org.codehaus.mojo plugin, you should probably send emails of this nature to the Codehaus Mojo list, not the Apache Maven Dev list. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Welcome Anders Hammar as a committer
Happy to have you on board, Anders! Wayne On 8/20/12, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I am probably jumping the gun by an hour or two... however the account has been created ;-) Welcome Anders! Glad to see our first “graduate” of the committer school ;-) -Stphen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Relase Apache Parent Pom 11
+1 Wayne On Tue, Aug 7, 2012 at 7:44 AM, Vincent Siveton vsive...@apache.org wrote: +1 Vincent 2012/8/5 Olivier Lamy ol...@apache.org: Hi, I'd like to release Apache Parent 11. Staging repository is here: https://repository.apache.org/content/repositories/orgapacheapache-120/ Staged documentation: http://maven.apache.org/pom/asf-11/ Diff from previous release: http://svn.apache.org/viewvc/maven/pom/tags/apache-11/pom.xml?r1=HEADr2=1154610diff_format=h Vote open for 72H. [+1] [0] [-1] Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Snark on the users list
Rev 1364633 is a small contribution to more stuff to link to. Also on the Windows pre-reqs page, it might be nice to say something about antivirus software sometimes preventing Java from running properly, or Windows Firewall (and various other Firewalls) actively preventing Java.exe from reaching out to the Internet to download stuff which is a key part of Maven -- so that users will know to add exceptions to grant such actions. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: How do I reply to an old message on the ml ?
If i do Users-Get.128170@m.a.o I Get a digest format that I cannot reply to How do I do this ?? I am not sure you can, or that its worth trying to figure it out. Just ask on the Maven Dev list and someone (like myself) can post a bump which you can reply to. But looks like Dennis already did it. :) I tend to not delete M-U which helps to explain 8gb of email @ Gmail and hmmm 10k unread. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Snark on the users list
user community is not a great place to get it, since that community expects that users have this level of skill and experience. -1 ... this really is off putting. Oh, well, so much for that idea. We just need someone to use the izPack or NSIS maven plugins against Maven itself, and produce an installer for Windows... ;) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Central is probably blocked in China
The fact is now, that without reasonably reliable access to Maven Central, one can not really participate in many, many of the Java projects at ASF. Can you not just file a bug report with the Firewall ops group in China and ask them nicely to open access to Central? ;-) But seriously, what can be done? Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: In Maven how can I recursively build -SNAPSHOT dependencies present in the filesystem but outside the reactor?
I have two projects as follows, in neighbouring directories on the filesystem: * project_a (-SNAPSHOT) * project_b (-SNAPSHOT, depends on project_a) This list is dedicated to discussion of the ongoing development of Maven itself. Please post your question(s) on the Maven Users list and someone will most likely respond to them. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Version scheme question
* 0.3 is Vaadin 6-based, 0.4 is Vaadin 7-based, 0.5 is Vaadin6-based, etc.: It's weird because the features of the library should be exactly the same (the only difference is the underlying API that is being used) How about 0.7 becomes Vaadin 7-based? Not sure what happens when Vaadin 10.x comes out. Also not sure what happens when you decide to release a proper 1.0 release. Maybe call it 1.7 to indicate stable and based on Vaadin 7? Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Version scheme question
Eventually, I'd like to release a proper 1.0. That's the whole idea. How can we keep a consistent version scheme in such a case? Another approach I've seen (and generally like) incorporates the API number in the artifact id itself and not as part of the version. I see this as being a superior option to the 0.6 vs 0.7 option. Then you could have util_vaadin6 version 1.1 and util_vaadin7 version 0.9 and could release bug fixes as needed. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven for TIBCO projects
We are looking for feature in Maven if we can able to automate build deployment tasks for TIBCO projects, your advise is appreciated on this. You should probably ask this question in a TIBCO forum or possibly the Maven Users list. This list is reserved for discussion of the development of Maven itself. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Frederic Mura is out of the office.
On Thu, Apr 5, 2012 at 5:36 AM, frederic.m...@pds-europe.com wrote: I will be out of the office starting 04/05/2012 and will not return until 04/10/2012. Makes me wonder what Julia Antonova/Tumlare is up to lately... and when her next vacation is! Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: M3 regression: Unreliable results, because reactor fails to calculate proper build order
for Maven plugins. Especially in this case where I need a prepared local repository and an own settings.xml to demonstrate the bug. I cannot promise You may find Stephen's mrm-maven-plugin to be helpful... http://mojo.codehaus.org/mrm-maven-plugin/ Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: applying MNG-3547 to maven 2.1
I am forced to use maven 2.1 at work, but I need something like this Please tell me you mean 2.2.1. Maven 2.1 should not be used. It has serious problems. Please use 2.0.11 or 2.2.1 or even better would be 3.0+... Wayne
Re: [VOTE] Apache Maven 3.0.4
+1 binding Tested on a few work and personal projects with no regressions noted. Not doing anything particularly complicated in those builds. Wayne On Tue, Jan 17, 2012 at 4:14 AM, Olivier Lamy ol...@apache.org wrote: Hello, After some RCs, it's now time to cut the release. So I start the vote for Apache Maven 3.0.4. The release notes is available here: http://maven.apache.org/docs/3.0.4/release-notes.html The staging repo: https://repository.apache.org/content/repositories/maven-081/ For convenience builds are available here: http://people.apache.org/~olamy/maven/3.0.4/ [+1] [0] [-1] Vote open for 72H. Here my +1 Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Using maven as appstore for java app
I was wondering if maven repository structure can be exploited to also distribute java applications. Same repository structure may be used on I'm sure this is already happening in some firms. You may find the Codehaus Mojo appassembler project [1] and/or the Webstart project [2] to be helpful in this regard. What are you specifically thinking about? [1] http://mojo.codehaus.org/appassembler/ [2] http://mojo.codehaus.org/webstart/ Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [ANN] Maven Release Plugin 2.2.2 Released
That should have been: The Maven team is pleased to announce the release of the Maven 2.x Release Plugin, version 2.2.2 Wayne On 12/16/11, sebb seb...@gmail.com wrote: On 17 December 2011 01:46, Stephen Connolly steph...@apache.org wrote: The Maven team is pleased to announce the release of the Maven XXX Plugin, version Y.Z X, Y Z? 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: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.2.2/version /plugin Release Notes - Maven 2.x Release Plugin - Version 2.2.2 ** Bug * [MRELEASE-354] - Versions defined in profiles are not updated * [MRELEASE-454] - The Release-Plugin does not rewrite dependencies in the DependencyManagement with scope import * [MRELEASE-577] - release:prepare does not pass argument --settings with current settings.xml to inner maven ** Improvement * [MRELEASE-708] - upgrade to last scm 1.6 to integrate new scm provider mks integrity ** New Feature * [MRELEASE-467] - Release preparation should update version of plugin dependencies Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven build include util classes
On 12/2/11, AK-47 akshay.learn...@gmail.com wrote: Hi My question mite be seems a bit older and answered alot, but i couldn't satify to what i got a change to read till now. My question is why Maven doesn't allow to include any user running util classes/jar into compile or package as ant and other build tool used to provide Please post this question on the Maven Users list and someone will respond to it. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Archetype version 2.2
+1 now that I see the site ;-) Wayne On Sat, Nov 19, 2011 at 2:50 PM, Olivier Lamy ol...@apache.org wrote: +1 (site is here: http://maven.apache.org/archetype-2.2/archetype/ :-) ) 2011/11/19 Benson Margulies bimargul...@apache.org: Hi, We solved 8 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095version=17651 There are plenty of issues still open in JIRA: https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+ARCHETYPE+AND+status+%3D+Open+ORDER+BY+priority+DESCmode=hide Staging repo: https://repository.apache.org/content/repositories/maven-223/ Staging site: http://maven.apache.org/archetype-2.2 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why does the archetype plugin have such negative feelings about .?
If someone puts a property into archetype.properties with a . in its name, it's *silently* ignored unless it's one of the special properties that maps to a configuration element. Anyone know why? I know there used to be an issue regarding resolving properties with dots in their names... You'd essentially lose all the content before the final dot (a.c.c.d turned into d)... so the general suggestion was to use underscores in place of dots since they did not exhibit the same behavior. But I don't know/recall any specifics beyond that right now. I'd assume there's something in JIRA about it. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Use aether 1.13 and sisu 2.3.0 as dependencies of Apache Maven
I propose to upgrade to: * aether 1.13 * sisu 2.3.0 [+1] I'm in favor of this upgrade and the other upgrade when release will be available under eclipse.org governance (binding) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
How to set src-folder correctly
We are using maven for own project types. However the source folders (src/main/java and src/test/java) are not the same since we are not using java. To let some plugins work correctly we need to ovrwrite them with the correct folders. 1. This email should have been sent to the Maven Users list. The Maven Developers list is reserved for discussions around the development of the Maven tool itself. Please send any replies to Maven Users list, not this one. 2. What you are requesting is trivially accomplished via various entries in your pom.xml files. This is documented on the Maven website. Ideally you would have a single top parent pom that all your projects inherit from, and set the proper values there (in the top parent). Wayne
Re: Maven dependency:tree vs. dependency:list
dependency:tree and dependency:list give me different result set on My environments: Maven 3.0.3 This is covered in the Maven 3.x compatibility notes: https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2
+1 binding for the upgrade I echo Mark's comments about SPI and maven-aether-plugin. Wayne 2011/8/18 Arnaud Héritier aherit...@gmail.com: Hi all, Thus as decided with Mark and Kristian I relaunch a new vote with a better scope about what we are voting for. Next releases of SISU and Aether will be released at Eclipse.org under EPL 1.0 license. Before they were published under ASL or dual ASL/EPL licenses thus as defined in our policy [1] this change put them in Category B [2] and we need to validate this change by a vote with a majority of the PMC in favor (but the vote is open to everybody). I push only one vote for both dependencies as for now I see no reason to accept one and not the other. This vote will be open for 6 days as we are in august (If we have not enough votes at the end of next wednesday will see if we really need to extend it). The vote : [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries published under EPL 1.0 License and released under eclipse.org governance [+0] No opinion, do what you want. [-1] I'm against because (please elaborate) Arnaud [1] http://maven.apache.org/developers/dependency-policies.html [2] http://www.apache.org/legal/resolved.html#category-b - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses
+1 from me I am ok with EPL licensed dependencies for the project and being at Eclipse gives me security about how those artifacts will be managed, an avenue for us to provide patches and see them included, etc. Wayne On Wed, Aug 17, 2011 at 9:20 AM, Arnaud HERITIER aherit...@apache.org wrote: My vote : +1 as I don't see for now (sadly it is sure) another good solution to serve ours users. Arnaud On Wed, Aug 17, 2011 at 4:19 PM, Arnaud HERITIER aherit...@apache.orgwrote: Hi all, Next releases of SISU and Aether will be done at Eclipse.org under EPL 1.0 license. Before they were published under ASL or dual ASL/EPL licenses thus as defined in our policy [1] this change put them in Category B [2] and we need to validate this change by a vote with a majority of the PMC in favor (but the vote is open to everybody). I push only one vote for both dependencies as for now I see no reason to accept one and not the other. This vote will be open for 1 week as we are in august (If we have not enough votes at the end of next wednesday will see if we really need to extend it). The vote : [+1] I'm in favor to use as Maven core dependencies SISU and AETHER libraries published under EPL 1.0 License. [+0] No opinion, do what you want. [-1] I'm against because (please elaborate) Arnaud [1] http://maven.apache.org/developers/dependency-policies.html [2] http://www.apache.org/legal/resolved.html#category-b - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Is Maven Site Plugin 3.0-beta-4 ready for release?
A thought: since 'extensions' has no 'management' or inheritance control, the use of it is actually harder and more obscure when people want to use other versions. It's far easier to just manage dependencies of the site plugin via pluginManagement. So, I'm in favor of using and documenting dependencies rather than extensions. +1 from me on this, totally agree with Benson here (tho a bit late to the thread) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re: Re: why Maven 3 is divided into eleven eclipse project?
Maybe you are right,but large project as hadoop have far less ecipse projects compared with maven, is that necessary to have eleven eclipse projects? why not 5 or less? Honestly, why do you care? Is there a specific criticism, comment or question you have, other than 11 projects seems like a lot, Hadoop has less? Or are you just trolling for fun? Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: central is down :(
On Sun, May 22, 2011 at 2:03 PM, Wendy Smoak wsm...@gmail.com wrote: On Sun, May 22, 2011 at 3:00 PM, John Casey jdca...@commonjava.org wrote: I've just tried building a test project that resolves artifacts from http://repo1.maven.org/maven2 and it's working. It wasn't responding earlier, even to display the 'browsing is disabled' page. Seems to be okay now. I didn't try to access things myself at the time, but I have seen a couple complaints on user@grails about Central being down this past Sunday... and someone said it was also down last Sunday as well... I don't tend to do much on Sunday so I haven't been impacted or noticed any outages. ;-) Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PROPOSAL] Maven App Engine?
I have some code I've been working on for about a year now, on and off. The point is to make it easier to embed Maven inside an application, including giving access to Maven components via injection. I haven't checked out the code yet, but embedding Maven is a common use case for a lot of people, so anything that we can do to enable this is a Good Thing and gets my support. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: question : create profiles for download resources, properties ....
I want to create some profiles in my pom.xml for download resources, properties of configuration that it's in a server machine. Wrong list - send to Maven Users for help. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Could not launch cc: java.io.IOException: Cannot run program cc
On Thu, Mar 24, 2011 at 3:23 AM, kalpeer1 bsc.ka...@gmail.com wrote: Hi All, I am getting a below error message during the maven build in cpp and c package. Send this question to Maven Users list and someone will reply to it. This is not the correct list for such a question. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Defining common localRepository that will work on both Windows and linux
My settings file in the .m2 folder begins like this- localRepositoryC:\maven-repo\/localRepository I want to make this generic and define a common localRepository which will work both on Windows and on Linux. Please help. If you drop the C:\ and just specify a path, it will be common to both Windows and Linux. I am pretty sure Windows uses the SystemDrive property (type set in MSDOS to see the value) to decide which drive the path is located on, so hopefully all your Windows users have that value the same. For example: localRepository/maven-repo//localRepository Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Beginners Maven error
But I cant get rid of the error Project build error: The property name is required to activate the profile . What the hell does that mean and how can I avoid it. Its really annoying. The command I executed from the command line is mvn compiler: compile -X These kinds of questions should be sent to the Maven Users list. This list is reserved for discussions around the development of Maven itself. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need Help w/ the Creation of a Maven Mojo
the baseline version. Any tips on how I might tackle this would be greatly appreciated! You should probably take a look a the Sonar project and their Maven plugin to see how they are doing similar things, and perhaps Cobertura as well, and then use that as a basis for some of your own work. http://www.sonarsource.org/ http://cobertura.sourceforge.net/ You may even discover that your work could leverage Sonar, and simply be a plugin to Sonar or something along those lines, rather than replicating a lot of existing work. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Invite Evgeny Mandrikov to join Maven committers
+1 Wayne On Wed, Jan 26, 2011 at 12:30 AM, Olivier Lamy ol...@apache.org wrote: Hello, I propose Evgeny Mandrikov as a new committer. He as done a lot of patches for Maven SCM, he is a Mojo and Sonar contributor @codehaus. Vote is open for 72H. Here my +1. Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Query re: Maven Repository
Unable to find resource 'opensymphony:quartz-all:pom:1.6.2' in repository central (http://repo1.maven.org/maven2) Ask the OpenSymphony folks about this one. Unable to find resource 'javax.transaction:jta:jar:1.0.1B' in repository central (http://repo1.maven.org/maven2) http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html Unable to find resource 'com.oracle:ojdbc14:jar:10.2.0.3.0' in repository central (http://repo1.maven.org/maven2) Oracle has never posted their ojdbc artifact in any repo that I'm aware of, probably for similar reasons to the Sun JTA jar above (licensing). . . . checking on the server we find that they’re indeed missing. Do you have any idea how they could suddenly go missing, and what we might do to replace them or ask the owner to replace them? Thanks in advance for any As Anders stated previously, deploy your own local copy of Nexus and manually install these artifacts in it, then all of your developers will get the files properly etc. And get used to the fact that not every jar you ever need/want to use as a dependency is going to be available in a Maven repo. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Why is Julia Antonova/Tumlare subscribed
Lurking is a constitutional right of the interwebs Ralph :-) Agreed, and anyway, her emails are a source of fun for us. Let her stay subscribed until she decides to speak up or unsubscribe. ;-) Just blacklist her if you really can't stand to see her emails... Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
Wahoo Julia going on break is like the summer solstice. ;-) wf On Sat, Jun 12, 2010 at 9:36 AM, Paul Benedict pbened...@apache.org wrote: If anyone should be allowed to send an OOO reminder, it's definitely Julia. Let the ceremonial rituals begin! I believe she has marked the start of the summer vacation season for us. Paul On Sat, Jun 12, 2010 at 7:04 AM, sebb seb...@gmail.com wrote: Have you seen this? http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova/Tumlareoutoftheoffice? But I agree it's annoying. The problem is that there are lots of different ways of denoting OoO messages. Just matching on subject line will result in false positives. I think many of them have the header: Auto-Submitted: auto-generated which is unlikely to be present in proper postings. On 12/06/2010, Martin Gainty mgai...@hotmail.com wrote: these transmissions are annoying and rude..is there a way we can filter emails from corporate is off the list maybe a maven-filter-plugin activated by quartz scheduler that reads out of office and redirects to the round-file? bedankt, Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Subject: Julia Antonova/Tumlare is out of office. From: juli...@tumlare.com To: dev@maven.apache.org Date: Sat, 12 Jun 2010 15:32:55 +0400 I will be out of the office starting 12.06.2010 and will not return until 15.06.2010. I have no acces to my mailbox, I will reply to your message upon return. For urgent issues please contact my colleagues: Sergey Khomyakov / Administration - serge...@tumlare.com Irina Pashina / Administration - secretary...@tumlare.com _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
Tim, this is a great addition to the FAQs! I especially like the calendar going back a few years. ;-) Wayne On Fri, Apr 30, 2010 at 2:33 PM, Tim O'Brien tobr...@discursive.com wrote: Ok, I'm glad we were all prepared for this. I've made sure to update the Maven FAQ to include this info for others that might be confused: http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova%2FTumlareoutoftheoffice%3F On Fri, Apr 30, 2010 at 2:17 PM, John Casey jdca...@commonjava.org wrote: It's good to ALWAYS know just where Julia is...or, rather, isn't. On 4/30/10 3:11 PM, Julia Antonova wrote: I will be out of the office starting 30.04.2010 and will not return until 04.05.2010. I have no acces to my mailbox, I will reply to your message upon return. For urgent issues please contact my colleagues: Sergey Khomyakov / Administration - serge...@tumlare.com Irina Pashina / Administration - secretary...@tumlare.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
I've been wondering that myself for months... nay years now. ;-) On Tue, May 4, 2010 at 1:01 PM, Brian Fox bri...@infinity.nu wrote: Clearly she doesn't read this list or she would have known by now to stop doing that. Should we just unsub her? On Tue, May 4, 2010 at 1:57 PM, Martin Gainty mgai...@hotmail.com wrote: i dont know if they have internet there yet but you *might* want to check her dacha outside of moscow Martin Gainty __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Date: Tue, 4 May 2010 12:34:41 -0500 Subject: Re: Julia Antonova/Tumlare is out of office. From: wayne...@gmail.com To: dev@maven.apache.org Tim, this is a great addition to the FAQs! I especially like the calendar going back a few years. ;-) Wayne On Fri, Apr 30, 2010 at 2:33 PM, Tim O'Brien tobr...@discursive.com wrote: Ok, I'm glad we were all prepared for this. I've made sure to update the Maven FAQ to include this info for others that might be confused: http://docs.codehaus.org/display/MAVENUSER/FAQs-1#FAQs-1-IsJuliaAntonova%2FTumlareoutoftheoffice%3F On Fri, Apr 30, 2010 at 2:17 PM, John Casey jdca...@commonjava.org wrote: It's good to ALWAYS know just where Julia is...or, rather, isn't. On 4/30/10 3:11 PM, Julia Antonova wrote: I will be out of the office starting 30.04.2010 and will not return until 04.05.2010. I have no acces to my mailbox, I will reply to your message upon return. For urgent issues please contact my colleagues: Sergey Khomyakov / Administration - serge...@tumlare.com Irina Pashina / Administration - secretary...@tumlare.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
I'm taking today AND tomorrow off!! ;-) On Fri, Apr 16, 2010 at 11:27 PM, Tim O'Brien tobr...@discursive.com wrote: By my tally that's 18 vacation days just this year. I think I'm going to take tomorrow off. These emails serve as a good reminder for us all. On Fri, Apr 16, 2010 at 11:01 PM, Paul Benedict pbened...@apache.org wrote: Wayne, great point. Makes me jealous too. On Fri, Apr 16, 2010 at 10:10 PM, Wayne Fay wayne...@gmail.com wrote: On Fri, Apr 16, 2010 at 11:46 AM, Julia Antonova juli...@tumlare.com wrote: I will be out of the office starting 16.04.2010 and will not return until 20.04.2010. Just like clockwork... Julia is on vacation again! /jealous Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
On Fri, Apr 16, 2010 at 11:46 AM, Julia Antonova juli...@tumlare.com wrote: I will be out of the office starting 16.04.2010 and will not return until 20.04.2010. Just like clockwork... Julia is on vacation again! /jealous Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Get the effective pom to a program
I want to get the effective pom of a given pom file in to a progam that I am writing. Is there a way to reuse the code in the maven help plugin to get this done? 1. Probably should be asking this on Maven Users list. 2. This should do it: mvn help:effective-pom | your-program Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Problem with wsdl2code
Internal error in the plugin manager executing goal 'org.apache.axis2:axis2-wsdl2code-maven-plugin:1.4.1:wsdl2code': Unable to find the mojo 'org.apache.axis2:axis2-wsdl2code-maven-plugin:1.4.1:wsdl2code' in the Sounds like an issue in the plugin. I'd report it to the Axis2 team and see what they say about it. Also compare the wsdl2code plugin artifacts in your local repo cache (size, timestamp, content?) to make sure they are identical -- one may be corrupt for some reason. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Julia Antonova/Tumlare is out of office.
You'd think Julia would eventually figure out that she should not be sending these out of office emails to public mailing lists... I guess not. WAyne On Thu, Feb 4, 2010 at 4:34 PM, Julia Antonova juli...@tumlare.com wrote: I will be out of the office starting 05.02.2010 and will not return until 08.02.2010. I have no acces to my mailbox, I will reply to your message upon return. For urgent issues please contact my colleagues: Elena Tonoyan / Administration - elen...@tumlare.com Daria Ignatieva / Administration - secretary...@tumlare.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven-war-plugin not installing war. Installs .jar and renames it to .war
It would be great if this would be fixed. It seems the maven-source-plugin works properly, but the maven-war-plugin does not. I would like to generate primary and secondary artifacts using a single pom file. It seems overly complex to have to make modules out of everything. Unless you fix it yourself, I don't see this situation changing. Make a module with the jar contents as Eric said in the Jira. Get used to making lots of modules for your code with Maven. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-gwt-plugin 1.2 documentation
It's not the wrong list, I reported some miss in the gwt plugin to Nicolas. Hopefully, he'll fix them quickly. I think Jason's point is that this discussion belongs on the mojo-dev or mojo-users list, not Maven dev, since this is a Mojo plugin... Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: a cleaned up central repository? (was: Maven Central Repository - Cleanup Efforts)
I have proposed in the original thread a solution, based on multiple index files, which index files would represent the output of CAs. If I configure in my Maven settings file (by URL) which index file I want to use, my Maven should be blind to any other artifacts on the repo. Allowing AND and OR operations on this cert lists would be a bonus. Who exactly is setting up, managing, and paying for the ongoing operation of these CAs? You didn't address this in the original thread, and right now I'm not aware of any existing organizations that would fill this void. Especially not for free. Without address that aspect, the rest of the discussion is not worth much IMO. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven Enterprise Edition from Overall.ca?
Just saw something odd in Gmail web clip/sponsored link while browsing emails to the list... Maven Enterprise Edition - www.overall.ca/maven - Build the ultimate toolbox for your Windows support tools From their site: Introducing Maven Enterprise Edition Your enterprise data is typically found in multiple sources. Maven Enterprise Edition enables your organization to build and deploy a complete Windows support dashboard, with all of the queries, support tools, scripts and enterprise information required to rapidly service your IT infrastructure. Your service desk can do what they do best; service your organization. Their About Us says they've been around since 2002. Click into the forums and the oldest post is 2008-12-02, so its hard to tell how old their Maven Enterprise Edition tool really is. Anyone know these guys? Obviously their Maven has no relationship whatsoever to this one. Pretty bad choice of names on their part, imo. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Enterprise Edition from Overall.ca?
Agree completely. Just thought it was not the world's best job name for what seems to be a new tool. Eventually all the good words in the dictionary are taken, so duplication is normal, but it was simply the Gmail sponsored link that made me aware of it. I bet this company is benefiting nicely from discussions about Apache Maven driving traffic to their Maven Enterprise Edition tool. More than one F/OSS tool has been forced to change its name due to trademark issues so this is just FYI... I can't imagine that would happen, but stranger things have happened. Wayne On Thu, Mar 26, 2009 at 5:01 AM, Brian E. Fox bri...@reply.infinity.nu wrote: It looks like a hardware tracking / provisioning tool not a build system. Shrug. Not related to Apache Maven at all it appears to me. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Thursday, March 26, 2009 2:19 AM To: Maven Developers List Subject: Maven Enterprise Edition from Overall.ca? Just saw something odd in Gmail web clip/sponsored link while browsing emails to the list... Maven Enterprise Edition - www.overall.ca/maven - Build the ultimate toolbox for your Windows support tools From their site: Introducing Maven Enterprise Edition Your enterprise data is typically found in multiple sources. Maven Enterprise Edition enables your organization to build and deploy a complete Windows support dashboard, with all of the queries, support tools, scripts and enterprise information required to rapidly service your IT infrastructure. Your service desk can do what they do best; service your organization. Their About Us says they've been around since 2002. Click into the forums and the oldest post is 2008-12-02, so its hard to tell how old their Maven Enterprise Edition tool really is. Anyone know these guys? Obviously their Maven has no relationship whatsoever to this one. Pretty bad choice of names on their part, imo. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Extending the maven pom.
I think Brett's point was that the original message was delivered to the Maven list without any content. If you follow the Nabble link you'll see what the original post was about. I believe people can edit/update their posts on Nabble, so the email we received was blank, but johnlon might not even realize what happened. He probably assumes it is like a msg board rather than an email gateway/interface. One of the many reasons I only use Nabble for reading email, not sending... Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Artifact Version Comparison
The JBoss Product Versioning [0] suggests the following additional well-known qualifiers: - CR - FINAL How is CR different from RC? One is Candidate Release, the other is Release Candidate. I think I'd pick one and forget about the other. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM Element for Source File Encoding
This idea with the warning was also proposed by two or three users on the list, especially Hervé put it nicely [0]. I took this happily up because I (still) believe that having builds out there which implicitly rely on the platform encoding and as such just break with the ideals of platform-independence and build reproducibility is nothing that should be promoted, not in general and in particular not by Maven. And I consider silent acceptance as a mild form of promotion. Maven is an opinionated piece of software. Let the PMC decide what their opinion is on this matter and then let it be implemented. My personal opinion is that file encoding should be consciously considered and declared, and as such warning is most appropriate rather than simply info. I could be talked into accepting an info that has build not fully reproducible etc text in it, but this is splitting hairs. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM Element for Source File Encoding
I agree and we can do this for 2.1. We can't break the existing contract which can potentially screw a lot of people. No one is proposing changing things for 2.0. If no encoding is declared, it will use the system default, as it has always done. We're just talking about INFO vs WARNING for informing users that they have not declared the file encoding as we would (strongly) prefer. A pretty small point in the grand scheme of things. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to start / stop the tomcat 6 server with maven2
As Brian said, send your questions to the Users list: Maven Users List [EMAIL PROTECTED] Also, do not send your emails repeatedly. If someone knows the answer, they will reply. Sending the same email 3+ times in 1 day will only make people angry, and they will be less likely to help you. Wayne On 3/25/08, Brian E. Fox [EMAIL PROTECTED] wrote: Please use the users list for these questions. The dev list is reserved for Maven Plugin development questions, discussions. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 4:32 AM To: dev@maven.apache.org Subject: how to start / stop the tomcat 6 server with maven2 How to start / stop the tomcat 6 server with maven2 Can any help me / send sample code / guide me Thanks Regards, Sridhar Thota, Accenture - India | O: +91 22 40444170 | Ext: 4170 | C: +91 9930245689 | Aim/gTalk: mails4sri | Mial/YIm/Msn: sridhar.thota -Original Message- From: PashaOvechkin [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 1:57 PM To: dev@maven.apache.org Subject: RE: How to build properties JAR Hmmm... By default? I create src/main/resources directory, and run my pom... Don't see any properties jar :| Brian E Fox wrote: Put them in src/main/resources and it should happen by default. -Original Message- From: PashaOvechkin [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2008 11:53 AM To: dev@maven.apache.org Subject: How to build properties JAR I need with Maven command get jar with properties files(only with properties files). What i need add in my pom.xml? (for example in the same directory with pom.xml I have aaa.properties and bbb.properties, and need jar with both files) Tanks!!! -- View this message in context: http://www.nabble.com/How-to-build-properties-JAR-tp16254904s177p1625490 4.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-to-build-properties-JAR-tp16254904s177p1627057 4.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Applet JARS inside WAR files using Maven 2.0
On Tue, 25 Mar 2008, [EMAIL PROTECTED] wrote: Hi, I have been scratching my head on this one for awhile. Please send these kinds of questions to the Maven Users list. This list is reserved for discussion of the development of Maven itself. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Relative path to local repository?
My gut is that the configuration in settings.xml should always be an absolute path. The way this user (in MECLIPSE-404) is using the configuration is simply an anti-pattern. Wayne On 3/18/08, Benjamin Bentmann [EMAIL PROTECTED] wrote: Hi, the recent release of maven-eclipse-plugin:2.5 brought up http://jira.codehaus.org/browse/MECLIPSE-404 which is caused by (windows) users specifying drive-relative paths to their local repos. Further progress on this issue would require some clarification: Is Maven supposed to support relative paths to the local repository or is the corresponding configuration in the settings.xml always expected to be an absolute path? In the later case, I would create an issue to make Maven actually validate the absoluteness of the path to save plugins from unexpected relative-path effects. Benjamin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Julia Antonova/Tumlare is out due to sick leave.
Oh no, Julia is out of the office again... I hope she feels better and returns to work soon. ;-) Wayne On 2/26/08, Julia Antonova [EMAIL PROTECTED] wrote: I will be out of the office starting 25.02.2008 and will not return until 29.02.2008. I will respond to your message when I return. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem creating j2ee-simple
What do you mean, you're using an old Maven central? Did you download the entire Central repo? You can always just manually create the file structure etc. The archetypes are simply available to make things easier for you to get stuff set up. Wayne On 12/12/07, Jens Rapp [EMAIL PROTECTED] wrote: hi there! i'm using an old (june 2006) maven central. creating a j2ee-simple I get an error unable to find resource 'archetype-resources/site/pom.xml' in any resource loader. the maven-archetype-j2ee-simple plugin release date is may, 07 2006. Is there any workaround to fix this? -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem creating j2ee-simple
Also, you should not post these types of questions to Dev. Instead, post to the Users list Wayne On 12/12/07, Wayne Fay [EMAIL PROTECTED] wrote: What do you mean, you're using an old Maven central? Did you download the entire Central repo? You can always just manually create the file structure etc. The archetypes are simply available to make things easier for you to get stuff set up. Wayne On 12/12/07, Jens Rapp [EMAIL PROTECTED] wrote: hi there! i'm using an old (june 2006) maven central. creating a j2ee-simple I get an error unable to find resource 'archetype-resources/site/pom.xml' in any resource loader. the maven-archetype-j2ee-simple plugin release date is may, 07 2006. Is there any workaround to fix this? -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release maven-site-plugin 2.0-beta-6
You're right. This popped up on Google search, but it seems to be a *very* old page. We should probably remove it completely! The correct url is: http://maven.apache.org/general.html Perhaps we can eliminate this page, and forward faq.html to general.html to avoid breaking the Google search? Wayne On 11/26/07, Dennis Lundberg [EMAIL PROTECTED] wrote: That page was published on 30 Jan 2006, so at least it wasn't this version of the plugin. Wayne Fay wrote: I'm not sure what version of site-plugin is responsible for the FAQ page, but if its this version, there seem to be some issues... http://maven.apache.org/faq.html Wayne On 11/25/07, William Ferguson [EMAIL PROTECTED] wrote: OK, I'm trying to validate but I guess I have some bad config. It looks like its attempting to retrieve the site-plugin POM from my mirror of central and the site-plugin jar from the staging area. D:\Modules\hubbub-log4jmvn site [INFO] Scanning for projects... [INFO] [INFO] Building hubbub-log4j [INFO]task-segment: [site] [INFO] [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from maven-staging [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from central Downloading: http://hubpc65:8080/artifactory/release/org/apache/maven/plugins/maven-s ite-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom Downloading: http://people.apache.org/~dennisl/staging-repository-site-plugin//org/ap ache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-be ta-6.jar 118K downloaded Build output snipped [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site': Unable to find the mojo 'org.apac he.maven.plugins:maven-site-plugin:2.0-beta-6:site' in the plugin 'org.apache.maven.plugins:maven-site-plugin' org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext [INFO] Settings.xml looks like: mirrors mirror mirrorOfcentral/mirrorOf nameBrisbane Maven Proxy for Yarris/name urlhttp://hubpc65:8080/artifactory/release/url /mirror /mirrors profiles profile idmaven-staging/id repositories repository idmaven-staging/id nameMaven Staging Repository/name urlhttp://people.apache.org/~dennisl/staging-repository-site-plugin// url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idmaven-staging/id nameMaven Staging Repository/name urlhttp://people.apache.org/~dennisl/staging-repository-site-plugin// url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /pluginRepository /pluginRepositories /profile profiles activeProfiles activeProfilemaven-staging/activeProfile /activeProfiles What do I need in settings.xml in order to retrieve the POM from the staging area? William -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, 25 November 2007 3:21 AM To: Maven Developers List Subject: [***POSSIBLE SPAM***] - [VOTE] Release maven-site-plugin 2.0-beta-6 - Sender is forged (SPF Fail) Hi, I'd like to release maven-site-plugin 2.0-beta-6. We have resolved 36 issues since the last release, 18 months ago. Release Notes: http://jira.codehaus.org
Re: [VOTE] Release maven-site-plugin 2.0-beta-6
I'm not sure what version of site-plugin is responsible for the FAQ page, but if its this version, there seem to be some issues... http://maven.apache.org/faq.html Wayne On 11/25/07, William Ferguson [EMAIL PROTECTED] wrote: OK, I'm trying to validate but I guess I have some bad config. It looks like its attempting to retrieve the site-plugin POM from my mirror of central and the site-plugin jar from the staging area. D:\Modules\hubbub-log4jmvn site [INFO] Scanning for projects... [INFO] [INFO] Building hubbub-log4j [INFO]task-segment: [site] [INFO] [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from maven-staging [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from central Downloading: http://hubpc65:8080/artifactory/release/org/apache/maven/plugins/maven-s ite-plugin/2.0-beta-6/maven-site-plugin-2.0-beta-6.pom Downloading: http://people.apache.org/~dennisl/staging-repository-site-plugin//org/ap ache/maven/plugins/maven-site-plugin/2.0-beta-6/maven-site-plugin-2.0-be ta-6.jar 118K downloaded Build output snipped [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-site-plugin:2.0-beta-6:site': Unable to find the mojo 'org.apac he.maven.plugins:maven-site-plugin:2.0-beta-6:site' in the plugin 'org.apache.maven.plugins:maven-site-plugin' org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext [INFO] Settings.xml looks like: mirrors mirror mirrorOfcentral/mirrorOf nameBrisbane Maven Proxy for Yarris/name urlhttp://hubpc65:8080/artifactory/release/url /mirror /mirrors profiles profile idmaven-staging/id repositories repository idmaven-staging/id nameMaven Staging Repository/name urlhttp://people.apache.org/~dennisl/staging-repository-site-plugin// url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idmaven-staging/id nameMaven Staging Repository/name urlhttp://people.apache.org/~dennisl/staging-repository-site-plugin// url releases enabledtrue/enabled /releases snapshots enabledfalse/enabled /snapshots /pluginRepository /pluginRepositories /profile profiles activeProfiles activeProfilemaven-staging/activeProfile /activeProfiles What do I need in settings.xml in order to retrieve the POM from the staging area? William -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Sunday, 25 November 2007 3:21 AM To: Maven Developers List Subject: [***POSSIBLE SPAM***] - [VOTE] Release maven-site-plugin 2.0-beta-6 - Sender is forged (SPF Fail) Hi, I'd like to release maven-site-plugin 2.0-beta-6. We have resolved 36 issues since the last release, 18 months ago. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=111 46styleName=Htmlversion=12151 Tag: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-site -plugin-2.0-beta-6/ Staging repo: http://people.apache.org/~dennisl/staging-repository-site-plugin/ The vote will be open for 72 hours. Here is my +1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To
Re: Proposal for a Maven Dependency Registry
I agree with Brett. Any organization that is seriously using Maven is probably running a proxy/repo manager. Also, I know how other people manage their repos, and it is a bit scary. I don't trust most of them to never change artifacts etc. Oh this jar has a bug, but its only been out for 2 weeks and not many people have it, so we're just going to recut the release. Wayne On 11/13/07, Brett Porter [EMAIL PROTECTED] wrote: I agree with what Brian has said. FWIW, any organisation can implement this internally in minutes by configuring any one of the available repository managers [1]. The only thing I'd add is that in my opinion Maven needs better support for true mirrors (of central, but also any other repo), as well as strong support for non-central repositories which is presumably the source of a problem you are having with right now to inspire this? Cheers, Brett [1] http://www.devzuz.org/blogs/oching/2007/11/05/119423340.html On 13/11/2007, at 4:07 AM, Brian E. Fox wrote: This sounds good on paper, but in practicality it could be troublesome. First of all, there are many more moving parts and we can't be sure of or control the reliability of all these remote repos. Recall the trouble we had with Ibiblio a few years ago and the instability there. Since central moved to Contegix, it has been remarkably fast and reliable. I believe there is also a hot back already available for this. Additionally, for locations that have restrictive proxy/firewall policies, this would be a nightmare. They would constantly need to have access opened up to new repos and it might be impossible to predict ahead of time exactly which ones they may need. For those reasons, I would be -1 on this. --Brian -Original Message- From: David Siefert [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 13, 2007 4:36 AM To: dev@maven.apache.org Subject: Proposal for a Maven Dependency Registry Hi, I am not sure if anyone has already asked about this, but in case not I am proposing the idea now: a Maven Dependency Registry. I created a very simple web application (could not attach here-- detected as spam) that accepts requests for files (presumably the Maven 2 convention for a dependency located in the repository), looks up a registry of groupId's based on a properties file, and sends an HTTP 302 redirect response with the appropriate registry location's full path. It is not perfect yet--it is just a Proof of Concept. I am attempting to solve some issues, namely: 1 Relieves the burden of the Maven projects staff of maintaining the big, bloated, disorganized repository. This effort will be handled by those who actually release libraries (such as JBoss.org, Codehaus, Apache projects, etc). The repo1.maven.org should eventually die off (dependencies removed as others register their groupId with their repository), or only be left for Maven itself and the bundled plugins that are maintained. 2 Since the original authors of the dependencies will maintain their own small release/snapshot repository, all the POM information will automatically be bundled, and nothing has to be fished down (transitive dependencies that were not specified because the libraries were loaded from a non-Maven project). Transitive dependencies stay on their respective repository and don't lose their valuable Maven build information. 3 Speedier access to the Maven core repository, and other repositories for that matter since the repository is smaller and not needed for everything. 4 Lower maintenance requirements of the Maven team--more time for bug fixing. Maybe these aren't good enough reasons, or developers of Maven may see a reason NOT to have a registry. That is why I am only proposing the idea and presenting a small proof of concept. If it is not ideal, then I won't waste my time developing this any further. I appreciate any and all feedback. Thanks, David Siefert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin Resolution Bug?
Try using the full name of the plug-in, something along these lines: mvn clean triemax:jalopy-maven-plugin:1.0:format If you couldn't tell, that's groupId:artifactId:version:mojo. Wayne On 10/17/07, Jan Nielsen [EMAIL PROTECTED] wrote: I have configured our local repository as a single repository, mirroring all repository requests, and I have configured the plugin groups to use triemax: pluginGroups pluginGrouptriemax/pluginGroup /pluginGroups mirrors mirror idinternal-repository/id nameMaven Repository Manager/name urlhttp://it.access.dev/repository/url mirrorOf*/mirrorOf /mirror /mirrors However, when I run: mvn clean jalopy:format -X the org.codehaus.mojo group ID is used to resolve the plugin instead of triemax. I have changed the name of the org.codehaus.mojo Jalopy instance which therefore fails to resolve as seen below. But how do I get Maven to actually use the configured triemax as the group identifier for this plugin??? It appears that I might be able to use the plugin-registry.xml to over-ride this (broken?) behavior if I knew how to use it...the Maven web page does not contain a schema: http://maven.apache.org/guides/introduction/introduction-to-plugin-registry.html Any ideas on how to work-around this issue, or fix it? Many thanks, -Jan + Error stacktraces are turned on. Maven version: 2.0.7 Java version: 1.6.0 OS name: windows xp version: 5.1 arch: x86 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Jan Nielsen\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\maven-2.0.7\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Meridian [INFO] Meridian Meta Data [INFO] Meridian Offer [INFO] Meridian Offer API [INFO] Meridian Offer Persistence [INFO] Meridian Samples [INFO] Merchant Samples [INFO] Merchant Samples API [INFO] Merchant Samples Migration [INFO] Merchant Samples Persistence [INFO] Merchant Samples CLI [INFO] Merchant Samples JSF Portlet [INFO] Searching repository for plugin with prefix: 'jalopy'. [DEBUG] Loading plugin prefixes from group: triemax [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [INFO] org.codehaus.mojo: checking for updates from Access Development Releases [INFO] org.codehaus.mojo: checking for updates from Codehaus Snapshots [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking for updates from Access Development Releases [DEBUG] repository metadata for: 'artifact org.codehaus.mojo:jalopy-maven-plugin' could not be found on repository: Access Development Releases [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking for updates from Codehaus Snapshots [DEBUG] repository metadata for: 'artifact org.codehaus.mojo:jalopy-maven-plugin' could not be found on repository: Codehaus Snapshots [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking for updates from central [DEBUG] repository metadata for: 'artifact org.codehaus.mojo:jalopy-maven-plugin' could not be found on repository: central [DEBUG] jalopy-maven-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.codehaus.mojo:jalopy-maven-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.codehaus.mojo:jalopy-maven-plugin:pom:LATEST [DEBUG] jalopy-maven-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.codehaus.mojo:jalopy-maven-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.codehaus.mojo:jalopy-maven-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.codehaus.mojo:jalopy-maven-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.codehaus.mojo:jalopy-maven-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1522) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:386) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:138) at
Re: Modifying deploy plugin to prevent deployment of existing versions
This is a not uncommon issue raised on the Users list, so I'm happy to see you addressing it, Jason. The general suggestion until now has been run Archiva or similar or run cron every hour to set -r on all artifacts in your repo but a native Maven solution will be much nicer. Wayne On 10/19/07, Brett Porter [EMAIL PROTECTED] wrote: I think that's a reasonable assumption. The worst cases I can think of: - it deploys again if the metadata is missing or is missing the version, no worse than now - it doesn't deploy again if the metadata thinks it is there and it isn't (which we can state clearly with a message so there'll be no doubt how to fix). Works for me. Thanks! - Brett On 19/10/2007, at 4:02 PM, Jason van Zyl wrote: On 18 Oct 07, at 10:40 PM 18 Oct 07, Brett Porter wrote: rock on. How are you going to implement? I'm presuming you also don't want to download the previous artifact, so either will trust the metadata, or maybe have a wagon.exists() method check that can HEAD the file on HTTP and (whatever else) on the others? I am assuming the metadata has not been diddled and use it if it is there. I also look for the checksum and compare them because in my case the source versioning is sometime wrong and it is actually something new so I issue a message in this case (my tool bumps the version automatically) but if they are the same then it's definitely a no no. I'm assuming people are not idiots and so they use the deploy plugin to populate their repositories so I'm not using wagon.exists() but that can't hurt either. The case is almost always a corporate environment so they have used the deployment plugin. - Brett On 19/10/2007, at 3:28 PM, Jason van Zyl wrote: I've been working on some release/deployment tools lately for a client and I modified their deployments so that you could not accidentally release the same version of an artifact more then once. I can stop this on the server side only when running a repository manager, but we have some simple Apache servers that are DAV enables and someone release an artifact with the same version by mistake and wreaked havoc for 4 hours. I think this one is pretty obvious, I'm not going to write a proposal I'm just going to fix it because it's not very bright that we allow the re-release of something that already has been. I'll leave a option to redeploy if you so choose in the event the driver knows what he's doing. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency:analyze changes
This seems to line up with what other plugins are doing, and the terminology seems clear as well, so this sounds like the best choice. It just took us a while to realize that. ;-) Wayne On 9/19/07, Mark Hobson [EMAIL PROTECTED] wrote: On 18/09/2007, Paul Gier [EMAIL PROTECTED] wrote: I think that's what I meant ;) Anyway, the surefire report plugin uses report and report-only to do something similar, so that seems consistent with Brian's suggestion of using analyze and analyze-only. Great, I think we're all in agreement now :) I've renamed analyze-attached to analyze-only, so the final state of affairs is: dependency:analyze - executes test-compile phase - for use standalone dependency:analyze-only - executes in phase verify - for use in the build lifecycle Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE: pre-configuring self written plugins
The defaults are in the source code, as you mentioned. Which will require compilation to change. So it sounds like your requirements cannot be met currently. Why don't you explain what exactly you're trying to achieve, and perhaps someone will have an alternate suggestion? Wayne On 9/19/07, Jens Rapp [EMAIL PROTECTED] wrote: well, i did this but i couldn't find where to set them- besides the declaration in the plugin's source code but i would have to recompile the plugin if those parameters are changed.. can you tell me where to find these defaults? Original-Nachricht Datum: Wed, 19 Sep 2007 09:33:01 -0400 Von: Brian E. Fox [EMAIL PROTECTED] An: Maven Developers List dev@maven.apache.org Betreff: RE: pre-configuring self written plugins Parameters in your plugins can have defaults. Take a look at any of the maven plugins for examples. -Original Message- From: Jens Rapp [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 8:29 AM To: dev@maven.apache.org Subject: pre-configuring self written plugins hi there! is there any way to pre-configure my own maven plugin so that i am able to create and modify a standard config without re-compiling? i don't want the users to be forced to configure some parameters by themselves. -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Classpath ordering of dependencies
It also sounds like perhaps you need an excludes in your dependency declaration, to get rid of that bad transitive dep. Wayne On 7 Sep 07, at 2:20 PM 7 Sep 07, Paul Gier wrote: I did a little more research, and it looks like the artifact was renamed, so maven didn't know they were the same artifact. For an example, if you create a project with a direct dependency on antlr:antlr:3.0b5 and have a transitive dependency on antlr:antlr: 2.7.1, you will get the 2.7.1 version in the classpath first because 3.0b5 has been renamed to groupId org.antlr When the groupId and artifactId are the same, then maven does the right thing and removed the transitive dependency. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [poll] Requiring users to specify plugin versions in Maven 2.1 or later
Reading more responses, it seems like a lot of people want A so Maven can help people with their builds. In the long-run (post 2.1), I also like A, but we can't jump there overnight. Today I prefer B, but I am OK with A if we do the following: 1. Have a tag in the pom, which is also available on the command line, named unstable_build. Archetype should be modified to insert this tag and it should default to true (for now). 2. If unstable_build is true, we should throw a message at the beginning and end of the build that says Maven is running in UNSTABLE build mode. Go here http://maven.apache.org/FAQ/UnstableBuild to get rid of this message. and then we have a FAQ that talks about versioning things, how to lock things down, why its a good thing, etc. 3. If unstable_build is true and versions are unspecified, then Maven works like it does today. The tag unstable_build is specifically chosen to be somewhat offensive/negative and with immediately obvious meaning -- hopefully this is true for our international friends, too. No QE/QA group in the world would allow a self-declared unstable build pass their organization. But new users or expert users who don't want their versions locked down (yet) can still get into Maven and get things done without hassles. I appreciate the comments about helping people get their builds right etc and generally agree, but I don't think we can jump to this extreme overnight. So let's deprecate the idea of not specifying versions and then perhaps we can eliminate it (require all versions) in 2.2, 2.3, or 3.x. Wayne On 9/2/07, Wayne Fay [EMAIL PROTECTED] wrote: [X] (B) Retain the current behaviour, but make using the enforcer a best practice to do the above, or some other control mechanism such as having the repository manager handle the available plugins I am thinking about the new user experience and winning more converts. As such, I think the current behavior is best. Once they get using Maven more seriously (and in corporate environments that know what they're doing), I think adding the Enforcer configuration and locking versions down will come naturally. But *requiring* it seems excessive -- unless we're doing that ourselves somewhere, with plugin packs or similar, then I feel better about it. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with ejb deployment
You should not be sending these emails to Maven Dev list. This has nothing to do with the development of Maven software. Instead you should be sending these emails to the Maven Users list: [EMAIL PROTECTED] See more info: http://maven.apache.org/mail-lists.html Wayne On 9/4/07, Hemant Ved [EMAIL PROTECTED] wrote: was6.0 On 9/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Which version of WebSphere is this? Hermod -Original Message- From: Hemant Ved [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 04, 2007 11:07 AM To: dev@maven.apache.org Cc: [EMAIL PROTECTED] Subject: Problem with ejb deployment Hi all I am trying to deploy ejb using maven and websphere application server? Can anybody please tell me which cargo plugin is required? I know there are cargo jboss and weblogic plugins available but does anybody know whether any Cargo Maven plugin is available for websphere? Also when I run the command mvn cargo:deploy I get the below error Internal error in the plugin manager executing goal 'org.codehaus.cargo:c argo-maven2-plugin:0.3.1:deploy': Unable to find the mojo ' org.codehaus.cargo:ca rgo-maven2-plugin:0.3.1:deploy' in the plugin ' org.codehaus.cargo:cargo-maven2-p lugin' Disclaimer: ' The contents of this electronic mail message are only binding upon Equens or its affiliates, if the contents of the message are accompanied by a lawfully recognized type of signature. The contents of this electronic mail message are priviliged and confidential and are intended only for use by the addressee. If you have received this electronic mail message by error, please notify the sender and delete the message without taking notices of its content, reproducing it and using it in any way.' Equens was founded by Interpay Nederland B.V. and Transaktionsinstitut für Zahlungsverkehrsdienstleistungen AG * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that the DnB NOR Group cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the anti virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [poll] Requiring users to specify plugin versions in Maven 2.1 or later
[X] (B) Retain the current behaviour, but make using the enforcer a best practice to do the above, or some other control mechanism such as having the repository manager handle the available plugins I am thinking about the new user experience and winning more converts. As such, I think the current behavior is best. Once they get using Maven more seriously (and in corporate environments that know what they're doing), I think adding the Enforcer configuration and locking versions down will come naturally. But *requiring* it seems excessive -- unless we're doing that ourselves somewhere, with plugin packs or similar, then I feel better about it. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [poll] Need for plugin packs / mixins for plugins
[ ] (A) Having a way to include a set of plugins in one small POM [ ] (B) Pasting a snippet in from the web site is sufficient [X] (D) Undecided I personally don't mind pasting a snippet and I think this is a good idea no matter what happens -- perhaps it could be included in the release notes for each version. I can also see the use of mixins. Especially if the Maven team is the one providing the mixin, and each mixin is linked to a specific Maven release version as a set of working, integration-tested plugin versions for this release which a lot of people expect from the tool. I am concerned though that providing mixins will send us further down the path of moving more and more pieces out of the pom which is not the right move IMO. If we add plugin+version in mixin v1, then people will want plugin+version+configuration in mixin v2, and in a short period of time we'll have re-invented parent and pluginManagement in non-pom files which really makes no sense at all. Instead of all this mixin stuff (and perhaps this isn't really related), I think we need to fix the way we develop and release plugins, and perhaps this means changing the way versions are resolved etc (which we've discussed before -- should [1.1, ) include alphas and betas etc -- I say no). I don't think we should have *any* plugin at an alpha phase for more than 30 days. Same goes for beta. Instead we should create pools of unit and integration tests, verify that things aren't broken when we add new functionality, and *release* new versions of plugins. I'd be super happy if a SINGLE rfe or bug fix in a plugin results in a new version (1.1.2 to 1.1.3). Instead we have months and even years in between plugin releases, and people are using alphas and betas and even adding snapshot repos to their poms etc, resulting in less stable builds than we can and should be delivering. Stability != no new releases. Wayne On 9/2/07, Jason van Zyl [EMAIL PROTECTED] wrote: What are the real requirements? They are: 1) An easy way to get a set of stable plugins that work together 2) To easily see what versions are contained in this set 3) To easily change or augment what is in this set The current mechanism + toolings works. I know what's going to happen with plugin packs. Someone is going to want to change a version of a plugin they are using and How do I find out what versions of plugins am I using, How do I override what version of a plugin I'm using if it's specified in a plugin pack?, Does plugin management win if it's in a plugin pack?. I found a bug in the way plugin packs are processed and I can't get a plugin version I need, is there a work around?. How do I configure plugins that have been defined in the plugin pack. So people are going to have to end up redeclaring bits to get configuration and execution information locked down and then you end up with a terrible configuration management problem. A fully, and clear, literal way to define this is what is most practical. The questions below are also framed to bias the answers. For A, plugin packs are not the only solution. In very practical terms the total number of plugins is not that high. What people want to know is the stable set. The core processing required for the notion of a plugin pack will not be straight forward and it's not necessary and adds almost no value and I'm certain it will lead to greater complexity. Users want 1), 2), and 3). The current mechanism plus minimal tooling, or no tooling if people cut and paste (big deal) covers those requirements. Plugin packs cover 1) and then it becomes another nightmare to maintain. I am not in favor of plugin packs. On 1 Sep 07, at 7:53 PM 1 Sep 07, Brett Porter wrote: Like the other poll, I'd like to hear from as many people as possible their opinion this topic (even if you just want to say '0' so we know where you stand). [ ] (A) Having a way to include a set of plugins in one small POM fragment would be a useful feature to have (if you have a use case other than the already stated standard plugins, please specify) [ ] (B) Pasting a snippet in from the web site is sufficient [ ] (C) No opinion [ ] (D) Undecided [ ] (E) Other (please specify) Thanks, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To
Re: http://jira.codehaus.org/browse/MNG-3151
If this is the case, how will we file it in JIRA? Do we need a needs votes version? Or just back to 2.0.x with a comment in there? I suppose a needs votes version is as valid as any other approach. Then assuming it gets enough votes and comments, we can worry about implementing it. How many users would you want to request it before thinking the use case is valid? Its a valid question, and I won't pretend to have an answer. I don't like magic numbers. But I do feel like this is an important issue with far-reaching implications and we should expect/require more than a normal level of discussion etc. I'm fine continuing the discussion here, asking for input from users@, or even posting a survey on maven.apache.org to get other people's input on this issue. Its easy enough to do with SurveyMonkey, assuming we can find someone to write it using neutral language to avoid unintended bias. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Failing build on transitive circular dependencies
I'm ok with this so long as it would bring along a flag somewhere circular.transitivewarn/ vs break or something, with default being break, so we can still accomodate people that are using deps like dom4j and jaxen. Also, it would need to be well-documented so we can point all the users@ people to the FAQ when they ask the inevitable question several times a week/month without Googling. Even better, I'd like the error message to include a URL to the proper entry in the FAQ, after it has been documented. Wayne On 8/29/07, Brett Porter [EMAIL PROTECTED] wrote: Pretty sure dom4j/jaxen still reference each other :( - Brett On 30/08/2007, at 12:00 AM, Mark Hobson wrote: Hi there, I've just encountered the silent disabling of circular dependencies in a build whilst refactoring projects. Previously I've seen these failing the build, as expected, but it appears that transitive circular dependencies are merely logged as debug. See the comment in DefaultArtifactCollector line 355 in 2.0.x: would like to throw this, but we have crappy stuff in the repo. I think we should be at a point where the repo metadata doesn't have circular dependencies. I propose to remove this and propagate the exception to fail the build - any opinions? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: http://jira.codehaus.org/browse/MNG-3151
Does anyone else think this is a terrible idea? If we allow this then there is no going back. Yah, I'd love to hear it if anyone can pick holes in it, as I don't want to steer down any bad tracks repository wise either. I'm not a huge fan simply because I like the simplicity of everything in one place. But I'm having trouble coming up with a really huge problem with it, other than the way it smells to me in general. I can understand both perspectives on the issue. I have some small concerns around making this far-reaching decision based on the needs/request of what seems to be a single customer. I'd prefer to let this be an open issue for a while and revisit it in 6mos, allow other customers to make their own possibly similar comments/demands, and see how it feels/smells in early 2008. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
