[
https://jira.codehaus.org/browse/MJAVADOC-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333292#comment-333292
]
Robert Scholte commented on MJAVADOC-376:
-----------------------------------------
@[~ryenus], the SNAPSHOT can be found at
https://repository.apache.org/content/repositories/snapshots/. SNAPSHOTs will
never end up in Maven Central.
I'm not sure if those properties can be unified, it all depends if the there's
already a property available for every classifier. We don't want to break
backwards compatibility.
Using {{"jdk6"}} as the classifier is confusing, because it's not the
classifier you specify as a dependency.
Actually, I'm curious about your convention, because it seems like the same
project also produces jdk4, jdk5 and jdk7, but all with different sources?
> please add property 'maven.javadoc.classifier'
> ----------------------------------------------
>
> Key: MJAVADOC-376
> URL: https://jira.codehaus.org/browse/MJAVADOC-376
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
> Reporter: ryenus
> Assignee: Olivier Lamy
> Fix For: 2.9.2
>
>
> We need an easier way to customize the name of the generated javadoc jar file.
> * For maven-jar-plugin, there's a {{classifier}} attribute.
> * For maven-source-plugin, it's even better, there's a
> {{maven.source.classifier}} property
> But for maven-javadoc-plugin, there's no chance to customize, the classifier
> is hardcoded to "javadoc", making it very hard to customize the file name of
> the generated javadoc jar, which is needed when a classifier is needed to
> differentiate an artifact for multiple jdk vesions.
> By adding support for the {{maven.javadoc.classifier}} property, it would be
> much more straightforward and consistent.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
