[
https://issues.apache.org/jira/browse/ROL-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030776#comment-15030776
]
Kohei Nozaki commented on ROL-2085:
-----------------------------------
Hi Dave, Thanks for the comment. I would start working for this in a separate
branch.
I found that this may bring larger impact than I thought because it depends on
some core classes of Roller. For example
{{org.apache.roller.weblogger.pojos.Weblog}} which is the argument of
{{WeblogEntryPlugin#init}} .
I think the new Maven project should contain only few classes that need to be
exposed as public interface, And should exclude any application logic on it. I
guess doing some refactoring before publishing might be better option.
> 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)
