Hello,
if somebody would confirm my changes are OK, I'd like to perform a release
of the maven-release-plugin - the last release is almost 4 years old.
На нд, 21.04.2019 г. в 13:29 ч. Petar Tahchiev
написа:
> Hi Robert,
> and thank you for your response. I have pushed a test which fails if I
>
Hi!
I resumed work on MSHARED-801 and I saw that for collecting dependencies I
need access to many aether classes. The current strategy is to shade the
necessary classes into the artifact-transfer jar file but this won't work
for collecting because it will actually force to use that classes of the
+1
Sylwester
niedz., 21 kwi 2019 o 09:08 Petar Tahchiev
napisał(a):
> I tested with our project. Seems good. +1 from me
>
> На сб, 20.04.2019 г. в 21:01 ч. Robert Scholte
> написа:
>
> > Hi,
> >
> > We solved 13 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=
On Sun 21 Apr 2019 at 16:24, Enrico Olivelli wrote:
> Hi,
> I want to commit this breaking change [1] in checkstyle plugin,
> that is the upgrade [2] to latest checkstyle (8.x) and thus the making
> Java 8 the minimum version for the plugin.
>
> Currently I have 3.0.1-SNAPSHOT on master,
> I thin
is someone working on it?
the code is here: https://github.com/apache/maven-jenkins-lib
PRs welcome
The deploy has to happen only from master branch, once the build and ITs run
on every platform and JDK is ok
Then the strategy to choose which build (platform and JDK) has to be deployed
will have
I must confess disabling the IT on Windows is just lazyness to avoid a stupid
failure on CI
don't hesitate to revert if you really prefer to find and fix the root cause:
I don't have any problem with job well done by others ;)
Regards,
Hervé
Le dimanche 21 avril 2019, 12:45:12 CEST Robert Sch
Hi,
I want to commit this breaking change [1] in checkstyle plugin,
that is the upgrade [2] to latest checkstyle (8.x) and thus the making
Java 8 the minimum version for the plugin.
Currently I have 3.0.1-SNAPSHOT on master,
I think I need to move to 3.1.0-SNAPSHOT.
Is is better to bump the versi
+1
I was able to check the binary with a build I did with Open JDK 7 latest from
my Linux box (while it had been built with old Oracle JDK 7u80 on Windows).
I opened and fixed MPMD-285 since there was a non-reproducible bit where we
have a solution.
Regards,
Hervé
Le jeudi 11 avril 2019, 20:3
The issue on Jenkins has to do with the @ in the path of the workspace. SCM
parses this as a username/password separator.
Based on the SCM Implementation for subversion[1] that's a bug: scm:svn:file://
doesn't support username+password
Robert
[1] https://maven.apache.org/scm/subversion.html
[h
Hi Robert,
and thank you for your response. I have pushed a test which fails if I
revert my changes. The test passes with my changes. Please could someone
have a look at what I have changed and if it is OK.
Thank you.
На нд, 21.04.2019 г. в 12:27 ч. Robert Scholte
написа:
> Hi Petar,
>
> IIRC t
Hi Petar,
IIRC the idea behind the original setup was to keep the original builder
immutable and to keep a clear separation between what was configured by
descriptor and what by commandline.
And IIRC there's a set of properties that should NEVER be overridden via
commandline.
Also, if this is
On 2019/04/08 11:21:19, Paul Hammant wrote:
> There's shades of https://en.wikipedia.org/wiki/XY_problem to what you>
> posting. I, for one, an interested in what your trying to make after
you've>
> solved this problem :)>
It's not trivial. There is a tool called "bnd" that supports the
developme
I tested with our project. Seems good. +1 from me
На сб, 20.04.2019 г. в 21:01 ч. Robert Scholte
написа:
> Hi,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317122&version=12340346&styleName=Text
>
> There are still a couple of issues left in JIR
13 matches
Mail list logo
