Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # dev >> assembly pom


Copy link to this message
-
Re: assembly pom
On Tue, Mar 13, 2012 at 6:25 PM, David Medinets
<[EMAIL PROTECTED]> wrote:
> On Tue, Mar 13, 2012 at 4:21 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>> I do not know how it happens, but somehow the jars generated by some
>> of the child projects end up in the top level lib dir.  Could that be
>> what this was doing?
>
> The question is answered in the top-level pom.xml file. There is a
> maven-jar-plugin section that sets outputDirectory to be ../../lib.
> Thus the jar files are placed into the top-level lib directory. I'd
> suggest this value be changed to ../../target/lib. And after the extra
> src level is removed, then ../target/lib or simply target/lib.

Unless we want to do all this the 'conventional' way ... which would
have the disadvantage of not building up the lib directory (or the
target/lib directory) incrementally.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB