[
http://issues.ops4j.org/browse/PAXURL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078#action_13078
]
Alin Dreghiciu commented on PAXURL-74:
--------------------------------------
For snapshots you must specified @snapshots on the repo url as shown in wiki:
http://wiki.ops4j.org//x/CoA6.
have you tried that? using @noreleases is in case that the repo should not
allow releases, since the default allows releases.
Can you giv it a try by using @snapshots ?
> Mvn handler fails to resolve snapshot when @noreleases is specified and no
> metadata is available
> ------------------------------------------------------------------------------------------------
>
> Key: PAXURL-74
> URL: http://issues.ops4j.org/browse/PAXURL-74
> Project: Pax URL
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 1.1.1
> Reporter: Greg Lucas
> Assignee: Alin Dreghiciu
>
> If for some reason there is no maven metadata in the remote repository the
> mvn protocol handler will attempt to resolve a *-SNAPSHOT file directly. This
> fails if the repository URL specifies @noreleases, even though that is a
> valid attribute for a snapshot repository.
> I tested this with 1.0.0 and 1.1.1. The issue is that after failing to find
> metadata resolveSnapshotVersion calls resolveExactVersion, which throws if
> @noReleases has been specified.
> I'm running in to this issue with artifacts deployed to a maven repo using
> Buildr, which does not generate the metadata.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
