[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830764#action_12830764
]
Paul Smith commented on HBASE-2099:
-----------------------------------
bq. Paul - Can you also help double check the pom.xml-s with this -
http://nexus.sonatype.org/oss-repository-hosting.html#4 , that all necessary
elements are present.
Ok, I've gone and added the missing ones which were: Licenses, developers (I
just added stack in as an example, I'll need more details, or you can fill it
in as a template later), URL, and Description. I've relocated the SCM
definition I had in hbase-core to be in the top-level pom, I think that makes
more sense there.
but here's the kicker:
bq. Make sure your POM does not contain repositories or pluginRepositories
element. Central repository must be self-contained, so all your dependencies
must be available in Central. You need to make sure your project can be built
without extra repositories or pluginRepositories.
unless Zookeeper and Thrift are put somewhere standard soon, you won't pass
this one. 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.
> 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.
