GitHub user ptahchiev opened a pull request:
https://github.com/apache/maven-release/pull/18
MRELEASE-985
This commit copies resolved snapshot dependencies system properties to the
release descriptor
and then checks if the those resolved snapshot dependencies contain the
SNAPSH
+1
Regards,
Hervé
Le mercredi 21 juin 2017, 20:16:08 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve
> rsion=12332979
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.or
I was thinking at something like the Maven Jenkins Seeding experiment [1] that
was done, with its DSL code [2]
IIUC, this new Jenkins feature could provide a more generic seeding?
Looks promising.
Whether we go with first or second option will be a matter of ETA and people
wanting to work on it
Am 2017-06-20 um 18:58 schrieb Guillaume Boué:
Yes, 3.0.0 is selected during conflict resolution. And this is part of
the issue: some classes of plexus-io 2.7.1, on which plexus-archiver 3.4
depends on, were removed in 3.0.0. So they are not present within the
resolved dependencies because 2.7.1
I'm fine with that:
style.color=[auto*|always|never]
the original PR is still based on a CLI option which I don't like because
all other style options are already and only controlled by system
properties.
I have to create a new branch if we can agree on this.
Robert
On Fri, 23 Jun 2017 16:
Am 2017-06-23 um 16:27 schrieb Robert Scholte:
MNG-6220: Add CLI options to control color output
by introducing system property style.color=[auto*|enabled|disabled]
This definitively needs polish and a value style like tree/grep. I left
several comments on the PR.
---
Looking for someone who can second the following issues:
MNG-6148: Can't package and assemble with JDK9/Jigsaw
MNG-6127: Fix plugin execution configuration interference
MNG-6220: Add CLI options to control color output
by introducing system property style.color=[auto*|enabled|disabled]
than
