You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/15 08:50:11 UTC
[jira] Created: (MAVEN-1446) Dependencies with identical artifactId, but different types
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Wed, 15 Sep 2004 2:49 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Wed, 15 Sep 2004 3:16 AM
Body:
The tlds should be renamed in the repo to something like spring-tld-1.0.tld
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1446?page=comments#action_24096
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Wed, 15 Sep 2004 3:16 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Felipe Leme
Created: Sun, 19 Sep 2004 10:21 AM
Body:
I agree with Brett, specially because changing the artifact name doesn't work - <artifact:deploy> will still use the name defined by the POM
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1446?page=comments#action_24255
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Sun, 19 Sep 2004 10:21 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Wed, 15 Sep 2004 3:16 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Sun, 19 Sep 2004 2:45 PM
Body:
As I commented in MAVEN-1087, quoting Trygve:
The type is not going to be a part of the dependency id in maven 2 so it should not become a part in maven 1 either.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1446?page=comments#action_24257
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Sun, 19 Sep 2004 2:45 PM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 15 Sep 2004 3:30 AM
Body:
why? It's better to fix the bug.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1446?page=comments#action_24099
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Wed, 15 Sep 2004 3:30 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1446) Dependencies with identical artifactId, but different types
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Julien Kirch
Created: Wed, 15 Sep 2004 3:01 AM
Body:
see MAVEN-1087
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1446?page=comments#action_24092
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1446
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1446
Summary: Dependencies with identical artifactId, but different types
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0
Assignee:
Reporter: Richard Easterling
Created: Wed, 15 Sep 2004 2:49 AM
Updated: Wed, 15 Sep 2004 3:01 AM
Description:
The central repository contains spring-1.0.jar and spring-1.0.tld entries under the springframework groupId. This should not be allowed because if you enter:
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
<type>tld</type>
</dependency>
<dependency>
<artifactId>spring</artifactId>
<groupId>springframework</groupId>
<version>1.0.2</version>
</dependency>
The second dependency (i.e. the jar file) can't be accessed from the POM code, it is simply ignored. The POM could should raise an excpetion if it finds a duplicate artifactId.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org