Re: [maven] 01/01: [MNG-6213] Validate scope in dependencyManagement

[Enrico Olivelli]

Il sab 29 dic 2018, 00:36 Michael Osipov  ha scritto:

> Am 2018-12-29 um 00:20 schrieb Enrico Olivelli:
> > Il ven 28 dic 2018, 23:40  ha scritto:
> >
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> michaelo pushed a commit to branch MNG-6213
> >> in repository https://gitbox.apache.org/repos/asf/maven.git
> >>
> >> commit 859e344f4d5f7bfa00caf7343ea6554138e9dcf7
> >> Author: Michael Warnecke <13...@nordakademie.de>
> >> AuthorDate: Sat Sep 23 18:37:09 2017 +0200
> >>
> >>  [MNG-6213] Validate scope in dependencyManagement
> >>
> >>  This closes #131
> >> ---
> >>   .../model/validation/DefaultModelValidator.java| 10 ++-
> >>   .../validation/DefaultModelValidatorTest.java  | 10 +++
> >>   .../validation/bad-dependency-management-scope.xml | 72
> >> ++
> >>   3 files changed, 90 insertions(+), 2 deletions(-)
> >>
> >> diff --git
> >>
> a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> >>
> b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> >> index 1c84776..f58d03a 100644
> >> ---
> >>
> a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> >> +++
> >>
> b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> >> @@ -105,13 +105,13 @@ public class DefaultModelValidator
> >> + ", the parent element cannot have
> the
> >> same groupId:artifactId as the project.",
> >> parent );
> >>   }
> >> -
> >> +
> >>   if ( equals( "LATEST", parent.getVersion() ) || equals(
> >> "RELEASE", parent.getVersion() ) )
> >>   {
> >>   addViolation( problems, Severity.WARNING,
> Version.BASE,
> >> "parent.version", null,
> >> "is either LATEST or RELEASE (both of
> them
> >> are being deprecated)", parent );
> >>   }
> >> -
> >> +
> >>   }
> >>
> >>   if ( request.getValidationLevel() >=
> >> ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_2_0 )
> >> @@ -598,6 +598,12 @@ public class DefaultModelValidator
> >>
> >>   validateEffectiveModelAgainstDependency( prefix,
> >> problems, m, d, request );
> >>   }
> >> +else
> >> +{
> >> +validateEnum( prefix + "scope", problems,
> >> Severity.WARNING, Version.V20, d.getScope(),
> >> +  d.getManagementKey(), d, "provided",
> >> "compile", "runtime", "test", "system",
> >> +  "import" );
> >>
> >
> > Don't we have a constant for the list of available scopes?
>
> None which I am aware of. Watch carefully because regular deps don't
> have "import" scope.
>

Oh I see,
Thanks for your advice

Enrico

> --


-- Enrico Olivelli

Re: VOTE] Release Maven Wagon version 3.3.0

[Dan Tran]

Revert  WAGON-537  fixes the
issue.

-D

On Fri, Dec 28, 2018 at 2:25 PM Michael Osipov  wrote:

> Am 2018-12-28 um 20:32 schrieb Dan Tran:
> > The regression was introduced by
> > https://jira.apache.org/jira/browse/WAGON-537 which has changes at
> > AbstractWagon used by all providers.  Best to localize the change for
> > http provider only
> >
> > note: wagon-maven-plugin uses its own wagon-ssh, but still share the base
> > class with its maven runtime. that is why no issue found when running
> with
> > maven 3.6.0, but only with maven 3.6.1 building with the latest wagon (
> ie
> > 3.3.0 at staging)
>
> That's a pointer. Did you bisect? Did you revert the changes on
> AbstractWagon and see that it works again?
>
> > On Fri, Dec 28, 2018 at 6:10 AM Tibor Digana 
> wrote:
> >
> >> +1
> >>
> >> On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov 
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> We solved 4 issues:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
> >>>
> >>> There are still a couple of issues left in JIRA:
> >>>
> >>>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >>>
> >>> Staging repo:
> >>> https://repository.apache.org/content/repositories/maven-1481/
> >>>
> >>>
> >>
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
> >>>
> >>> Source release checksum(s):
> >>> wagon-3.3.0-source-release.zip
> >>> sha512:
> >>>
> >>>
> >>
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
> >>>
> >>> Staging site:
> >>> https://maven.apache.org/wagon-archives/wagon-LATEST/
> >>>
> >>> Guide to testing staged releases:
> >>> http://maven.apache.org/guides/development/guide-testing-releases.html
> >>>
> >>> Vote open for 72 hours.
> >>>
> >>> [ ] +1
> >>> [ ] +0
> >>> [ ] -1
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
> >>
> >
>
>

Re: [maven] 01/01: [MNG-6213] Validate scope in dependencyManagement

[Michael Osipov]

Am 2018-12-29 um 00:20 schrieb Enrico Olivelli:

Il ven 28 dic 2018, 23:40  ha scritto:


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

michaelo pushed a commit to branch MNG-6213
in repository https://gitbox.apache.org/repos/asf/maven.git

commit 859e344f4d5f7bfa00caf7343ea6554138e9dcf7
Author: Michael Warnecke <13...@nordakademie.de>
AuthorDate: Sat Sep 23 18:37:09 2017 +0200

 [MNG-6213] Validate scope in dependencyManagement

 This closes #131
---
  .../model/validation/DefaultModelValidator.java| 10 ++-
  .../validation/DefaultModelValidatorTest.java  | 10 +++
  .../validation/bad-dependency-management-scope.xml | 72
++
  3 files changed, 90 insertions(+), 2 deletions(-)

diff --git
a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
index 1c84776..f58d03a 100644
---
a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
+++
b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
@@ -105,13 +105,13 @@ public class DefaultModelValidator
+ ", the parent element cannot have the
same groupId:artifactId as the project.",
parent );
  }
-
+
  if ( equals( "LATEST", parent.getVersion() ) || equals(
"RELEASE", parent.getVersion() ) )
  {
  addViolation( problems, Severity.WARNING, Version.BASE,
"parent.version", null,
"is either LATEST or RELEASE (both of them
are being deprecated)", parent );
  }
-
+
  }

  if ( request.getValidationLevel() >=
ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_2_0 )
@@ -598,6 +598,12 @@ public class DefaultModelValidator

  validateEffectiveModelAgainstDependency( prefix,
problems, m, d, request );
  }
+else
+{
+validateEnum( prefix + "scope", problems,
Severity.WARNING, Version.V20, d.getScope(),
+  d.getManagementKey(), d, "provided",
"compile", "runtime", "test", "system",
+  "import" );



Don't we have a constant for the list of available scopes?


None which I am aware of. Watch carefully because regular deps don't 
have "import" scope.


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

Re: [maven] 01/01: [MNG-6213] Validate scope in dependencyManagement

[Enrico Olivelli]

Il ven 28 dic 2018, 23:40  ha scritto:

> This is an automated email from the ASF dual-hosted git repository.
>
> michaelo pushed a commit to branch MNG-6213
> in repository https://gitbox.apache.org/repos/asf/maven.git
>
> commit 859e344f4d5f7bfa00caf7343ea6554138e9dcf7
> Author: Michael Warnecke <13...@nordakademie.de>
> AuthorDate: Sat Sep 23 18:37:09 2017 +0200
>
> [MNG-6213] Validate scope in dependencyManagement
>
> This closes #131
> ---
>  .../model/validation/DefaultModelValidator.java| 10 ++-
>  .../validation/DefaultModelValidatorTest.java  | 10 +++
>  .../validation/bad-dependency-management-scope.xml | 72
> ++
>  3 files changed, 90 insertions(+), 2 deletions(-)
>
> diff --git
> a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> index 1c84776..f58d03a 100644
> ---
> a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> +++
> b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
> @@ -105,13 +105,13 @@ public class DefaultModelValidator
>+ ", the parent element cannot have the
> same groupId:artifactId as the project.",
>parent );
>  }
> -
> +
>  if ( equals( "LATEST", parent.getVersion() ) || equals(
> "RELEASE", parent.getVersion() ) )
>  {
>  addViolation( problems, Severity.WARNING, Version.BASE,
> "parent.version", null,
>"is either LATEST or RELEASE (both of them
> are being deprecated)", parent );
>  }
> -
> +
>  }
>
>  if ( request.getValidationLevel() >=
> ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_2_0 )
> @@ -598,6 +598,12 @@ public class DefaultModelValidator
>
>  validateEffectiveModelAgainstDependency( prefix,
> problems, m, d, request );
>  }
> +else
> +{
> +validateEnum( prefix + "scope", problems,
> Severity.WARNING, Version.V20, d.getScope(),
> +  d.getManagementKey(), d, "provided",
> "compile", "runtime", "test", "system",
> +  "import" );
>

Don't we have a constant for the list of available scopes?

Enrico


+}
>  }
>  }
>  }
> diff --git
> a/maven-model-builder/src/test/java/org/apache/maven/model/validation/DefaultModelValidatorTest.java
> b/maven-model-builder/src/test/java/org/apache/maven/model/validation/DefaultModelValidatorTest.java
> index 3f31526..a9d4c00 100644
> ---
> a/maven-model-builder/src/test/java/org/apache/maven/model/validation/DefaultModelValidatorTest.java
> +++
> b/maven-model-builder/src/test/java/org/apache/maven/model/validation/DefaultModelValidatorTest.java
> @@ -339,6 +339,16 @@ public class DefaultModelValidatorTest
>  assertTrue( result.getWarnings().get( 1 ).contains( "test:g" ) );
>  }
>
> +public void testBadDependencyManagementScope()
> +throws Exception
> +{
> +SimpleProblemCollector result = validate(
> "bad-dependency-management-scope.xml" );
> +
> +assertViolations( result, 0, 0, 1 );
> +
> +assertContains( result.getWarnings().get( 0 ), "test:g" );
> +}
> +
>  public void testBadDependencyVersion()
>  throws Exception
>  {
> diff --git
> a/maven-model-builder/src/test/resources/poms/validation/bad-dependency-management-scope.xml
> b/maven-model-builder/src/test/resources/poms/validation/bad-dependency-management-scope.xml
> new file mode 100644
> index 000..6b37a85
> --- /dev/null
> +++
> b/maven-model-builder/src/test/resources/poms/validation/bad-dependency-management-scope.xml
> @@ -0,0 +1,72 @@
> +
> +
> +
> +  4.0.0
> +  aid
> +  gid
> +  0.1
> +
> +  
> +
> +  
> +test
> +a
> +0.2
> +  
> +  
> +test
> +b
> +0.2
> +compile
> +  
> +  
> +test
> +c
> +0.2
> +runtime
> +  
> +  
> +test
> +d
> +0.2
> +test
> +  
> +  
> +test
> +e
> +0.2
> +provided
> +  
> +  
> +test
> +f
> +0.2
> +import
> +  
> +  
> +test
> +g
> +1
> +pom
> +include
> +  
> +
> +  
> +
>
> --


-- Enrico Olivelli

Re: VOTE] Release Maven Wagon version 3.3.0

[Michael Osipov]

Am 2018-12-28 um 20:32 schrieb Dan Tran:

The regression was introduced by
https://jira.apache.org/jira/browse/WAGON-537 which has changes at
AbstractWagon used by all providers.  Best to localize the change for
http provider only

note: wagon-maven-plugin uses its own wagon-ssh, but still share the base
class with its maven runtime. that is why no issue found when running with
maven 3.6.0, but only with maven 3.6.1 building with the latest wagon ( ie
3.3.0 at staging)


That's a pointer. Did you bisect? Did you revert the changes on 
AbstractWagon and see that it works again?



On Fri, Dec 28, 2018 at 6:10 AM Tibor Digana  wrote:


+1

On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov 
wrote:


Hi,

We solved 4 issues:



https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436


There are still a couple of issues left in JIRA:



https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved


Staging repo:
https://repository.apache.org/content/repositories/maven-1481/



https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip


Source release checksum(s):
wagon-3.3.0-source-release.zip
sha512:



c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560


Staging site:
https://maven.apache.org/wagon-archives/wagon-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

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









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

Re: VOTE] Release Maven Wagon version 3.3.0

[Dan Tran]

The regression was introduced by
https://jira.apache.org/jira/browse/WAGON-537 which has changes at
AbstractWagon used by all providers.  Best to localize the change for
http provider only

note: wagon-maven-plugin uses its own wagon-ssh, but still share the base
class with its maven runtime. that is why no issue found when running with
maven 3.6.0, but only with maven 3.6.1 building with the latest wagon ( ie
3.3.0 at staging)

-D


On Fri, Dec 28, 2018 at 6:10 AM Tibor Digana  wrote:

> +1
>
> On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov 
> wrote:
>
> > Hi,
> >
> > We solved 4 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1481/
> >
> >
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
> >
> > Source release checksum(s):
> > wagon-3.3.0-source-release.zip
> > sha512:
> >
> >
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
> >
> > Staging site:
> > https://maven.apache.org/wagon-archives/wagon-LATEST/
> >
> > Guide to testing staged releases:
> > http://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Is it possible to make a parameter configurable ONLY via its alias?

[Tad Cordle]

I'm working on a plugin
 that
has nested parameters, and I'd like to introduce aliases to give people the
option of more concise configuration. For example, instead of writing:


  
baseImage

  user
  pass

  


they can instead write:


  baseImage
  user
  pass


However, it doesn't seem to be possible to declare aliases directly on
nested parameters. My workaround for this is to create a new top-level
field for each parameter. For example, the original configuration is
possible using this in the mojo:

public static class AuthConfiguration {
  @Parameter private String username;
  @Parameter private String password;
}
public static class FromConfiguration {
  @Parameter private String image;
  @Parameter private AuthConfiguration auth = new AuthConfiguration();
}
@Parameter private FromConfiguration from = new FromConfiguration();

And to create an alias, I add a new field, and choose one of the values in
the getter:

@Parameter(alias = "from.image")
private String fromImageAlias;

String getFromImage() {
  if (fromImageAlias != null) {
return fromImageAlias;
  }
  return from.image;
}

This works, but since the alias is just an alias and not a replacement for
the field name, it's still possible to configure the parameter using the
name of the field. e.g.


  baseImage


Is it somehow possible to expose a parameter only by its alias, and
disallow configuration using the field name? Or even better, is there a way
of configuring aliases on nested parameters that I don't know about?

P.S. I notice the maven docs

 say "nested bean injection requires Sisu or JSR330 annotations". Can this
be used to accomplish what I'm looking for, and if so how?

Re: [maven-jenkins-lib] branch master updated: Activate sonarqube on first project

[Robert Scholte]

Already done :)

But contacting the SonarQube Administrator might be interesting too.

On Fri, 28 Dec 2018 13:40:54 +0100, Enrico Olivelli   
wrote:



Robert,
I think this commit is breaking all of the builds, like this:
https://builds.apache.org/job/maven-box/job/maven-assembly-plugin/job/MASSEMBLY-901/

[ERROR] Failed to execute goal
org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254:sonar
(default-cli) on project maven-assembly-plugin: You're not authorized
to execute any SonarQube analysis. Please contact your SonarQube
administrator. -> [Help 1]

Can we rollback this change ?
Enrico

Il giorno ven 28 dic 2018 alle ore 12:47  ha  
scritto:


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

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


The following commit(s) were added to refs/heads/master by this push:
 new 852083f  Activate sonarqube on first project
852083f is described below

commit 852083f271f8ad153ee6e2c4b40c2d43adbdd5c3
Author: rfscholte 
AuthorDate: Fri Dec 28 12:45:30 2018 +0100

Activate sonarqube on first project
---
 vars/asfMavenTlpPlgnBuild.groovy | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/vars/asfMavenTlpPlgnBuild.groovy  
b/vars/asfMavenTlpPlgnBuild.groovy

index 3c3d212..ca8658c 100644
--- a/vars/asfMavenTlpPlgnBuild.groovy
+++ b/vars/asfMavenTlpPlgnBuild.groovy
@@ -121,6 +121,8 @@ def doCreateTask( os, jdk, maven, tasks, first,  
plan, taskContext )

   ]
   if (!first) {
 cmd += '-Dfindbugs.skip=true'
+  } else {
+cmd += 'sonar:sonar'
   }
   if (jdk == '7') {
 // Java 7u80 has TLS 1.2 disabled by default: need to explicitely  
enable




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


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

Re: VOTE] Release Maven Wagon version 3.3.0

[Tibor Digana]

+1

On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov  wrote:

> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12344436
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1481/
>
> https://repository.apache.org/content/repositories/maven-1481/org/apache/maven/wagon/wagon/3.3.0/wagon-3.3.0-source-release.zip
>
> Source release checksum(s):
> wagon-3.3.0-source-release.zip
> sha512:
>
> c467bf8d9f5b54602f53ed34e117753f48cf25b611c79dbbba55706ce34a6bb0dec65447a84d6dc5122615147fe4ce19102a94a37d4a0b3a15382aa7fdba7560
>
> Staging site:
> https://maven.apache.org/wagon-archives/wagon-LATEST/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [maven-jenkins-lib] branch master updated: Activate sonarqube on first project

[Enrico Olivelli]

Robert,
I think this commit is breaking all of the builds, like this:
https://builds.apache.org/job/maven-box/job/maven-assembly-plugin/job/MASSEMBLY-901/

[ERROR] Failed to execute goal
org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254:sonar
(default-cli) on project maven-assembly-plugin: You're not authorized
to execute any SonarQube analysis. Please contact your SonarQube
administrator. -> [Help 1]

Can we rollback this change ?
Enrico

Il giorno ven 28 dic 2018 alle ore 12:47  ha scritto:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> rfscholte pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
>  new 852083f  Activate sonarqube on first project
> 852083f is described below
>
> commit 852083f271f8ad153ee6e2c4b40c2d43adbdd5c3
> Author: rfscholte 
> AuthorDate: Fri Dec 28 12:45:30 2018 +0100
>
> Activate sonarqube on first project
> ---
>  vars/asfMavenTlpPlgnBuild.groovy | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/vars/asfMavenTlpPlgnBuild.groovy 
> b/vars/asfMavenTlpPlgnBuild.groovy
> index 3c3d212..ca8658c 100644
> --- a/vars/asfMavenTlpPlgnBuild.groovy
> +++ b/vars/asfMavenTlpPlgnBuild.groovy
> @@ -121,6 +121,8 @@ def doCreateTask( os, jdk, maven, tasks, first, plan, 
> taskContext )
>]
>if (!first) {
>  cmd += '-Dfindbugs.skip=true'
> +  } else {
> +cmd += 'sonar:sonar'
>}
>if (jdk == '7') {
>  // Java 7u80 has TLS 1.2 disabled by default: need to explicitely enable
>

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

Re: [VOTE] Release Apache Maven Shared Component: Maven Dependecy Analyzer Version 1.11.1

[Olivier Lamy]

+1

On Wed, 26 Dec 2018 at 08:28, Karl Heinz Marbaise  wrote:

> Hi,
>
> We solved 1 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12344667
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1480/
>
> https://repository.apache.org/content/repositories/maven-1480/org/apache/maven/shared/maven-dependency-analyzer/1.11.1/maven-dependency-analyzer-1.11.1-source-release.zip
>
> Source release checksum(s):
> maven-dependency-analyzer-1.11.1-source-release.zip sha512:
>
> 7d8880bac7cfb5f9f01f0b82e6d1dc1b9a4e0f79e0c76f9d807182fcad5e3e8c57c0c019cb1177b87a1e85f92aff3770585422be691f5cfafb529e633af35600
>
> Staging site:
> http://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven Shared Component: Maven Dependecy Analyzer Version 1.11.1

[Hervé BOUTEMY]

+1

notice: working on reproducible builds for the JVM to avoid such issue in the 
future (= published binary that has an issue)
stay tuned...

Regards,

Hervé

Le mardi 25 décembre 2018, 23:28:15 CET Karl Heinz Marbaise a écrit :
> Hi,
> 
> We solved 1 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12344667
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20XX%20AND%
> 20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1480/
> https://repository.apache.org/content/repositories/maven-1480/org/apache/mav
> en/shared/maven-dependency-analyzer/1.11.1/maven-dependency-analyzer-1.11.1-
> source-release.zip
> 
> Source release checksum(s):
> maven-dependency-analyzer-1.11.1-source-release.zip sha512:
> 7d8880bac7cfb5f9f01f0b82e6d1dc1b9a4e0f79e0c76f9d807182fcad5e3e8c57c0c019cb11
> 77b87a1e85f92aff3770585422be691f5cfafb529e633af35600
> 
> Staging site:
> http://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Kind regards
> Karl Heinz Marbaise
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org





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