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
cm-maven-repo.itcnetworks:8081/maven_repo/org/apache/maven/plugins/maven-metadata.xml
> with
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml
>
> And perhaps replace your files (the xml, the sha1 and the md5) with the
> files from repo1.
>
> Hth
d checksums, IIRC. I 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 Scu
t;
> Nick Stolwijk
>
>
> -Original Message-
> From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
> Sent: Wed 2/13/2008 14:24
> To: Maven Users List
> Subject: Re: NullPointerException in maven
>
> Nope, it doesn't.
>
>
> On Feb 13, 2008 3:16 PM, <[EMAIL
>
> If you try to get
> http://ecm-maven-repo.itcnetworks: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
ther developers.
> Don't mess with these, or you can get weird effects.
>
> Hth,
>
> Nick Stolwijk
>
>
> -Original Message-
> From: Ionut Scutaru [mailto:[EMAIL PROTECTED]
> Sent: Wed 2/13/2008 13:00
> To: users@maven.apache.org
> Subject: NullPointe
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 -DupdateBranchVe
Hi guys,
What's the recommended usage of the 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 helpf
ially and makes 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 Scut
ecute(
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..
t makes me afraid 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.
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
12 matches
Mail list logo