db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Todorov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-5668) Derby does not publish source artifacts to Maven Central
Date Thu, 13 Jun 2013 11:57:21 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682153#comment-13682153
] 

Martin Todorov edited comment on DERBY-5668 at 6/13/13 11:55 AM:
-----------------------------------------------------------------

Yeah, but if you're publishng Maven artifacts, then you must support the Maven way of working.
IDE-s expect you to have *-sources.jar and/or *-javadoc.jar files for each of your artifacts
in order to be able to show you javadocs.
I am working on the derby-maven-plugin (https://github.com/carlspring/derby-maven-plugin)
using IntelliJ Idea and (obviously) Maven. In order to be able to figure certain things out,
I usually end up browsing the Derby code's SVN and online javadocs outside my IDE. Needless
to say, this is not very nice. It also takes a while to figure things out this way.

I understand that this is a large project and that it has it's legacies. I actually wanted
to go give this a go myself, but then I had a look at the way things are built and got shocked!
No offence.

Is there a way I can help get the sources / javadocs per module so I can attach them to the
Maven build? Where can I find the javadoc generation bit? Are you producing one large javadoc
/ source file?
                
      was (Author: carlspring):
    Yeah, but if you're publishng Maven artifacts, then you must support the Maven way of
working. IDE-s expect you to have *-sources.jar and/or *-javadoc.jar files for each of your
artifacts in order to be able to show you javadocs.
I am working on the [https://github.com/carlspring/derby-maven-plugin|derby-maven-plugin]
using IntelliJ Idea and (obviously) Maven. In order to be able to figure certain things out,
I usually end up browsing the Derby code's SVN and online javadocs outside my IDE. Needless
to say, this is not very nice. It also takes a while to figure things out this way.

I understand that this is a large project and that it has it's legacies. I actually wanted
to go give this a go myself, but then I had a look at the way things are built and got shocked!
No offence.

Is there a way I can help get the sources / javadocs per module so I can attach them to the
Maven build? Where can I find the javadoc generation bit? Are you producing one large javadoc
/ source file?
                  
> 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 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

Mime
View raw message