that's default inheritance from svn heritage :-)
use https://git-wip-us.apache.org/repos/asf?p=maven-scm.git
On 21 March 2014 11:41, Chris Graham wrote:
> Hi All.
>
> In looking at:
>
> http://maven.apache.org/scm/maven-scm-plugin/source-repository.html
>
> I can wee the Web Access link as:
Hi All.
In looking at:
http://maven.apache.org/scm/maven-scm-plugin/source-repository.html
I can wee the Web Access link as:
https://git-wip-us.apache.org/repos/asf?p=maven-scm.git/maven-scm-plugin
but it returns a 404!
What is it meant to be?
-Chris
Hi,
We are bumping into the following problem, a partial archetype contains files
that already exist in the maven project. At the moment this goes into error
although it seems that it should go into warning (looking at the name of the
method used).
org.apache.maven.archetype.generator.Default
Hi Mirko,
>
Both the Maven 3[0] and Maven 2[1] build fail because two of the
components (maven-shared-utils, maven-jar-signer) are currently voted
on, so are not available in Central.
1) I see there is a staging-group at
https://repository.apache.org/content/repositories/maven-staging-group
Hello,
I now committed some stuff in the maven-javadoc-plugin and got failed
Jenkins builds.
I was not very worried about me breaking things because the module
itself did build.
Both the Maven 3[0] and Maven 2[1] build fail because two of the
components (maven-shared-utils, maven-jar-signer) are