[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802000#action_12802000
]
Paul Smith commented on HBASE-2099:
-----------------------------------
I don't think Maven can pull from a local directory, BUT, what would be 'wrong'
with just, say, 'mvn deploy:deploy-file' these 2 to, say,
people.apache.org/~psmith/..
The jars need to come from a repo, there's no requirement that it be a 'flashy'
one.. :)
Now, specifically, why CAN'T the zookeeper final be uploaded to Maven central?
That's a 'released' product from an Apache point of view? (or are you using a
Snapshot one, and if so, then Apache Public Snapshots is fine too).
thrift is in incubation, I know an incubation project can't publish official
releases, but I don't think that means they can't publish a snapshot. I could
look into that if you like, but otherwise just hosting these @
people.apache.org.. is an interim measure.
Once I have the repositories defined in the pom (lunch time today), I'll write
the list, I'd like to get to the point where I would think that anyone could
follow my steps to a clean trunk, and it should just build.
Thanks for everyone's feedback!
> 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.5.patch, HBASE-2099.6.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.
