Am 2021-06-27 um 09:16 schrieb Mark Derricutt:
Interesting - updating to this version from 1.7.0 in my own plugin now
yields an NPE when creating a RepositorySystem - guess I know one thing I’m
working on this week :)
If you think this is a bug and you have a reproducer, please report it!
Than
Hi,
I am in the process of modularizing one of my projects and hit some
rather annoying limitations that I thought needed changes to my Maven
build and dependencies due to the way the Java module system works, but
it turned out that this is by design and there is a way out. Alan
Bateman sugge
Hi,
My English is poor, but I hope for help in this place.
I am trying to manipulate an org.apache.maven.model.Model via a maven extension
and at the same time create a new POM file. But unfortunately the new location
of the POM file does not apply. The plugins (e.g. maven-deploy-plugin) still
Hi,
I think flatten-maven-plugin is doing something like that, see:
https://github.com/mojohaus/flatten-maven-plugin/blob/4efae7e8d180e838ff25a1daffab712166911328/src/main/java/org/codehaus/mojo/flatten/FlattenMojo.java#L224
Cheers,
Falko
Hello all!
I have the same issue as back from 2009[1]. I'm not sure if it ever
worked or even supposed to. I thought something is off with my project
(single pom). However, I see the same issue even if I use maven
archetype to generate a new one.
I see that JIRA moved to https://issues.apache.org
Thanks, Falko. In my question I mentioned the flatten plugin with snippets of
code. Can I access MavenProject in a Maven Extension? The flatten plugin uses
this Injection @Parameter (defaultValue = "$ {project}", readonly = true,
required = true)
MavenProject project;
What would the equiva
Thanks, Falko. In my question I mentioned the flatten plugin with snippets of
code. Can I access MavenProject in a Maven Extension? The flatten plugin uses
this Injection @Parameter (defaultValue = "$ {project}", readonly = true,
required = true)
MavenProject project;
What would the equiva
Hi,
To me, looking at javadoc or jxr output during "mvn site:run" is not supposed
to work: "mvn site:run" is here to help write markup for the site, to quickly
see the output when you update markdown/apt/... source
Why are you trying to use site:run to look at javadoc or jxr?
Notice, whatever
Sorry, I totally missed that flatten bit in your message.
You can access all projects via the MavenSession that get's passed in to your
extension.
See getProjects().
Cheers,
Falko
-
To unsubscribe, e-mail: users-unsubscr...@mav
Hello Hervé,
On Mon, Jun 28, 2021 at 1:51 PM, Hervé BOUTEMY wrote:
> To me, looking at javadoc or jxr output during "mvn site:run" is not supposed
> to work: "mvn site:run" is here to help write markup for the site, to quickly
> see the output when you update markdown/apt/... source
It is fin
10 matches
Mail list logo