[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830575#action_12830575
]
stack commented on HBASE-2099:
------------------------------
@ Kay Kay, regards the below comment over in the infrastructure issue -- since
closed and I'm not sure what it means when its been closed -- on group and
artifactid....
"Stack -
Would it be useful to have the groupId as - org.apache.hadoop.hbase and
then publish artifacts as hbase-core / hbase-client etc. Let me know your
thoughts on the same."
... you think the above better than my suggestion of groupid org.apache.hadoop
and our artifactid of hbase?
I suppose we'll want to publish other than hbase.jar up to maven. There will
be hbase-stargate.war and hbase-transacation.jar etc. hbase.jar should become
hbase-core then as you suggest (and as Paul had it originally up in the pom
above before I asked him to change it).
What are the pros/cons you see to using groupid of o.a.h.h rather than o.a.h?
Related, its a good ways of I think but there is talk of a few of the hadoop
projects moving up to be top-level apache projects. HBase is probably a good
candidate so our default package would become o.a.hbase at some stage in the
future. This would seem to argue in favor of your suggestion for a groupid of
o.a.h.h Kay Kay?
> Move build to Maven
> -------------------
>
> Key: HBASE-2099
> URL: https://issues.apache.org/jira/browse/HBASE-2099
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: stack
> Attachments: findbugs.html, findbugs.html, HBase Move Script.txt,
> HBASE-2099.9.patch, test-reports.zip
>
>
> This issue is for discussing pros and cons of moving hbase build to Apache
> Maven.
> Maven, if you take on its paradigm, does a lot for you. There are also a
> bunch of nice plugins that do nice reports on state of project; findbugs,
> that nice plugin where you can give out urls that will resolve to lines in
> source code (a doxygen-like thing ... I've forgotten its name). Other
> examples are a docbook plugin that would do the build inline with doc build.
> We could start up the hbase book using docbook format and the hbase book
> would ride along with versions.
> As I see it -- and its a while since I've done this stuff so things may have
> since changed -- in the way of an easy move to maven is our src/contrib
> content. Maven would have these as distinct projects pulling in their hbase
> dependency or, if you wanted to take on the maven subproject notion, then,
> hbase would be at same level in build as the contribs -- it would be a
> subproject too just built before the others.
> Anyone interested in working on this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
