[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836136#action_12836136
]
Paul Smith commented on HBASE-2099:
-----------------------------------
bq. [WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
Ok, I had read up about that exact warning earlier in the week. It is related
to the fact that one has to have the 'assembly:assembly' text during a full
distribution, that is, to get the full tar ball, you have to invoke the
assembly plugin's goal.
This is because I have configured this assembly in the top-level pom.
Apparently this is 'not the preferred way'. Instead, a new sub-module should be
created to host this. Basically shift the definition into a, say, 'dist'
sub-module.
I'd like to experiment with this after it's in trunk and I can use git more
effectively to publish potential changes for review (if Ryan is ok with me
using his github repo, otherwise I could create my own I guess) I think my
patch contains 'just enough' to get started, but not enough for an official
release (a few other reasons it's not ready yet anyway).
bq. INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
to be honest, no idea. Seems benign though. maybe an errant INFO level log
message (perhaps should be DEBUG..). Can follow up with maven-user list if
it's annoying.
bq. [WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestDeleteCompare.java
longer than 100 characters.
The 'official' tar spec does not support filenames > 100 chars. In practice,
the tar ball works fine. I've seen this plenty of times during our own Aconex
builds and not a single server has yet failed to unpack it. It's perhaps
targetted to warn for _really_ old or esoteric Unix distributions.
May even be able to turn it off via config, not sure yet.
bq. Oh, and how do I build the package? I can't. I have to go back to my mvn
checkout, is that right?
i have no idea what you mean here... sorry.
> 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.13.patch, HBASE-2099.14.patch, mvn.out, 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.
