On Sat, Feb 23, 2008 at 3:42 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> Wendy Smoak wrote:
>
> > mvn deploy site:stage-deploy
>
> I still can't get that to work. I was never able to use it for Surefire
> 2.4.2, even though "mvn site-deploy" worked just fine; it kept prompting
> me for a p
Wendy Smoak wrote:
If you make a change to a plugin that affects the documentation (new
parameter, etc.,) you can publish the updated website along with the
snapshot jar with:
mvn deploy site:stage-deploy
I still can't get that to work. I was never able to use it for Surefire
2.4.2, even
Now the question is "do we have to change this order ?".
Have a look at MRESOURCES-39 [1].
Users complains about system properties (-D in the mvn cli) doesn't win.
IMHO, system props should wins.
This was the case with maven1 [2].
Thougths ?
Thanks,
--
Olivier
[1] http://jira.codehaus.org/brow
Yes, I know. I previously made the change in the classes copied from
plexus-utils. This change is here only to track the plexus-utils version where
the original modifications are.
Selon Dennis Lundberg <[EMAIL PROTECTED]>:
> The site plugin still has a prerequisite of Maven 2.0.2, so this change
I agree with Jason's comments below. We need to be careful when
upgrading the Maven prerequisite for plugins.
As far as I have seen, the number one reason for bumping the
prerequisite to Maven 2.0.6 is so that a version of plexus-utils > 1.1
can be used. There can be two reasons for this. Eith
If you make a change to a plugin that affects the documentation (new
parameter, etc.,) you can publish the updated website along with the
snapshot jar with:
mvn deploy site:stage-deploy
(Check that you're using a recent version of the maven-plugins parent
which has the site plugin configuratio
On 23-Feb-08, at 5:26 AM, Olivier Lamy wrote:
Hi,
Ok I understand the point (I have reverted the commit).
But 2.0.6 has been released ~ 1 year ago.
There are still lots of people using 2.0.5 due to some core+surefire
problems. But really if people have products building with version of
Ma
The site plugin still has a prerequisite of Maven 2.0.2, so this change
will have no effect for people running Maven up to (and including)
version 2.0.5.
[EMAIL PROTECTED] wrote:
Author: hboutemy
Date: Sat Feb 23 01:14:34 2008
New Revision: 630418
URL: http://svn.apache.org/viewvc?rev=630418&
Regardless of the current state of the documentation, you must deploy
the documentation for the version being released. It is part of our
release process [1], see point 8. This helps our users know exactly
which version of the docs they are reading.
As a personal preference, I consider the doc
I still use 2.0.5 daily at the office.
I do have 2.0.7 and 2.0.8 installed too, but there's some bad juju (re:
bugs) starting in 2.0.6+ WRT corporate repositories, wagon lightweight
http, non-projects (archetype, install-file, deploy-file, eclipse,
etc...) and also plugin resolution. So we are
Hi Tomasz,
The documentation for the plugin is currently under construction.
I hope to publish a better asap.
Regards
Raphaël
2008/2/23, Tomasz Pik <[EMAIL PROTECTED]>:
> On Sat, Feb 23, 2008 at 1:20 AM, Brian Fox <[EMAIL PROTECTED]> wrote:
> > The Maven team would like to announce the releas
Hi,
Ok I understand the point (I have reverted the commit).
But 2.0.6 has been released ~ 1 year ago.
What could be the time to wait to add a core prerequisite ? (Note :
the jar plugin have this prerequisite and I haven't yet seen user
complaining).
I don't know how many people use mvn before 2.0.
On Sat, Feb 23, 2008 at 1:20 AM, Brian Fox <[EMAIL PROTECTED]> wrote:
> The Maven team would like to announce the release of Maven Archetype
> 2.0-alpha-2. This release corrected backwards compatibility with the
> 1.0 version and a few windows issues. The site has also been updated
> and deploye
13 matches
Mail list logo
