Hi Jamal,
Jamal B wrote:
Interesting
Taking your suggestion, it looks like it is coming in from another compile
dependency, and was promoted to compile.
[INFO] +- org.apache.maven.shared:maven-shared-jar:jar:1.1:compile
[INFO] | +- org.codehaus.plexus:plexus-digest:jar:1.0:compile
I'm assuming it is a bug and opened
http://jira.codehaus.org/browse/MSOURCES-66
On 6/3/13 2:26 PM, Kurt T Stam wrote:
Hi guys,
I'm trying to add 'test-jar' resources to my assembly; i.e. the
following jars are created by one of our other modules:
main:
-rw-r--r-- 1 kstam admin 11603
the packaging is `jar` not `test-jar` there is only one artifact with
`test-jar` packaging, namely the `test-jar`
You want to use
includeorg.apache.juddi:**uddi-tck:jar:test-sources/**include
includeorg.apache.juddi:**uddi-tck:jar:test-javadoc/**include
Not a bug
On 4 June 2013 14:02, Kurt T
Hi guys
i'm try to implement my first plugin
so i did just a plugin that print a log on the screen
this is the code
and this is the pom related to this plugin, from the pom generated from the
plugin archetype i have just add the maven-plugin-plugin to add the prefix
pojo to make same test
1. Please use a propper mail agent that does not strip the code from you
email
2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know
where to look for your plugin
On 4 June 2013 15:30, alesky alessandro.dotta...@gmail.com wrote:
Hi guys
i'm try to implement my first
1. Please use a propper mail agent that does not strip the code from you
email
ok i will do the next time sorry to all, i was supposing that in this way
there was all the information to undestand my issue
2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know
where to look
Man i have your same issue
i use this strategy to reduce the number manually file that i have to update
when i change version
in my main parent pom i added
1)in the dependencies management all the sub project
2)a property with the version of my project
so at list i have reduced the manually
plugins are not executed unless the packaging for the specified project
injects an execution OR you specify an execution for the plugin yourself
On 4 June 2013 16:01, alesky alessandro.dotta...@gmail.com wrote:
1. Please use a propper mail agent that does not strip the code from you
email
ok
eg
project
...build
...plugins
...plugin
...executions
...execution
On 4 June 2013 16:46, Stephen Connolly stephen.alan.conno...@gmail.comwrote:
plugins are not executed unless the packaging for the specified project
injects an execution OR you specify an execution for
To summarize for any future thread readers...
Right now, the site plugin, and its related report plugins, are highly
unlikely to work reliably for any non-standard project layout (and I
personally haven't tried a layout that does work).
If you have just one extra layer between your
Thank you Stephen,
After also updating the dependencies in the pom to:
dependency
groupIdorg.apache.juddi/groupId
artifactIduddi-tck/artifactId
version${project.parent.version}/version
classifiertest-javadoc/classifier
typejar/type
ok Stephen thanks
specifying an execution to the plugin it works
but i would like to injects an execution in the packaging for the specified
plugin project
in the way that i can use the plugin in this way, and don't have to force
the user to specific the execution
but i didn't found any
IIUC, you are trying to bind a plugin execution to a phase?
Check this link
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Configuring_Build_Plugins
Basically, you need an execution tag with the configuration for the
plugin and a phase that the plugin is bound to
so if you
If I understand correctly, you want to be able to execute your plugin
without having to declare it. If so then your are on the right path since
the only way to do that is to create a custom lifecycle.
Hope this helps.
Cheers
-- Baptiste
Le 4 juin 2013 19:17, alesky alessandro.dotta...@gmail.com
Mon, 3 Jun 2013 07:04:58 -0700 (PDT), /Evan/:
http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html#Javadoc_Configuration
That section warns me that the behaviour is different, but not *how* it
differs. In the example at the bottom of that page the javadoc:javadoc uses
elements from
If I enable manifest class path creation, the jar or assembly or shade plugin
will create a manifest class path that lists all of my dependencies in the same
directory. But what if I need them in different directories? Our current
requirements place certain jars in specific directories so that
How do you decide which artifacts go into which folder?
If this is done by hand, then there's your answer: specify the complete
classpath yourself.
Otherwise I'd suggest to write a custom ManifestResourceTransformer for
the maven-shade-plugin.
Robert
Op Tue, 04 Jun 2013 20:11:21 +0200
17 matches
Mail list logo
