On 08/04/18 02:04, Olivier Lamy wrote:
I have disabled it as there were some errors (not sure what) with using the
configfile provider plugin.
But yup good catch we definitely need to do it only for one jdk...

would be better...

not sure how to do the deploy at end as it was done previously by the maven
plugin. (probably someone need to write a plugin for this :-) )

did I miss something ? What do you mean by this?

Kind regards
Karl  Heinz Marbaise

On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rfscho...@apache.org> wrote:

Hi Olivier,

doesn't this mean that we get about 8 deployments (2 oses times 4 jdks) of
the same artifacts?
This is a potential problem for the metadata files.
Is it possible to do it really at the end by Jenkins?


On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:

This is an automated email from the ASF dual-hosted git repository.

olamy pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.

     from 50410a9  Add JDK 10 to the jdk default
      add 96afe26  auto deploy if we are currently on master branch
      new bb8b8c8  Merge pull request #1 from olamy/master

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

Summary of changes:
  vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
  1 file changed, 19 insertions(+), 11 deletions(-)

To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to