[PLUTO-173] Build (mvn install) fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0-alpha1
• Fix Version/s: 1.1.0-alpha1
• Component/s: build system, portlets-testsuite
• Environment: Windows XP SP1, JDK_1.5.0_04, Maven 2.0 (released)
• Assignee: Unassigned
• Reporter: Graham klyne
• Created: 20/Oct/05 22:16
• Updated: 22/Feb/07 04:58
• Resolved: 02/Nov/05 12:35

Description

Build failure performing "mvn install" command:

Here's the fix I found. Symptoms are below. In file Pluto-1.1\pluto-testsuite\pom.xml I changed the <build> section
thus:

[[
<build>
<finalName>pluto-testsuite</finalName>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<!--
<version>1.0-SNAPSHOT</version>
-->
<version>2.0</version>
<configuration>
<descriptor>src/assemble/bin.xml</descriptor>
<finalName>pluto-testsuite-${pom.version}</finalName>
</configuration>
</plugin>
</plugins>
</build>
]]

(i.e. updated reference to <version>1.0-SNAPSHOT</version> top 2.0, as that's what all the other sub-projects use.)

Before this, the symptom was:
[[
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-assembly-plugin
Version: 1.0-SNAPSHOT

Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-assembly-plugin:1.0-SNAPSHOT:pom

from the specified remote repositories:
central (http://repo1.maven.org/maven2)
]]

(This was with two other repositories (labelled "m1" and "m2") commented out of the top-level pom.xml. With these not commented out I was getting authentication errors. With the above fix applied, I have been able to reinstate the repositories causing authentication errors, but that may be because the required resources are now present in the maven repository?)