Just one more thing: Can you check that the user deploying 2.0.14 has
"annotate" permissions on the local repository?
You can check in the "Effective Permissions" tab or in the access.log file
for denied request.
Hope it helps,
Fred.
On Mon, Jul 26, 2010 at 9:33 AM, Yossi Shaul <[email protected]> wrote:
> Hi Jan,
>
> Artifactory calculates maven metadata after each deployment of a pom file
> if the
> snapshot behavior policy is deployer. What is the policy of your
> repository?
> Have you seen any exceptions in the log?
>
> Also turn on debug log for the metadata calculator by adding the following
> to $ARTIFACTORY_HOME/etc/logback.xml:
>
> <logger name="org.artifactory.maven.MavenMetadataCalculator">
> <level value="debug"/>
> </logger>
>
>
> Yossi
>
>
> On Mon, Jul 26, 2010 at 1:54 AM, Jan Palmquist <[email protected]>wrote:
>
>>
>> Hello,
>>
>> I have a problem regarding artifactory (2.2.4 r11256) and
>> maven-metadata.xml
>> files for some of the artifacts in a local repository. The problem has
>> been
>> around for a while and probably relates to several previous versions of
>> artifactory since this artifactory instance has been around for several
>> years now.
>>
>> There are two local repositories (one for snapshots and the other for
>> releases) to which the build server (TeamCity) deploys (maven deploy
>> plugin
>> configured with the lightweight wagon-provider) artifacts to artifactory.
>>
>> As time has passed, one of the artifacts (a pom project) has the following
>> snapshot versions (maven-metadata.xml from the snapshot repository):
>> <?xml version="1.0" encoding="UTF-8"?>
>> <metadata>
>> <groupId>my.company.project</groupId>
>> <artifactId>project-parent</artifactId>
>> <version>2.0.1-SNAPSHOT</version>
>> <versioning>
>> <latest>2.0.1-SNAPSHOT</latest>
>> <versions>
>> <version>1.7.1-SNAPSHOT</version>
>> <version>1.7.0.1-SNAPSHOT</version>
>> <version>2.0.1-SNAPSHOT</version>
>> <version>2.0.2-SNAPSHOT</version>
>> <version>2.0.3-SNAPSHOT</version>
>> <version>2.0.4-SNAPSHOT</version>
>> <version>2.0.5-SNAPSHOT</version>
>> <version>2.0.6-SNAPSHOT</version>
>> <version>2.0.7-SNAPSHOT</version>
>> <version>2.0.8-SNAPSHOT</version>
>> <version>2.0.9-SNAPSHOT</version>
>> <version>2.0.10-SNAPSHOT</version>
>> <version>2.0.11-SNAPSHOT</version>
>> <version>2.0.12-SNAPSHOT</version>
>> <version>2.0.13-SNAPSHOT</version>
>> <version>2.0.14-SNAPSHOT</version>
>> </versions>
>> <lastUpdated>20100723010316</lastUpdated>
>> </versioning>
>> </metadata>
>>
>> The latest build deployed a 2.0.14-SNAPSHOT at 20100723010316, but that
>> seem
>> not to be reflected in the artifact metadata in any way except that there
>> indeed exist a 2.0.14-SNAPSHOT version.
>>
>> Actually, the 2.0.14-SNAPSHOT version does not have a maven-metadata.xml
>> to
>> begin with (as I would have expected).
>>
>> Version 2.0.1-SNAPSHOT has the following maven-metadata.xml:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <metadata>
>> <groupId>my.company.project</groupId>
>> <artifactId>project-parent</artifactId>
>> <version>2.0.1-SNAPSHOT</version>
>> <versioning>
>> <snapshot>
>> <buildNumber>27</buildNumber>
>> </snapshot>
>> <lastUpdated>20090518135240</lastUpdated>
>> </versioning>
>> </metadata>
>>
>> Version 2.0.13-SNAPSHOT has the following maven-metadata.xml:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <metadata>
>> <groupId>my.company.project</groupId>
>> <artifactId>project-parent</artifactId>
>> <version>2.0.13-SNAPSHOT</version>
>> <versioning>
>> <snapshot>
>> <buildNumber>1</buildNumber>
>> </snapshot>
>> <lastUpdated>20100331204229</lastUpdated>
>> </versioning>
>> </metadata>
>>
>> After inspecting the 2.0.13-SNAPSHOT, I can also tell that the metadata
>> file
>> has not been updated as expected after the initial deploy (since build
>> number and update time does not reflect all times that version has been
>> rebuilt and deployed).
>>
>> As stated above, 2.0.14-SNAPSHOT does not have a maven-metadata.xml at
>> all.
>>
>> The main problem at hand is that client side mvn builds do not detect that
>> the snapshot has been re-deployed, and the latest snapshot will not be
>> downloaded even if using -U to the mvn command line.
>>
>> Is my artifactory corrupt?
>> Is there a way to manually trigger metadata to be rebuilt?
>> Anyone else having detected a corresponding problem?
>> Any solution or workaround available?
>>
>> Of course, since this is a snapshot, I could probably just delete the
>> whole
>> artifact and re-deploy a fresh 2.0.14-SNAPSHOT and forget about earlier
>> snapshots, but what if something similar happens to an artifact version in
>> the releases repository?
>>
>> Any suggestions are welcome and assistance is greatly appreciated!
>>
>> Regards - Janne
>>
>> --
>> View this message in context:
>> http://forums.jfrog.org/maven-metadata-xml-for-artifacts-seem-corrupt-tp5336149p5336149.html
>> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>
>
>
> ------------------------------------------------------------------------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
--
Co. Founder and Chief Architect
JFrog Ltd
http://www.jfrog.org/
http://twitter.com/freddy33
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
