[jira] Commented: (MAVENUPLOAD-588) please upload A2J beta2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-588?page=comments#action_52171 ] nicolas de loof commented on MAVENUPLOAD-588: - I've updated bundle and checked for valid XML > please upload A2J beta2 > --- > > Key: MAVENUPLOAD-588 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-588 > Project: maven-upload-requests > Type: Task > Reporter: nicolas de loof > > > A2J is a tool for converting ASN specifications into a collection of java > classes capable of encoding and decoding the data units defined by those > specifications. A2J also includes a set of runtime classes that support > serialising ASN types to and from BER streams. A2J is licensed under the LGPL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-599) please upload Struts-dialogs on ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-599?page=comments#action_52170 ] nicolas de loof commented on MAVENUPLOAD-599: - I've updated upload bundle to correct pom. > please upload Struts-dialogs on ibiblio > --- > > Key: MAVENUPLOAD-599 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-599 > Project: maven-upload-requests > Type: Task > Reporter: nicolas de loof > > > Struts Dialogs is a library for Struts 1.2.x framework, which improves > development process and makes applications more robust and user-friendly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-600) please upload Struts-dialogs wizard extension on ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-600?page=comments#action_52169 ] nicolas de loof commented on MAVENUPLOAD-600: - I've updated bundle and checked for valid XML > please upload Struts-dialogs wizard extension on ibiblio > > > Key: MAVENUPLOAD-600 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-600 > Project: maven-upload-requests > Type: Task > Reporter: nicolas de loof > > > Struts Dialogs is a library for Struts 1.2.x framework, which improves > development process and makes applications more robust and user-friendly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
+2 Emmanuel Fabrizio Giustina a écrit : Some time ago I started a simple plugin for m2 which converts maven 1 project.xml to pom.xml (pom conversion + few basic plugin configuration from project.properties to pom.xml). This allows an easy conversion of maven 1 projects, for users willing to migrate to m2. The initial code is available at http://jira.codehaus.org/browse/MNG-1530 I would like to add this plugin to svn + refactoring the pom converter to a separate artifact, which can be shared between the plugin and repository tools (see http://jira.codehaus.org/browse/MRM-29 ) Please vote the following: [ ] add the new plugin [ ] add a new module with the pom converter ... about the pom converter stuff (if we decide to add it) we should also decide where to put it. If outside the plugin dir, I will need a "sponsor" who can do that, since I only have access to the svn plugins area. fabrizio - 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] surefire/maven-surefire-plugin release
+1 Emmanuel Jason van Zyl a écrit : Hi, Surefire will now fork tests and I've updated the surefire plugin accordingly so I think it's time for a release. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
+3 Emmanuel Fabrizio Giustina a écrit : Hi devs I would like to start a vote for the release of a couple of m1/m2 plugins: - m2 eclipse plugin 2.0 the current released version has a list of show stopper bugs: wtp support and multiproject are broken, dependencies with system scope have a wrong path, source jars are not added also if already available in the local repository and some more... Now everything has been fixed, and only 2 bugs are still open (transitive provided scope and requirement to have an installed version of the projects in reactor builds) which IMHO are not required for a release. A lot of testcases have been added which cover most all the common directory layouts/dependency types. Based on this, I would like to bump the current version from 2.0 beta3 and release it as final 2.0! - maven1 eclipse plugin 1.10 it still has a few open issues, some of them fixed in the m2 version, but the version in svn has a lot of fixes/new features that users are awaiting for. So I would like to release a new version now before going on with development. - maven1 jira plugin 1.2 Not many changes after the previous version, just a couple of useful fixes and support for standard jira urls (without the numeric project id) Vote is open for 72 hours as usual. I'll start with a (non binding) +1 for all. [ ] m2 eclipse plugin 2.0 [ ] maven1 eclipse plugin 1.10 [ ] maven1 jira plugin 1.2 Cheers, fabrizio - 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]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/28-Nov-2005_12.32.18/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Does the eclipse plugin support ...
Hi I have 2 questions regarding the eclipse plugin (2.0-beta-3-SNAPSHOT from svn): 1. Does the eclipse plugin support source file excludes. My pom contains: maven-compiler-plugin **/*Factory.java for which I would expect in the .classpath: but I get: should I file a JIRA issue? 2. As far as I understand, the eclipse:eclipse "goal" runs as part of the generate-sources "phase". I guess it thereby pick up paths created by other plugins as additions to the compileSourceRoot. One of my plugins filters sources and does this as part of the process-sources phase. It adds a path to compileSourceRoot which is ignored by the eclipse plugin. Should one not run the eclipse goal as part of the process-resources phase (just before compile), when all paths are in order? If so, shall I file a JIRA issue? Regards Mark Donszelmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Brett Porter wrote: Jason van Zyl wrote: It's not supplanting the mailing list, it's providing a clear location for the actions taken by the project. I totally agree with the need to track stuff properly as I am generally the one chasing things up, my point was just ot give John a chance to finish what he's started. Sure, we think in different ways (which is good) and I don't track things on a daily basis whereas you generally do. I comtemplate my navel for days at a time and then step back into the list. I generally just start answering questions as I see them but I'd much rather go to MPA to get a summary. I generally don't go back and read the mailing lists when I've been in navel land. I trust the list has been dealth with. I don't want to and shouldn't have to look at the mailing list to figure out that a new repository is going to be created or whatever. How do you see this working - create an issue before sending any ideas to the list? No, no. You/John and whomever else decided that you were going to create a place for the shared plugin tools. Once that was decided it should be recorded in MPA as a plan of action. Seems like unnecessary overhead to me, but given we generally agree it probably isn't much different. I just think things take shape on the list first, then you file an issue when you've decided what you want to do. The person starting the thread follows it up. If nobody cares enough to do that, let it die. Absolutely, things happen on this list but must be captured before passing out of the current frame of reference. A group of people may be active in forming a decision and some may not. My attention span and focus doesn't lend itself toward daily dilligence, but I still want to know what's going on when I have a spot of time. I have a system for dealing with mail, and I like using the mailing list. I'm sure I'm not alone. I skip over JIRA stuff much more quickly and its a whole lot slower to operate with while in the discussion phase. I do not want to use JIRA for discussion. As long as we're just tracking and its easy, I'm all for it. Discussing thing is JIRA, I agree, is pointless. Just the capture of the decisions and plan of action after the decisions have been made. I actually don't care about looking at the discussion as I trust it's been dealt with appropriately. I just want to know that "we decided to create a module for shared plugin goop". For the purposes you are talking about, like a/c creation, it sounds great. You might also look into the (STATUS) mails that other projects get from a certain file - maybe we can easily maintain a little list in SVN that can be used for these issues if it is more convenient. Just tossing out ideas Ideally there should be many ways to push information into the system and get it out. I, for example, setup a JIRA project for me and I mail stuff into JIRA using some ruby junk. We should be able to extract stuff from JIRA/Confluence and create reports, or take stuff from SVN and push things into JIRA/Confluence. My current pet project is the board report. For most of the things I've always reported on I think I can automated: new commiters, new projects, releases. Being the lazy ass I am I'm positive I can find a way to do this while i'm sitting on the beach staring at my navel. And when I come back from the beach look at MPA and see everything interesting that has happened. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org We all have problems. How we deal with them is a measure of our worth. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/27-Nov-2005_11.42.01/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Jason van Zyl wrote: > It's not supplanting the mailing list, it's providing a clear location > for the actions taken by the project. I totally agree with the need to track stuff properly as I am generally the one chasing things up, my point was just ot give John a chance to finish what he's started. How do you see this working - create an issue before sending any ideas to the list? Seems like unnecessary overhead to me, but given we generally agree it probably isn't much different. I just think things take shape on the list first, then you file an issue when you've decided what you want to do. The person starting the thread follows it up. If nobody cares enough to do that, let it die. I have a system for dealing with mail, and I like using the mailing list. I'm sure I'm not alone. I skip over JIRA stuff much more quickly and its a whole lot slower to operate with while in the discussion phase. I do not want to use JIRA for discussion. As long as we're just tracking and its easy, I'm all for it. For the purposes you are talking about, like a/c creation, it sounds great. You might also look into the (STATUS) mails that other projects get from a certain file - maybe we can easily maintain a little list in SVN that can be used for these issues if it is more convenient. Just tossing out ideas - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Brett Porter wrote: Jason van Zyl wrote: Brett Porter wrote: No, its for plugin shared library space: see <[EMAIL PROTECTED]> Can you guys please put stuff that is planned for the project in MPA. The vote was only on the 22nd. We can't have other tools supplant the mailing list as far fewer people follow it. Now that we've all discussed it, the action items should go in there, sure. It's not supplanting the mailing list, it's providing a clear location for the actions taken by the project. Trying to sift though the mailing list is tedious and discussions can always occur on the mailing lists but someone needs to capture the discussion. The mailing list does nothing to capture the salient points of a conversation. It's not the overriding of the mailing list for the conversion, I'm just saying distill the conversation and push it into JIRA. N people should not have to sift though the mailing list to figure out what's going on with the project at a given point in time whether that be people internal or external to the project. They should go to MPA (or the equivalent) and see it clearly. And MPA should be pointed at when we're discussing things like creating new repositories or any infrastructural change. Why I see this as important as it provides some audit trail for the project. There is no way you're going to be able to pick off all these salient points from the mailing list once they have passed out of the current frame of reference. Absolutely no chance. What I want to use if for is to provide key points in the report to the board. If the information is captured at the point of discussion it will work. If I happen to not follow the mailing list for a week I should still be able to see what's currently slated for the project, and that should be visible over a span of time. Not only important for us but for interested parties like the board or people stepping into the project looking at what's going on. As a matter of practice in the hopes of providing more visibility I would like to see the salient points of these types of discussions go into MPA. I've been trying to track new commiters, and infrastructural changes and hope to be able to point the board at the issues. I would actually like to setup JIRA (or Foo issue tracker) and Confluence (or Bar wiki) in a standard way (a la Maven) so that I can extract this information for a report to the board and, possibly the community in general actually. The information passes by all of us so lets try to capture it and make it accessible. The mailing list is not accessible as it requires the duplication of human effort to find everything all over again. If someone else is running with something I don't want to have to track them in order to know what's going on, but it would be nice to see that somewhere. Everyone is going to have some interest in something and naturally be more involved in some issue or another and that's great. But if I or anyone else is not watching and the information isn't captured sifting through mailing lists isn't efficient, appealing or useful. No, I created a converter component in /components/trunk like I said I was going to (And had planned to last week but got side tracked). Well, I don't realy know any more. I've been working off the assumption anything not bundled in Maven goes there, but again this is pretty closely tied to the maven-model release so maybe its better off staying in /components. Right, this is why I think recording things like this in MPA is important as I have no idea what's what at the moment insofar as new project setup. We capture everything else in JIRA. I think our process is just as important to capture. Mailing lists just aren't enough by themselves. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-612) ASM 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-612?page=comments#action_52161 ] Eugene Kuleshov commented on MAVENUPLOAD-612: - Good point. Though in most of the cases it may not be a good idea to have asm.jar added transiently because it is a primary package... Anyways, I'll fix that for the next releases. Thanks for pointing it out. > ASM 2.2 > --- > > Key: MAVENUPLOAD-612 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-612 > Project: maven-upload-requests > Type: Task > Reporter: Eugene Kuleshov > Assignee: Carlos Sanchez > Attachments: asm-2.2-bundle.zip > > > http://www.md.pp.ru/~eu/11/asm-2.2-bundle.zip > http://asm.objectweb.org/ > http://asm.objectweb.org/team.html > ASM is a Java bytecode manipulation framework. It can be used to dynamically > generate stub classes or other proxy classes, directly in binary form, or to > dynamically modify classes at load time, i.e., just before they are loaded > into the Java Virtual Machine. > PS: it seems that upload guide needs to be updated to reflect custom JIRA > fields.. > PPS: here is request from Groovy developers for this ASM revision uploaded on > Ibiblio > Original Message > Subject: [asm] ASM 2.2 release > Date: Sat, 26 Nov 2005 18:19:37 + > From: Russel Winder <[EMAIL PROTECTED]> > To: ASM List <[EMAIL PROTECTED]> > CC: Guillaume Laforge <[EMAIL PROTECTED]> > Hi, > I was trying to upgrade Groovy to use ASM v2.2 but the jar files do not > yet seem to have been entered into the Maven repository. Does this mean > we should stay with v2.1? > Thanks. > Russel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-9) migrate converter to repository manager
[ http://jira.codehaus.org/browse/MRM-9?page=all ] Brett Porter updated MRM-9: --- Remaining Estimate: 2 hours Original Estimate: 2 hours Environment: Summary: migrate converter to repository manager (was: rename repoclean) > migrate converter to repository manager > --- > > Key: MRM-9 > URL: http://jira.codehaus.org/browse/MRM-9 > Project: Maven Repository Manager > Type: Task > Components: repository-converter > Reporter: Brett Porter > Assignee: Brett Porter > Fix For: 1.0-alpha-1 > > Original Estimate: 2 hours > Remaining: 2 hours > > 'nuff said! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Mon Nov 28 03:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051128.033001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.033001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Mon Nov 28 03:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051128.03.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.03.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Jason van Zyl wrote: > Brett Porter wrote: > >> No, its for plugin shared library space: see >> <[EMAIL PROTECTED]> > > Can you guys please put stuff that is planned for the project in MPA. > The vote was only on the 22nd. We can't have other tools supplant the mailing list as far fewer people follow it. Now that we've all discussed it, the action items should go in there, sure. > And what Fabrizio wants to work on falls into this pot? > As far as I understand, he wants to work on the plugin which is completely separate. If modifications are needed to the converter, then yes. >> I'm already done. > > You've setup the shared plugin shared library space? No, I created a converter component in /components/trunk like I said I was going to (And had planned to last week but got side tracked). > >> I'd rather not circumvent John's handling of the vote, >> and it would be good if that was eventually added there. It's over 72 >> hours, but we're probably just waiting for him to arise from Turkey coma. > > All right but what about tools in general what may or may not be used in > plugins. The conversion tool for example is something that would > definitely be used in/outside the context of a plugin. Well, I don't realy know any more. I've been working off the assumption anything not bundled in Maven goes there, but again this is pretty closely tied to the maven-model release so maybe its better off staying in /components. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Mon Nov 28 02:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.024500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Mon Nov 28 02:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20051128.023000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051128.023000.txt
[jira] Commented: (MAVENUPLOAD-612) ASM 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-612?page=comments#action_52158 ] Carlos Sanchez commented on MAVENUPLOAD-612: Well, I imagine that the subprojects like asm-utils depend on asm. Without dependency info i'll have to declare both, with it one is enough > ASM 2.2 > --- > > Key: MAVENUPLOAD-612 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-612 > Project: maven-upload-requests > Type: Task > Reporter: Eugene Kuleshov > Assignee: Carlos Sanchez > Attachments: asm-2.2-bundle.zip > > > http://www.md.pp.ru/~eu/11/asm-2.2-bundle.zip > http://asm.objectweb.org/ > http://asm.objectweb.org/team.html > ASM is a Java bytecode manipulation framework. It can be used to dynamically > generate stub classes or other proxy classes, directly in binary form, or to > dynamically modify classes at load time, i.e., just before they are loaded > into the Java Virtual Machine. > PS: it seems that upload guide needs to be updated to reflect custom JIRA > fields.. > PPS: here is request from Groovy developers for this ASM revision uploaded on > Ibiblio > Original Message > Subject: [asm] ASM 2.2 release > Date: Sat, 26 Nov 2005 18:19:37 + > From: Russel Winder <[EMAIL PROTECTED]> > To: ASM List <[EMAIL PROTECTED]> > CC: Guillaume Laforge <[EMAIL PROTECTED]> > Hi, > I was trying to upgrade Groovy to use ASM v2.2 but the jar files do not > yet seem to have been entered into the Maven repository. Does this mean > we should stay with v2.1? > Thanks. > Russel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Mon Nov 28 02:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.023000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-612) ASM 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-612?page=comments#action_52157 ] Eugene Kuleshov commented on MAVENUPLOAD-612: - Thans Carls. Actually there is no runtime dependencies. > ASM 2.2 > --- > > Key: MAVENUPLOAD-612 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-612 > Project: maven-upload-requests > Type: Task > Reporter: Eugene Kuleshov > Assignee: Carlos Sanchez > Attachments: asm-2.2-bundle.zip > > > http://www.md.pp.ru/~eu/11/asm-2.2-bundle.zip > http://asm.objectweb.org/ > http://asm.objectweb.org/team.html > ASM is a Java bytecode manipulation framework. It can be used to dynamically > generate stub classes or other proxy classes, directly in binary form, or to > dynamically modify classes at load time, i.e., just before they are loaded > into the Java Virtual Machine. > PS: it seems that upload guide needs to be updated to reflect custom JIRA > fields.. > PPS: here is request from Groovy developers for this ASM revision uploaded on > Ibiblio > Original Message > Subject: [asm] ASM 2.2 release > Date: Sat, 26 Nov 2005 18:19:37 + > From: Russel Winder <[EMAIL PROTECTED]> > To: ASM List <[EMAIL PROTECTED]> > CC: Guillaume Laforge <[EMAIL PROTECTED]> > Hi, > I was trying to upgrade Groovy to use ASM v2.2 but the jar files do not > yet seem to have been entered into the Maven repository. Does this mean > we should stay with v2.1? > Thanks. > Russel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Mon Nov 28 02:15:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.021501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Mon Nov 28 02:00:01 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051128.020001.txt
Re: [vote] new plugin (maven1 plugin for m2)
Brett Porter wrote: No, its for plugin shared library space: see <[EMAIL PROTECTED]> Can you guys please put stuff that is planned for the project in MPA. And what Fabrizio wants to work on falls into this pot? I'm already done. You've setup the shared plugin shared library space? I'd rather not circumvent John's handling of the vote, and it would be good if that was eventually added there. It's over 72 hours, but we're probably just waiting for him to arise from Turkey coma. All right but what about tools in general what may or may not be used in plugins. The conversion tool for example is something that would definitely be used in/outside the context of a plugin. Once there, I imagine all plugin devs will have access to it. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Mon Nov 28 02:00:01 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.020001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-563) Add htmlparser
[ http://jira.codehaus.org/browse/MAVENUPLOAD-563?page=all ] Carlos Sanchez closed MAVENUPLOAD-563: -- Resolution: Incomplete > Add htmlparser > -- > > Key: MAVENUPLOAD-563 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-563 > Project: maven-upload-requests > Type: Task > Reporter: siegfried heintze > Assignee: Carlos Sanchez > Attachments: htmlparser-1.6.jar, htmlparser-1.6.jar, htmlparser-1.6.jar > > > I would like to use the parser at http://htmlparser.sourceforge.net . > I've put the bundle on my personal web site > http://www.heintze.com/maven/htmlparser-1.6.jar . > This is my first try at using maven 1.0.1. > Please up load this so I can use htmlparser. > Thanks, > Siegfried -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-570) statx-utils
[ http://jira.codehaus.org/browse/MAVENUPLOAD-570?page=all ] Carlos Sanchez closed MAVENUPLOAD-570: -- Assign To: Carlos Sanchez Resolution: Incomplete > statx-utils > --- > > Key: MAVENUPLOAD-570 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-570 > Project: maven-upload-requests > Type: Task > Reporter: Matthew Pocock > Assignee: Carlos Sanchez > > > A bundle of stax-utils taken from > https://stax-utils.dev.java.net/files/documents/1519/11894/stax-utils-20050302.tar.gz -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Mon Nov 28 01:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.014500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-559) Mustang b56 jnlp-servlet library
[ http://jira.codehaus.org/browse/MAVENUPLOAD-559?page=all ] Carlos Sanchez closed MAVENUPLOAD-559: -- Resolution: Incomplete > Mustang b56 jnlp-servlet library > > > Key: MAVENUPLOAD-559 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-559 > Project: maven-upload-requests > Type: Task > Reporter: Jerome Lacoste > Assignee: Carlos Sanchez > Attachments: jnlp-servlet-1.0-6.0-b56.jar, jnlp-servlet-1.0-6.0-b56.jar > > > http://coffeebreaks.org/software/misc/jnlp-servlet-1.0-6.0-b56.jar > http://mustang.dev.java.net/ for the original code. > See also > http://www.java.net/download/jdk6/jdk-6_0-ea-src-b56-jrl-13_oct_2005.jar > JNLP Servlet is part of Mustang under the BSD license. It automates the use > of pack200 which achieces great compression for webstart applications. > It will be used by users of the Webstart Plugin: > http://docs.codehaus.org/display/MOJO/Webstart+Plugin > It doesn't automate the clipping of nose hairs. Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Jason van Zyl wrote: > Brett Porter wrote: > >>> We need all the help we can with the conversion stuff. Sounds good. >> >> >> I actually had this on my list already. Doing it now. Doesn't need a >> vote, I think. > > Sorry, I think I missed something. Setting up a maven-repository-tools > directory structure for tools like this conversion tool? No, its for plugin shared library space: see <[EMAIL PROTECTED]> > >> I think it should be part of the tools stuff we discussed. Since it >> isn't set up yet, I'll keep it in components. > > If this is for tools, I can setup the directory structure, SVN and the > like very shortly. Why don't we set this up and just give Fabrizio > access? I can register the pertinent issues here: > http://jira.codehaus.org/browse/MPA. > I'm already done. I'd rather not circumvent John's handling of the vote, and it would be good if that was eventually added there. It's over 72 hours, but we're probably just waiting for him to arise from Turkey coma. Once there, I imagine all plugin devs will have access to it. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-560) pack200 ant tasks
[ http://jira.codehaus.org/browse/MAVENUPLOAD-560?page=all ] Carlos Sanchez closed MAVENUPLOAD-560: -- Resolution: Incomplete > pack200 ant tasks > - > > Key: MAVENUPLOAD-560 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-560 > Project: maven-upload-requests > Type: Task > Reporter: Jerome Lacoste > Assignee: Carlos Sanchez > Attachments: pack200-1.0.jar > > > http://coffeebreaks.org/software/misc/pack200-1.0.jar > http://java-pack200-ant-task.dev.java.net/ > Original source/binary bundle is at: > https://java-pack200-ant-task.dev.java.net/files/documents/1526/6272/ant-task.zip > Ant tasks for performing pack200 operations. Used by the upcoming webstart > plugin (http://docs.codehaus.org/display/MOJO/Webstart+Plugin) > Please upload! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-558) Berkeley db java edition 2.0.83
[ http://jira.codehaus.org/browse/MAVENUPLOAD-558?page=all ] Carlos Sanchez closed MAVENUPLOAD-558: -- Resolution: Fixed > Berkeley db java edition 2.0.83 > --- > > Key: MAVENUPLOAD-558 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-558 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > Assignee: Carlos Sanchez > > > Note that the bundle jar also contains sources: > Carlos, is there any way to have sources artifacts uploaded as well? I can > help on ehancing the script/tool used for the automatic upload if you give me > some pointers on where I can find it on svn. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-552) loga script bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-552?page=all ] Carlos Sanchez closed MAVENUPLOAD-552: -- Assign To: Carlos Sanchez Resolution: Incomplete > loga script bundle > -- > > Key: MAVENUPLOAD-552 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-552 > Project: maven-upload-requests > Type: Task > Reporter: Marouane ALBAIRAT > Assignee: Carlos Sanchez > Attachments: loga-1.2-bundle.jar > > > loga is a tiny script interpreter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-610) Upload XWork-Spring Integration to central Maven Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-610?page=all ] Carlos Sanchez closed MAVENUPLOAD-610: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload XWork-Spring Integration to central Maven Repository > --- > > Key: MAVENUPLOAD-610 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-610 > Project: maven-upload-requests > Type: Task > Reporter: Matt Raible > Assignee: Carlos Sanchez > > > Please upload xwork-spring integration bundle for integration WebWork and > Spring in WebWork 2.x. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-609) maven taglib plugin 1.4.2 for maven 1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-609?page=all ] Carlos Sanchez closed MAVENUPLOAD-609: -- Assign To: Carlos Sanchez Resolution: Fixed > maven taglib plugin 1.4.2 for maven 1 > - > > Key: MAVENUPLOAD-609 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-609 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > Assignee: Carlos Sanchez > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-612) ASM 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-612?page=all ] Carlos Sanchez closed MAVENUPLOAD-612: -- Assign To: Carlos Sanchez Resolution: Fixed I've uploaded them by hand becuase this doesn't follow the rules for upload bundles. Also dependencies sections are empty, meaning that it won't work with transitive dependencies correctly under maven2 > ASM 2.2 > --- > > Key: MAVENUPLOAD-612 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-612 > Project: maven-upload-requests > Type: Task > Reporter: Eugene Kuleshov > Assignee: Carlos Sanchez > Attachments: asm-2.2-bundle.zip > > > http://www.md.pp.ru/~eu/11/asm-2.2-bundle.zip > http://asm.objectweb.org/ > http://asm.objectweb.org/team.html > ASM is a Java bytecode manipulation framework. It can be used to dynamically > generate stub classes or other proxy classes, directly in binary form, or to > dynamically modify classes at load time, i.e., just before they are loaded > into the Java Virtual Machine. > PS: it seems that upload guide needs to be updated to reflect custom JIRA > fields.. > PPS: here is request from Groovy developers for this ASM revision uploaded on > Ibiblio > Original Message > Subject: [asm] ASM 2.2 release > Date: Sat, 26 Nov 2005 18:19:37 + > From: Russel Winder <[EMAIL PROTECTED]> > To: ASM List <[EMAIL PROTECTED]> > CC: Guillaume Laforge <[EMAIL PROTECTED]> > Hi, > I was trying to upgrade Groovy to use ASM v2.2 but the jar files do not > yet seem to have been entered into the Maven repository. Does this mean > we should stay with v2.1? > Thanks. > Russel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-611) Upload Asterisk-Java 0.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-611?page=all ] Carlos Sanchez closed MAVENUPLOAD-611: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload Asterisk-Java 0.2 > > > Key: MAVENUPLOAD-611 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-611 > Project: maven-upload-requests > Type: Task > Reporter: Stefan Reuter > Assignee: Carlos Sanchez > > > http://www.asteriskjava.org/ > http://www.asteriskjava.org/latest/team-list.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-29) Factorize pom conversion out of repoclean
[ http://jira.codehaus.org/browse/MRM-29?page=all ] Brett Porter closed MRM-29: --- Resolution: Fixed > Factorize pom conversion out of repoclean > - > > Key: MRM-29 > URL: http://jira.codehaus.org/browse/MRM-29 > Project: Maven Repository Manager > Type: Improvement > Components: repository-converter > Versions: 1.0 > Reporter: Carlos Sanchez > Assignee: Brett Porter > Fix For: 1.0 > > Original Estimate: 30 minutes >Time Spent: 30 minutes > Remaining: 0 minutes > > Take the conversion classes and move them to a separate project or maven > model so they can be reused in other places, eg. a m1->m2 plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-29) Factorize pom conversion out of repoclean
[ http://jira.codehaus.org/browse/MRM-29?page=all ] Brett Porter updated MRM-29: Remaining Estimate: 30 minutes Original Estimate: 30 minutes > Factorize pom conversion out of repoclean > - > > Key: MRM-29 > URL: http://jira.codehaus.org/browse/MRM-29 > Project: Maven Repository Manager > Type: Improvement > Components: repository-converter > Versions: 1.0 > Reporter: Carlos Sanchez > Assignee: Brett Porter > Fix For: 1.0 > > Original Estimate: 30 minutes > Remaining: 30 minutes > > Take the conversion classes and move them to a separate project or maven > model so they can be reused in other places, eg. a m1->m2 plugin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/27-Nov-2005_08.31.49/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPA-28) Process Dan Tran
[ http://jira.codehaus.org/browse/MPA-28?page=comments#action_52150 ] Jason van Zyl commented on MPA-28: -- Dan, how are you making out with the CLA and CCLA? > Process Dan Tran > > > Key: MPA-28 > URL: http://jira.codehaus.org/browse/MPA-28 > Project: Maven Project Administration > Type: Task > Components: new-commiters > Reporter: Jason van Zyl > Assignee: Jason van Zyl > > > Voted in as a committer for Maven SCM and Maven Plugins. Not sure where we > are in the process other then the completion of the vote. I will follow up > with Dan in IRC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Brett Porter wrote: We need all the help we can with the conversion stuff. Sounds good. I actually had this on my list already. Doing it now. Doesn't need a vote, I think. Sorry, I think I missed something. Setting up a maven-repository-tools directory structure for tools like this conversion tool? I think it should be part of the tools stuff we discussed. Since it isn't set up yet, I'll keep it in components. If this is for tools, I can setup the directory structure, SVN and the like very shortly. Why don't we set this up and just give Fabrizio access? I can register the pertinent issues here: http://jira.codehaus.org/browse/MPA. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - checkout] Mon Nov 28 00:15:01 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20051128.001502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20051128.001502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
+1 for all On 11/27/05, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: > Hi devs > I would like to start a vote for the release of a couple of m1/m2 plugins: > > - m2 eclipse plugin 2.0 > the current released version has a list of show stopper bugs: wtp > support and multiproject are broken, dependencies with system scope > have a wrong path, source jars are not added also if already available > in the local repository and some more... > Now everything has been fixed, and only 2 bugs are still open > (transitive provided scope and requirement to have an installed > version of the projects in reactor builds) which IMHO are not required > for a release. A lot of testcases have been added which cover most all > the common directory layouts/dependency types. > Based on this, I would like to bump the current version from 2.0 > beta3 and release it as final 2.0! > > - maven1 eclipse plugin 1.10 > it still has a few open issues, some of them fixed in the m2 version, > but the version in svn has a lot of fixes/new features that users are > awaiting for. So I would like to release a new version now before > going on with development. > > - maven1 jira plugin 1.2 > Not many changes after the previous version, just a couple of useful > fixes and support for standard jira urls (without the numeric project > id) > > > Vote is open for 72 hours as usual. I'll start with a (non binding) +1 for > all. > > [ ] m2 eclipse plugin 2.0 > [ ] maven1 eclipse plugin 1.10 > [ ] maven1 jira plugin 1.2 > > > Cheers, > fabrizio > > - > 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] plugin releases
ditto Jason's feedback on the open issues, +1 * 3 otherwise. is v1.10 going to be problematic with any hokey version comparisons? - Brett Jason van Zyl wrote: > Fabrizio Giustina wrote: >> Hi devs >> I would like to start a vote for the release of a couple of m1/m2 >> plugins: >> >> - m2 eclipse plugin 2.0 >> the current released version has a list of show stopper bugs: wtp >> support and multiproject are broken, dependencies with system scope >> have a wrong path, source jars are not added also if already available >> in the local repository and some more... >> Now everything has been fixed, and only 2 bugs are still open >> (transitive provided scope and requirement to have an installed >> version of the projects in reactor builds) which IMHO are not required >> for a release. A lot of testcases have been added which cover most all >> the common directory layouts/dependency types. >> Based on this, I would like to bump the current version from 2.0 >> beta3 and release it as final 2.0! > > If none of those are critical then +1 > > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10500&sorter/order=DESC&sorter/field=priority&resolution=-1&component=11797 > > >> - maven1 eclipse plugin 1.10 >> it still has a few open issues, some of them fixed in the m2 version, >> but the version in svn has a lot of fixes/new features that users are >> awaiting for. So I would like to release a new version now before >> going on with development. > > +1 > >> - maven1 jira plugin 1.2 >> Not many changes after the previous version, just a couple of useful >> fixes and support for standard jira urls (without the numeric project >> id) > > +1 > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Brett Porter wrote: > Jason van Zyl wrote: >> Fabrizio Giustina wrote: >>> Some time ago I started a simple plugin for m2 which converts maven 1 >>> project.xml to pom.xml (pom conversion + few basic plugin >>> configuration from project.properties to pom.xml). This allows an easy >>> conversion of maven 1 projects, for users willing to migrate to m2. >>> The initial code is available at http://jira.codehaus.org/browse/MNG-1530 >>> >>> I would like to add this plugin to svn + refactoring the pom converter >>> to a separate artifact, which can be shared between the plugin and >>> repository tools (see http://jira.codehaus.org/browse/MRM-29 ) >>> >>> Please vote the following: >>> [ ] add the new plugin >> +1 > > +1 (to add it to the sandbox doesn't require a vote, but I'm happy for > this to go straight to /plugins/trunk). One more thing... maybe this should be incorporated into the maven-one-plugin in the sandbox? After that, it can be moved over and a vote for a release, I think. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Jason van Zyl wrote: > Fabrizio Giustina wrote: >> Some time ago I started a simple plugin for m2 which converts maven 1 >> project.xml to pom.xml (pom conversion + few basic plugin >> configuration from project.properties to pom.xml). This allows an easy >> conversion of maven 1 projects, for users willing to migrate to m2. >> The initial code is available at http://jira.codehaus.org/browse/MNG-1530 >> >> I would like to add this plugin to svn + refactoring the pom converter >> to a separate artifact, which can be shared between the plugin and >> repository tools (see http://jira.codehaus.org/browse/MRM-29 ) >> >> Please vote the following: >> [ ] add the new plugin > > +1 +1 (to add it to the sandbox doesn't require a vote, but I'm happy for this to go straight to /plugins/trunk). > >> [ ] add a new module with the pom converter > > +1 > > We need all the help we can with the conversion stuff. Sounds good. I actually had this on my list already. Doing it now. Doesn't need a vote, I think. On that token, please don't upload anything directly to java-repository. I have no idea where that code came from - I can only assume from maven-model-2.0-all and trimmed? Where did the pom come from? Officially, only PMC members can endorse a release through their votes when the entire community brings it up. It's not something we can "just do" as that hits the mirrors. Since this is a derivative of an existing voted on release, I think it is ok - but discussing on this list in future would be a better idea. If you don't get a response, be persistent - most likely someone has flagged it and not got around to it :) > >> ... about the pom converter stuff (if we decide to add it) we should >> also decide where to put it. If outside the plugin dir, I will need a >> "sponsor" who can do that, since I only have access to the svn plugins >> area. I think it should be part of the tools stuff we discussed. Since it isn't set up yet, I'll keep it in components. > > It would be nice if you made it a tool that would be used inside a mojo. > As most of our tools are plexus components I think doing the same would > make sense. Plexus components are easy to reuse inside Mojos and are > also resuable in other tools which are usually Plexus-based in our case. > > We might want to start collecting our repo management code here: > > http://svn.apache.org/viewcvs.cgi/maven/repository-manager/ This isn't repo management, so I'll keep it in components. > > And move the maven-repository-tools in there as well. Yep, eventually. > > If you have time and code to contribute I would be +1 for giving you > access the the repository-manager module. Likewise. I'll be starting some discussion soon. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] surefire/maven-surefire-plugin release
Hi, Surefire will now fork tests and I've updated the surefire plugin accordingly so I think it's time for a release. +1 -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-23) Don't create empty m2 poms when there's no m1 pom
[ http://jira.codehaus.org/browse/MRM-23?page=all ] Brett Porter closed MRM-23: --- Resolution: Won't Fix Fix Version: (was: 1.0) m2 doesn't deal with artifacts without poms very nicely right now. We can use the status instead. > Don't create empty m2 poms when there's no m1 pom > - > > Key: MRM-23 > URL: http://jira.codehaus.org/browse/MRM-23 > Project: Maven Repository Manager > Type: Improvement > Components: repository-converter > Reporter: Carlos Sanchez > Assignee: Brett Porter > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1693) .wtpmodules does not use same output directory as compiler
[ http://jira.codehaus.org/browse/MNG-1693?page=all ] fabrizio giustina closed MNG-1693: -- Assign To: fabrizio giustina Resolution: Fixed fixed in svn for 2.0b3 > .wtpmodules does not use same output directory as compiler > -- > > Key: MNG-1693 > URL: http://jira.codehaus.org/browse/MNG-1693 > Project: Maven 2 > Type: Bug > Components: maven-eclipse-plugin > Versions: 2.0.1 > Reporter: Barry Kaplan > Assignee: fabrizio giustina > > > When the output path is overriden via the outputDirectory configuration > property, the 'java-output-path' property in .wtpmodules does not use this > value. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-58) resources get incorrect path when maven run from parent directory
[ http://jira.codehaus.org/browse/MPECLIPSE-58?page=all ] fabrizio giustina closed MPECLIPSE-58: -- Assign To: fabrizio giustina Resolution: Cannot Reproduce Fix Version: 1.10 Closing as cannot reproduce, according to the last comment > resources get incorrect path when maven run from parent directory > - > > Key: MPECLIPSE-58 > URL: http://jira.codehaus.org/browse/MPECLIPSE-58 > Project: maven-eclipse-plugin > Type: Bug > Versions: 1.9 > Reporter: Barry Kaplan > Assignee: fabrizio giustina > Fix For: 1.10 > Attachments: MPECLIPSE-58_patch1.txt > > > When building the eclipse projects via the multiproject plugin, and running > the target from the parent project (ie, generating all eclipse projects in > one go) the directories defined by the maven sub-projects are > imported incorrectly -- they are given the path of the parent not the > sub-project in which they are defined. > If the eclipse is then generated directly from within the sub-project, the > resources will be correc in .classpath. > For a concrete example/test-case try to build the eclipse projects for > activemq. The activemq core module contains a resource for 'src/conf', which > will get a directory as I described above. > (hmmm, is this clear?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] new plugin (maven1 plugin for m2)
+2 Arnaud > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de > Fabrizio Giustina > Envoyé : dimanche 27 novembre 2005 22:35 > À : Maven Developers List > Objet : [vote] new plugin (maven1 plugin for m2) > > Some time ago I started a simple plugin for m2 which converts > maven 1 project.xml to pom.xml (pom conversion + few basic > plugin configuration from project.properties to pom.xml). > This allows an easy conversion of maven 1 projects, for users > willing to migrate to m2. > The initial code is available at > http://jira.codehaus.org/browse/MNG-1530 > > I would like to add this plugin to svn + refactoring the pom > converter to a separate artifact, which can be shared between > the plugin and repository tools (see > http://jira.codehaus.org/browse/MRM-29 ) > > Please vote the following: > [ ] add the new plugin > [ ] add a new module with the pom converter > > ... about the pom converter stuff (if we decide to add it) we > should also decide where to put it. If outside the plugin > dir, I will need a "sponsor" who can do that, since I only > have access to the svn plugins area. > > fabrizio > > - > 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]
[jira] Closed: (MPECLIPSE-59) Skipped dependency with eclipse.dependency false
[ http://jira.codehaus.org/browse/MPECLIPSE-59?page=all ] fabrizio giustina closed MPECLIPSE-59: -- Assign To: fabrizio giustina Resolution: Won't Fix Fix Version: 1.10 I can't see any valid use case why the eclipse project should not contain dependencies needed when building using maven. Closing as a won't fix, please reopen the bug if you think this could be needed and post a valid use case. > Skipped dependency with eclipse.dependency false > - > > Key: MPECLIPSE-59 > URL: http://jira.codehaus.org/browse/MPECLIPSE-59 > Project: maven-eclipse-plugin > Type: Bug > Environment: Java 1.4.2_04, win2k > Reporter: Henri Bonnehuit > Assignee: fabrizio giustina > Priority: Minor > Fix For: 1.10 > > > A dependency element like: > true > in project.xml causes maven eclipse to skip the dependency completely, > rather than reverting to simple .classpath entry. > I have maven-eclipse-plugin-1.9.jar and maven v. 1.0.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] plugin releases
> > > Vote is open for 72 hours as usual. I'll start with a (non > binding) +1 for all. > > [ +1] m2 eclipse plugin 2.0 > [ +1] maven1 eclipse plugin 1.10 > [ +1] maven1 jira plugin 1.2 Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-227) struts 1.2.4 and 1.2.8 dependencies still broken
[ http://jira.codehaus.org/browse/MEV-227?page=comments#action_52144 ] Wendy Smoak commented on MEV-227: - The 1.2.8 pom is in now the Apache repo: http://www.apache.org/dist/java-repository/struts/poms/ Please re-generate the m2 pom and let's see what we get. > struts 1.2.4 and 1.2.8 dependencies still broken > > > Key: MEV-227 > URL: http://jira.codehaus.org/browse/MEV-227 > Project: Maven Evangelism > Type: Sub-task > Reporter: denis Cabasson > Assignee: Carlos Sanchez > > > Looks like the dependencies are still broken -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-64) Add ability to specify eclipse.dependency in property files
[ http://jira.codehaus.org/browse/MPECLIPSE-64?page=all ] fabrizio giustina closed MPECLIPSE-64: -- Assign To: fabrizio giustina Resolution: Won't Fix Fix Version: 1.10 Closing as won't fix, for the reasons explained by Eric months ago. > Add ability to specify eclipse.dependency in property files > --- > > Key: MPECLIPSE-64 > URL: http://jira.codehaus.org/browse/MPECLIPSE-64 > Project: maven-eclipse-plugin > Type: Improvement > Reporter: Jason Madden > Assignee: fabrizio giustina > Fix For: 1.10 > Attachments: check-local.diff > > > It would be nice if the "eclipse.dependency" property could be specified in > property files in addition to in the project.xml. This would allow some > developers to have certain dependencies reference eclipse projects that not > all developers have, by including the appropriate entries in their local > build.properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-612) ASM 2.2
ASM 2.2 --- Key: MAVENUPLOAD-612 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-612 Project: maven-upload-requests Type: Task Reporter: Eugene Kuleshov Attachments: asm-2.2-bundle.zip http://www.md.pp.ru/~eu/11/asm-2.2-bundle.zip http://asm.objectweb.org/ http://asm.objectweb.org/team.html ASM is a Java bytecode manipulation framework. It can be used to dynamically generate stub classes or other proxy classes, directly in binary form, or to dynamically modify classes at load time, i.e., just before they are loaded into the Java Virtual Machine. PS: it seems that upload guide needs to be updated to reflect custom JIRA fields.. PPS: here is request from Groovy developers for this ASM revision uploaded on Ibiblio Original Message Subject:[asm] ASM 2.2 release Date: Sat, 26 Nov 2005 18:19:37 + From: Russel Winder <[EMAIL PROTECTED]> To: ASM List <[EMAIL PROTECTED]> CC: Guillaume Laforge <[EMAIL PROTECTED]> Hi, I was trying to upgrade Groovy to use ASM v2.2 but the jar files do not yet seem to have been entered into the Maven repository. Does this mean we should stay with v2.1? Thanks. Russel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-62) maven.eclipse.conclasspath is ignored when junit test src is not present
[ http://jira.codehaus.org/browse/MPECLIPSE-62?page=all ]
fabrizio giustina closed MPECLIPSE-62:
--
Assign To: fabrizio giustina (was: David Eric Pugh)
Resolution: Fixed
Fix Version: 1.10
fixed in svn
> maven.eclipse.conclasspath is ignored when junit test src is not present
> -
>
> Key: MPECLIPSE-62
> URL: http://jira.codehaus.org/browse/MPECLIPSE-62
> Project: maven-eclipse-plugin
> Type: Bug
> Versions: 1.9
> Environment: XP, jdk 1.4.2
> Reporter: Dan Tran
> Assignee: fabrizio giustina
> Fix For: 1.10
>
>
> Tracing thru the jelly code and tested it myself, maven-eclipse-plugin
> completely ignore the processing of maven.eclipse.conclasspath when the
> ${unitTestSourcesPresent} is not true.
> the code is in src/plugin-resources/templates/classpath.jelly
> is it a bug?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] plugin releases
Fabrizio Giustina wrote: Hi devs I would like to start a vote for the release of a couple of m1/m2 plugins: - m2 eclipse plugin 2.0 the current released version has a list of show stopper bugs: wtp support and multiproject are broken, dependencies with system scope have a wrong path, source jars are not added also if already available in the local repository and some more... Now everything has been fixed, and only 2 bugs are still open (transitive provided scope and requirement to have an installed version of the projects in reactor builds) which IMHO are not required for a release. A lot of testcases have been added which cover most all the common directory layouts/dependency types. Based on this, I would like to bump the current version from 2.0 beta3 and release it as final 2.0! If none of those are critical then +1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10500&sorter/order=DESC&sorter/field=priority&resolution=-1&component=11797 - maven1 eclipse plugin 1.10 it still has a few open issues, some of them fixed in the m2 version, but the version in svn has a lot of fixes/new features that users are awaiting for. So I would like to release a new version now before going on with development. +1 - maven1 jira plugin 1.2 Not many changes after the previous version, just a couple of useful fixes and support for standard jira urls (without the numeric project id) +1 -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] new plugin (maven1 plugin for m2)
Fabrizio Giustina wrote: Some time ago I started a simple plugin for m2 which converts maven 1 project.xml to pom.xml (pom conversion + few basic plugin configuration from project.properties to pom.xml). This allows an easy conversion of maven 1 projects, for users willing to migrate to m2. The initial code is available at http://jira.codehaus.org/browse/MNG-1530 I would like to add this plugin to svn + refactoring the pom converter to a separate artifact, which can be shared between the plugin and repository tools (see http://jira.codehaus.org/browse/MRM-29 ) Please vote the following: [ ] add the new plugin +1 [ ] add a new module with the pom converter +1 We need all the help we can with the conversion stuff. Sounds good. ... about the pom converter stuff (if we decide to add it) we should also decide where to put it. If outside the plugin dir, I will need a "sponsor" who can do that, since I only have access to the svn plugins area. It would be nice if you made it a tool that would be used inside a mojo. As most of our tools are plexus components I think doing the same would make sense. Plexus components are easy to reuse inside Mojos and are also resuable in other tools which are usually Plexus-based in our case. We might want to start collecting our repo management code here: http://svn.apache.org/viewcvs.cgi/maven/repository-manager/ And move the maven-repository-tools in there as well. If you have time and code to contribute I would be +1 for giving you access the the repository-manager module. fabrizio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org We all have problems. How we deal with them is a measure of our worth. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: best practices of naming WAS: svn commit: r349270
I just wanted to capture what I thought we were doing currently (albeit inconsistently). I'm happy to discuss. I certainly see your points below, but I think there are also good cases for separation (eg Jorg was asking about excalibur, and it made sense to me for all the components to have their own group, just like maven plugins and maven archetypes). Others? - Brett Vincent Massol wrote: > >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >> Sent: dimanche 27 novembre 2005 19:09 >> To: commits@maven.apache.org >> Subject: svn commit: r349270 - >> /maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt > > [snip] > >> + * A good way to determine the granularity of the group ID is to use the >> project structure. That is, if >> + the current project is a multiple module project, it should append a new >> identifier to the parent's >> + group ID. >> + >> + eg. <<>>, <<>>, >> <<>> >> + > > Ooops... I've just changed that yesterday on the cargo project. I had the > groupIds which were following the nested directory structure but I've > decided to go back to using a single groupid (org.codehaus.cargo) instead > (http://jira.codehaus.org/browse/CARGO-220). > > My reasons were the following: > > * It's easier for cargo users to have to remember a single groupId > > * In any case as we're using fully qualified artifact id there's no > possibility of clashing and it's kind of duplicating the information to put > the hierarchy information both groupId and artifactId. > > * The groupId really represents the project. > > * If we were to use different groupIds using the dotted notation, the m1 > repository on ibiblio would look pretty crowded as we'll have the following > directories at the top level: > org.codehaus.cargo/ > org.codehaus.cargo.core/ > org.codehaus.cargo.core.api/ > org.codehaus.cargo.core.containers/ > [...] > > As this is about best practices I'm curious to know what others think. I > have asked this question on IRC too at that time and Trygve seemed to agree > with this reasoning. > > Thanks > -Vincent > > > > > > > ___ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.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]
[vote] new plugin (maven1 plugin for m2)
Some time ago I started a simple plugin for m2 which converts maven 1 project.xml to pom.xml (pom conversion + few basic plugin configuration from project.properties to pom.xml). This allows an easy conversion of maven 1 projects, for users willing to migrate to m2. The initial code is available at http://jira.codehaus.org/browse/MNG-1530 I would like to add this plugin to svn + refactoring the pom converter to a separate artifact, which can be shared between the plugin and repository tools (see http://jira.codehaus.org/browse/MRM-29 ) Please vote the following: [ ] add the new plugin [ ] add a new module with the pom converter ... about the pom converter stuff (if we decide to add it) we should also decide where to put it. If outside the plugin dir, I will need a "sponsor" who can do that, since I only have access to the svn plugins area. fabrizio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/27-Nov-2005_04.31.18/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release maven-one-plugin?
Vincent Massol wrote: > >> -Original Message- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: dimanche 27 novembre 2005 18:35 >> To: Maven Developers List >> Subject: Re: Release maven-one-plugin? >> >> You in particular have reported this before, its in JIRA, its not fixed. > > Really? Am I loosing my mind due to my old age? :-) It could be me too :) > > I don't recall this. I do recall there being an issue with snapshot > repositories not working when specifying false but this > doesn't seem to be the case here as putting it to true doesn't help. That is what I was referring to. You didn't mention it failed when true too - it might be related to metadata getting "stuck" - does -U work when it is set to true? Is the repository present? mvn projecthelp:effective-pom/effective-settings will clarify. Thanks, Brett > > If you could point me to my issue that would be great! > > Thanks > -Vincent > >> Vincent Massol wrote: -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: samedi 26 novembre 2005 23:32 To: Maven Developers List Subject: Re: Release maven-one-plugin? It was on snapshots.maven.codehaus.org like the other snapshots at one point. I assume it still is. >>> Right. I've checked and it's in there, thanks. >>> >>> What's strange is that I already have that snapshot repository defined >> in my >>> project: >>> >>> >>> >>> >>> false >>> >>> snapshots >>> Maven Central Development Repository >>> http://snapshots.maven.codehaus.org/maven2 >>> >>> >>> >>> However, m2 is not looking in it apparently: >>> >>> " >>> C:\dev\cargo\trunk\extensions\maven>mvn install -X >>> [...] >>> [DEBUG] maven-one-plugin: using locally installed snapshot >>> [DEBUG] Artifact not found - using stub model: Unable to determine the >>> latest version >>> >>> org.apache.maven.plugins:maven-one-plugin:pom:LATEST >>> >>> >>> [DEBUG] Using defaults for missing POM >>> org.apache.maven.plugins:maven-one-plugin:pom:LATEST >>> [DEBUG] maven-one-plugin: using locally installed snapshot >>> [DEBUG] Artifact not found - using stub model: Unable to determine the >>> release version >>> >>> org.apache.maven.plugins:maven-one-plugin:pom:RELEASE >>> >>> >>> [DEBUG] Using defaults for missing POM >>> org.apache.maven.plugins:maven-one-plugin:pom:RELEASE >>> [INFO] >>> >> >>> [ERROR] BUILD ERROR >>> [INFO] >>> >> >>> [INFO] The plugin 'org.apache.maven.plugins:maven-one-plugin' does not >> exist >>> or no valid version could be found >>> [INFO] >>> >> >>> [DEBUG] Trace >>> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin >>> 'org.apache.maven.plugins:maven-one-plugin' does not exist or no valid >>> version could be found >>> " >>> >>> Thanks >>> -Vincent >>> >>> >>> >>> >>> >>> >>> >> __ >> _ >>> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! >> Messenger >>> Téléchargez cette version sur http://fr.messenger.yahoo.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] > > > > > > > > ___ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.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]
RE: svn commit: r349270 - /maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: dimanche 27 novembre 2005 19:09 > To: commits@maven.apache.org > Subject: svn commit: r349270 - > /maven/site/trunk/src/site/apt/guides/mini/guide-naming-conventions.apt [snip] > + * A good way to determine the granularity of the group ID is to use the > project structure. That is, if > + the current project is a multiple module project, it should append a new > identifier to the parent's > + group ID. > + > + eg. <<>>, <<>>, > <<>> > + Ooops... I've just changed that yesterday on the cargo project. I had the groupIds which were following the nested directory structure but I've decided to go back to using a single groupid (org.codehaus.cargo) instead (http://jira.codehaus.org/browse/CARGO-220). My reasons were the following: * It's easier for cargo users to have to remember a single groupId * In any case as we're using fully qualified artifact id there's no possibility of clashing and it's kind of duplicating the information to put the hierarchy information both groupId and artifactId. * The groupId really represents the project. * If we were to use different groupIds using the dotted notation, the m1 repository on ibiblio would look pretty crowded as we'll have the following directories at the top level: org.codehaus.cargo/ org.codehaus.cargo.core/ org.codehaus.cargo.core.api/ org.codehaus.cargo.core.containers/ [...] As this is about best practices I'm curious to know what others think. I have asked this question on IRC too at that time and Trygve seemed to agree with this reasoning. Thanks -Vincent ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release maven-one-plugin?
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: dimanche 27 novembre 2005 18:35 > To: Maven Developers List > Subject: Re: Release maven-one-plugin? > > You in particular have reported this before, its in JIRA, its not fixed. Really? Am I loosing my mind due to my old age? :-) I don't recall this. I do recall there being an issue with snapshot repositories not working when specifying false but this doesn't seem to be the case here as putting it to true doesn't help. If you could point me to my issue that would be great! Thanks -Vincent > Vincent Massol wrote: > > > >> -Original Message- > >> From: Brett Porter [mailto:[EMAIL PROTECTED] > >> Sent: samedi 26 novembre 2005 23:32 > >> To: Maven Developers List > >> Subject: Re: Release maven-one-plugin? > >> > >> It was on snapshots.maven.codehaus.org like the other snapshots at one > >> point. I assume it still is. > > > > Right. I've checked and it's in there, thanks. > > > > What's strange is that I already have that snapshot repository defined > in my > > project: > > > > > > > > > > false > > > > snapshots > > Maven Central Development Repository > > http://snapshots.maven.codehaus.org/maven2 > > > > > > > > However, m2 is not looking in it apparently: > > > > " > > C:\dev\cargo\trunk\extensions\maven>mvn install -X > > [...] > > [DEBUG] maven-one-plugin: using locally installed snapshot > > [DEBUG] Artifact not found - using stub model: Unable to determine the > > latest version > > > > org.apache.maven.plugins:maven-one-plugin:pom:LATEST > > > > > > [DEBUG] Using defaults for missing POM > > org.apache.maven.plugins:maven-one-plugin:pom:LATEST > > [DEBUG] maven-one-plugin: using locally installed snapshot > > [DEBUG] Artifact not found - using stub model: Unable to determine the > > release version > > > > org.apache.maven.plugins:maven-one-plugin:pom:RELEASE > > > > > > [DEBUG] Using defaults for missing POM > > org.apache.maven.plugins:maven-one-plugin:pom:RELEASE > > [INFO] > > > > > [ERROR] BUILD ERROR > > [INFO] > > > > > [INFO] The plugin 'org.apache.maven.plugins:maven-one-plugin' does not > exist > > or no valid version could be found > > [INFO] > > > > > [DEBUG] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > > 'org.apache.maven.plugins:maven-one-plugin' does not exist or no valid > > version could be found > > " > > > > Thanks > > -Vincent > > > > > > > > > > > > > > > __ > _ > > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! > Messenger > > Téléchargez cette version sur http://fr.messenger.yahoo.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] ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Perforce patch
Any ETA on integrating SCM-79 into the trunk? I don't want it to fall through the cracks and I can't assign it to anyone. http://jira.codehaus.org/browse/SCM-79
[vote] plugin releases
Hi devs I would like to start a vote for the release of a couple of m1/m2 plugins: - m2 eclipse plugin 2.0 the current released version has a list of show stopper bugs: wtp support and multiproject are broken, dependencies with system scope have a wrong path, source jars are not added also if already available in the local repository and some more... Now everything has been fixed, and only 2 bugs are still open (transitive provided scope and requirement to have an installed version of the projects in reactor builds) which IMHO are not required for a release. A lot of testcases have been added which cover most all the common directory layouts/dependency types. Based on this, I would like to bump the current version from 2.0 beta3 and release it as final 2.0! - maven1 eclipse plugin 1.10 it still has a few open issues, some of them fixed in the m2 version, but the version in svn has a lot of fixes/new features that users are awaiting for. So I would like to release a new version now before going on with development. - maven1 jira plugin 1.2 Not many changes after the previous version, just a couple of useful fixes and support for standard jira urls (without the numeric project id) Vote is open for 72 hours as usual. I'll start with a (non binding) +1 for all. [ ] m2 eclipse plugin 2.0 [ ] maven1 eclipse plugin 1.10 [ ] maven1 jira plugin 1.2 Cheers, fabrizio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1695) Generated outputpath is outside the eclipse project
[ http://jira.codehaus.org/browse/MNG-1695?page=comments#action_52139 ]
fabrizio giustina commented on MNG-1695:
thanks for testing the new revision.
Btw, the warnings are generated because of the include pattern for resources in
your poms (this is expected, since the plugin doesn't support include patters
yet)
**/*.xml
> Generated outputpath is outside the eclipse project
> ---
>
> Key: MNG-1695
> URL: http://jira.codehaus.org/browse/MNG-1695
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0.1
> Environment: plugin revision 349173, windows xp, running from a partition
> mounted at 'R'
> Reporter: Barry Kaplan
> Fix For: 2.0.1
> Attachments: eclipse-plugin-test-project.zip
>
>
> In the sample multi-project attached, the generated eclipse project
> outputpath will have the drive letter appended.
> In iris-env/pom.xml I have tried several different variants of
>
>...
>
> These are the summarized results for the iris-infra project:
> 1) outputDirectory = "target/eclipse-classes" --> eclipse output =
> "R:/eclipse-plugin-test-project/target/eclipse-classes"
> 2) outputDirectory = "/target/eclipse-classes" --> eclipse output =
> "R:/target/eclipse-classes"
> 3) outputDirectory = "//target/eclipse-classes" --> eclipse output =
> "//target/eclipse-classes"
> - eclipse complains with the error "Path '/target/eclipse-classes' must
> denote location inside project iris-infra"
> - the plugin generates these warnings:
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> 4) outputDirectory = "//${project.artifactId}/target/eclipse-classes" -->
> eclipse output = "//iris-infra/target/eclipse-classes"
> - this path works for eclipse
> - the plugin generates these warnings, and runs very slowly
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_52134 ] Carlos Sanchez commented on MNG-678: Mario Ivankovits from commons-vfs, they use scp with jsch, said I've never seen this problem and there were no reports like this. Could it be, that the time after creating the session and requesting a channel is too long idle and thus the server ended it? Just a wild guess ... > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0.1 > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1695) Generated outputpath is outside the eclipse project
[ http://jira.codehaus.org/browse/MNG-1695?page=all ]
Barry Kaplan closed MNG-1695:
-
Resolution: Fixed
Fix Version: 2.0.1
Already fixed at the time this issue was reported by rev 349273.
> Generated outputpath is outside the eclipse project
> ---
>
> Key: MNG-1695
> URL: http://jira.codehaus.org/browse/MNG-1695
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0.1
> Environment: plugin revision 349173, windows xp, running from a partition
> mounted at 'R'
> Reporter: Barry Kaplan
> Fix For: 2.0.1
> Attachments: eclipse-plugin-test-project.zip
>
>
> In the sample multi-project attached, the generated eclipse project
> outputpath will have the drive letter appended.
> In iris-env/pom.xml I have tried several different variants of
>
>...
>
> These are the summarized results for the iris-infra project:
> 1) outputDirectory = "target/eclipse-classes" --> eclipse output =
> "R:/eclipse-plugin-test-project/target/eclipse-classes"
> 2) outputDirectory = "/target/eclipse-classes" --> eclipse output =
> "R:/target/eclipse-classes"
> 3) outputDirectory = "//target/eclipse-classes" --> eclipse output =
> "//target/eclipse-classes"
> - eclipse complains with the error "Path '/target/eclipse-classes' must
> denote location inside project iris-infra"
> - the plugin generates these warnings:
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> 4) outputDirectory = "//${project.artifactId}/target/eclipse-classes" -->
> eclipse output = "//iris-infra/target/eclipse-classes"
> - this path works for eclipse
> - the plugin generates these warnings, and runs very slowly
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1695) Generated outputpath is outside the eclipse project
[ http://jira.codehaus.org/browse/MNG-1695?page=comments#action_52130 ]
Barry Kaplan commented on MNG-1695:
---
Ah, sorry. I just updated to 349273 the correct path is now created! (Wish
I tried this before setting up this issue :-(
I still get the "WARNING] This plugin currently doesn't support include
patterns for resources. Adding the entire directory. ", so you I think you are
right that this could be unrelated. The eclipse projects are generated at top
speed also.
So I will close this issue now.
thanks!!
> Generated outputpath is outside the eclipse project
> ---
>
> Key: MNG-1695
> URL: http://jira.codehaus.org/browse/MNG-1695
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0.1
> Environment: plugin revision 349173, windows xp, running from a partition
> mounted at 'R'
> Reporter: Barry Kaplan
> Attachments: eclipse-plugin-test-project.zip
>
>
> In the sample multi-project attached, the generated eclipse project
> outputpath will have the drive letter appended.
> In iris-env/pom.xml I have tried several different variants of
>
>...
>
> These are the summarized results for the iris-infra project:
> 1) outputDirectory = "target/eclipse-classes" --> eclipse output =
> "R:/eclipse-plugin-test-project/target/eclipse-classes"
> 2) outputDirectory = "/target/eclipse-classes" --> eclipse output =
> "R:/target/eclipse-classes"
> 3) outputDirectory = "//target/eclipse-classes" --> eclipse output =
> "//target/eclipse-classes"
> - eclipse complains with the error "Path '/target/eclipse-classes' must
> denote location inside project iris-infra"
> - the plugin generates these warnings:
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> 4) outputDirectory = "//${project.artifactId}/target/eclipse-classes" -->
> eclipse output = "//iris-infra/target/eclipse-classes"
> - this path works for eclipse
> - the plugin generates these warnings, and runs very slowly
> [INFO] [eclipse:eclipse]
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
> [WARNING] This plugin currently doesn't support include patterns for
> resources. Adding the entire directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level
[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52129 ] Barry Kaplan commented on MNG-1605: --- Ok, I created MNG-1695 and attached a sample project hierarchy that can be used to demostrate the problem. As for: >> A correct output path would have the project prepended, eg: >> "iris-infra/target/eclipse-classes" >why? Shouldn't the output simply be path="target/eclipse-classes"/> ? Eclipse then complains "Path '/target/eclipse-classes' must denote location inside project iris-infra". This is one the cases in MNG-1695, but you will need to load the project in eclipse, and then open the project properties build path tab to see the message. > Allow eclipse source to be specified at the dependency level > > > Key: MNG-1605 > URL: http://jira.codehaus.org/browse/MNG-1605 > Project: Maven 2 > Type: New Feature > Components: maven-eclipse-plugin > Versions: 2.0 > Reporter: Barry Kaplan > Assignee: fabrizio giustina > > > Many (most?) projects do not have sources uploaded. And in any case, most > projects only need a small subset of the sources. Source downloading, even > (especially?) for sources that don't exist, is very time consuming. > Therefore, it would be nice to specify this eclipse plugin specific option as > the dependency level. Maybe something like: > > backport-util-concurrent > backport-util-concurrent > 2.0_01_pd > runtime > > > > > (For this to be general, it would of course require a much different model > than the simple plugin-level property injection. ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1695) Generated outputpath is outside the eclipse project
Generated outputpath is outside the eclipse project
---
Key: MNG-1695
URL: http://jira.codehaus.org/browse/MNG-1695
Project: Maven 2
Type: Bug
Components: maven-eclipse-plugin
Versions: 2.0.1
Environment: plugin revision 349173, windows xp, running from a partition
mounted at 'R'
Reporter: Barry Kaplan
Attachments: eclipse-plugin-test-project.zip
In the sample multi-project attached, the generated eclipse project outputpath
will have the drive letter appended.
In iris-env/pom.xml I have tried several different variants of
...
These are the summarized results for the iris-infra project:
1) outputDirectory = "target/eclipse-classes" --> eclipse output =
"R:/eclipse-plugin-test-project/target/eclipse-classes"
2) outputDirectory = "/target/eclipse-classes" --> eclipse output =
"R:/target/eclipse-classes"
3) outputDirectory = "//target/eclipse-classes" --> eclipse output =
"//target/eclipse-classes"
- eclipse complains with the error "Path '/target/eclipse-classes' must denote
location inside project iris-infra"
- the plugin generates these warnings:
[INFO] [eclipse:eclipse]
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
4) outputDirectory = "//${project.artifactId}/target/eclipse-classes" -->
eclipse output = "//iris-infra/target/eclipse-classes"
- this path works for eclipse
- the plugin generates these warnings, and runs very slowly
[INFO] [eclipse:eclipse]
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
[WARNING] This plugin currently doesn't support include patterns for resources.
Adding the entire directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-611) Upload Asterisk-Java 0.2
Upload Asterisk-Java 0.2 Key: MAVENUPLOAD-611 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-611 Project: maven-upload-requests Type: Task Reporter: Stefan Reuter http://www.asteriskjava.org/ http://www.asteriskjava.org/latest/team-list.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (CONTINUUM-477) Improve performance of enqueuing projects
[ http://jira.codehaus.org/browse/CONTINUUM-477?page=comments#action_52128 ] Brett Porter commented on CONTINUUM-477: is that delay realy the enqueuing, or just waiting to see the front page come back? > Improve performance of enqueuing projects > - > > Key: CONTINUUM-477 > URL: http://jira.codehaus.org/browse/CONTINUUM-477 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.1 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > Actually, plexus projects are enqueuing in more than 2 minutes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-18) fileset support
fileset support --- Key: ARCHETYPE-18 URL: http://jira.codehaus.org/browse/ARCHETYPE-18 Project: Maven Archetype Type: Improvement Components: maven-archetype-plugin Reporter: Jorg Heymans Assigned to: Jason van Zyl it would be great if the descriptor supported filesets of some sort, as it's currently a pain creating descriptors for archetypes that contain a large amount of files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ruby-Mojo support
Happy birthday! Eric Redmond wrote: > Oh, right! I feel silly for asking now... thanks. > > Of course I'll contribute when I feel more comfortable with its stability. > > I'll get back on this tomorrow... its my birthday today :) > > Thanks! > Eric > > On 11/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: >> The project building the plugin can add this without modifying the >> original plugin plugin: >> >> >> >> maven-plugin-plugin >> >> >> ... >> maven-plugin-tools-ruby >> ... >> >> >> >> We'd be very interested in this support. Are you willing to contribute >> it back to the project? >> >> Cheers, >> Brett >> >> >> Eric Redmond wrote: >>> Maven developers: >>> >>> I have just completed a couple projects to add Ruby support for Maven 2, >>> allowing one to write mojos in Ruby as well as generate mojo descriptors >>> based upon RDoc markup. But I have run into a hurdle. I currently am >> making >>> the plugin:descriptor run my RubyExtractor by adding the >>> maven-plugin-tools-ruby project to the maven-plugin-plugin dependency >> list. >>> I figured when running the descriptor goal on the plugin project, it >>> populates the mojoDescriptorExtractors with those injected by Plexus, >> which >>> naturally must exist in the classpath space (I believe I am correct >> here). >>> So my question is: is there another way I am missing in which to add my >>> RubyExtractor to the plugin "descriptor" which does not include >> modifying >>> the maven-plugin-plugin project in any way? >>> >>> Thanks! >>> Eric >>> >> - >> 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]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/27-Nov-2005_12.31.06/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ruby-Mojo support
Oh, right! I feel silly for asking now... thanks. Of course I'll contribute when I feel more comfortable with its stability. I'll get back on this tomorrow... its my birthday today :) Thanks! Eric On 11/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > The project building the plugin can add this without modifying the > original plugin plugin: > > > > maven-plugin-plugin > > > ... > maven-plugin-tools-ruby > ... > > > > We'd be very interested in this support. Are you willing to contribute > it back to the project? > > Cheers, > Brett > > > Eric Redmond wrote: > > Maven developers: > > > > I have just completed a couple projects to add Ruby support for Maven 2, > > allowing one to write mojos in Ruby as well as generate mojo descriptors > > based upon RDoc markup. But I have run into a hurdle. I currently am > making > > the plugin:descriptor run my RubyExtractor by adding the > > maven-plugin-tools-ruby project to the maven-plugin-plugin dependency > list. > > I figured when running the descriptor goal on the plugin project, it > > populates the mojoDescriptorExtractors with those injected by Plexus, > which > > naturally must exist in the classpath space (I believe I am correct > here). > > > > So my question is: is there another way I am missing in which to add my > > RubyExtractor to the plugin "descriptor" which does not include > modifying > > the maven-plugin-plugin project in any way? > > > > Thanks! > > Eric > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
[jira] Commented: (MNG-441) surefire plugin needs to be able to fork tests
[ http://jira.codehaus.org/browse/MNG-441?page=comments#action_52127 ] Joakim Erdfelt commented on MNG-441: Additional note. This is required for the Cobertura plugin to work properly. > surefire plugin needs to be able to fork tests > -- > > Key: MNG-441 > URL: http://jira.codehaus.org/browse/MNG-441 > Project: Maven 2 > Type: Improvement > Components: maven-surefire-plugin > Reporter: Brett Porter > Fix For: 2.0.1 > Attachments: SurefirePlugin.java, pom.xml > > > they can leak memory, so a "fork once for all" option would be good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release maven-one-plugin?
You in particular have reported this before, its in JIRA, its not fixed. - Brett Vincent Massol wrote: > >> -Original Message- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: samedi 26 novembre 2005 23:32 >> To: Maven Developers List >> Subject: Re: Release maven-one-plugin? >> >> It was on snapshots.maven.codehaus.org like the other snapshots at one >> point. I assume it still is. > > Right. I've checked and it's in there, thanks. > > What's strange is that I already have that snapshot repository defined in my > project: > > > > > false > > snapshots > Maven Central Development Repository > http://snapshots.maven.codehaus.org/maven2 > > > > However, m2 is not looking in it apparently: > > " > C:\dev\cargo\trunk\extensions\maven>mvn install -X > [...] > [DEBUG] maven-one-plugin: using locally installed snapshot > [DEBUG] Artifact not found - using stub model: Unable to determine the > latest version > > org.apache.maven.plugins:maven-one-plugin:pom:LATEST > > > [DEBUG] Using defaults for missing POM > org.apache.maven.plugins:maven-one-plugin:pom:LATEST > [DEBUG] maven-one-plugin: using locally installed snapshot > [DEBUG] Artifact not found - using stub model: Unable to determine the > release version > > org.apache.maven.plugins:maven-one-plugin:pom:RELEASE > > > [DEBUG] Using defaults for missing POM > org.apache.maven.plugins:maven-one-plugin:pom:RELEASE > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The plugin 'org.apache.maven.plugins:maven-one-plugin' does not exist > or no valid version could be found > [INFO] > > [DEBUG] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-one-plugin' does not exist or no valid > version could be found > " > > Thanks > -Vincent > > > > > > > ___ > Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger > Téléchargez cette version sur http://fr.messenger.yahoo.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]
[jira] Closed: (MAVENUPLOAD-583) Upload maven model v3 for use in a maven 2 plugin
[ http://jira.codehaus.org/browse/MAVENUPLOAD-583?page=all ] fabrizio giustina closed MAVENUPLOAD-583: - Assign To: fabrizio giustina Resolution: Fixed fixed, maven-model-v3 has been uploaded to the apache repository. > Upload maven model v3 for use in a maven 2 plugin > - > > Key: MAVENUPLOAD-583 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-583 > Project: maven-upload-requests > Type: Wish > Reporter: fabrizio giustina > Assignee: fabrizio giustina > > > see MNG-1436 for the related issue: > maven-model-all can't be loaded by a plugin and the artifact needs to be > redeployed with only v3 classes with a different artifact id. > related ml thread > http://mail-archives.apache.org/mod_mbox/maven-dev/200511.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[REPOCLEAN] Error(s) occurred while converting repository
Errors occurred while performing maven-1 to maven-2 repository conversion. For more details, see: http://test.maven.codehaus.org/reports/repoclean/27-Nov-2005_08.30.54/repository.report.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release maven-one-plugin?
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: samedi 26 novembre 2005 23:32 > To: Maven Developers List > Subject: Re: Release maven-one-plugin? > > It was on snapshots.maven.codehaus.org like the other snapshots at one > point. I assume it still is. Right. I've checked and it's in there, thanks. What's strange is that I already have that snapshot repository defined in my project: false snapshots Maven Central Development Repository http://snapshots.maven.codehaus.org/maven2 However, m2 is not looking in it apparently: " C:\dev\cargo\trunk\extensions\maven>mvn install -X [...] [DEBUG] maven-one-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-one-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-one-plugin:pom:LATEST [DEBUG] maven-one-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-one-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-one-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-one-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-one-plugin' does not exist or no valid version could be found " Thanks -Vincent ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1605) Allow eclipse source to be specified at the dependency level
[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52123 ] fabrizio giustina commented on MNG-1605: Hi Barry, would you mind opening a separate issue for the problems you reported and with some more explanations? > When the eclipse project is generated from the leaf project directory, the > output path is created correctly as "target/eclipse-classes". > However, when I generated eclipse projects via the root project using > multi-project, the output path has a drive letter prepended, eg > "R:target/eclipse-classes". I tried reproducing this with a unit test, and I'm going to fix some issues, but I'm not sure if it's the same problem you are seeing with the drive letter... can you post the eclipse plugin configuration in both the parent and module pom.xml + a description of your directory layout? > A correct output path would have the project prepended, eg: > "iris-infra/target/eclipse-classes" why? Shouldn't the output simply be ? > This caused the following warnings: > [WARNING] This plugin currently doesn't support include patterns for > resources. Adding the entire directory. I wasn't unable to reproduce this problem, the warning should be issued only if you are using include/exclude patters in resource dirs, are you sure this is related to the path with the // prepended? > Allow eclipse source to be specified at the dependency level > > > Key: MNG-1605 > URL: http://jira.codehaus.org/browse/MNG-1605 > Project: Maven 2 > Type: New Feature > Components: maven-eclipse-plugin > Versions: 2.0 > Reporter: Barry Kaplan > Assignee: fabrizio giustina > > > Many (most?) projects do not have sources uploaded. And in any case, most > projects only need a small subset of the sources. Source downloading, even > (especially?) for sources that don't exist, is very time consuming. > Therefore, it would be nice to specify this eclipse plugin specific option as > the dependency level. Maybe something like: > > backport-util-concurrent > backport-util-concurrent > 2.0_01_pd > runtime > > > > > (For this to be general, it would of course require a much different model > than the simple plugin-level property injection. ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-678) scp intermittently failing deploying artifact
[ http://jira.codehaus.org/browse/MNG-678?page=comments#action_52121 ] Vincent Massol commented on MNG-678: Brett, I've just tried using an IP but I got the same result: " [INFO] [deploy:deploy] [INFO] Retrieving previous build number from cargo-snapshot The authenticity of host '64.7.141.17' can't be established. RSA key fingerprint is 28:5c:69:90:31:43:99:f2:2c:85:33:86:44:02:91:3b. Are you sure you want to continue connecting? (yes/no): yes Uploading: scp://64.7.141.17/home/projects/cargo/dist2-snapshot/org/codehaus/cargo/cargo-core-api-util/0.7-SNAPSHOT/cargo-core-api-util-0.7-20051127.101717-3.jar 11K uploaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error performing commands for file transfer session is down " > scp intermittently failing deploying artifact > - > > Key: MNG-678 > URL: http://jira.codehaus.org/browse/MNG-678 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0-alpha-3 > Environment: JDK 1.5, Red Hat 9 > Reporter: Joe Futrelle > Assignee: Brett Porter > Fix For: 2.0.1 > > > Some of the time, deploying artifacts fails during the scp transfer. The > bottom of the stack trace is reproduced below. If I run the m2 deploy enough > times, it succeeds; not sure why. > This is not an unknown issue with Jsch; apparently client code can cause > behavior like this if it doesn't dispose of connections properly. Possibly a > plugin that's runs before the deploy phase is messing up the connection state > somehow? > Caused by: org.apache.maven.wagon.TransferFailedException: Error occured > while deploying 'ncsa/gsbt/1.0-SNAPSHOT/gsbt-1.0-20050728.190330-38.pom.sha1' > to remote repository: scp://chasm.ncsa.uiuc.edu//home/futrelle/m2/repository > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:331) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:167) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:91) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:73) > ... 17 more > Caused by: com.jcraft.jsch.JSchException: session is down > at com.jcraft.jsch.Channel.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:271) > ... 20 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVENUPLOAD-609) maven taglib plugin 1.4.2 for maven 1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-609?page=comments#action_52120 ] fabrizio giustina commented on MAVENUPLOAD-609: --- id removed, upload bundle is updated > maven taglib plugin 1.4.2 for maven 1 > - > > Key: MAVENUPLOAD-609 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-609 > Project: maven-upload-requests > Type: Task > Reporter: fabrizio giustina > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
