Hello,
On Tue, Apr 15, 2014 at 12:14 AM, Eric Kolotyluk
eric.koloty...@gmail.comwrote:
I have the following
repositories
repository
idsonatype/id
nameSonatype Maven OSS Repository/name
releases
enabledtrue/enabled
Couldn't find the answer to this yet...
I am using the exec-maven-plugin to launch a Java process. Before calling
exec:exec, I am trying to get antrun plugin to create an endorsed dir and
copy a dependency jar ( hopefully referred to by artifact id) into that dir.
Then exec java process will
:
THis is a limitation in the current implementation, but you can work
around it by running:
m2 generate-sources javadoc:javadoc
On 10/27/05, Peter Lynch [EMAIL PROTECTED] wrote:
[snip]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
ohhh the trick is it will only work if the xmlbeans plugin detects
there are new sources to generate. In other words
mvn clean generate-sources javadoc:javadoc
^
-Peter
Peter Lynch wrote:
Doesn't work for me. Is there some specific pom setting I need?
The javadoc plugin just
Sorry this may be old news but, but I am wondering if Maven 2 has plugin
classloader seperation to avoid this? I'm scared of what the answer
might be ;)
-Peter
Brett Porter wrote:
I don't think this is a specific bug as much as it might be a weird
combination of dependencies that clash.
The only name currently supported is 'apache'
The only version currently supported is '2.x'
The validation is done in plugin.jelly.
-Peter
Kelly Sonderegger wrote:
I can't seem to find the documentation on webserver goal available
property values.
e.g. the doc talks about properties such as
Neil Blue wrote:
Hello,
I have been writing my first plugin, and ran:
maven plugin
this copied the new plubin jar to ~/.maven/repository... is this right as I
though the plugins went in ~/.maven/plugin ?
Cheers
Neil
I think you want plugin:install or plugin:deploy.
The default goal of
