+1 (non binding)
Tested on a few work projects
Le jeu. 14 nov. 2019 à 03:32, Tibor Digana a
écrit :
> +1: all is successful
> Karl, this plugin supports many packaging types. Would it make sense to
> have a native support of all of them in the POM like this
> par ?
>
> On Mon, Nov 11, 2019 at 9:
+1: all is successful
Karl, this plugin supports many packaging types. Would it make sense to
have a native support of all of them in the POM like this
par ?
On Mon, Nov 11, 2019 at 9:03 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/Release
Let's not mention JDK as a good example today because of:
1. almost every release was about the switch-case, and little improvement
in Lambda. Now it looks like they do not have language architect although
we know that Oracle has the architect.
2. Valhalla can be enabled in CLI but this produced in
On Wed 13 Nov 2019 at 19:29, Robert Scholte wrote:
> The name of the branch contains MNG-5668, but it contains much more.
> I'd likely lead to comments like "great", without being explicit saying
> which part(s).
> I am aware there's all proposals touch the same code, but can be released
> isolat
I'm hearing a lot of subtly different descriptions of what different
developers and subprojects use the term "milestone" for.
It's certainly reasonable to have a major version bump in the plugin
and drop support for Maven 2.0. The goal that the plugin major version
should match the Maven major ver
On Wed 13 Nov 2019 at 19:29, Robert Scholte wrote:
> The name of the branch contains MNG-5668, but it contains much more.
> I'd likely lead to comments like "great", without being explicit saying
> which part(s).
> I am aware there's all proposals touch the same code, but can be released
> isolat
The name of the branch contains MNG-5668, but it contains much more.
I'd likely lead to comments like "great", without being explicit saying which
part(s).
I am aware there's all proposals touch the same code, but can be released
isolated from each other.
e.g. if the enums-value are changed to "p
Robert Scholte:
In case of plugins going from 2.x to 3.x is a huge step and an opportunity to
break backwards compatibility.
Most important, as mentioned by Stephen, is dropping Maven 2 support.
Next, this is the best chance to remove deprecated parameters, refactoring
code, etc, before we're bo
i forgot to say that the work in Surefire splits to multiple Mx which are
dependent.
so the milestones are useful for the Surefire, IMO.
not sure how about in the oher plugins,, enforcer, release plugin, etc. but
they may have different visions with the releases.
On Wed, Nov 13, 2019 at 3:26 PM Ti
I think i can see the complexity the best in Surefire. That's why we have
these milestones because finally we have to break some compatibility in
order to fix the bugs.
Let me pls explain why.
The thing is that we are in the situation where we cannot fix the bugs
without changing e.g. the API for
Oh I forgot, Surefire further complicates things as it has an API that
needs to be implemented by providers, so we need to try and encode that
API's breaking changes into our version number also... a lot of stuff to
try and encode in a version number... I fear semver is not up to the job
On Wed,
I think the fundamental problem here is that we (i.e. maven developers) do
not have a shared understanding of how we want to use version numbers.
There are a group of people who want to use semantic versioning such that
the major version is only incremented for "breaking" changes, minor version
fo
To my thinking, a release candidate is believed to be done. All
features are complete and no unshippable bugs are known. An RC is
posted to give users a chance to shake out any unknown bugs. If no
unknown bugs are found then the RC is the release, module a version
change.
A milestone, by contrast,
Hi,
We solved 43 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12344668
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%
I am going to send the Vote email in few minutes.
It took some time today because the Jacoco failed within
maven-javadoc-plugin which repeats the lifecycle and compilation.
Yesterday i pushed very important fix and updated the documentatio. Now it
is complete.
On Wed, Nov 13, 2019 at 1:05 PM Olivi
Awesome!
On Tue, 12 Nov 2019 at 9:39 pm, Tibor Digana wrote:
> Hi,
>
> There are altogether 43 bugfixes in the JIRA.
> I would like to start a new release Vote today evening.
>
> Kind regards,
> Tibor17
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
16 matches
Mail list logo
