How to set filesetManifestConfig from maven-assembly-plugin
Hi, is there a way to set the value filesetManifestConfig in src/main/java/org/codehaus/plexus/archiver/jar/JarArchiver.java (plexus-archiver) from the maven-assembly-plugin? It would be great if I could set this value from the maven-assembly plugin to merge or mergewithoutmain. What do you think about enhancing src/main/java/org/apache/maven/archiver/MavenArchiveConfigura tion.java (maven-archiver) with above option? with kind regards thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Assembly plugin: use unpacked existing manifest
Hi, When I unpack a dependency in the assembly plugin can I somehow use the already existing manifest file from this unpacked jar? And I want to change the Main-Class header in this manifest file! Is this possible? The archives plugin seems to always override an already existing manifest file from an unpacked dependency. With kind regards Thomas With kind regards Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Changing maven central mirror results in redownload of all dependencies?
Hi, I have the impression that changing the maven central mirror in the settings.xml does result in redownloading of all dependencies?! Why is that the case? Can I supress this? I.e. the artifacts are actually the same! With kind regards Thomas
Re: Graph of lifecycle and plugin executions
Am 17.11.2015 5:22 nachm. schrieb Jason van Zyl : > > > > On Nov 17, 2015, at 11:02 AM, Thomas Meyer wrote: > > > > Hi, > > > > okay thanks. > > > > Another question: > > > > What does it mean when a mojo execution is forked? > > > > It corresponds to the execute annotation[1] where if you execute a goal and > need to make sure the prerequisite lifecycle has run prior to said goal then > Maven will “fork” a lifecycle to make sure this requirement is met. Before > the goal is executed the lifecycle is run up to the phase you specify your > goal needs. So your Mojo might have something like: > > @Execute(phase=“LifecyclePhase.COMPILE”) > > As your mojo needs to operate on compiled classes this will make sure the > compiled classes are there. > > [1]: > https://github.com/apache/maven-plugin-tools/blob/trunk/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Execute.java > Hi, many thanks for the hint! I understand it now. So basically every mojo callable from command line somehow need to set this annotation and all mojos only usable in the pom doesn't! Thank you! > > > I tried to find some documentation about it, but I failed. > > > > The maven CLI execution event logger class seems to give some hint: > >>>> fork started and so on. > > > > Given the following pom > > https://github.com/thomasmey/einkaufsliste-server/blob/master/pom.xml > > > > The wildfly-swarm-plugin has two executions, but the compiler step and the > > annotation preprocessor plugin seems to be executed for both mojo > > executions? Why is that? I had the idea that each mojo execution happens > > only once without all predecessors for each defined execution step, but > > that doesn't seem to be the case. > > > > So who can bring some light in this and/or point me in the right direction > > and some documentation? > > > > With kind regards > > Thomas > > > > > > Am 16.11.2015 4:04 nachm. schrieb Jason van Zyl : > >> > >> If you use Eclipse you can go to the project properties and from there > >> Maven > Lifecycle Mapping and you’ll see something like this: > >> > >> > >> > >> If you don’t use Eclipse you can probably use this: > >> > >> https://github.com/takari/maven-profiler > >> > >> It was made for profiling but will show you the executions. There is > >> another more recent tool that shows the lifecycle but I can’t recall at > >> the moment what that is. I will try to remember and post when I do. > >> > >>> On Nov 16, 2015, at 9:55 AM, Thomas Meyer wrote: > >>> > >>> Hi, > >>> > >>> How can I print a graph of a given maven invocation with the lifecycle > >>> and for each lifecycle step which plugins are executed? > >>> > >>> E.g. > >>> > >>> lifecycle: > >>> step 3: generate-sources > >>> plugin 1 - maven-processor-plugin > >>> plugin 2 - ... > >>> step 4: process-sources > >>> plugin 1 - xxx > >>> > >>> because in my pom, a plugin is executed several times but it shouldn't! > >>> So i want to find out why. I tried with mvn -X but I couldn't see why a > >>> plugin was executed twice. > >>> > >>> with kind regards > >>> thomas > >>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: users-h...@maven.apache.org > >>> > >> > >> Thanks, > >> > >> Jason > >> > >> -- > >> Jason van Zyl > >> Founder, Takari and Apache Maven > >> http://twitter.com/jvanzyl > >> http://twitter.com/takari_io > >> - > >> > >> First, the taking in of scattered particulars under one Idea, > >> so that everyone understands what is being talked about ... Second, > >> the separation of the Idea into parts, by dividing it at the joints, > >> as nature directs, not breaking any limb in half as a bad carver might. > >> > >> -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Takari and Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/takari_io > - > > Be not afraid of growing slowly, be only afraid of standing still. > > -- Chinese Proverb > > > > > > > > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: Graph of lifecycle and plugin executions
Hi, okay thanks. Another question: What does it mean when a mojo execution is forked? I tried to find some documentation about it, but I failed. The maven CLI execution event logger class seems to give some hint: >>> fork started and so on. Given the following pom https://github.com/thomasmey/einkaufsliste-server/blob/master/pom.xml The wildfly-swarm-plugin has two executions, but the compiler step and the annotation preprocessor plugin seems to be executed for both mojo executions? Why is that? I had the idea that each mojo execution happens only once without all predecessors for each defined execution step, but that doesn't seem to be the case. So who can bring some light in this and/or point me in the right direction and some documentation? With kind regards Thomas Am 16.11.2015 4:04 nachm. schrieb Jason van Zyl : > > If you use Eclipse you can go to the project properties and from there Maven > > Lifecycle Mapping and you’ll see something like this: > > > > If you don’t use Eclipse you can probably use this: > > https://github.com/takari/maven-profiler > > It was made for profiling but will show you the executions. There is another > more recent tool that shows the lifecycle but I can’t recall at the moment > what that is. I will try to remember and post when I do. > >> On Nov 16, 2015, at 9:55 AM, Thomas Meyer wrote: >> >> Hi, >> >> How can I print a graph of a given maven invocation with the lifecycle >> and for each lifecycle step which plugins are executed? >> >> E.g. >> >> lifecycle: >> step 3: generate-sources >> plugin 1 - maven-processor-plugin >> plugin 2 - ... >> step 4: process-sources >> plugin 1 - xxx >> >> because in my pom, a plugin is executed several times but it shouldn't! >> So i want to find out why. I tried with mvn -X but I couldn't see why a >> plugin was executed twice. >> >> with kind regards >> thomas >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Takari and Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/takari_io > - > > First, the taking in of scattered particulars under one Idea, > so that everyone understands what is being talked about ... Second, > the separation of the Idea into parts, by dividing it at the joints, > as nature directs, not breaking any limb in half as a bad carver might. > > -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) > > > > > > > > > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Graph of lifecycle and plugin executions
Hi, How can I print a graph of a given maven invocation with the lifecycle and for each lifecycle step which plugins are executed? E.g. lifecycle: step 3: generate-sources plugin 1 - maven-processor-plugin plugin 2 - ... step 4: process-sources plugin 1 - xxx because in my pom, a plugin is executed several times but it shouldn't! So i want to find out why. I tried with mvn -X but I couldn't see why a plugin was executed twice. with kind regards thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to package a maven project source code only
Am Sonntag, den 14.06.2015, 16:48 +0200 schrieb Robert Scholte: > Hi, Hi Robert, > > this is probably what you are looking for: > http://maven.apache.org/plugins/maven-assembly-plugin/descriptor > -refs.html#project > > You only have to configure the assembly plugin with > >project > Yes, that looks very like it; I will give it a try! Thanks! > > thanks, > Robert > > Op Sun, 14 Jun 2015 16:21:38 +0200 schreef Thomas Meyer < > tho...@m3y3r.de>: > > > Hi, > > > > How to package a build-able source code .tar.gz file from a small > > maven > > project (quickstart archetype)? > > > > mvn source:jar seems to only package the sources, the pom.xml is > > missing! > > > > I would like to enter mvn package:buildableProject or something > > like > > that. > > > > Does there already exists a plugin that packages all source files > > and > > the pom.xml, README.md,etc... for easy distribution to others or do > > I > > need to manually tar and gzip the relevant directories and files? > > > > with kind regards > > thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to package a maven project source code only
Hi, How to package a build-able source code .tar.gz file from a small maven project (quickstart archetype)? mvn source:jar seems to only package the sources, the pom.xml is missing! I would like to enter mvn package:buildableProject or something like that. Does there already exists a plugin that packages all source files and the pom.xml, README.md,etc... for easy distribution to others or do I need to manually tar and gzip the relevant directories and files? with kind regards thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Dependency Plugin Default life cycle phase not executed
Am 02.06.2015 8:28 nachm. schrieb Anton Tanasenko :
>
> That's the point. You don't have to specify an execution phase if a default
> one is set.
> But you do have to express your intent to execute the mojo during build by
> specifying an execution itself.
Okay, I see! Thanks for your support!
>
> In case of dependency:unpack, its
>
> ...
>
>
> ..
> unpack
> ...
>
>
>
>
> See, no phase.
>
> 2015-06-02 20:16 GMT+03:00 Thomas Meyer :
>
> >
> > Am 02.06.2015 6:58 nachm. schrieb Anton Tanasenko > >:
> > >
> > > Hi, you probably missed the previous section:
> > >
> >
> > Oops :-)
> >
> > Okay, I understand now.
> >
> > But one more question: what use has the assigned default life cycle of the
> > resp Mojo class when you need to explicitly specify the execution phase in
> > the pom?
> >
> > > If you intend to configure this mojo for execution on the command line
> > > using:
> > > mvn dependency:copy
> > >
> > > you must not put the configuration inside the executions tag. Your
> > > configuration should look like this:
> > > ...
> > >
> > > 2015-06-02 19:36 GMT+03:00 Thomas Meyer :
> > >
> > > > Hi,
> > > >
> > > > I've a question regarding the maven dependency plugin:
> > > >
> > > > In the usage description (
> > > > https://maven.apache.org/plugins/maven-dependency-plugin/usage.html )
> > in
> > > > section "The dependency:unpack mojo" it's written that:
> > > >
> > > > "you must not put the configuration inside the executions tag. Your
> > > > configuration should look like this:"
> > > >
> > > > But this doesn't seem to be true as the plugin seems not get executed
> > at
> > > > all, at least for a project with package type "war".
> > > >
> > > > So what am I missing here?
> > > > Any ideas?
> > > >
> > > > My expectation was that the plugin gets executed in the generated
> > sources
> > > > phase.
> > > >
> > > > Here an excerpt of my pom file:
> > > >
> > > >
> > > > [...]
> > > >
> > > >
> > > > maven-dependency-plugin
> > > > 2.10
> > > >
> > > >
> > > >
> > > > [...]
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > org.bsc.maven
> > > > maven-processor-plugin
> > > > 2.2.4
> > > >
> > > >
> > > > process
> > > > generate-sources
> > > >
> > > > process
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ${project.build.directory}/generated-sources
> > > >
> > > >
> > > > org.mapstruct.ap.MappingProcessor > > > processor>
> > > >
> > > >
> > > >
> > > >
> > > > org.mapstruct
> > > > mapstruct-processor
> > > > ${version.mapstruct}
> > > >
> > > >
> > > >
> > > >
> > > > I'm using maven 3.3.1.
> > > >
> > > > With kind regards
> > > > Thomas
> > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Anton.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
>
> --
> Regards,
> Anton.
Re: Maven Dependency Plugin Default life cycle phase not executed
Am 02.06.2015 6:58 nachm. schrieb Anton Tanasenko :
>
> Hi, you probably missed the previous section:
>
Oops :-)
Okay, I understand now.
But one more question: what use has the assigned default life cycle of the resp
Mojo class when you need to explicitly specify the execution phase in the pom?
> If you intend to configure this mojo for execution on the command line
> using:
> mvn dependency:copy
>
> you must not put the configuration inside the executions tag. Your
> configuration should look like this:
> ...
>
> 2015-06-02 19:36 GMT+03:00 Thomas Meyer :
>
> > Hi,
> >
> > I've a question regarding the maven dependency plugin:
> >
> > In the usage description (
> > https://maven.apache.org/plugins/maven-dependency-plugin/usage.html ) in
> > section "The dependency:unpack mojo" it's written that:
> >
> > "you must not put the configuration inside the executions tag. Your
> > configuration should look like this:"
> >
> > But this doesn't seem to be true as the plugin seems not get executed at
> > all, at least for a project with package type "war".
> >
> > So what am I missing here?
> > Any ideas?
> >
> > My expectation was that the plugin gets executed in the generated sources
> > phase.
> >
> > Here an excerpt of my pom file:
> >
> >
> > [...]
> >
> >
> > maven-dependency-plugin
> > 2.10
> >
> >
> >
> > [...]
> >
> >
> >
> >
> >
> > org.bsc.maven
> > maven-processor-plugin
> > 2.2.4
> >
> >
> > process
> > generate-sources
> >
> > process
> >
> >
> >
> >
> >
> > ${project.build.directory}/generated-sources
> >
> >
> > org.mapstruct.ap.MappingProcessor > processor>
> >
> >
> >
> >
> > org.mapstruct
> > mapstruct-processor
> > ${version.mapstruct}
> >
> >
> >
> >
> > I'm using maven 3.3.1.
> >
> > With kind regards
> > Thomas
>
>
>
>
> --
> Regards,
> Anton.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven Dependency Plugin Default life cycle phase not executed
Hi,
I've a question regarding the maven dependency plugin:
In the usage description (
https://maven.apache.org/plugins/maven-dependency-plugin/usage.html ) in
section "The dependency:unpack mojo" it's written that:
"you must not put the configuration inside the executions tag. Your
configuration should look like this:"
But this doesn't seem to be true as the plugin seems not get executed at all,
at least for a project with package type "war".
So what am I missing here?
Any ideas?
My expectation was that the plugin gets executed in the generated sources phase.
Here an excerpt of my pom file:
[...]
maven-dependency-plugin
2.10
[...]
org.bsc.maven
maven-processor-plugin
2.2.4
process
generate-sources
process
${project.build.directory}/generated-sources
org.mapstruct.ap.MappingProcessor
org.mapstruct
mapstruct-processor
${version.mapstruct}
I'm using maven 3.3.1.
With kind regards
Thomas
