[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835883#action_12835883
]
stack commented on HBASE-2099:
------------------------------
Paul, so, now jars are showing up in the tarball. Good stuff. The Talisker
must have done the job.
What about these warnings....
{code}
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
[WARNING] NOTE: Currently, inclusion of module dependencies may produce
unpredictable results if a version conflict occurs.
{code}
... and
{code}
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added, skipping
[INFO] contrib/transactional/hbase-contrib-transactional-0.20.2-SNAPSHOT.jar
already added,
{code}
... and
{code}
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestDeleteCompare.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestGetClosestAtOrBefore.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestGetDeleteTracker.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestKeyValueScanFixture.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestKeyValueSkipListSet.java
longer than 100 characters.
[WARNING] Entry:
hbase-0.20.2-SNAPSHOT/core/src/test/java/org/apache/hadoop/hbase/regionserver/TestMinorCompactingStoreScanner.java
longer than 100 characters.
{code}
Otherwise, it runs nice and prompt.
Oh, and how do I build the package? I can't. I have to go back to my mvn
checkout, is that right?
> 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.
