[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830776#action_12830776
]
Kay Kay commented on HBASE-2099:
--------------------------------
{quote}
. I've relocated the SCM definition I had in hbase-core
{quote}
Great. I believe the important distinction is to have connection and
developerConnection nodes available under scm , since that would be used by the
maven-release plugin.
{quote}
unless Zookeeper and Thrift are put somewhere standard soon, you won't pass
this one.
{quote}
Yes. As far as zookeeper is concerned - it will be available soon in a maven
snapshot repository with the next release. As far as thrift is concerned - we
can publish ourselves once a groupId is identified for hbase.
{quote}
it's unclear what the use of googlecode, java.net and codehaus repositories
means for this as well. Seems odd to eliminate us based on that.. ? Could
someone in a more sensible timezone chat with some of the sonatype guys or
their IRC channel about this? there must be a bucket load of Apache projects
that wouldn't qualify there.
{quote}
I do not think this is a major showstopper because those original instructions
that I had pasted are for artifacts to be uploaded to central maven repository
, but when it comes to apache snapshot maven repository ( as it applies for
hbase), the criteria are more relaxed. So - that should not be a showstopper I
guess. I will confirm this with the sonatype people on this as well.
> 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.
