I am assuming you are using mvn clean since the maven-clean-plugin is
running. Running mvn clean causes a different lifecycle than the default one
to run, and it doesn't contain the validate phase. The clean lifecycle has
these phases [1]:
-pre-clean
-clean
-post-clean
If you bind the antrun
the archetype-metadata.xml file is read using mvn archetype:generate goal
Regards,
Raphaël
2008/7/31, Alexandre Touret [EMAIL PROTECTED]:
Hello,
I m currently trying to inject a custom property in the execution of the
creation of a project my an archetype. I'd like to maven resolves
I have a multimodule project where some module tests have dependencies
on other modules tests.
I can use both
classifiertests/classifier
scopetest/scope
and
typetest-jar/type
scopetest/scope
I think I notice that the type test-jar works when I build it in
reactor without installing while the
Lukas,
Thanks for replying. I've attached the whole maven.xml. We also have
separate maven.xml for each of subprojects.
Also, the problem with your suggestion is that if I add
maven:addPath id=maven.test.compile.src.set
refid=your_test_sources/
it'll fail with the same error as it requires
We have our own dependency management system (DMS) integrated in our own build
server. Yes, our own, it was developed about 3-4 years ago (in this time we did
not find anything acceptable) and it works fine, but we would like to use maven
and I spent about a week on research. Unfortunately it I
Did you use a mirrorOf *? What is the exact error you get?
On 8/1/08 12:10 AM, freak182 [EMAIL PROTECTED] wrote:
Hello,
here is the scenario to make it more clear:
1. a fresh install apache maven and set the mirror to internal repo to nexus
(nexus is also fresh install and
I just reproduced your problem: the maven.test.compile.src.set variable
is not initialized if there are no test sources present in your project.
So I suppose there are no tests in some of your subprojects. This is
certainly a bug in the test plugin but given the current state of m1.1
it's
I have a server which is running Proximity to build a maven repository. If I
want to remove an artifact from the repository can I simply delete the
directory? Is there other files that might be looking for it?
--
View this message in context:
Hi everyone,
Awhile ago, I mentioned that we were starting the process of putting
together the 2.0.10 release of Maven. We've already been through a
series of three release candidates that gave us the opportunity to iron
out the worst wrinkles, and now I believe we have a release candidate
Hi,
(a bit of crossposting here, also sent to the jetty list)
I'm trying to run a jetty server with jotm through maven, and
everything except the jotm configuration works as it's supposed to.
Have anyone had any success with this configuration? As far as I've
understood it from previous
Hi again,
Please disregard this message. It was sent prematurely, before I'd seen
that some regressions have been found.
We'll try this again once we can be more certain that the regressions
are cleared.
Thanks for your patience,
-john
John Casey wrote:
Hi everyone,
Awhile ago, I
If you do separate the configuration from the build, then how you
manage it is really dependant on how others deploy the application.
Can you clarify this?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 31, 2008 6:03 PM
To: Maven Users List
Hi togehter,
I was searching the internet for an hour now, and can't find a nice
solution for my really easy problem.
We have a maven project, which produces a war file, which actually
works great.
Further we have a server whith different jetty-servers running.
Dev-Server, Test-Server,
If it is not broken, don't fix it!
What you have sounds like it works for you and solves the problems you
have encountered.
If you have a working dependency management system that does not have any
problems... leave it working.
If, however, you have problems, then Maven could well have the
Wow, I didn't know about that, I will try this now.
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message.
Any disclosure,
On Fri, Aug 1, 2008 at 7:34 AM, Fritz Richter
[EMAIL PROTECTED] wrote:
Now, I just want to deploy our war-file to the server via scp.
If I configure the pom like the following:
distributionManagement
That is for deploying to a remote Maven repository, not to an app
server. The name of the
Hi there,
You should be able to delete it using some DAV tool (issue a delete
from that tool).
But yes, you can delete it safely from the backing FS storage too. But
in this case, you should delete the attributes associated with those
files too.
And btw, you should switch to Proximity
Thanks Wendy,
I found the docs here:
http://docs.atlassian.com/maven-upload-plugin/1.1/index.html
Cheers Fritz
Am 01.08.2008 um 16:41 schrieb Wendy Smoak:
On Fri, Aug 1, 2008 at 7:34 AM, Fritz Richter
[EMAIL PROTECTED] wrote:
Now, I just want to deploy our war-file to the server via scp.
Hello.
I am new to Maven, and I am a bit confuse about the porpuse of directory
src/main/config porpuse
I have been looking for information about it but it does not seems to be
much.
I initially thought that in directory src/main/resources I could put any
static resource used by the jar
Say you are deploying to Jetty , and you configure all your database
settings via jetty.xml that is part of the installation. I'm just
saying that while it can help, that's typically out of the scope of
Maven so what ever tool you choose (if any at all) for that env should
manage and version the
Hi Wendy,
because I can't change the name of the resource on the des-side,
I want to try out Don's stuff.
To search in the list archives, can you give me a hint / keyword?
Cheers
Fritz
Atlassian has a 'Maven Upload Plugin' though I can't find the docs
atm. And recently Don created a
On Fri, Aug 1, 2008 at 11:00 AM, DOMINGUEZ Felipe
[EMAIL PROTECTED] wrote:
I am new to Maven, and I am a bit confuse about the porpuse of directory
src/main/config porpuse
I have been looking for information about it but it does not seems to be
much.
I initially thought that in directory
Thanks a lot Lukas, that worked!
Alexey Yudichev.
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: 01 August 2008 14:48
To: Maven Users List
Subject: Re: maven-test-plugin-1.8.2/plugin.jelly:46:72:
maven:addPath: cannot find the path to add to specified by 'id':
Geoffrey Wiseman wrote:
On Fri, Aug 1, 2008 at 11:00 AM, DOMINGUEZ Felipe
[EMAIL PROTECTED] wrote:
I am new to Maven, and I am a bit confuse about the porpuse of directory
src/main/config porpuse
...
Can any body clarify the usage of src/main/config and what is maven
approach
So say you're deploying to jetty - AND you're deploying a daemon
process locally AND you're deploying to jboss (a separate webapp).
Where do you store that configuration such that its centralized and
you're not updating a million profiles (or profiles.xml files)?
Settings.xml?
I find it
It should be possible to remove them that way. You may have to reindex
to clear anything else. We strongly recommend proximity users upgrade to
Nexus: http://nexus.sonatype.org, it has all the proximity functionality
/ stability plus lots more. (you can delete artifacts right from the ui
for
The Maven team is pleased to announce the release of the Maven DOAP
Plugin, version 1.0.
This plugin generates a Description of a Project (DOAP) file from
information in a POM.
http://maven.apache.org/plugins/maven-doap-plugin/
You can run mvn -up to get the latest version of the plugin, or
Hi,
I'm using maven 2.0.7 and I'm getting the following error during
dependencies report generation stage of site:site:
Maven Site Plugin
[INFO] Generating Dependencies report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
If you supply us with a POM we might be able to help you.
Krishnamurthi, Venkat wrote:
Hi,
I'm using maven 2.0.7 and I'm getting the following error during
dependencies report generation stage of site:site:
Maven Site Plugin
[INFO] Generating Dependencies report.
[INFO]
Currently, our tests are the longest-running part of our Maven lifecycle and
we'd like to have Cobertura fail if a test case fails so that Surefire isn't
needed.
Is it possible to have Cobertura fail when a test fails? Normally, it only
fails if one of its conditions aren't met (e.g., line
Thanks a lot for your help! Please find the pom.xml below
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
Could someone please supply me a default checkstyle license file?
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message.
Any
What is it you want? The license for the Checkstyle product?
Morgovsky, Alexander (US - Glen Mills) wrote:
Could someone please supply me a default checkstyle license file?
This message (including any attachments) contains confidential information intended for a specific individual and
Hello,
sorry for maybe a stupid question but I really do not know is it possible.
I have a plugin defining some property named abc with value '1'. like this:
properties
abc1/abc
/properties
I call this plugin from my project with something like this:
build
It looks like the assembly plugin can do line feed filtering, but not in a
format-specific way as far as I can see. Like, it'd be nice to have CRLFs
in the ZIP and just LFs in the .tar.gz. I could do that with two assembly
descriptors, but that'd involve duplication. Am I missing a way to make
we've had tests that pass when run with cobertura and fail without. so
I always recommend running twice. additionally we've had tests that
pass normally, but fail with cobertura. in both cases the root cause
analysis was a bug in our code. run them twice and if either run fails
you likely
Even if a test fails during the Cobertura phase, Cobertura won't fail, as
long as the coverage criteria are met. That's what I'm trying to get around.
AFAIK, the only thing surefire has that Cobertura doesn't is the ability to
fail when a test fails.
Cobertura should definitely have a way to fail
On Fri, Aug 1, 2008 at 8:33 AM, Fritz Richter
[EMAIL PROTECTED] wrote:
Hi Wendy,
because I can't change the name of the resource on the des-side,
What do you mean?
I want to try out Don's stuff.
To search in the list archives, can you give me a hint / keyword?
This is what I was thinking
So after trying out more complex scenarios with my first solution (like
calling Class.forName from a class that was injected by the Plexus
container) it turned out it wasn't a complete solution. So learned alot
more about Plexus and the ClassWorlds framework and I ended up discovering a
much
Does anyone have some insight as to why the uberjar functionality of the
Classworlds project hasn't gotten much support with Maven 2?
http://classworlds.codehaus.org/uberjar.html
It seems like a really useful setup as it preserves some of the information
that the assembly plugin strips, such as
In particular, it was really slow.
Rather than jar-in-jar execution, most solutions have focused on
repacking a single JAR and combining the resources as well as
rewriting references and in some cases stripping out unneeded code.
I recommend looking at the Shade plugin in Maven.
Cheers,
Brett
41 matches
Mail list logo
