[
http://jira.codehaus.org/browse/MANTTASKS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175080#action_175080
]
Herve Boutemy commented on MANTTASKS-142:
-----------------------------------------
I just checked: as expected, Maven core does not support remote repositories
without id
{code}org.apache.maven.artifact.InvalidRepositoryException: Repository ID must
not be empty (URL is: file://${user.dir}/src/test/repo).
at
org.apache.maven.project.ProjectUtils.buildArtifactRepository(ProjectUtils.java:101){code}
Then I think Maven Ant Tasks should not really support this case either: any
algorithm that tries to compute a human readable defautl id cannot work.
I propose the following:
- add a warning if no id is defined
- compute a default value as simple as hex-encoded MD5-digest
> Default remote repository id not safe
> -------------------------------------
>
> Key: MANTTASKS-142
> URL: http://jira.codehaus.org/browse/MANTTASKS-142
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.0.9
> Reporter: Benjamin Bentmann
> Priority: Minor
> Fix For: 2.0.10, 2.1.0
>
>
> The default id for a remote repository is just the repo URL. However, a URL
> typically contains all kind of characters that are not safe for usage in
> local file paths. E.g. the colon ':' from the URL scheme will just blow up on
> Windows. The slashes from the URL also cause troubles for a path that is
> meant to be a simple file name instead of a directory spec.
> Better choices for the default repo id could be the host name only or just
> some hex-encoded MD5-digest of the URL.
--
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
