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

Willis Blackburn commented on WICKET-3365:
------------------------------------------

Please consider:

1.  The project does provide a "wicket" component, so it must be a legitimate 
part of the release.

2.  Every single release from 1.3.0 through 1.5-M3 included the sources for the 
"wicket" artifact.  I only noticed this when I changed from 1.5-M3 to 1.5-RC1.

3.  Providing the "wicket" artifact but not providing the sources needlessly 
imposes a penalty on Maven users who choose to reference that artifact from 
their pom.xml files:  their IDEs will be unable to find the sources.  I suppose 
that those people could go download the individual source jars and reference 
them from the IDE, but I think that those people would rather just change 
pom.xml to reference the component artifacts.  

4.  There must be a process for creating the "wicket" artifact and its sources, 
as evidenced by the fact that those jars have been part of the release for 
years.  It seems likely that the source-generation part is just broken.

If the project wants to deprecate the "wicket" artifact then that's fine, but 
in that case, I think that it should simply be eliminated.  But if the project 
is going to continue to provide the artifact, then I think that it should 
provide the corresponding source artifact too.

W








> 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: Martin Grigorov
>
> 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.

Reply via email to