Wow, xdoclet-1.2.3 is the latest version, which was published in 2005, and there have been whole 14 messages on the developer mailing list and 26 messages on the user mailing list during the last 3 years. I am afraid this project is dead.You can download the source code yourself from
First I thought this could be a problem in the dependency plugin, but I see
the same result when viewing this in the dependency hierachy of m2e (which
uses Maven 3.0.4). Seems to be a bug - you should file a ticket.
/Anders
On Tue, Dec 4, 2012 at 9:00 PM, Dmitry Batrak batr...@gmail.com wrote:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-components.html
/Anders
On Wed, Dec 5, 2012 at 8:30 AM, Dirk Olmes d...@xanthippe.ping.de wrote:
Hi,
as part of our build wer're building client specific installer zips.
These are around 10 different assembly
I'm back with a strange behaviour. In a separate project which has profiles
defined exactly the same way, passing the option '-P [profile name]' does
not work at all, Maven continues to use the default activated profile. Here
is a working example:
project xmlns=http://maven.apache.org/POM/4.0.0;
Taken from
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Deactivating a profile
Starting with Maven 2.0.10, one or more profiles can be deactivated using
the command line by prefixing their identifier with either the character
'!' or '-' as shown below:
mvn
so you need to do ' -P vm,!dev '
That is not true. Enabling the vm profile will disable the
activeByDefault one (dev) automatically.
/Anders
On 12/5/12 7:53 AM, Javix serguei.camb...@atos.net wrote:
I'm back with a strange behaviour. In a separate project which has
profiles
defined
Hey all,
Seeing some odd behaviour with maven-exec-plugin and JVM arguments that
seem to be eluding me. I have the following config:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.2.1/version
configuration
executablejava/executable
I think I ran into something similar the other day. You need to put each of
the arguments in a separate argument element.
argument-Dcom.sun.management.jmxremote/argument
argument-Djava.awt.headless=true/argument
argument-Xmx1024m/argument
etc.
/Anders
On Wed, Dec 5, 2012 at 10:05 PM, Mark
Anders,
Mmm that sounds plausible altho so far I don't seem to see any
difference in behaviour, my ps aux output shows
amrk 6040 0.0 5.7 4054184 478464 s000 S+ 10:53am 3:57.72 /usr/bin/java
-Dcom.sun.management.jmxremote -Djava.awt.headless=true -Xmx1024m
-XX:+CMSClassUnloadingEnabled
Hello,
I'm able to use mvn release:prepare but I run into an issue when I use mvn
release:perform.
My problem is that my scm data in my pom points to our git repository which
contains multiple projects.
Is there a way to tell release:perform to only checkout or export a
subdirectory of the
Despite reading and re-reading the docs, and googling, for the past half-hour,
I can't see how useScope or scopes is useful in the maven ant task unless I use
a separate POM file.
If I list all my dependencies directly in my ant build script, there appears to
be no way to reference one
please read the last two lines
F:\work\7832e3bc4d2f257b\dashboard-core\target\classes (Access is
denied)
Le mercredi 5 décembre 2012 15:00:24 David Hoffer a écrit :
I have a multi-module maven build and can't get the site build to
work. It's currently failing with this error. The module its
12 matches
Mail list logo