You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/12/24 20:19:14 UTC
[jira] [Resolved] (HBASE-12310) Remove custom doclet from
hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-12310.
------------------------------------
Resolution: Not a Problem
Ok, I will resolve this as not a problem.
> Remove custom doclet from hbase-annotations
> -------------------------------------------
>
> Key: HBASE-12310
> URL: https://issues.apache.org/jira/browse/HBASE-12310
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
>
> hbase-annotations includes a custom doclet used for filtering APIs out of the user API javadoc given our project specific interface annotations. However, this is problematic for a few reasons:
> - To build the doclet we include a system scope dependency to tools.jar. Default Nexus rules disallow that. Staging downstream HBase artifacts will be problematic. I don't know how we were able to release 0.98.7 with this in place. I think someone will be looking into the Apache Nexus configuration.
> - As I understand it, system scope dependencies will not be supported by Maven 4 because they've been determined to be generally problematic.
> - As [~busbey] mentioned on HBASE-12299, the root pom specifies the javadoc dependency for all modules and it creates a circular need with the hbase-annotations module.
> Do we really need a custom doclet? Can we simply remove all of this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)