archiva-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno F (JIRA)" <>
Subject [jira] Commented: (MRM-1357) Allow deployment of attached release artifacts if POM is identical
Date Mon, 08 Mar 2010 09:54:06 GMT


Bruno F commented on MRM-1357:

I really wonder if it is a matter of Maven repository manager or deploy plugin.

On one hand we have some related logic in Archiva...:
- snapshot-only of release-only repositories
- forbid re-deployment of release artifacts
... so it could make sense to extend that logic.

But on the other hand, it seems understandable to consider that it is a deploy plugin problem:
when a multi-artifacts project deployment fails in the middle (let's say for a network reason),
the deploy plugin should be able to deploy only the "delta", thus preventing from re-deploying
the artifacts that already are. In this regard, such a capability (if implemented by retrieving
artifacts from the MRM and by making a comparison, and not by storing some state on the client-side)
would solve the problem described above.

I don't know if it is relevant but: could it be that the MRM is the only place where some
transactional logiccan be placed  (in a multi-user environment) in order to ensure that a
release artifact will not be re-deployed with the same version number but not the same "binary

Anyway, I am a too recent Maven user to really feel or know where the correction should be

> Allow deployment of attached release artifacts if POM is identical
> ------------------------------------------------------------------
>                 Key: MRM-1357
>                 URL:
>             Project: Archiva
>          Issue Type: Improvement
>          Components: WebDAV Interface
>    Affects Versions: 1.3
>         Environment: Windows XP SP3
>            Reporter: Bruno F
>             Fix For: Backlog
> In the context of the build of a native application, one might have zip-artifacts containing
several DLL or so files like:
>   boost:boost_regex:1.34.1:zip
> In order to distinguish between platforms, it seems to be recommended to use the classifier:
>   boost:boost_regex:1.34.1:zip:bin-x86-windows-vc8
> or:
>   boost:boost_regex:1.34.1:zip:bin-x86-linux2.6-gcc3.3 
> The new feature that prevents from deploying a release artifact is really great but it
lacks the possibility to deploy attached artifacts when the POM is the same (modulo platform-dependent
line-break concerns, and that's important!).
> In the example above, it could enable to deploy the boost:boost_regex:1.34.1:zip:bin-x86-windows-vc8
artifact from a Windows machine(coming along with a boost:boost_regex:1.34.1:pom artifact),
then to deploy the boost:boost_regex:1.34.1:zip:bin-x86-linux2.6-gcc3.3 artifact from a Linux
machine (coming along with the same boost:boost_regex:1.34.1:pom artifact).
> Maybe this could be generalized to any kind of artifact? If the artifact to deploy is
the same, Archiva should not fail and simply skip the deployment of that artifact?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message