Hi there,
the command line argument works (for me). But in Hudson (V 1.394), You
need to add the '-s .../settings.xml' arguments to each project's build
configuration. A global settings configuration for all Maven builds
could only be set using the 'MAVEN_OPTS' with the
I understand that passwords can be encrypted using the technique
described at http://maven.apache.org/guides/mini/guide-encryption.html
- however that can easily be circumvented by anyone who has access to
the settings-security.xml file.
However, I also know that other software uses techniques of
Hi,
trying to generate the site of one of my projects, with Maven 3.0.2
and maven-site-plugin 3.0-beta-3, fails with the error message below.
The error message indicates that the site descriptor of the parent POM
is missing. That is missing indeed, because the parent POM doesn't
have a site and,
I want to
- build my maven modules top-down using snapshot dependencies among each other
- start my appserver with cargo
- run the integration-tests and
- keep the appserver running afterwards.
A simplified project structure might look like this
pom.xml
|_ moduleA
|_ moduleB
|_ moduleC
|_
This question might be better to post to the cargo user list than this
generic Maven list.
Anyways, if you would like to keep the app server running afterwards, I
would separate things into distinct steps, like:
mvn cargo:start - start the server (and possibly deploy)
do what ever you want to do
Hi,
according to the Cargo docs mvn cargo:help prints a short description, but
that seems to work only with Maven 2; with Maven 3 I'm getting the following
error:
(...)
[ERROR] No plugin found for prefix 'cargo' in the current project and in the
plugin groups [org.apache.maven.plugins,
Hi Thorsten,
which version of the cargo plugin do you use?
Can you give a snippet of your POM.xml where you configure cargo, cause i'm
using cargo with maven 3.0.X
Kind regards
Karl Heinz Marbaise
--
MfG
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 /
You need to declare 'org.codehaus.cargo' as a pluginGroup in your
settings.xml:
pluginGroups
pluginGrouporg.codehaus.cargo/pluginGroup
/pluginGroups
/Anders
On Wed, Feb 9, 2011 at 15:31, Thorsten Heit th...@gmx.de wrote:
Hi,
according to the Cargo docs mvn cargo:help prints a short
started working with an alias:
alias mvn='mvn -s .../settings.xml'
But this wouldn't work on Windows machines ...
I've done something similar with mvnclienta and mvnclientb. You
simply copy the mvn.bat file, rename it, and insert the -s
.../settings-clienta.xml into the call to mvn
Hi
I will try to explain better my current solution, because i would like to
know if this is the better approach.
As I referenced my requirement is to generate the multiple WARs and
aggregate the WARs in a EAR. I also like to generate skinny wars, and
include the common, and 3rd party JARs only
- however that can easily be circumvented by anyone who has access to
the settings-security.xml file.
In Windows environments, use NTFS and limit access to be r/w to the
owner only. In Unix environments, chmod 600 on the file. Honestly, how
much more security do you need?
Do any of the
I apologize if this is a really basic problem but I am at a point where I
need some help from SOMEBODY:
I am experiencing a situation where my command-line Maven 3.0.2 build is
always failing with the following error (trace abbreviated for brevity):
Caused by: java.lang.ClassNotFoundException:
Hey,
I'm using Maven 2.0.9. Not by choice, if it matters.
Yesterday I took a project out of SVN which I built for the first time. But
to my surprise the build failed, eventhough it's currently running on
several servers around here. The reason for it? A transitive dependency
that's
You,re cutting away so much of the log that it doesn't even show 2.7.1
being run ;)
Maybe
mvn --fail-never --file CSKAutoCommon\pom.xml help:effective-pom
Can provide some insight ?
Kristian
on., 09.02.2011 kl. 08.59 -0700, skrev twilliamso...@oreillyauto.com:
I apologize if this is a
How about deploying your common and common-overlay into common folder of
your app server?
AFAIK most app servers that doesn't support ear deployment will still have
the common/shared folder to run components that are accessible from the
deployed war files.
---
daniel baktiar
That's VERY cool. I didn't know it could do that.I found that it's
defaulting to 2.7.1 so I have forced that to 2.5 explicitly in the POM (I
guess the default previously was 2.5). I apologize for not RTFM more
carefully.
From: Kristian Rosenvold kristian.rosenv...@gmail.com
To:
Hi to all,
i have a question concerning the site.xml descriptormay be i oversight
something but i'm a little bit astonished, cause during the release cylcle
the site.xml will be deployed to the repository
So my question is: Why is the site.xml descriptor deployed to the
repository? I
Hi Folks,
I have some tests running that read a system property to determine where some
resources should be read from. I've defined that property inside a master pom
file, and created profiles that activate that property on other projects pom
files. The structure is somehow like this:
jochen-2 wrote:
... because the parent POM doesn't have a site and, in particular, no site
descriptor.
the parent's site.xml isn't deployed to the site repo, it's deployed to the
end-state repo alongside the primary artifact (jar,pom,etc.)
If you want your project's site descriptor to be
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 2.7
The Maven Plugin Plugin is used to create a Maven plugin descriptor for
any Mojo's found in the source tree, to include in the JAR. It is also
used to generate report files for the Mojos as well as for
Karl-Heinz: The answer is that site.xml might be required by modules,
if they have
menu ref=parent/
in their own site.xml. In that case the parents site.xml is loaded
from the repository.
But, on a related matter, and because I have posted this question just
today: How do I achieve that the
Thanks. I don't understand the reason for removing the deployment by
default (one more example where the POM grows without an apparent
reason), but your explanation helped.
On Wed, Feb 9, 2011 at 7:12 PM, lukewpatterson lukewpatter...@gmail.com wrote:
jochen-2 wrote:
... because the parent
On 2011-02-09 19:49, Jochen Wiedmann wrote:
Thanks. I don't understand the reason for removing the deployment by
default (one more example where the POM grows without an apparent
reason), but your explanation helped.
The reason was to properly separate Maven 3 from the documentation
generation
On Wed, Feb 9, 2011 at 8:03 PM, Dennis Lundberg denn...@apache.org wrote:
The reason was to properly separate Maven 3 from the documentation
generation framework (i.e. Doxia) on one hand and the Site Plugin on the
other hand. This makes it possible to use other documentation generation
On 2011-02-09 20:08, Jochen Wiedmann wrote:
On Wed, Feb 9, 2011 at 8:03 PM, Dennis Lundberg denn...@apache.org wrote:
The reason was to properly separate Maven 3 from the documentation
generation framework (i.e. Doxia) on one hand and the Site Plugin on the
other hand. This makes it possible
CL sent this to me privately, forwarding back to the list, I have
nothing to add...
-- Forwarded message --
Date: Tue, Feb 8, 2011 at 4:33 PM
Subject: RE: Eclipse Plugin - how to remove M2_REPO classpath variable (re-post)
but nothing is stopping you from doing it manually by
Hi Jochen,
Karl-Heinz: The answer is that site.xml might be required by modules,
if they have
menu ref=parent/
in their own site.xml. In that case the parents site.xml is loaded
from the repository.
Hm...what i don't understand why this is handled without saying it
explicit...for
I've just figured out that the setting I need is arguments from relase
plugin.
Using that solved my problem.
Felipe Roos
http://www.linkedin.com/in/feliperoos
Achar desculpas para os nossos
defeitos não nos torna melhores
- Mensagem original
De: Felipe Roos
Hi,
which version of the cargo plugin do you use?
Can you give a snippet of your POM.xml where you configure cargo, cause i'm
using cargo with maven 3.0.X
For testing purposes I only added the following minimalist configuration
snippet to my pom.xml as explained on the Cargo website
Hi,
You need to declare 'org.codehaus.cargo' as a pluginGroup in your
settings.xml:
pluginGroups
pluginGrouporg.codehaus.cargo/pluginGroup
/pluginGroups
Ok, thanks, I'll try it tomorrow when I'm back at work.
OTOH: Why can Maven 2 find the Cargo plugin without having the above
this is a result of somebody having put dependencies in a profile activated
by java version.
a mistake was made when the pom schema was defined in allowing dependencies
to be part of profiles.
it cannot be corrected until maven 3.1 or later
- Stephen
---
Sent from my Android phone, so random
I have no clue. There shouldn't be any difference. I'm guessing there is
some difference in your maven 2 and maven 3 execution environments.
/Anders
On Wed, Feb 9, 2011 at 20:52, Thorsten Heit th...@gmx.de wrote:
Hi,
You need to declare 'org.codehaus.cargo' as a pluginGroup in your
I have no clue. There shouldn't be any difference. I'm guessing there is
some difference in your maven 2 and maven 3 execution environments.
Nope:
I unpacked the binary tar archives for both Maven 2 and 3 in /usr/local, i.e.
there are directories /usr/local/apache-maven-{2.2.1, 3.0.2}. There's
On Wed, Feb 9, 2011 at 2:53 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
this is a result of somebody having put dependencies in a profile activated
by java version.
a mistake was made when the pom schema was defined in allowing dependencies
to be part of profiles.
Are you
Hi All
Not sure if anyone can help but I having a problem running the site goal on a
project.
My Maven projects are structured as follows:
NB App Parent
-- application
-- branding
-- db
-- mainui
I am getting the following error if I run the site goal on NB App
Parent, it seems to be becasue
Caused by: org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to execute goal on project application: Could not resolve
dependencies for project
com.copperarrow.crmdc:application:nbm-application:0.1: The following
artifacts could not be resolved:
To create your own repository, use: nbm:populate-repository
Why don't you try running the mvn nbm:populate:repository command
I mistyped, that is supposed to be mvn nbm:populate-repository obviously.
Wayne
-
To
I'm saying it cannot be fixed/changed before 3.1.
I'm not saying whether it will be fixed/changed
re your other question, I'd need more details/example pom(s)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of
Environment: Maven version 2.2.1 JUnit version 3.8.1
My JUnit test case reads the input file. I put this file into
src/test/resources folder.
In JUnit the following line gives me FileNotFoundException
File f = new File(myfile);
Question: how to specify in pom.xml file that my test input
Things in src/test/resources are in the class path. So, you can open
streams to them with getClass().getResourceAsStream(name).
Or, move it to src/test/data, and then configure a system prop in surefire like:
data${basedir}/src/test/data/data
and do System.getProperty(data) in your junit
I tried to follow your 2nd advice: added
data${basedir}/src/test/data/data into surefire
plugin
artifactIdmaven-surefire-plugin/artifactId
version2.4.3/version
configuration
forkModenever/forkMode
reportFormatxml/reportFormat
configuration
data${project.basedir}/src/test/data/data
/configuration
What makes you think that is the right way to do it? Doesn't seem like
you read the documentation about system properties and Surefire.
42 matches
Mail list logo
