You should be able to get around this behavior and end up with the same
checksum:
http://maven.apache.org/guides/mini/guide-archive-configuration.html
On Mon, Apr 9, 2012 at 1:18 PM, Noam Y. Tenne <[email protected]> wrote:
> It's true that Maven modifies the produced artifact on every reactor
> build, even when the code itself was not modified; but that is the behavior
> of Maven.
> Although Artifactory has many features that are "tailor-made" to suit
> specific build tools, it actually serves as a general purpose binary
> repository manager and any file can be stored no matter how it was produced.
> So this feature can save a lot of time and bandwidth when deploying from
> an environment which doesn't modify the checksum of the artifact willy
> nilly, or if deploying a copy of an artifact that is already stored within
> Artifactory.
>
>
> On Sun, Apr 8, 2012 at 8:31 PM, Rajwinder Makkar
> <[email protected]>wrote:
>
>> I am little confused with this API :
>>
>> As per documentation :
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Deploy Artifact by Checksum
>>
>> Description: Deploy an artifact to the specified destination by checking
>> if the artifact content already exists in Artifactory.
>> If Artifactory already contains a readable artifact with the same
>> checksum the artifact content will be copied over to the new location and
>> return a response without requiring a content transfer.
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>> As with any maven build i do mvn clean deploy. This means that the
>> artifact will always be having a new md5 checksum no matter even if the
>> code is same. Then how come it can ever match the checksum of artifact in
>> artifactory ? For artifactory every time it will be a new artifact as the
>> checksum will be different.
>>
>> So what is the purpose of "deploy artifact by checksum"
>>
>> -Raj
>>
>>
>> On Sun, Apr 8, 2012 at 7:34 AM, Noam Y. Tenne <[email protected]> wrote:
>>
>>> A basic guide can be found in the wiki page I linked to (
>>> http://wiki.jfrog.org/confluence/display/RTF/User+Plugins), but don't
>>> hesitate to contact us for any more info.
>>> BTW, the user plugins are only available as an addon (part of
>>> Artifactory's Pro version), but you can download a free eval from
>>> here<https://secure.artifactoryonline.com/registration/evaluateaddons.html>
>>> .
>>>
>>> Cheers,
>>> Noam
>>>
>>>
>>> On Sun, Apr 8, 2012 at 5:24 PM, Rajwinder Makkar <
>>> [email protected]> wrote:
>>>
>>>> Hmm .. this is smart approach Noam .. let me give it a try .. I assume
>>>> it needs to be written in groovy .. but can u point me to the link for
>>>> documentation regarding this like how to create aftercreate hook ?
>>>>
>>>> Thanks much
>>>> Raj
>>>>
>>>>
>>>> On Sun, Apr 8, 2012 at 4:44 AM, Noam Y. Tenne <[email protected]> wrote:
>>>>
>>>>> Actually, this can be achieved by utilizing our user
>>>>> plugins<http://wiki.jfrog.org/confluence/display/RTF/User+Plugins>
>>>>> :
>>>>>
>>>>> 1. Create a temporary repository for deployments apart from you
>>>>> original target repository and direct all your deployments to that temp
>>>>> repo.
>>>>> 2. Revoke delete permissions from the original target repository
>>>>> and provide delete permissions to the temp repo.
>>>>> 3. Write a user plugin with the "afterCreate" hook that checks
>>>>> each deployment performed on the temp repo; if the artifact doesn't
>>>>> already
>>>>> exist in the "real" target repository, copy it to there; if the
>>>>> artifact
>>>>> already exists, do nothing with it.
>>>>>
>>>>> HTH,
>>>>> Noam
>>>>>
>>>>> On Sun, Apr 8, 2012 at 12:24 PM, Noam Y. Tenne <[email protected]>wrote:
>>>>>
>>>>>> Hi Raj,
>>>>>>
>>>>>> Currently, there's no way to achieve this; but you may open a feature
>>>>>> request in our JIRA <https://issues.jfrog.org> if you feel this
>>>>>> feature is needed.
>>>>>>
>>>>>> Cheers,
>>>>>> Noam
>>>>>>
>>>>>> On Sun, Apr 8, 2012 at 9:32 AM, Rajwinder Makkar <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Is there any way in artifactory to configure this :
>>>>>>>
>>>>>>> If an artifact that is sent for deployment to a repo has existing
>>>>>>> version in the same repo then ignore that artifact. Ignore means dont
>>>>>>> overwrite and dont fail the build either.
>>>>>>>
>>>>>>> Or basically if i remove delete permission then it should not send
>>>>>>> failure to maven build.
>>>>>>>
>>>>>>> -Raj
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> For Developers, A Lot Can Happen In A Second.
>>>>>>> Boundary is the first to Know...and Tell You.
>>>>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>>>>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>>>>>> _______________________________________________
>>>>>>> Artifactory-users mailing list
>>>>>>> [email protected]
>>>>>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> For Developers, A Lot Can Happen In A Second.
>>>>> Boundary is the first to Know...and Tell You.
>>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>>>> _______________________________________________
>>>>> Artifactory-users mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> For Developers, A Lot Can Happen In A Second.
>>>> Boundary is the first to Know...and Tell You.
>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>>> _______________________________________________
>>>> Artifactory-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> For Developers, A Lot Can Happen In A Second.
>>> Boundary is the first to Know...and Tell You.
>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>>> http://p.sf.net/sfu/Boundary-d2dvs2
>>> _______________________________________________
>>> Artifactory-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
>
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
