[
https://issues.apache.org/jira/browse/DERBY-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860173#comment-13860173
]
Peter Hansson commented on DERBY-5668:
--------------------------------------
Just wanted to chime in on this. I was really surprised to see that Derby
project does not publish Sources and Javadocs to Maven Central. After all most
open source projects I work with do this. Even just think of other Apache
projects like *Commons* or *Cassandra*. You'll notice that indeed they attach
their Javadocs and sources.
I'm assuming that most projects today would use the
[maven-release-plugin|http://maven.apache.org/maven-release/maven-release-plugin/]
to do the actual release. This is the "official" way to do releases with Maven
and it will automatically attach sources and javadocs. It will also create tags
in your SCS (e.g. Subversion) for your release. In other words: The whole
process is really automated and sources and javadocs attachment is something
you get for free. If you do things The-Maven-Way you'll actually have to make
and effort _not_ to upload sources and javadocs.
> Derby does not publish source artifacts to Maven Central
> --------------------------------------------------------
>
> Key: DERBY-5668
> URL: https://issues.apache.org/jira/browse/DERBY-5668
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.8.2.2
> Reporter: Martin Todorov
> Labels: Maven
>
> Since this is an opensource project whose sources one can navigate online via
> the https subversion repository, these artifacts should be available for
> Maven as well. If they exist, the IDE-s can attach their sources to your
> project thus you can see how things work and what you need to fix/adjust/use.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
