You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jörgen Persson (JIRA)" <ji...@apache.org> on 2011/01/24 21:32:43 UTC

[jira] Issue Comment Edited: (WICKET-3365) 1.5-RC1 sources seem to be missing in Maven repository

    [ https://issues.apache.org/jira/browse/WICKET-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985965#action_12985965 ] 

Jörgen Persson edited comment on WICKET-3365 at 1/24/11 3:31 PM:
-----------------------------------------------------------------

Actually, accordingly to the announce mail (http://apache-wicket.1842946.n4.nabble.com/announce-Wicket-1-5-RC1-is-released-td3231848.html) the recommended artifact to use for maven users is wicket, not wicket-core:

< . . .snippet . . . >

* To use in Maven:
<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.5-RC1</version>
</dependency> 

< . . .snippet . . . >

      was (Author: shakespear):
    Actually, accordingly to the announce mails the recommended artifact to use for maven users is wicket, not wicket-core:

< . . .snippet . . . >

* To use in Maven:
<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.5-RC1</version>
</dependency> 

< . . .snippet . . . >
  
> 1.5-RC1 sources seem to be missing in Maven repository
> ------------------------------------------------------
>
>                 Key: WICKET-3365
>                 URL: https://issues.apache.org/jira/browse/WICKET-3365
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5-RC1
>            Reporter: Willis Blackburn
>            Assignee: Jeremy Thomerson
>            Priority: Minor
>
> I saw a 1.5-RC1 build here:
> http://repo1.maven.org/maven2/org/apache/wicket/wicket/1.5-RC1/
> but it looks like the sources are missing.  There are source jar files, but they don't contain any classes.  Was that intentional or is something wrong with the build process?

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