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/07/23 02:02:10 UTC
[jira] Closed: (MAVEN-654) No version causes bad jar name
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Thu, 22 Jul 2004 8:01 PM
can overrride if necessary with <jar/>, but not encouraging it.
Better error handling should be present in the new model.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-654
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-654
Summary: No version causes bad jar name
Type: Improvement
Status: Closed
Priority: Trivial
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0-beta-10
Assignee:
Reporter: dion gillard
Created: Mon, 4 Aug 2003 10:01 PM
Updated: Thu, 22 Jul 2004 8:01 PM
Description:
Just something that occurred to me the other day. If I have:
<dependency>
<id>javamail</id>
</dependency>
It really should be smart and look for javamail.jar and not javamail-.jar.
There's enough in the way of non-versioned jars [especially from sun] that
this would be a nice pain reducer.
Hen
---------------------------------------------------------------------
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