Vincent Siveton wrote:
2008/6/2, Dennis Lundberg <[EMAIL PROTECTED]>:

Lukas Theussl wrote:


Hrm, ok. But if we release site and pir plugins (which is slated to happen

soonish, right?), these people will be bitten by the same problems anyway,
unless maven-2.0.10 gets released in the meantime and they upgrade
immediately. (And btw, shouldn't versions be specified even for snapshots
anyway?)

Yes, people who don't specify a version will be automatically upgraded,
when the new releases come out shortly. (Yes, people should specify
versions!)

There are two problems with putting out a next version SNAPSHOT before the
upcoming version is released. I already mentioned handling bug reports. The
other problem is that the first SNAPSHOT (2.0-beta-7-SNAPSHOT in this case)
will not get nearly as much real world testing as it should, because a lot
of users have already been automatically upgraded to the next SNAPSHOT
(2.0-beta-8-SNAPSHOT in this case).



WDYT to add a classifier for plugins using doxia-beta-1?

I don't see the need for that, unless it is considered a recommended practice that we agree upon in general. Specifying a maven-2.0.10 prereq should be enough.


Cheers,

Vincent


I just wanted to make it easy to test doxia-beta-1, but if this causes

confusion, I don't care to remove it (can I just remove a snapshot from the
repo?).

It should be possible to remove the jars, but I suspect one also needs to
manually adjust the metadata files. I think the sync time for removing is
longer than it is for adding.

In cases like this a deploy:undeploy goal would be handy for SNAPSHOT
artifacts.



-Lukas


Dennis Lundberg wrote:


Lukas Theussl wrote:



I have uploaded the new snapshots with changed version number exactly

because I didn't want to interrupt the release process for
site-plugin-2.0-beta-7 and pir-2.1. How come people are already getting
these snapshots, I thought they'd have to explicitly ask for them?


If they don't specify a version and have opted to use our snapshot repo,

they will get the latest SNAPSHOT. In this case 2.0-beta-8-SNAPSHOT and
2.2-SNAPSHOT.

The only way for them to get 2.0-beta-7-SNAPSHOT and 2.1-SNAPSHOT now is

to explicitly specify those version in their POMs.


-Lukas


Brian E. Fox wrote:



I don't follow what you're asking

-----Original Message-----
From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Monday, June

02, 2008 2:32 PM

To: Maven Developers List
Subject: Multiple concurrent SNAPSHOTs for MSITE and MPIR isn't

working

Hi

Having two concurrent SNAPSHOT versions for maven-site-plugin and

maven-project-info-reports-plugin just isn't working.
Issues are starting to pour in for the the newest SNAPSHOTs, when we are in
the process of releasing the older SNAPSHOTs.

Can we please remove the 2.0-beta-8-SNAPSHOT and 2.2-SNAPSHOT

respectively until 2.0-beta-7 and 2.1 has been released?



---------------------------------------------------------------------

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]





--
Dennis Lundberg


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to