yes, this is currently for 3.5.0 that this fix should be in, then with this
seconding principle
once Maven 3.5.0 is out, we'll need to define if we continue that way or not
Regards,
Hervé
Le samedi 14 janvier 2017, 12:24:09 CET Stephen Connolly a écrit :
> The "seconding" thing was from my per
The "seconding" thing was from my perspective just a 3.5.0 thing...
If people like it, fine. But it might be a bit much as a project culture
On Sat 14 Jan 2017 at 03:42, Hervé BOUTEMY wrote:
> > This also brings me to another point: could somebody second MNG-6109[2]
>
> > for M3.5.0, so I can l
I suggest confirming it on the original thread so all the decisions are
easier to trace back
Robert
On Sat, 14 Jan 2017 04:40:02 +0100, Hervé BOUTEMY
wrote:
This also brings me to another point: could somebody second MNG-6109[2]
for M3.5.0, so I can lock the Maven version in the maven-pl
> This also brings me to another point: could somebody second MNG-6109[2]
> for M3.5.0, so I can lock the Maven version in the maven-plugin-plugin
> which may use the plugin.xml or should scan the code for the @since value.
oh, yes, seconded, I'm confident in this little bugfix
(I don't know if I s
That's in JIRA of course, poms need to be updated.
On Thu, 12 Jan 2017 12:47:48 +0100, Robert Scholte
wrote:
to change the version to 3.5.1 in the pom
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additio
It's always hard to predict the next version. I would expect it to be 3.6,
until we received a bug report[1], which made me decide to change the
version to 3.5.1 in the pom with the idea to do a release soon.
This also brings me to another point: could somebody second MNG-6109[2]
for M3.5.0,
Hi,
For MPLUGIN, the only unreleased version in JIRA is currently 3.5.1, but
the version in the POM themselves is 3.6-SNAPSHOT. Should the version in
JIRA be changed, or can I update the POM versions? I'd lean on updating
JIRA based on the current version history (and maybe even to 3.6.0 to
align
