Hi,
master seems by far enough to me, and I think support for specific other
branches should be considered in another future step if it happens to be
requested one day.
About nightly, I think it's usually not such a good rule. I wrote about it
some time ago when I started to deal with release
+1 for master and nightly, timezone is not so important
Enrico
Il gio 10 gen 2019, 21:44 Stephen Connolly
ha scritto:
> I say if we are doing automatic snapshot deployment, master branch only and
> either weekly or daily or on every commit... pick one for all our projects.
>
> Other branches
As I wrote in many Jira issues over years on this topic, I'm not in favor of
that
To me, staying with the same default plugins versions from Maven version to
Maven version is a feature: nobody should expect to change his Maven version
to change the plugins versions
The best practice is to
I say if we are doing automatic snapshot deployment, master branch only and
either weekly or daily or on every commit... pick one for all our projects.
Other branches would just confuse things so keep them as manual deployment
and if doing that require the branch name included in the version
We already had this discussion so many times and it always turns to non
ended complicated discussion with very complicated cases which NEVER happen
here
So the most important is: We must take it easy and avoid overthinking!.
+1 for every night a master snapshot or every master changes.
but
+1 for upgrading all of the plugins
+1 for 3.7.0
Many plugins released recently have improvements in speed and jdk support
Having a new release with all greatest and latest versions will be
very appreciated by users
Enrico
Il giorno gio 10 gen 2019 alle ore 20:50 Stephen Connolly
ha scritto:
>
No reason that we cannot call the next release 3.7.0 and include the bump,
mind you
On Thu 10 Jan 2019 at 16:31, Anders Hammar wrote:
> IMHO it shouldn't be done in a patch release, but rather a minor release
> (3.7.0).
>
> /Anders (mobile)
>
> Den tors 10 jan. 2019 17:09 skrev Tibor Digana :
>
I would like to enable Travis on other plugins, maybe I can do it on
plugins which have active prs
Okay?
Enrico
Il lun 7 gen 2019, 02:46 Manfred Moser ha
scritto:
> Fair enough. If its just for outside contributor PRs I am agree with not
> owning the risk ;-)
>
> Stephen Connolly wrote on
Ping
Il dom 6 gen 2019, 13:27 Robert Scholte ha scritto:
> Brian,
>
> can you pick this up?
>
> thanks,
> Robert
>
> On Sat, 05 Jan 2019 12:11:41 +0100, Enrico Olivelli
>
> wrote:
>
> > Can any admin create this project ?
> > for Maven Scripting Plugin
> >
how about just deploy nightly snapshot of active 'main' branch ( ie master)?
-D
On Thu, Jan 10, 2019 at 9:03 AM Robert Scholte wrote:
> Now that we use branches actively, it is way more important where a
> SNAPSHOT is coming from.
> I've seen it too often that people thought they were testing
Now that we use branches actively, it is way more important where a
SNAPSHOT is coming from.
I've seen it too often that people thought they were testing with a
version from a specific branch, but that it was redeployed with another
version.
The first steps are done to rewrite the pom-file
IMHO it shouldn't be done in a patch release, but rather a minor release
(3.7.0).
/Anders (mobile)
Den tors 10 jan. 2019 17:09 skrev Tibor Digana :
> Why we use old versions in default-bindings.xml?
> Can we update all versions in 3.6.1 release?
>
> Here is MNG-6557 which is related to Surefire
Why we use old versions in default-bindings.xml?
Can we update all versions in 3.6.1 release?
Here is MNG-6557 which is related to Surefire but I guess this Jira issue
can be freely related to all plugins.
WDYT?
Any objections to update all plugins and assign this issue in 3.6.1?
Cheers
Tibor
On Thu, 10 Jan 2019 at 09:11, Mickael Istria wrote:
> Hi,
>
> Eclipse m2e, as a consumer of Maven as a library, would love to see the
> latest HEAD from master published automatically as SNAPSHOTs soon after
> every change is made. This seems like a requirement to enable continuous
> feedback
Hi,
Eclipse m2e, as a consumer of Maven as a library, would love to see the
latest HEAD from master published automatically as SNAPSHOTs soon after
every change is made. This seems like a requirement to enable continuous
feedback from m2e to Maven.
Publishing some other branches or commits
Hi all,
Final update about m2e coverage of Maven project: the full test suite now
reports coverage and reports are still visible at
https://sonarcloud.io/component_measures?id=m2e-covering-maven=coverage
. This can help to identify, by comparing it with plain Maven coverage
reports, which area of
The question is more what our policy is.
In my opinion you need one of two policies:
* snapshots are deployed manually
* snapshots are deployed automatically from a specific branch
We have used manual as our policy. If we change that’s fine, but we should
stop manual deployment and clarify the
17 matches
Mail list logo
