Hi,
Recently we needed to create a new branch for our code and we realized the
documentation generated by maven with mvn site:site will drift apart in
time. So we need to deploy both versions of the site (multiple versions for
the future maybe ?)
I was wondering if there are some best practices
Guys,
We have a local repository where we put all the artifacts that we need in
our project. Recently though I added a new version of the maven-release
plugin and, when I try to use it, I'm getting a NullPointerException as
follows:
[EMAIL PROTECTED] trunk]$ mvn -X release:branch
,
Nick Stolwijk
-Original Message-
From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 13:00
To: users@maven.apache.org
Subject: NullPointerException in maven
Guys,
We have a local repository where we put all the artifacts that we need in
our project. Recently though
:8081/maven_repo/org/apache/maven/plugins/maven-metadata.xml.sha1from
a browser or wget, does that succeed?
Hth,
Nick S.
-Original Message-
From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 14:11
To: Maven Users List
Subject: Re: NullPointerException in maven
: Ionut Scutaru [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 14:11
To: Maven Users List
Subject: Re: NullPointerException in maven
Sorry, I wasn't clear enough.. It's an internal remote repository on a
server.
I uploaded the artifacts using the deploy plugin. (we did that for all
our
don't know who had them or
if they still exist.
Some of maven 2 developers are often on IRC, maybe you could ask them if
they still have those scripts.
Hth,
Nick Stolwijk
-Original Message-
From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 14:33
To: Maven Users
/maven/plugins/maven-metadata.xml
And perhaps replace your files (the xml, the sha1 and the md5) with the
files from repo1.
Hth,
Nick Stolwijk
-Original Message-
From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 15:05
To: Maven Users List
Subject: Re
it less e.g.
X.Y.Z-A X.Y.Z
which obviously causes odd behaviour..
I use versions like 1.0, 1.1, 1.2
and patches being builds off branches being 1.0.1, 1.0.2, 1.1.2 etc etc
On Wednesday 31 October 2007 02:33, Ionut Scutaru wrote:
Hi guys,
We have a multi-module project; we are using
Hi guys,
What's the recommended usage of the scm tag in a project with multiple
modules ? Should it be specified in each pom.xml file, in the root and in
each module ? Or is it enough to mention it once, in the root pom.xml file ?
I searched on Google almost an hour but couldn't find anything
Hi guys,
We have a multi-module project; we are using 1.0.0-SNAPSHOT as version for
every module. We are trying to have a release at the end of every week, so
our releases get the following form: 1.0.0-Wxx. In time we realized we need
to branch the project before releasing it so we have some time
of applying this procedure for our entire
project. Guys, you really need to improve its reliability ...
On 10/30/07, Ionut Scutaru [EMAIL PROTECTED] wrote:
Hi guys,
We have a multi-module project; we are using 1.0.0-SNAPSHOT as version for
every module. We are trying to have a release at the end
(
DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
On 10/30/07, Ionut Scutaru [EMAIL PROTECTED] wrote:
Actually it's working fine... I was able to do
12 matches
Mail list logo
