[jira] [Commented] (ROL-2085) Extracting plugin interfaces to a separate Maven project and publish it to Maven Central

["David Johnson (JIRA)" <ji...@apache.org>]

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

David Johnson commented on ROL-2085:
------------------------------------

I think this is a great idea and would make Roller plugin development much easier.  I don't think Roller has ever published Maven Central artifacts so we will have to learn that process (I did it once before for ROME but that was long ago).

> Extracting plugin interfaces to a separate Maven project and publish it to Maven Central
> ----------------------------------------------------------------------------------------
>
>                 Key: ROL-2085
>                 URL: https://issues.apache.org/jira/browse/ROL-2085
>             Project: Apache Roller
>          Issue Type: Wish
>            Reporter: Kohei Nozaki
>            Assignee: Roller Unassigned
>            Priority: Trivial
>
> Every Roller plugins depend on some interfaces of Roller such as:
> * org.apache.roller.weblogger.business.plugins.entry.WeblogEntryPlugin
> * org.apache.roller.weblogger.business.plugins.comment.WeblogEntryCommentPlugin
> * org.apache.roller.weblogger.ui.rendering.plugins.comments.CommentAuthenticator
> I think it's useful if these interfaces are published on Maven Central. If they are on Maven Central, Plugin developers or users no longer need to acquire entire the source code of Roller and execute {{mvn install}} for it. Build instruction of a plugin (e.g. https://github.com/lbtc-xxx/roller-asciidoctorj-plugin#how-to-use-for-wildfly ) can be simplified as it will only need just execute {{mvn package}}.
> Any advices / opinions are welcome.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)