You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Karlberg (JIRA)" <ji...@apache.org> on 2007/09/13 11:53:32 UTC

[jira] Created: (WICKET-967) wicketstuff SNAPSHOT repository missign -jdk14 and -jdk15 artifacts.

wicketstuff SNAPSHOT repository missign -jdk14 and -jdk15 artifacts.
--------------------------------------------------------------------

                 Key: WICKET-967
                 URL: https://issues.apache.org/jira/browse/WICKET-967
             Project: Wicket
          Issue Type: Bug
            Reporter: Johan Karlberg


http://wicketstuff.org/maven/repository/org/apache/wicket/ is missing the -jdk14 and -jdk15 artifacts. These are depended upon as parents of core wicket poms, and as such, snapshots are currently uninstallable via maven unless the missing artifacts (of potentially stale versions) already existing in ones local repo.

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

[jira] Closed: (WICKET-967) wicketstuff SNAPSHOT repository missign -jdk14 and -jdk15 artifacts.

Posted by "Johan Karlberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Johan Karlberg closed WICKET-967.
---------------------------------

    Resolution: Fixed

> wicketstuff SNAPSHOT repository missign -jdk14 and -jdk15 artifacts.
> --------------------------------------------------------------------
>
>                 Key: WICKET-967
>                 URL: https://issues.apache.org/jira/browse/WICKET-967
>             Project: Wicket
>          Issue Type: Bug
>            Reporter: Johan Karlberg
>
> http://wicketstuff.org/maven/repository/org/apache/wicket/ is missing the -jdk14 and -jdk15 artifacts. These are depended upon as parents of core wicket poms, and as such, snapshots are currently uninstallable via maven unless the missing artifacts (of potentially stale versions) already existing in ones local repo.

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