You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2007/06/06 04:40:25 UTC

[jira] Resolved: (WICKET-283) deploy maven snapshots on wicketstuff.org properly

     [ https://issues.apache.org/jira/browse/WICKET-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius resolved WICKET-283.
------------------------------------

    Resolution: Fixed

Seems to be ok now

> deploy maven snapshots on wicketstuff.org properly
> --------------------------------------------------
>
>                 Key: WICKET-283
>                 URL: https://issues.apache.org/jira/browse/WICKET-283
>             Project: Wicket
>          Issue Type: Bug
>          Components: site
>            Reporter: Eelco Hillenius
>
> Snapshots are currently copied after bamboo builds (if I'm correct) so that they are available for our users from http://wicketstuff.org/maven/repository/. However, it seems that the meta data that is used to determine the last modified date etc for snapshots is not properly changed. See for instance http://wicketstuff.org/maven/repository/org/apache/wicket/wicket-datetime/1.3-incubating-SNAPSHOT/maven-metadata-local.xml:
> which says the last update was feb 5, while the timestamp of the snapshot is from feb 13.
> This is probably the reason why I never get snapshot updates when I'm trying to build using that repo.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.