hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kay Kay (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Sun, 07 Feb 2010 02:08:28 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830609#action_12830609

Kay Kay commented on HBASE-2099:

| We may get a bit philosophical here, but my own personal view is that a binary download
of a release of a project shouldn't need all things needed to build the product - that's what
SVN/Git is for. The sources and javadocs are there as reference material for the user of the
binary. Even if there was a standalone, in the majority of cases they're there for IDE's to
have it added as source material for the artifact for the users project. I can easily change
this to have the sources unpacked, in fact the default is to have it unpacked, maybe it's
clearer and more generally 'usable' for the new user to see the sources unpacked just waiting
for perusal.

But - when we publish an artifact , we can always add sources and javadocs as separate artifacts
(for the same version) - right ??  So - binary would just have .class / .jar files as a library
to link against, by other apps as needed ? 

> 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,
> 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.

View raw message