Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to
cut the 3.1.0-beta-1 this weekend if there are no objections.
Thanks,
Jason
--
Jason van Zyl
Founder CTO, Sonatype
Founder, Apache Maven
Is there an expert about the // build who could have a look at the last
comment provided by Dimitri :
http://jira.codehaus.org/browse/MNG-4996?focusedCommentId=326816page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-326816
I know him, he'll be happy to help us more to
For the record, see https://jira.codehaus.org/browse/MNGSITE-180
Cross-posting to dev list so that PMC can discuss that issue at what should
be the exact wording.
Cheers
2013/6/12 Stephen Connolly stephen.alan.conno...@gmail.com
On 12 June 2013 11:04, Stephen Colebourne scolebou...@joda.org
Perhaps we are at the point where we should start breaking builds rather
than just giving a stern warning... certainly the warning has been there
for long enough
MNG-3762
Say there is a maven-whatever-plugin available in central which needs to
be renamed to whatever-maven-plugin. Is there a
relocation pom will not work for plugins... (we maybe should look into that
though)
Simplest is just to move to the new ID and tell your users to change...
that's what jetty did
On 18 June 2013 16:00, Christian Schulte c...@schulte.it wrote:
Perhaps we are at the point where we should start
Am 06/18/13 17:32, schrieb Stephen Connolly:
relocation pom will not work for plugins... (we maybe should look into that
though)
Simplest is just to move to the new ID and tell your users to change...
that's what jetty did
Ok. Thanks for clarifying.
--
Christian
Well ... documentation is good, but enforcement and a friendly but clearly
phrased error message containing:
1. What is wrong with the current naming,
2. What should be done to correct the problems, and
3. A reference to further reading on the topic (for example *why*
something is
Maven Plugin Plugin already gives a big friendly warning...
Once we get the wording on the website right, we will flip the switch and
break people's builds if they are bold...
On 18 June 2013 17:06, Lennart Jörelid lennart.jore...@gmail.com wrote:
Well ... documentation is good, but
Thanks to Eric, we now have a tool to check dist content
And I just added it to our Jenkins instance, to build once a day: you can look
at the result [1]
I just had to remove the preview of site, since Firefox isn't available on the
CI server (or not able to start in headless mode)
Any
yes, there doesn't seem to be much people reporting any issues.
Do we have any meaning of measuring the use of this new version?
I'm missing time at the moment to work on code.
But I'd like to work on little POM schema additions, like encoding
configuration: the precise list of additions that
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I plan to
cut the 3.1.0-beta-1 this weekend if there are no objections.
+1 - have been using it all week with no issues.
One thing I would love to see ( and I should really raise a JIRA for
this ),
11 matches
Mail list logo
