RFR: versions-maven-plugin issue 356

Hello! Could someone take a look at https://github.com/mojohaus/versions-maven-plugin/issues/356 ? I haven't yet opened a PR, but I can do that if necessary. -- Mark Raynsford | http://www.io7m.com pgpsvr_N0n09w.pgp Description: OpenPGP digital signature

How are artifacts resolved from the reactor via LegacyRepositorySystem?

Hello. I'm currently trying to debug https://issues.apache.org/jira/browse/MASSEMBLY-848 and am reaching this line: https://github.com/apache/maven-plugins/blob/trunk/maven-assembly-plugin/src/main/java/org/apache/maven/plugins/assembly/artifact/DefaultDependencyResolver.java#L232 I'm debugging

Re: Running a plugin integration test from an IDE?

On 2017-02-16T18:32:10 +0100 "Robert Scholte" wrote: > If you have a project under maven-assembly-plugin/src/it/projects/bugs and > want to debug it, try: > > mvn verify -Prun-its -Dinvoker.mavenExecutable=mvnDebug > -Dinvoker.test=projects/bugs (point to test-directory) > > You'll see that

Re: Running a plugin integration test from an IDE?

Hello! I think I may have explained myself poorly. I'm not really looking for a general way to take a project and make it debuggable. I'm looking for a concrete way to work on a bug in the Assembly plugin. On 2017-02-16T13:39:33 + John Patrick wrote: > this might work and is what I get int

Re: Running a plugin integration test from an IDE?

On 2017-02-14T15:13:46 + org.apache.maven.u...@io7m.com wrote: > > I can't work out how to run this integration > test from an IDE (Intellij IDEA, in this case) so that I can try to > step through the execution with a debugger and see what's going on. So nobody knows how to run an integration

Running a plugin integration test from an IDE?

Hello. I'm having a look at working on https://issues.apache.org/jira/browse/MASSEMBLY-848 but I've never worked on any of the "official" Maven plugins before. It seems like the most obvious way to start working on the bug is to introduce the files attached to that report as an integration test in

Re: Issues with independent module versions

I've filed an issue against the Assembly plugin, although the Dependency plugin is also affected. https://issues.apache.org/jira/browse/MASSEMBLY-848 Maven itself appears to resolve the dependencies correctly, but evidently some plugins don't go via the same mechanism. M pgpGZ63hG9L65.pgp Desc

Re: Issues with independent module versions

On 2017-02-07T11:47:16 + org.apache.maven.u...@io7m.com wrote: > Here's an example project that uses version ranges to specify > intra-project dependencies between modules: > > https://github.com/io7m/independent-versioning-20170207 Interestingly, these issues don't arise with older Maven

Issues with independent module versions

Hello. I'm investigating the use of independent module versions in a multi-module project and am finding that things seem to work poorly. By this, I mean that the modules within a project have different version numbers and refer to each other via version ranges. Here's an example project that use

Re: Using the Maven API outside of a plugin?

On 2017-01-01T17:37:26 +0100 "Robert Scholte" wrote: > Hi, > > doing this outside the context of Maven is probably hard to do. What you > at least need is the maven-artifact-resolver[1] (that's the project where > the development of Eclipses Aether[2] continues), though is has not been > r

Using the Maven API outside of a plugin?

Apologies if this isn't an appropriate subject for this list. I tried the user list and got no response. Perhaps it is more of a development question... Hello. I'm writing a small program to analyze the dependencies of Maven projects. There are numerous examples of how to do this from within a Ma