Author: brett
Date: Tue Oct 2 08:09:25 2012
New Revision: 1392782
URL: http://svn.apache.org/viewvc?rev=1392782&view=rev
Log:
replace vmbuild references
Modified:
incubator/npanday/trunk/pom.xml
incubator/npanday/trunk/site/src/site/apt/guide/advanced/dependencies.apt
incubator/npanday/trunk/site/src/site/apt/guide/devinfra/artifact-repository.apt
Modified: incubator/npanday/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/pom.xml?rev=1392782&r1=1392781&r2=1392782&view=diff
==============================================================================
--- incubator/npanday/trunk/pom.xml (original)
+++ incubator/npanday/trunk/pom.xml Tue Oct 2 08:09:25 2012
@@ -59,7 +59,7 @@ under the License.
<repository>
<id>3rdparty</id>
<name>3rd Party .NET Repository</name>
- <url>http://vmbuild.apache.org/archiva/repository/3rdparty</url>
+
<url>https://archiva-repository.apache.org/archiva/repository/3rdparty</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
Modified:
incubator/npanday/trunk/site/src/site/apt/guide/advanced/dependencies.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/guide/advanced/dependencies.apt?rev=1392782&r1=1392781&r2=1392782&view=diff
==============================================================================
--- incubator/npanday/trunk/site/src/site/apt/guide/advanced/dependencies.apt
(original)
+++ incubator/npanday/trunk/site/src/site/apt/guide/advanced/dependencies.apt
Tue Oct 2 08:09:25 2012
@@ -61,7 +61,7 @@ Project Dependencies
As mentioned above, the special type of <<<gac_msil>>> is available to refer
to dependencies in the GAC.
For all other dependencies, they should be located in a remote artifact
repository. NPanday offers a few dependencies
- in the repository
{{http://vmbuild.apache.org/archiva/repository/3rdparty/}}. More commonly
however, you will establish
+ in the repository
{{https://archiva-repository.apache.org/archiva/repository/3rdparty/}}. More
commonly however, you will establish
and populate your own artifact repository as described in
{{{../devinfra/artifact-repository.html} Setting up an Artifact Repository}}.
Modified:
incubator/npanday/trunk/site/src/site/apt/guide/devinfra/artifact-repository.apt
URL:
http://svn.apache.org/viewvc/incubator/npanday/trunk/site/src/site/apt/guide/devinfra/artifact-repository.apt?rev=1392782&r1=1392781&r2=1392782&view=diff
==============================================================================
---
incubator/npanday/trunk/site/src/site/apt/guide/devinfra/artifact-repository.apt
(original)
+++
incubator/npanday/trunk/site/src/site/apt/guide/devinfra/artifact-repository.apt
Tue Oct 2 08:09:25 2012
@@ -26,8 +26,19 @@ Setting up an Artifact Repository
will operate similarly. Instructions on installing Archiva can be found on
the
{{{http://archiva.apache.org/docs/1.3/quick-start.html} Archiva web site}}.
+* Proxying Future Releases
+
+ NPanday releases are mirrored to the central repository configured by
+ default in Maven and all known repository managers. There should be nothing
+ more to do once you've installed a repository manager to get access to new
+ NPanday releases.
+
* Creating an NPanday repository
+ If you're prefer to download the repository from the release and unpack it
+ into your repository manager, rather than proxy them from an external
+ location on deman, you can do so.
+
~~TODO: pictures would help
Logged in as the administrator created when installed, go to the
<Repositories> tab and add a new managed repository.
@@ -54,26 +65,6 @@ Setting up an Artifact Repository
You will next need to configure Maven to use this remote repository. This
can be done using the instructions shown on
the Archiva web site,
{{{http://archiva.apache.org/docs/1.3/userguide/using-repository.html}
Configuring Maven 2 to use an Archiva repository}}.
-* Proxying Future Releases
-
- An alternative to downloading the releases from the NPanday site is to
automatically obtain them from the NPanday
- repository on demand using Archiva's repository proxy feature.
-
- To do so, first go to the <Repositories> tab and add a new <remote>
repository (below the <managed> repositories at
- the top). The fields used will be:
-
- * <Identifier>: <<<npanday.remote>>>
-
- * <Name>: NPanday Remote Repository
-
- * <URL>: {{http://vmbuild.apache.org/archiva/repository/npanday-group}}
-
- []
-
- After this is added, you can connect the previous <<<npanday>>> repository
with the <<<npanday.remote>>> repository
- using a proxy connector. You can find more information on the Archiva web
site, under
- {{{http://archiva.apache.org/docs/1.3/adminguide/proxy-connectors.html}
Understanding Proxy Connector Configuration of Apache Archiva}}.
-
* Separate NPanday Release Repository
The above techniques provide repositories that contain not only the NPanday
releases, but also all of the artifacts
@@ -90,7 +81,7 @@ Setting up an Artifact Repository
* the Open RDF repository, which can be proxied from
{{http://repository.aduna-software.org/maven2}}.
Only the <<<info/aduna/**>>> and <<<org/openrdf/**>>> artifacts need to
be proxied.
- * 3rd party .NET dependencies. Some can be obtained from
{{http://vmbuild.apache.org/archiva/repository/3rdparty/}},
+ * 3rd party .NET dependencies. Some can be obtained from
{{https://archiva-repository.apache.org/archiva/repository/3rdparty/}},
or they can be uploaded manually to your own managed repository.
Currently, only NUnit is included there.
[]
