Hi all!
I'm using Maven Site Plugin to generate my project page and the JXR Plugin
to publish the source code. But I don't want to publish sources of test
classes. Does anybody know if it is possible to disable Test Source Xref
report. I've only found this
Hi,
I'm using Maven 3.0.3. I've included this plugin in a profile in my parent
pom, however, when I run my parent pom, I don't want this to be executed as
part of the parent pom being built (I do want it executed for each of the
child modules). How can I make this plugin not run during the
I have a situation where many of my projects need to produce an adjunct
artifact (in addition to the primary JAR) for later collection into my
distribution image.
I'd like to simplify the process that I use to generate the distribution
image, as right now the POM for the distribution project
I have a situation where many of my projects need to produce an adjunct
artifact (in addition to the primary JAR) for later collection into my
distribution image.
What types of things are stored in your adjunct artifacts? How are
they created? Why can those things not live in the primary
At first sight, I'd say this is a use case for pluginManagement.
You'd need to add the configuration you show above inside the
pluginManagement part in your parent pom.
Then, in each child module where you want to execute maven-antrun-plugin
based on that config, you just put:
build
plugins
Wayne Fay wayne...@gmail.com wrote on 04/02/2013 03:23:03 PM:
I have a situation where many of my projects need to produce an
adjunct
artifact (in addition to the primary JAR) for later collection into my
distribution image.
What types of things are stored in your adjunct artifacts? How
A trick i use, provided the plugin has a configuration to skip a run, is
having something like this in the parent
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.4/version
executions
execution
Hello Dave,
you could try to activate this profile depending on the existence of a
given file in your modules, e.g. the existence of a
src/test/resources/liquibase.properties (see
http://www.liquibase.org/manual/liquibase.properties).
Regards
Mirko
Regards Mirko
--
Thanks to all for your answers. Alejandro, tried yours and it worked. Loved
the fact it didn't require any configurations in the child projects. Rock
on, - Dave
--
View this message in context:
Thanks to all for your answers. Alejandro, tried yours and it worked. Loved
the fact it didn't require any configurations in the child projects. Rock
I'd be slightly concerned with his answer (trick) because it seems
like a bug that might get fixed at some point. So long as you realize
this
10 matches
Mail list logo