The Apache Maven team is pleased to announce the release of the Maven
Fluido Skin, version 1.11.1.
https://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in your project's site configuration:
org.apache.maven.skins
maven-fluido-skin
1.11.1
Release Notes - Maven
Well, using the session for that would be much simpler... just my 5 cents
So you could use participant only to implement this "protection", but keep
using spy for the rest.
T
On Wed, Jun 29, 2022 at 1:24 PM François Guillot <
francoisguillo...@gmail.com> wrote:
> Hey,
>
> Thanks for all your
Hey,
Thanks for all your suggestions.
I don't like AbstractMavenLifecycleParticipant that much because it doesn't
offer fine-grained callbacks. Only sessionStar/End and projectsRead.
While EventSpy allows to hook into many more events fired by the
EventCatapult.
But this is just a detail.
Thanks
And one more thing
Migrate off from legacy Plexus XML
src/main/resources/META-INF/plexus/components.xml
and use JSR330 instead:
- add javax.inject:javax.inject:1 as dependency
- annotate your imple with @Singleton/@Named( "default" )
- use sisu-maven-plugin in the build to index annotated
Also, if you'd not use oldie EventSpy, but
AbstractMavenLifecycleParticipant instead, you'd gain access to session,
and would become even simpler:
just stick something with specific (to your extension, like G:A) key and
dummy value (Boolean,TRUE) into session.
And then you know: if that key IS
Howdy,
First of all, if you alter the maven classpath, there is not much Maven
itself can do (as it happens before maven happens). How are conflicting
classes handled depends on Java, not Maven.
So, I'd really just neglect the use of `maven.ext.class.path` (or adding
things to lib/ext). Using
jbossws project jaxws-tools-maven-plugin requires the updates in
maven-plugin-testing-harness-3.4.0-SNAPSHOT.
When is this version expected to go final
