Hi,
From time to time developers change assembly descriptors and then what I think
is being packaged may not actually be what I expect to be packaged.
Anyone out there taking steps to verify the contents of an archive and if so
how are you going about such?
I was thinking of writing a number
Whatever strategy you opt for should be one that the team is comfortable
with and is willing to support. I'm a fan of the flat approach. I try to
keep modules as simple as possible this way builds fail fast with
immediate feedback to the team.
I use Maven in our environment to build out server,
When running any mvn command (tried 3.0.3 and 3.0.4) on OSX Lion I see numerous
lines of output similar to below. I added a mac box to my build farm. The Maven
repo is hosted on a net app box that is visible to all my Redhat, Windows and
now OSX build nodes via an NFS mount. The build doesn't
I wasn't aware that a shared local repo wasn't supported. I just switched
over all nodes to a local repo throughout the build farm and the warnings
did indeed disappear.
Version of Java used on this particular OSX node is
java version 1.6.0_31
Java(TM) SE Runtime Environment (build
The use of classifiers may help out in this case.
The major Maven packaging plugins like jar, ear, and war allow the use of a
classifier to be configured. For each of your streams if you pass in a property
at build time -Dstream=value then you could set the classifier to this
property and all
Hi,
How do people approach the need to generate a jar multiple times using
classifiers.
My specific requirement is that I have a module which needs to be built against
Axis2 1.3 and Axis2 1.4 and have 2 jars in the repo with distinct classifiers.
I can get this to work using profiles but this
We use the build-helper-maven-plugin to do exactly this. We wrapper the Ant
project with basic Maven and then configure the plugin to do the rest.
Works a treat
--
Robert
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Thursday, April 30, 2009 10:19 AM
To: Maven
In the past i've made use of the Build Helper plug-in to attach additional
artifacts
http://mojo.codehaus.org/build-helper-maven-plugin
-Original Message-
From: David C. Hicks [mailto:dhi...@i-hicks.org]
Sent: Tuesday, February 17, 2009 4:27 PM
To: Maven Users List
Subject: Re: How to
Hi,
Do version ranges work across Maven plugins or are they limited to Maven core
functionality?
As an example I defined a dependency with a range of version
[4.4.2.01,)/version and all was well. But when I tried to use the same
notation with the maven-dependency-plugin 2.0 it results in a
It is possible to just run unit tests or integration tests from a module but it
gets messy and over complicated.
For example I have projects that separate tests by placing all unit tests in a
directory called unit and all integration tests in a directory called it.
With such a separation it
on the Maven site
--
Robert
-Original Message-
From: Olivier Dehon [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 23, 2008 5:38 AM
To: Maven Users List
Subject: Re: Property that defines the generated artifact name
On Sat, 2008-11-22 at 22:41 -0800, Bracewell, Robert wrote
Hi,
When I run mvn scm:checkout I keep hitting the issue below:
[INFO] Cannot run status command :
Embedded error: Can't login.
Perforce password (P4PASSWD) invalid or unset.
[INFO]
I am using Perforce and I have tried
Looking for insight's into how other users are managing unit and integration
tests in current 2.0.x.
At the moment the projects I have store unit tests under **/unit/** and
integration tests under **/it/**
I have compiler and surefire plugin configurations to exclude it tests and then
have a
I have a super pom which several of my product lines use as a parent. So for
functionality I want across several product lines I add such to the super pom.
If a product needs to diverge then I override at the product level pom.
Basically all my components that make up a build specify their
version of the
maven-dependency-plugin is due to be released?
I was working on some issues earlier this week at the hackathon to
prepare for a release. I'll see if this one can get included.
-Original Message-
From: Bracewell, Robert [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November
Hi,
I am looking to find out if it's possible to know when such is due and what the
planned list of Jira fixes would be?
Thanks,
Robert
--
Robert
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 1:52 PM
To: Maven Users List
Subject: Re: How do I found out when the next version of the
maven-dependency-plugin is due to be released?
On Wed, Nov 5, 2008 at 3:14 PM, Bracewell, Robert
Hi,
Is it possible to fail a build or generate a report if the scope defined for
dependencies at a parent pom level are overridden at a module level?
Would the enforcer plugin allow me to write a custom rule to implement such or
could this be achieved via a different route?
--
Robert
We use both Sonar and the site plug-in.
Sonar is run to provide metrics which the dev team find handy. We have
Sonar invoked via Hudson for every development task submitted to
relevant modules in our SCM system. This way developers can quickly see
if metrics go up or down. We use the site to
I have never got filtering working with filesets
The Maven documentation states filtering only works on files
So switching to files solved my issues
--
Robert
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Christopher Patti
Sent: 20 June 2008 22:46
To:
Hi,
I am unable to generate PMD/CPD metrics for a test suite as part of a
multi-module build.
The parent pom pulls version 2.3 of the PMD plugin and sets the
includeTests setting to true. The PMD and CPD reports are generated but
do not include the test metrics.
However if I generate a site from
-
From: Michael Delaney [mailto:[EMAIL PROTECTED]
Sent: 10 June 2008 17:01
To: Maven Users List
Subject: RE: Release plugin questions
Sorry, I am still getting the same error when I add that to the pom.xml file.
-Original Message-
From: Bracewell, Robert [mailto:[EMAIL PROTECTED]
Sent
Try specifying the developerConnection, e.g.,
!-- P4 Location --
scm
connectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/connection
developerConnectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/developerConnection
/scm
-Original
In our organization it depends on the project but I have projects that
release twice a week internally. Other groups or projects that are
reliant on such artifacts can then decide as and when they want to
depend on the new artifacts that were deployed.
-Original Message-
From: Geoffrey
Hi,
I am trying to get an understanding of how users are using the Maven
toolset with SCM tools such as Perforce to handle branching strategies.
Does anyone know of any such white papers or further reading or be
willing to share current practices?
Do users tend to use a dense hierarchical
.
One day i'll get around to putting something up on the net about how
i've
structured my projects and why.
On Thu, 29 May 2008 21:42:14 Bracewell, Robert wrote:
Hi,
I am trying to get an understanding of how users are using the Maven
toolset with SCM tools such as Perforce to handle branching
Use an environmental property
For example some other system could set the env var called P4_CL and
then you could reference it using ${env.P4_CL}
-Original Message-
From: Richard Chamberlain [mailto:[EMAIL PROTECTED]
Sent: 22 May 2008 11:10
To: Maven Users List
Subject: Getting a dynamic
Yes I have had the same issue in multi-module projects using filesets.
I had to change the fileset to be files and it worked.
The Maven assembly plugin documentation page states Filtering is only
enabled inside files...
-Original Message-
From: Richard Chamberlain [mailto:[EMAIL
Hi all,
Investigating the use of the release:branch goal but running into
issues. The error is listed below. I have to say that I have no issue
using the release:prepare goal so everything seems to be in place with
the SCM section of the pom.
Does anyone use the release:branch goal in
.
-Original Message-
From: Bracewell, Robert [mailto:[EMAIL PROTECTED]
Sent: 06 May 2008 12:42
To: users@maven.apache.org
Subject: Perforce and release:branch goal
Hi all,
Investigating the use of the release:branch goal but running into
issues. The error is listed below. I have to say that I
Hi,
Can you expand a little?
What do you mean by a perforce numbered artefact?
Would you not have the potential for several P4 CLs that affect any one
artefact?
What we do is embed a unique id as a java class which can then be
queried via a UI. We also embed this unique id as part of the
) and it would be
good to name my artefact myapp-1.3-SNAPSHOT-12345.jar where 12345 is the
perforce changelist number when the build occurred.
When the build failed I can sync my code to 12345 and be able to debug
it instantly.
Richard
-Original Message-
From: Bracewell, Robert [mailto
Hi,
I would like to be able to refer to a dependency via a property. As an
example consider the site phase which runs numerous reporting plugins
and such a plugin requires a license.
I have the license sitting in the repository as an artefact and I define
the artefact as a dependency in the
Hi,
Noticed an oddity with filtering in that it is replacing the wrong
properties under certain conditions. The key thing to note in below
mockup is the url property in pom.xml
Contents of pom.xml:
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
34 matches
Mail list logo