[
https://issues.apache.org/jira/browse/WICKET-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985582#action_12985582
]
Martin Grigorov commented on WICKET-3365:
-----------------------------------------
I see two solutions:
# to not deploy wicket.jar in Maven repos. As this has been discussed several
times this .jar is for ANT users. Maven users are recommended to use
wicket-core. But I see even Wicket developers are confused and advertise Maven
dependency to wicket.jar in the release notes. I guess the users will be even
more confused.
# to find a way to create -sources and -javadoc packages for o.a.w:wicket
module and change all other modules (like -extentions, -spring, ...) to depend
on o.a.w:wicket instead of o.a.w:wicket-core. This solution will be less
confusing for all of us.
> 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.