Re: Deployment Request - Struts 2.05

2007-02-09 Thread Carlos Sanchez
fixed ;) On 2/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: Excellent. I was just following the instructions in the README.txt -Ted. On 2/9/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > Hey Ted, it's automatically done after ~4 hours, let me know if > there's any problem > > On 2/9/07, Ted Hus

Re: Deployment Request - Struts 2.05

2007-02-09 Thread Ted Husted
Excellent. I was just following the instructions in the README.txt -Ted. On 2/9/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: Hey Ted, it's automatically done after ~4 hours, let me know if there's any problem On 2/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: > Please deploy the org/apache/stru

Re: Deployment Request - Struts 2.05

2007-02-09 Thread Carlos Sanchez
Hey Ted, it's automatically done after ~4 hours, let me know if there's any problem On 2/9/07, Ted Husted <[EMAIL PROTECTED]> wrote: Please deploy the org/apache/struts/struts2 artifacts from the m2-ibiblio-rsync-repository folder. Specifically, the 2.0.5 versions of struts2-api struts2-parent

Deployment Request - Struts 2.05

2007-02-09 Thread Ted Husted
Please deploy the org/apache/struts/struts2 artifacts from the m2-ibiblio-rsync-repository folder. Specifically, the 2.0.5 versions of struts2-api struts2-parent struts2-apps struts2-pell-multipart-plugin struts2-blank struts2-plexus-plugin struts2-codebehind-plugin struts2-plugins struts2-config

Re: Symbolic Links - eclipse:eclipse

2007-02-09 Thread Jason van Zyl
On 9 Feb 07, at 1:21 PM 9 Feb 07, Bernhard C Gass wrote: Hello, I am not reading the mailing lists on a regular basis so please forgive me if that issue was raised already. I do not want to restructure the SCM, so I made a symbolic link to the source code. That works fine with Maven in ge

Symbolic Links - eclipse:eclipse

2007-02-09 Thread Bernhard C Gass
Hello, I am not reading the mailing lists on a regular basis so please forgive me if that issue was raised already. I do not want to restructure the SCM, so I made a symbolic link to the source code. That works fine with Maven in general, but the eclipse plugin substitutes the link with th

Re: [vote] Release Maven Parent POM 5 and Maven Plugins Parent POM 8

2007-02-09 Thread Jason van Zyl
On 9 Feb 07, at 12:46 PM 9 Feb 07, Dennis Lundberg wrote: Jason van Zyl wrote: On 9 Feb 07, at 12:22 PM 9 Feb 07, Dennis Lundberg wrote: I must have misunderstood what you were trying to accomplish Jason. I was under the impression that the changes to the parent poms were made so that *dire

Re: **/pom.xml is part of the ignore list during the check-for-local-modifications phase within the release process

2007-02-09 Thread Jörg Schaible
Brett Porter wrote: > On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote: > >>> AFAIK the reason the poms are excluded is because they're modified >>> by the >>> release process; if the check for local modifications is run after >>> the pom >>> is modified, it's impossible to do a release. So this c

Re: [vote] Release Maven Parent POM 5 and Maven Plugins Parent POM 8

2007-02-09 Thread Dennis Lundberg
Jason van Zyl wrote: On 9 Feb 07, at 12:22 PM 9 Feb 07, Dennis Lundberg wrote: I must have misunderstood what you were trying to accomplish Jason. I was under the impression that the changes to the parent poms were made so that *direct* releases would work well. After that, the work on enabl

Re: [vote] Release Maven Parent POM 5 and Maven Plugins Parent POM 8

2007-02-09 Thread Jason van Zyl
On 9 Feb 07, at 12:22 PM 9 Feb 07, Dennis Lundberg wrote: I must have misunderstood what you were trying to accomplish Jason. I was under the impression that the changes to the parent poms were made so that *direct* releases would work well. After that, the work on enabling *staged* releas

Re: [vote] Release Maven Parent POM 5 and Maven Plugins Parent POM 8

2007-02-09 Thread Dennis Lundberg
I must have misunderstood what you were trying to accomplish Jason. I was under the impression that the changes to the parent poms were made so that *direct* releases would work well. After that, the work on enabling *staged* releases would start. That is what I would prefer. Not everybody has

[vote-result] release maven-ejb-plugin 2.1

2007-02-09 Thread Stephane Nicoll
Vote results: +1 (bindings): Jason, Joakim, Stéphane +1 (non bindings): Wayne, Daniel The voting thread is http://www.nabble.com/-vote--release-maven-ejb-plugin-2.1-tf3189055s177.html The release is being moved from the staging repo to the main repo. Cheers, Stéphane --

Re: Where is the 2.0.5 release?

2007-02-09 Thread Jason van Zyl
On 9 Feb 07, at 8:47 AM 9 Feb 07, Jason Dillon wrote: Has this gotten stalled? Its been a few weeks now and still nothing... There were two issues discovered, one fixed and being verified the other a serious regression which I started looking at last night. Jason. --jason -

Where is the 2.0.5 release?

2007-02-09 Thread Jason Dillon
Has this gotten stalled? Its been a few weeks now and still nothing... --jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

about Maven release-plugin

2007-02-09 Thread Guijie (Maggie) Ma
Hi, I'm a user of Maven and Maven is very good for my work. But in the use, we have found a problem: when we do the project release, e.g. mvn release:prepare, we need input the release version and the new development version manually for each modules. I want to know whether release-plugin can h