Hi,
my opinion is cleary to deploy to central as we did before...to give
others a chance to test.
I can often see that many people are automatically downloading Maven
from Central (download from Apache dist etc. is not a good idea apart
from that blocked) for example with travis, ship-it, appveyor etc. or
with Jenkins as well..
To give the best availability is to use Central...
I'm not a fan of making a message into Maven alpha/beta saying this is a
alpha version...(mvn -V will already print that out). That message will
not prevent one of using it...
So in the end it's up to the users to decide to use an alpha/beta or
later upgrade or not...
Kind regards
Karl Heinz Marbaise
On 25/02/17 22:55, Karl Heinz Marbaise wrote:
Hi,
based on the started discussion about either to bring 3.5.0-alpha-1 to
Central or not I would suggest to discuss in a separate thread and
prevent using the VOTE's threads for that (as Stephen already mentioned).
Using Central:
o Everybody can use it and make tests on it.
Using an other repository:
o Which one?
Using only dist area? Or something different?
WDY?
Based on earlier releases which had been in Central with alpha's:
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
