Hi,
I couldn´t resolve ${project.scm.tag} in a multimodule build:
when calling mvn clean install -Prelease (to test the release profile) a
file named version.properties gets always filtered to:
# Buildversion
productVersion=HEAD
I expected productVersion=TEST-TAG instead.
My parent pom.xml
I think this question have been asked before
http://maven.40175.n5.nabble.com/Enforcer-Plugin-and-Dependency-Resoluti
on-td208432.html
Is there any update on whether this issue is fixed, or is there any
workaround?
Enforcer plugin become almost useless in multi-module project because of
this
Doesn't anybody have an idea?
On 06.11.2010 19:09, Asmann, Roland wrote:
Hi all,
I'm having some problems with properties in archetypes. I read that it
is possible to have files and directories renamed with properties
(http://jira.codehaus.org/browse/ARCHETYPE-191), but this seems to be
I tried using this some time ago and remember this cannot be used for
generic properties, only for groupId (if I remember correctly). The
archetype plugin has some limitations at the moment. I hope this can be
improved soon.
Joachim
On 11/18/2010 12:36 PM, Asmann, Roland wrote:
Doesn't
Hi Waseem,
I dont have maven book which is u saying to read pages 32 to 42.
Could u please share with me.
I am getting same error. i am very frustured with this issue.
I am working on this issue last 2 days but i am not able to resolve.
Please help me.
Thanks Regards,
Sachin
Hi folks,
I am trying to use the embedder on my project and run into different
behaviour between embedder (class MavenCLI) and the maven command line.
The command that gets executed looks like:
mvn -X -gs ...\maven.settings.xml -f ...\simple-pom.xml clean
Using the embedder with an
Hi,
I'm trying to perform a release of a multi-modul project on a nexus
repository.
I've got a strange issue : the first file is successfully transfered and
visible under the nexus repository, but after this first file transfert, the
release process exits with an error 400.
Can you help me to
I would start by checking for any error message. Either from Maven or in the
Nexus log. That should shed some light on this.
/Anders
On Thu, Nov 18, 2010 at 18:34, sandraB sandra.boga...@gmail.com wrote:
Hi,
I'm trying to perform a release of a multi-modul project on a nexus
repository.
On 18/11/2010, at 4:51 PM, Ron Wheeler wrote:
On 17/11/2010 6:42 PM, Wayne Fay wrote:
This seems off-topic for the Maven list?
Perhaps not. I like the fact that STS comes bundled with Maven
2.2.1 and m2e. If you're a Maven developer then this is a good IDE bundle.
I personally don't
Hi,
we're aiming at a bugfix release of Maven 3 in the next week and
following tradition we invite interested users in taking the RC for a
test drive in order to detect and fix potential regressions since
version 3.0 before the actual release of 3.0.1.
For the duration of the RC testing,
On 18/11/2010 5:39 PM, Brett Porter wrote:
On 18/11/2010, at 4:51 PM, Ron Wheeler wrote:
On 17/11/2010 6:42 PM, Wayne Fay wrote:
This seems off-topic for the Maven list?
Perhaps not. I like the fact that STS comes bundled with Maven
2.2.1 and m2e. If you're a Maven developer then this is a
This is in reply to an earlier post where I was complaining that hudson
changes default maven behavior and does not fail the build on test failures.
This means that the deploy goal would result in actually deploying the
artifacts even though the tests failed.
Here is the code from
12 matches
Mail list logo
