Re: Mojo MavenProject reload

2014-02-27 Thread Jörg Hohwiller
Hi, Do your SCM thing (e.g. switch) and then start a new maven build from there (e.g. via exec-maven-plugin). Regards Jörg Am 27.02.2014 04:28, schrieb Igor Fedorenko: No, not possible. MavenProject instances are read at the very beginning of the build and do not change during the build. -

Re: mvnDebug transport error 202: bind failed: Permission denied

2014-02-27 Thread Jörg Hohwiller
Am 27.02.2014 23:04, schrieb Jörg Hohwiller: My actual problem I want to trace down is this one: java.lang.NoSuchMethodError: org.apache.maven.project.MavenProject.getProjectBuilderConfiguration()Lorg/apache/maven/project/ProjectBuilderConfiguration; IMHO MavenProject.getProjectBuilderConfigur

Re: mvnDebug transport error 202: bind failed: Permission denied

2014-02-27 Thread Igor Fedorenko
If you are an Eclipse user, you may want to try my Maven Development Tools [1], which lets you debug through mojo and maven core code right from m2e workspace. There is no MavenProject#getProjectBuilderConfiguration in any version of Maven I checked (3.2.1, 3.1.2, 2.0.9), check current master for

mvnDebug transport error 202: bind failed: Permission denied

2014-02-27 Thread Jörg Hohwiller
Hi there, I am back on Mojo and trying to debug maven. However, it is simply not working: C:\consumer-maven-plugin>mvnDebug consumer:consumer Preparing to Execute Maven in Debug Mode ERROR: transport error 202: bind failed: Permission denied ["transport.c",L41] ERROR: JDWP Transport dt_socket f

Re: Exposing security vulnerability information (CVEs) when building with Maven

2014-02-27 Thread Paul Benedict
Maybe in model 5.0.0, if POM fragments are implemented (MNG-5102), this feature can be more seamless. If there was (1) a POM element that represented CVE information and (2) a repository out there that hosted independent fragments about the vulnerabilities, builds could automatically be warned/halt

Re: Exposing security vulnerability information (CVEs) when building with Maven

2014-02-27 Thread Jason van Zyl
The RedHat idea is a good one but the implementation is fairly poor insofar as it requires you to download an H2 database before you can actually check your build. I noticed that if the process is interrupted you are forced to download the database again. Good idea with the enforcer plugin, but

Re: Exposing security vulnerability information (CVEs) when building with Maven

2014-02-27 Thread Barrie Treloar
On 27 February 2014 21:17, Bernd Eckenfels wrote: > Hello Mark, > > Just wanted to point you to a redhat project which I recently discovered, as > it seems to have potential for this (even if the approach is not the most > decentralized one): > > The Victims Database maps JAR Signatures to known

Re: Exposing security vulnerability information (CVEs) when building with Maven

2014-02-27 Thread Bernd Eckenfels
Hello Mark, Just wanted to point you to a redhat project which I recently discovered, as it seems to have potential for this (even if the approach is not the most decentralized one): The Victims Database maps JAR Signatures to known vulnerabilities, if this is extended with maven coordinates

Exposing security vulnerability information (CVEs) when building with Maven

2014-02-27 Thread Mark Thomas
Hi, For those of you that don't know me, one of my roles at the ASF is as a member of the Apache Security Team. One of the common problems we face when processing a security vulnerability report is how to identify the projects that depend on the vulnerable library. What I wanted to explore with th