Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.1-beta-3
-
Fix Version/s: 1.1-rc1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
I am using the build of 2006-07-23. Whenever I do jar:install or jar:deploy or war:install or war:deploy it does it.
Same thing for struts-module plugin or other custom plugins I developed.
It seems to come directly from the maven code as it is common to all plugins I've tried.
If I have the following coonfiguration in the POM:
<id>id</id>
<groupId>group</groupId>
<artifactId>artifact</artifactId>
<currentVersion>2.11-beta2</currentVersion>
Here is the output:
jar:install:
[echo] Installing...
Uploading to group/jars/id-2.11-beta2.jar:
.................... (467K)
Uploading to group/poms/id-2.11-beta2.pom:
.................... (16K)
BUILD SUCCESSFUL
Total time : 12 seconds
Finished at : Monday, July 31, 2006 10:02:49 BST AM
If id is a combination of group and artifact like this
<id>group:artifact</id>
<groupId>group</groupId>
<artifactId>artifact</artifactId>
<currentVersion>2.11-beta2</currentVersion>
Here is the output
jar:jar:
[jar] Building jar: C:\eclipse\workspace\DBInterface\target\group:artifact-2.11-beta2.jar
jar:install:
[echo] Installing...
Uploading to group/jars/group:artifact-2.11-beta2.jar:
(0K)
Uploading to group/poms/group:artifact-2.11-beta2.pom:
.................... (16K)
BUILD SUCCESSFUL
If I remove the id element, it works as expected:
jar:jar:
[jar] Building jar: C:\eclipse\workspace\DBInterface\target\artifact-2.11-beta2.jar
jar:install:
[echo] Installing...
Uploading to group/jars/artifact-2.11-beta2.jar:
.................... (467K)
Uploading to group/poms/artifact-2.11-beta2.pom:
.................... (16K)
BUILD SUCCESSFUL
Issue Links
| This issue relates to: | ||||
| MAVEN-1704 | artifactId is used as groupId when the latest is not defined |
|
|
|