I just looked at the code. It is only adding the versioned class paths when
there is a module descriptor in the current source directory. I might be able
to put one in here, as a workaround.
> On Feb 12, 2019, at 2:47 PM, Robert Scholte wrote:
>
> I thought I had written an IT for it, but can'
I thought I had written an IT for it, but can't find it.
Looks like you found a bug.
Robert
On Tue, 12 Feb 2019 20:03:10 +0100, Russell Gold
wrote:
But it doesn’t appear to be working for me.
[INFO] --- maven-compiler-plugin:3.8.0:compile (java9) @ pfl-basic ---
[DEBUG] Configuring mojo
But it doesn’t appear to be working for me.
> [INFO] --- maven-compiler-plugin:3.8.0:compile (java9) @ pfl-basic ---
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile from plugin
> realm ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:3.8
Hi Russ,
There's no way to configure this, the plugin will do it for you[1]
thanks,
Robert
[1]
https://github.com/apache/maven-compiler-plugin/blob/master/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java#L328-L346
On Tue, 12 Feb 2019 18:56:52 +0100, Russell Gold
wrote:
Version 3.8.0 of the maven-compiler-plugin supports a multiReleaseOutput option
which can compile classes directly to the appropriate
META-INF/versions/{release} directory, which is very nice. What I don’t see,
though, is how to tell it to use the previous release as its dependency. That
is, gi
Adding the plugin won't be enough, you'll have explicitly name the mojo in
an . What defaultPhase does is that you don't have to specify a
in the .
Actually, you can even list all mojos in the same even if
they're bound to different default phases:
…
…
…
mojo1
You still need to declare an execution for the plugin in your pom.xml. In
the execution you don't need to declare the phase though as you have a
default one defined in the mojo.
/Anders
On Tue, Feb 12, 2019 at 9:40 AM Dirk Olmes wrote:
> Hi,
>
> I'm creating a Maven plugin using Java Annotation
Hi,
I'm creating a Maven plugin using Java Annotations and I'd like my
plugin to be bound to a default lifecycle phase so I don't have to
explicitly bind it to a phase in my regular projects.
So far I use
@Mojo(name = "generate", defaultPhase = LifecyclePhase.GENERATE_SOURCES)
public class MyMoj
Greetings,
I'm Carmine, a researcher at the University of Zurich interested in
supporting developers working with CI/CD.
Among the benefits provided by Continuous Integration (CI), increased team
productivity and release frequency are perceived as the main advantages.
However, changes that contai
