Found this JIRA at MDEPLOY
* https://issues.apache.org/jira/projects/MDEPLOY/issues/MDEPLOY-217
* https://issues.apache.org/jira/projects/MDEPLOY/issues/MDEPLOY-199
Looks the place to look for is at maven-resolver? which responsible to
download maven-metadata and calculate next build numbe
On Sat, 14 Sep 2019 07:17:16 +0200, Dan Tran wrote:
Still waiting for the maven dev team to chime in if there is possible
solution
Tamás is dev team member :)
I don't know which code is responsible for adding the buildnumer.
Personally I'd like to invest in MNG-5666[1], which should already
Dan, you know how we solved this problem, we wrote Jenkinsfile with
interactive GUI. The release manager of QA filled out the items in web GUI
of Jenkins, means Version, Deployment IP in QA machines and some build
options. Simply we moved the responsibility to the person who argued the
most about t
Any volunteer to work on a fix?
Enrico
Il sab 14 set 2019, 10:08 Jonathan Chen ha scritto:
> Hi,
>
> I didn't find a matching issue, so I raised MNG-6765 so that it can be
> tracked.
> https://issues.apache.org/jira/browse/MNG-6765
>
> Cheers.
> --
> Jonathan Chen
>
> On Sat, 14 Sep 2019 at 19
Hi,
I didn't find a matching issue, so I raised MNG-6765 so that it can be tracked.
https://issues.apache.org/jira/browse/MNG-6765
Cheers.
--
Jonathan Chen
On Sat, 14 Sep 2019 at 19:47, Jonathan Chen wrote:
>
> Hi,
>
> Thanks for that. Is there a JIRA reference for this bug?
>
> Cheers.
> --
Hi,
Thanks for that. Is there a JIRA reference for this bug?
Cheers.
--
Jonathan Chen
On Sat, 14 Sep 2019 at 17:39, Jeff MAURY wrote:
>
> This is a know case between tycho pomless and maven 3.6.2
>
> Le sam. 14 sept. 2019 à 05:26, Jonathan Chen a écrit :
>
> > Hi,
> >
> > I'm currently attem
