You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@fluo.apache.org by GitBox <gi...@apache.org> on 2018/06/18 14:57:56 UTC

[GitHub] keith-turner commented on issue #536: Avoid dependency hell

keith-turner commented on issue #536: Avoid dependency hell
URL: https://github.com/apache/fluo/issues/536#issuecomment-398083783
 
 
   > The shaded jar was finished, is this still relevant?
   
   Yeah, its still relevant.   The shading work that was was only for thrift.  I think we should make it easy to build a shaded version of Fluo from source.  I don't think the project should release a shaded version of Fluo to Maven central.  We should just document how a user could do this if they are having problems with dependencies.  We can also test the shaded version of Fluo and ensure it works.
   
   One possible way to do this is to add a maven profile and document how to use it.  The user facing docs would look something like the following.
   
    * Obtain source tar ball from ....
    * tar xf .... 
    * cd fluo-x.y.z
    * mvn package -PshadeAll -Daccumulo.version=$AV  -Dhadoop.version=$HV -Dzookeeper.version=$ZV
    * cp <path to shaded tar> <your des>
   
   We could also look into making the Docker build file use this.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services