Nabble - Maven

[jira] Commented: (MAVENUPLOAD-2279) please sync org.bluestemsoftware

2008-12-02T18:12:19Z

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156424#action_156424 ]

twayne commented on MAVENUPLOAD-2279:
-------------------------------------

Hi Carlos,

Here's extract from log (not sure what the warning means):

Dec 1 09:54:23 ip-208-109-219-84 sshd[16163]: Connection from 207.182.253.34 port 60783
Dec 1 09:54:25 ip-208-109-219-84 sshd[16163]: reverse mapping checking getaddrinfo for haw-207-182-253-34.vel.net [207.182.253.34] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec 1 09:54:25 ip-208-109-219-84 sshd[16163]: Failed publickey for archiva from 207.182.253.34 port 60783 ssh2
Dec 1 09:54:32 ip-208-109-219-84 sshd[16164]: Connection closed by 207.182.253.34

I can run the following w/ my pub/priv key w/out error (so i know permissions are set correctly):

rsync --include=*/ --include=**/maven-metadata.xml* --exclude=* -Lrtivz "--rsh=ssh" archiva@...:/var/archiva/data/repositories/internal test

Also, I added authorized_keys2 file (only had authorized_keys,) which may be the problem depending upon version of ssh you're client is using???

Here's the maven public key contained within the above files:

ssh-dss AAAAB3NzaC1kc3MAAACBAL9WxLqVn4DgS3pl6XrHQ467FLfhX+9ESYUQNsmqOxsubixtVVfiNFDpDI/LlSZSs9YcKr6XUMrVy58y3yg8pxR+T+4h3xGlUIhr/YJ60z02X7mSYNa8S2uVVL2Gou8z/GjDJnlY1GGzqXwKI07WdQ8QSAK8AYgAAZfVzn4VbCcjAAAAFQCnVrFfasrKOb6s8gteHeYyYPgndwAAAIEAhtVdf/cQ+KuzBQQqEhz9O7rqSh5GqZE177oY+2lPNpR8lKg2TRk87j3sh506gmpk82Gm4RvAOBOI6zEwLoOLsR+ucVSzUfhqgGanUworHVUnGQ7mIBqBq91JVVGORfVfK5/omi0ShIdhyZscf3vmeE3GiYtH8J3aUbGXxylkpLYAAACAOBk/ghnjuujhVo4sypxn0ATVLJ4ZcyHkl2vC4SE6VQ2XgYQv3P+NLbQtKoiNASifF1V0sOrzXxPzhPwWoh+8SxVqVLui7VC+2MKgd3etBJ3tllXIjgsxL9k8LxfDwsM+3dmICf28YQePRt4XkXADthdhOdkgG7MnpSidVmNBgDc= maven@...

> please sync org.bluestemsoftware
> --------------------------------
>
> Key: MAVENUPLOAD-2279
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2279
> Project: Maven Upload Requests
> Issue Type: Wish
> Reporter: twayne
>
> http://www.networksolutions.com/whois/results.jsp?domain=bluestemsoftware.org

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

From forum: Maven - Issues

RE: LATEST and RELEASE

2008-12-02T17:28:23Z

Just an observation from today when RELEASE didn't work for us.

I was at someone's desk who normally build's the parent pom we are
trying to reference as RELEASE. His last build of the pom or perhaps
every build to his local repository is done without mvn install
-DupdateReleaseInfo=true (so false.) The dependent project failed to
build due to not resolving the RELEASE version. He rebuilt the parent
(corporate pom) with -DupdateReleaseInfo=true and then it worked.

My guess is that when RELEASE version is being resolved it finds the
artifact in the local repository but doesn't find the release metadata
and fails.
Perhaps, while resolving RELEASE all configured repositories need or
should be consulted... Seems like that doesn't happen. (first find fail)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

From forum: Maven - Users

svn commit: r722695 - /maven/mercury/branches/722617/pom.xml

2008-12-02T16:09:00Z

Author: ogusakov
Date: Tue Dec 2 16:09:00 2008
New Revision: 722695

URL: http://svn.apache.org/viewvc?rev=722695&view=rev
Log:
had to add repo to the POM to make grid build work :(

Modified:
maven/mercury/branches/722617/pom.xml

Modified: maven/mercury/branches/722617/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/pom.xml?rev=722695&r1=722694&r2=722695&view=diff
==============================================================================
--- maven/mercury/branches/722617/pom.xml (original)
+++ maven/mercury/branches/722617/pom.xml Tue Dec 2 16:09:00 2008
@@ -42,6 +42,16 @@
<module>mercury-event</module>
<module>mercury-logging</module>
</modules>
+
+ <repositories>
+ <repository>
+ <id>sona.plexus.releases</id>
+ <url>http://repository.sonatype.org/content/repositories/plexus-releases-oss</url>
+ <snapshots><enabled>false</enabled></snapshots>
+ <releases><enabled>true</enabled></releases>
+ </repository>
+ </repositories>
+

<properties>

@@ -515,14 +525,5 @@
<url>http://svn.apache.org/viewvc/maven/mercury/trunk/</url>
</scm>

- <repositories>
- <repository>
- <id>sona.plexus.releases</id>
- <url>http://repository.sonatype.org/content/repositories/plexus-releases-oss</url>
- <snapshots><enabled>false</enabled></snapshots>
- <releases><enabled>true</enabled></releases>
- </repository>
- </repositories>
-

</project>

From forum: Maven - Commits

svn commit: r722686 - /maven/mercury/branches/722617/pom.xml

2008-12-02T16:01:17Z

Author: ogusakov
Date: Tue Dec 2 16:01:16 2008
New Revision: 722686

URL: http://svn.apache.org/viewvc?rev=722686&view=rev
Log:
had to add repo to the POM to make grid build work :(

Modified:
maven/mercury/branches/722617/pom.xml

Modified: maven/mercury/branches/722617/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/pom.xml?rev=722686&r1=722685&r2=722686&view=diff
==============================================================================
--- maven/mercury/branches/722617/pom.xml (original)
+++ maven/mercury/branches/722617/pom.xml Tue Dec 2 16:01:16 2008
@@ -515,4 +515,14 @@
<url>http://svn.apache.org/viewvc/maven/mercury/trunk/</url>
</scm>

+ <repositories>
+ <repository>
+ <id>sona.plexus.releases</id>
+ <url>http://repository.sonatype.org/content/repositories/plexus-releases-oss</url>
+ <snapshots><enabled>false</enabled></snapshots>
+ <releases><enabled>true</enabled></releases>
+ </repository>
+ </repositories>
+
+
</project>

From forum: Maven - Commits

[jira] Commented: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository

2008-12-02T15:44:19Z

[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156408#action_156408 ]

Nick Stolwijk commented on SCM-262:
-----------------------------------

Wouldn't it be possible to take the revision number at start of the release and give that to svn checkout and svn copy? Noone can change a revision so you will be save.

> scm:tag for subversion tagging from local version of code, not directly from repository
> ---------------------------------------------------------------------------------------
>
> Key: SCM-262
> URL: http://jira.codehaus.org/browse/SCM-262
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Reporter: Stephan Heilner
> Fix For: future
>
>
> In theory, you shouldn't tag or branch from a local and potentially different version of the code. From what I can tell, the scm:tag imports your existing code into a new tag. With subversion, tagging is very lightweight if you do a 'svn copy trunk_url tag_url'. The way it currently works make sense for other repositories such as CVS but not for subversion.

From forum: Maven - Issues

svn commit: r722662 - in /maven/mercury/branches/722617: ./ mercury-artifact/ mercury-crypto/ mercury-crypto/mercury-crypto-api/ mercury-crypto/mercury-crypto-basic/ mercury-event/ mercury-external/ mercury-logging/ mercury-md/ mercury-md/mercury-md-sa...

2008-12-02T15:12:21Z

Author: ogusakov
Date: Tue Dec 2 15:12:21 2008
New Revision: 722662

URL: http://svn.apache.org/viewvc?rev=722662&view=rev
Log:
preparing for the test release

Modified:
maven/mercury/branches/722617/mercury-artifact/pom.xml
maven/mercury/branches/722617/mercury-crypto/mercury-crypto-api/pom.xml
maven/mercury/branches/722617/mercury-crypto/mercury-crypto-basic/pom.xml
maven/mercury/branches/722617/mercury-crypto/pom.xml
maven/mercury/branches/722617/mercury-event/pom.xml
maven/mercury/branches/722617/mercury-external/pom.xml
maven/mercury/branches/722617/mercury-logging/pom.xml
maven/mercury/branches/722617/mercury-md/mercury-md-sat/pom.xml
maven/mercury/branches/722617/mercury-md/mercury-md-shared/pom.xml
maven/mercury/branches/722617/mercury-md/pom.xml
maven/mercury/branches/722617/mercury-util/pom.xml
maven/mercury/branches/722617/pom.xml

Modified: maven/mercury/branches/722617/mercury-artifact/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-artifact/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-artifact/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-artifact/pom.xml Tue Dec 2 15:12:21 2008
@@ -7,7 +7,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

</project>
\ No newline at end of file

Modified: maven/mercury/branches/722617/mercury-crypto/mercury-crypto-api/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-crypto/mercury-crypto-api/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-crypto/mercury-crypto-api/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-crypto/mercury-crypto-api/pom.xml Tue Dec 2 15:12:21 2008
@@ -3,7 +3,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-crypto</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<artifactId>mercury-crypto-api</artifactId>

Modified: maven/mercury/branches/722617/mercury-crypto/mercury-crypto-basic/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-crypto/mercury-crypto-basic/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-crypto/mercury-crypto-basic/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-crypto/mercury-crypto-basic/pom.xml Tue Dec 2 15:12:21 2008
@@ -6,7 +6,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-crypto</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<dependencies>

Modified: maven/mercury/branches/722617/mercury-crypto/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-crypto/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-crypto/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-crypto/pom.xml Tue Dec 2 15:12:21 2008
@@ -5,7 +5,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<artifactId>mercury-crypto</artifactId>

Modified: maven/mercury/branches/722617/mercury-event/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-event/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-event/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-event/pom.xml Tue Dec 2 15:12:21 2008
@@ -3,7 +3,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>
<artifactId>mercury-event</artifactId>
<name>Mercury Event Framework</name>

Modified: maven/mercury/branches/722617/mercury-external/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-external/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-external/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-external/pom.xml Tue Dec 2 15:12:21 2008
@@ -7,7 +7,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<dependencies>

Modified: maven/mercury/branches/722617/mercury-logging/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-logging/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-logging/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-logging/pom.xml Tue Dec 2 15:12:21 2008
@@ -3,7 +3,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>
<artifactId>mercury-logging</artifactId>
<name>Mercury Logging</name>

Modified: maven/mercury/branches/722617/mercury-md/mercury-md-sat/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-md/mercury-md-sat/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-md/mercury-md-sat/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-md/mercury-md-sat/pom.xml Tue Dec 2 15:12:21 2008
@@ -6,7 +6,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-md</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<build>

Modified: maven/mercury/branches/722617/mercury-md/mercury-md-shared/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-md/mercury-md-shared/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-md/mercury-md-shared/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-md/mercury-md-shared/pom.xml Tue Dec 2 15:12:21 2008
@@ -8,7 +8,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-md</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>

<build>

Modified: maven/mercury/branches/722617/mercury-md/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-md/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-md/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-md/pom.xml Tue Dec 2 15:12:21 2008
@@ -4,14 +4,13 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>
<artifactId>mercury-md</artifactId>
<packaging>pom</packaging>
<name>Mercury Metadata</name>

<modules>
- <module>mercury-md-sat</module>
<module>mercury-md-shared</module>
</modules>

Modified: maven/mercury/branches/722617/mercury-util/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/mercury-util/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/mercury-util/pom.xml (original)
+++ maven/mercury/branches/722617/mercury-util/pom.xml Tue Dec 2 15:12:21 2008
@@ -3,7 +3,7 @@
<parent>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury</artifactId>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
</parent>
<artifactId>mercury-util</artifactId>
<name>Mercury Shared Utilities</name>

Modified: maven/mercury/branches/722617/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/pom.xml?rev=722662&r1=722661&r2=722662&view=diff
==============================================================================
--- maven/mercury/branches/722617/pom.xml (original)
+++ maven/mercury/branches/722617/pom.xml Tue Dec 2 15:12:21 2008
@@ -12,7 +12,7 @@
<artifactId>mercury</artifactId>
<packaging>pom</packaging>
<name>Mercury</name>
- <version>1.0.0-alpha-2-SNAPSHOT</version>
+ <version>1.0.0-alpha-2-722647</version>
<description>Maven Mercury is a replacement for the Maven Artifact subsystem, and a complete replacement for the HTTP/HTTPS/DAV/DAVS portions of the existing transport.</description>

<developers>
@@ -47,8 +47,6 @@

<mercury.version>${project.version}</mercury.version>

- <maven.version>3.0-SNAPSHOT</maven.version>
-
<plexus.appbooter.version>1.4</plexus.appbooter.version>
<plexus.container.version>1.0-beta-3.0.1</plexus.container.version>
<classworlds.version>1.3</classworlds.version>
@@ -222,88 +220,12 @@
<artifactId>mercury-crypto-basic</artifactId>
<version>${mercury.version}</version>
</dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-api</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-local-m2</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-local-m2</artifactId>
- <classifier>tests</classifier>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-remote-m2</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-virtual</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-repo-cache-fs</artifactId>
- <version>${mercury.version}</version>
- </dependency>

<dependency>
<groupId>org.apache.maven.mercury</groupId>
<artifactId>mercury-md-sat</artifactId>
<version>${mercury.version}</version>
</dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-transport-api</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-transport-http</artifactId>
- <version>${mercury.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.mercury</groupId>
- <artifactId>mercury-transport-http</artifactId>
- <classifier>tests</classifier>
- <version>${mercury.version}</version>
- </dependency>
-
- 
- <dependency>
- <groupId>org.apache.maven</groupId>
- <artifactId>maven-mercury</artifactId>
- <version>${maven.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.wagon</groupId>
- <artifactId>wagon-provider-api</artifactId>
- <version>${wagon.provider.api.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.apache.maven.wagon</groupId>
- <artifactId>wagon-provider-test</artifactId>
- <version>${wagon.provider.api.version}</version>
- <scope>test</scope>
- </dependency>


<dependency>

From forum: Maven - Commits

svn commit: r722659 - /maven/mercury/branches/722617/pom.xml

2008-12-02T15:00:20Z

Author: ogusakov
Date: Tue Dec 2 15:00:20 2008
New Revision: 722659

URL: http://svn.apache.org/viewvc?rev=722659&view=rev
Log:
preparing for the release

Modified:
maven/mercury/branches/722617/pom.xml

Modified: maven/mercury/branches/722617/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/branches/722617/pom.xml?rev=722659&r1=722658&r2=722659&view=diff
==============================================================================
--- maven/mercury/branches/722617/pom.xml (original)
+++ maven/mercury/branches/722617/pom.xml Tue Dec 2 15:00:20 2008
@@ -36,15 +36,11 @@
<modules>
<module>mercury-artifact</module>
<module>mercury-md</module>
- <module>mercury-repo</module>
- <module>mercury-transport</module>
<module>mercury-external</module>
<module>mercury-crypto</module>
<module>mercury-util</module>
<module>mercury-event</module>
<module>mercury-logging</module>
- <module>mercury-plexus</module>
- <module>mercury-wagon</module>
</modules>

<properties>

From forum: Maven - Commits

[jira] Closed: (MNGSITE-66) Bad link on the intro to repositories page

2008-12-02T14:58:19Z

[ http://jira.codehaus.org/browse/MNGSITE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNGSITE-66.
------------------------------------

Assignee: Benjamin Bentmann
Resolution: Fixed

Fixed in [r722657|http://svn.eu.apache.org/viewvc?view=rev&revision=722657].

> Bad link on the intro to repositories page
> ------------------------------------------
>
> Key: MNGSITE-66
> URL: http://jira.codehaus.org/browse/MNGSITE-66
> Project: Maven 2 Project Web Site
> Issue Type: Bug
> Reporter: Eric Haszlakiewicz
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> On the page:
> http://maven.apache.org/guides/introduction/introduction-to-repositories.html
> The "The Hype About Repository Managers" link at the bottom of the page points at:
> http://www.devzuz.org/blogs/oching/2007/11/05/1194233400000.html
> when it should point at this instead:
> http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/

From forum: Maven - Issues

svn commit: r722657 - /maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt

2008-12-02T14:56:05Z

Author: bentmann
Date: Tue Dec 2 14:56:04 2008
New Revision: 722657

URL: http://svn.apache.org/viewvc?rev=722657&view=rev
Log:
[MNGSITE-66] Bad link on the intro to repositories page

Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt

Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt?rev=722657&r1=722656&r2=722657&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt (original)
+++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-repositories.apt Tue Dec 2 14:56:04 2008
@@ -184,7 +184,7 @@

* External Links

- * {{{http://www.devzuz.org/blogs/oching/2007/11/05/1194233400000.html}The Hype About Repository Managers}}
+ * {{{http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/}The Hype About Repository Managers}}

* {{{http://maven.apache.org/archiva}Archiva}}

From forum: Maven - Commits

[jira] Closed: (ARCHETYPE-81) Archetype not downloaded until pom is placed in working dir

2008-12-02T14:54:19Z

[ http://jira.codehaus.org/browse/ARCHETYPE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raphaël Piéroni closed ARCHETYPE-81.
------------------------------------

Resolution: Cannot Reproduce

Thanks to Tim Reilly.
This is issue is closed by obsolescence.

> Archetype not downloaded until pom is placed in working dir
> -----------------------------------------------------------
>
> Key: ARCHETYPE-81
> URL: http://jira.codehaus.org/browse/ARCHETYPE-81
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0-alpha-4
> Reporter: Tim Reilly
> Fix For: 2.0-alpha-5
>
>
> Our archetype is hosted internally in the company repository.
> Our settings.xml contains profiles with the internal repository locations.
> I mkdir C:\temp\archtest
> I execute mvn archetype:create -D.... etc
> I get "could not download archetype ... from central
> Next I put a valid pom.xml in the working dir
> I execute mvn archetype:create -D etc
> I get an expected error since the directory is not empty, but now if I check my local repository the archetype is downloaded from the company repository. !! Why wasn't it found until a pom.xml is in the directory?
> Now I delete the pom.xml
> Now I can build sucessfully.
> It would appear the profiles where we define our repositories are not being used until the pom.xml is available. But even mvn -P archetype:create doesn't resolve the issue.

From forum: Maven - Issues

[jira] Closed: (MNGSITE-71) Mistakes in "Introduction to the Dependency Mechanism"

2008-12-02T14:50:19Z

[ http://jira.codehaus.org/browse/MNGSITE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNGSITE-71.
------------------------------------

Assignee: Benjamin Bentmann
Resolution: Fixed

Fixed in [r722656|http://svn.eu.apache.org/viewvc?view=rev&revision=722656].

> Mistakes in "Introduction to the Dependency Mechanism"
> ------------------------------------------------------
>
> Key: MNGSITE-71
> URL: http://jira.codehaus.org/browse/MNGSITE-71
> Project: Maven 2 Project Web Site
> Issue Type: Bug
> Reporter: Trevor Harmon
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> There is an introduction to the dependency mechanism here:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> But it has some mistakes. First, there is at least one misspelling: "managemnet".
> Also, some of the sample POMs refer to "maven-test" as the groupId, but I believe the groupIds should be "test" instead. With "maven-test", the dependencies are all distinct (test:a, test:c, maven-test:a, and maven-test:c), and the explanatory text (such as "a and c both are declared as dependencies of the project") does not make sense.

From forum: Maven - Issues

svn commit: r722656 - /maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt

2008-12-02T14:47:30Z

Author: bentmann
Date: Tue Dec 2 14:47:30 2008
New Revision: 722656

URL: http://svn.apache.org/viewvc?rev=722656&view=rev
Log:
[MNGSITE-71] Mistakes in "Introduction to the Dependency Mechanism"

Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt

Modified: maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt?rev=722656&r1=722655&r2=722656&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt (original)
+++ maven/site/trunk/src/site/apt/guides/introduction/introduction-to-dependency-mechanism.apt Tue Dec 2 14:47:30 2008
@@ -374,13 +374,13 @@
</dependencyManagement>
<dependencies>
<dependency>
- <groupId>maven-test</groupId>
+ <groupId>test</groupId>
<artifactId>a</artifactId>
<version>1.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
- <groupId>maven-test</groupId>
+ <groupId>test</groupId>
<artifactId>c</artifactId>
<scope>runtime</scope>
</dependency>
@@ -395,7 +395,7 @@
* a and c both are declared as dependencies of the project so version 1.0 is used due to
dependency mediation. Both will also have runtime scope since it is directly specified.

- * b is defined in B's parent's dependency managemnet section and since dependency management
+ * b is defined in B's parent's dependency management section and since dependency management
takes precedence over dependency mediation for transitive dependencies, version 1.0 will be
selected should it be referenced in a or c's pom. b will also have compile scope.

@@ -447,13 +447,13 @@
</dependencyManagement>
<dependencies>
<dependency>
- <groupId>maven-test</groupId>
+ <groupId>test</groupId>
<artifactId>a</artifactId>
<version>1.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
- <groupId>maven-test</groupId>
+ <groupId>test</groupId>
<artifactId>c</artifactId>
<scope>runtime</scope>
</dependency>

From forum: Maven - Commits

[jira] Closed: (ARCHETYPE-110) Maven archetype overwrites parent information

2008-12-02T14:44:19Z

[ http://jira.codehaus.org/browse/ARCHETYPE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raphaël Piéroni closed ARCHETYPE-110.
-------------------------------------

Resolution: Fixed

Fixed since revision 722648
Thanks to Jason Voegele patch.

> Maven archetype overwrites parent information
> ---------------------------------------------
>
> Key: ARCHETYPE-110
> URL: http://jira.codehaus.org/browse/ARCHETYPE-110
> Project: Maven Archetype
> Issue Type: Bug
> Reporter: Peter Liljenberg
> Priority: Critical
> Fix For: 2.0-alpha-5
>
> Attachments: ARCHETYPE-110.patch
>
>
> When creating a new archetype that I want to use for my projects I ran into some trouble with the created/copied pom.xml.
> The archetype pom.xml (\src\main\resources\archetype-resources\pom.xml) looks like this:
> <project>
> <parent>
> <groupId>group</groupId>
> <artifactId>masterpom</artifactId>
> <version>1.0</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <groupId>group</groupId>
> <artifactId>${artifactId}</artifactId>
> <version>1.0</version>
> </project>
> When I run my archetype it creates a pom.xml that looks like:
> <project>
> <parent>
> <artifactId>integration</artifactId>
> <groupId>group</groupId>
> <version>1.0</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <groupId>group</groupId>
> <artifactId>test</artifactId>
> <version>1.0</version>
> </project>
> Where "integration" is the name of the pom in the folder that I'm running mvn archetype:create from.
> Digging into the source we find in DefaultArchetype.java that processTemplate is indeed reading the parent pom and overwriting whatever was found in the original pom.xml.
> Is this really what we want to achieve? It should be possible to keep the parent-pom from the pom.xml in the archetype since it reduces the need for all developers to change their newly created pom.xml.
> <code>
> processTemplates
> if ( parentModel != null )
> {
> Parent parent = new Parent();
> parent.setGroupId( parentModel.getGroupId() );
> if ( parent.getGroupId() == null )
> {
> parent.setGroupId( parentModel.getParent().getGroupId() );
> }
> parent.setArtifactId( parentModel.getArtifactId() );
> parent.setVersion( parentModel.getVersion() );
> if ( parent.getVersion() == null )
> {
> parent.setVersion( parentModel.getParent().getVersion() );
> }
> generatedModel.setParent( parent );
> </code>
> Two alternative solutions:
> * If the parent-pom is specified in the archetype-pom, don't replace it
> * A parameter that we can supply that will leave the archetype-pom parent setting untouched.
> I vote for solution number 1....

From forum: Maven - Issues

svn commit: r722648 - /maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java

2008-12-02T14:42:34Z

Author: rafale
Date: Tue Dec 2 14:42:33 2008
New Revision: 722648

URL: http://svn.apache.org/viewvc?rev=722648&view=rev
Log:
Fix for ARCHETYPE-110
applied patch from Jason Voegele

Modified:
maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java

Modified: maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java
URL: http://svn.apache.org/viewvc/maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java?rev=722648&r1=722647&r2=722648&view=diff
==============================================================================
--- maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java (original)
+++ maven/archetype/trunk/archetype-common/src/main/java/org/apache/maven/archetype/common/DefaultPomManager.java Tue Dec 2 14:42:33 2008
@@ -161,6 +161,11 @@
XmlPullParserException
{
Model generatedModel = readPom( pom );
+ if( null != generatedModel.getParent() )
+ {
+ getLogger().info( "Parent element not overwrited in " + pom );
+ return;
+ }

Model parentModel = readPom( parentPom );

From forum: Maven - Commits

svn commit: r722647 - /maven/mercury/branches/722617/

2008-12-02T14:38:34Z

Author: ogusakov
Date: Tue Dec 2 14:38:34 2008
New Revision: 722647

URL: http://svn.apache.org/viewvc?rev=722647&view=rev
Log:
trying the release

Added:
maven/mercury/branches/722617/
- copied from r722646, maven/mercury/trunk/

From forum: Maven - Commits

svn commit: r722641 - /maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml

2008-12-02T14:27:33Z

Author: ogusakov
Date: Tue Dec 2 14:27:33 2008
New Revision: 722641

URL: http://svn.apache.org/viewvc?rev=722641&view=rev
Log:
preparing for the release

Modified:
maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml

Modified: maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml
URL: http://svn.apache.org/viewvc/maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml?rev=722641&r1=722640&r2=722641&view=diff
==============================================================================
--- maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml (original)
+++ maven/mercury/trunk/mercury-md/mercury-md-shared/pom.xml Tue Dec 2 14:27:33 2008
@@ -43,7 +43,7 @@
<plugin>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-component-metadata</artifactId>
- <version>1.0-beta-3-SNAPSHOT</version>
+ <version>1.0-beta-3.0.1</version>
<executions>
<execution>
<goals>

From forum: Maven - Commits

[jira] Closed: (MNGSITE-73) The example for specifying the MAVEN_OPTS is incorrect for the Unix installation instructions

2008-12-02T14:26:19Z

[ http://jira.codehaus.org/browse/MNGSITE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNGSITE-73.
------------------------------------

Assignee: Benjamin Bentmann
Resolution: Fixed

Fixed in [r722638|http://svn.eu.apache.org/viewvc?view=rev&revision=722638].

> The example for specifying the MAVEN_OPTS is incorrect for the Unix installation instructions
> ---------------------------------------------------------------------------------------------
>
> Key: MNGSITE-73
> URL: http://jira.codehaus.org/browse/MNGSITE-73
> Project: Maven 2 Project Web Site
> Issue Type: Bug
> Reporter: umesh balasubramaniam
> Assignee: Benjamin Bentmann
> Priority: Minor
>
> The step 4 of the installation documentation says: Optional: Add the MAVEN_OPTS environment variable to specify JVM properties, e.g. export MAVEN_OPTS=-Xms256m -Xmx512m. This environment variable can be used to supply extra options to Maven.
> This should be e.g. export MAVEN_OPTS="-Xms256m -Xmx512m"

From forum: Maven - Issues

svn commit: r722638 - /maven/site/trunk/src/site/apt/download.apt.vm

2008-12-02T14:24:12Z

Author: bentmann
Date: Tue Dec 2 14:24:12 2008
New Revision: 722638

URL: http://svn.apache.org/viewvc?rev=722638&view=rev
Log:
[MNGSITE-73] The example for specifying the MAVEN_OPTS is incorrect for the Unix installation instructions

Modified:
maven/site/trunk/src/site/apt/download.apt.vm

Modified: maven/site/trunk/src/site/apt/download.apt.vm
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/download.apt.vm?rev=722638&r1=722637&r2=722638&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/download.apt.vm (original)
+++ maven/site/trunk/src/site/apt/download.apt.vm Tue Dec 2 14:24:12 2008
@@ -106,7 +106,7 @@

[[3]] Add the <<<M2>>> environment variable, e.g. <<<export M2=$M2_HOME/bin>>>.

- [[4]] <<Optional>>: Add the <<<MAVEN_OPTS>>> environment variable to specify JVM properties, e.g. <<<export MAVEN_OPTS=-Xms256m -Xmx512m>>>.
+ [[4]] <<Optional>>: Add the <<<MAVEN_OPTS>>> environment variable to specify JVM properties, e.g. <<<export MAVEN_OPTS="-Xms256m -Xmx512m">>>.
This environment variable can be used to supply extra options to Maven.

[[5]] Add <<<M2>>> environment variable to your path, e.g. <<<export PATH=$M2:$PATH>>>.

From forum: Maven - Commits