I don't have an answer, but I do have a question: I've seen this
"bootstrap" situation w/ internal repo's discussed before, and my
solution was to use a "common" (or "bootstrap") parent pom as the parent
for all our project poms. For example:
ParentPom:
...
<groupId>org.mine</groupId>
<artifactId>pomCommon</artifactId>
<packaging>pom</packaging>
<version>1.0-SNAPSHOT</version>
<name>Shared Maven settings - Parent pom</name> ...
<repositories>
<repository>
<id>internal.repo.release</id>
<name>Release Repo</name>
<url>...</url>
</repository>
<repository>
<id>internal.repo.snapshot</id>
<name>Snapshot Repo</name>
<url>...</url>
</repository>
<repository>
<id>central</id>
<name>Maven Proxy of Central repo</name>
<url>http://...maven proxy box...:9999/repository</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>internal.repo.release</id>
<name>Release Repo</name>
<url>...</url>
</pluginRepository>
<pluginRepository>
<id>internal.repo.snapshot</id>
<name>Snapshot Repo</name>
<url>...</url>
</pluginRepository>
<pluginRepository>
<id>central</id>
<name>Maven Proxy of Central repo</name>
<url>http://...maven proxy box...:9999/repository</url>
</pluginRepository>
</pluginRepositories>
...
Then all Project POMS's have:
<parent>
<groupId>org.mine</groupId>
<artifactId>pomCommon</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
<groupId>org.mine.proj</groupId>
<artifactId>...</artifactId>
...
With this approach, a new machine need only get the pomCommon installed
in their local repo (could be done via a boostrap project, script, or
whatever). From then on, they always hit the internal remote repos. One
advantage here is updates to the pomCommon will automatically propogate
to users. Am I missing something fundamental here?
Dan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 12:13 PM
To: Maven Users List
Subject: [M2] another internal remote repository question
Like many other posts on this mailing list, I'm currently struggling to
get my internal remote repository working correctly.
Having developed a new archetype for developers to use internally to
build adaptors, I am also providing them with a pre-configured
maven-2.0.2 installation that contains a profile (activated by default -
see below section from
settings.xml) which points to our internal remote repositories. If this
worked, it would prevent developers having to run 'maven install' on the
top level project to create, build and install all artifacts into their
local repository.
Note that when users start to build these adaptors, they have no project
(and therefore no pom.xml), hence to create an instance of the
archetype, maven needs to download the archetype from our internal
remote repositories (hence the below configuration in settings.xml).
Project artifacts are deployed to repository with
id='jpm-inhouse-release'
Project artifact dependencies are held in repository with id='
jpm-ibiblio-mirror'
<profile>
<id>use-jpm-repositories</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>jpm-inhouse-release</id>
<name>Corporate Internal release repository</name>
<url>
http://corporate.domain.com/svn/repos/mavenRepository/trunk/m2repository
-jpm-release
</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>jpm-inhouse-snapshot</id>
<name>Corporate Internal snapshot repository </name>
<url>
http://corporate.domain.com/svn/repos/mavenRepository/trunk/m2repository
-jpm-snapshot
</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>jpm-ibiblio-mirror</id>
<name>Corporate Internal mirror of ibiblio repository</name>
<url>
http://corporate.domain.com/svn/repos/mavenRepository/trunk/m2repository
</
url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
</profile>
When creating an adaptor instance using our archetype, maven never
attempts to retrieve the dependencies from 'jpm-ibiblio-mirror' even
though it exists and is configured in settings.xml.
C:\temp\ixgf>createAdapter TestAdaptor
ECHO is off.
"creating new adapter instance called 'TestAdaptor'"
ECHO is off.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] com.jpmorgan.adaptor: checking for updates from central [INFO]
org.apache.maven.plugins: checking for updates from central [INFO]
org.codehaus.mojo: checking for updates from central [INFO] artifact
org.apache.maven.plugins:maven-archetype-plugin: checking for up dates
from central
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin
-parent/2.0-beta-1/maven-plugin-parent-2.0-beta-1.pom
6K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.jar
6K downloaded
Does anyone know why maven is not trying to download these artifacts
from the repositories configured in the above profile within my
settings.xml?
Thanks,
John
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of any
financial instrument or as an official confirmation of any transaction.
All market prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice. Any
comments or statements made herein do not necessarily reflect those of
JPMorgan Chase & Co., its subsidiaries and affiliates.
--------------------------------------------------
This e-mail and any files transmitted with it may contain privileged or
confidential information.
It is solely for use by the individual for whom it is intended, even if
addressed incorrectly.
If you received this e-mail in error, please notify the sender; do not
disclose, copy, distribute,
or take any action in reliance on the contents of this information; and delete
it from
your system. Any other use of this e-mail is prohibited.
Thank you for your compliance.
--------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
