[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830608#action_12830608
]
Paul Smith commented on HBASE-2099:
-----------------------------------
back to some things stack said in another post:
bq. I like the way you have sources bundled up a jar but I think needs a bit
more work. When I undo it, sources are not buildable (fellas like being able to
do this). There is no build.xml. Test source should probably be there too.
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.
I would propose we produce 2 tar balls as is mostly standard, and Maven
Assembly plugin has a definition right out of the box for a sources-like tar
bal:
http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#src
(look at both the 'sources' descriptor and the one below it 'project'. stack
may be thinking of 'project'. I'll add both so you can see.
> 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.
