Re: Cannot Inject MavenRepositorySystem into my Plugin Mojo

2014-10-06 Thread Stuart McCulloch
The org.apache.maven.bridge package is not currently exposed to plugins from maven-core (see importMavenApi in DefaultClassRealmManager) which is why you get an exception trying to access it. Could you use the org.apache.maven.repository.RepositorySystem component instead? This would also be mo

RE: Cannot Inject MavenRepositorySystem into my Plugin Mojo

2014-10-06 Thread Robert Patrick
.. import org.apache.maven.repository.RepositorySystem; ... public class MyMojo extends Abstract Mojo { @Component protected RepositorySystem repositorySystem; ... works for me... -- Robert Patrick VP, FMW Platform Engineering, Oracle Corporation 7460 Warren Pkwy, Ste.

[GitHub] maven-surefire pull request: SUREFIRE-1101 Surefire does not shutd...

2014-10-06 Thread Tibor17
GitHub user Tibor17 opened a pull request: https://github.com/apache/maven-surefire/pull/51 SUREFIRE-1101 Surefire does not shutdown thread-pools programatically af... ...ter test run has finished. The threads executing tests in parallel should be shutdown after the test ru

Cannot Inject MavenRepositorySystem into my Plugin Mojo

2014-10-06 Thread Arnaud Derasse
Hello all, -- -- Short Version -- -- I am tryting to access MavenRepositorySystem from my mojo to call buildArtifactRepository() When executing the goal, I have a ClassDefNotFound error : [WARNING] Error injecting: com.enyx.maven.plugin.enyx_maven_p

Re: PR 24 for plexus-compiler

2014-10-06 Thread John Casey
Thanks, I'll give it a shot tomorrow most likely, and report back. -john On 10/05/2014 05:56 PM, Olivier Lamy wrote: Perso, I find using github really convenient. Moving somewhere else will take a lot of time.. (Maybe at least an independant github orga) (but ATM I don't have enough bandwith to

Re: svn commit: r1628003 - /maven/shared/trunk/maven-shared-utils/pom.xml

2014-10-06 Thread Robert Scholte
Hi Karl-Heinz, *I* think the Jira-issue should be removed. It suggests change in behavior which it doesn't and will only confuse users. In the end it is only a compile-time adjustment, at runtime the dependency will always be replaced with the executing Maven version. For housekeeping I don'