Re: help on shade plugin

you can exclude files by specifying a filter Here is a working filter from pom. It filters out all META_INF/LICENSE files from all dependencies. thanks Arun build plugins plugin groupIdorg.apache.maven.plugins/groupId

Re: shade issues with manifest entries

Any pointers would be greatly appreciated. On Thu, Mar 15, 2012 at 12:25 PM, Arun Ramakrishnan sinchronized.a...@gmail.com wrote: We use shade to build a uber jar. We use this to run jobs on hadoop ( a distributed computing framework ). Now, shade used to be working good. But, after I made

Re: shade issues with manifest entries

Ah, yes. Thanks. Removing restlet fixed the issue. Not sure how i missed it. But, still I would like to use restlet in the future. Will prob ask the osgi or restlet group. thanks Arun On Thu, Mar 15, 2012 at 2:58 PM, Wayne Fay wayne...@gmail.com wrote: Now, shade used to be working good.

Recommended practices for managing/distributing dependencies for maven built jars outside the build lifecycle

For lack of better articulation in the subject line, let me explain a bit more in detail as to what I am trying to figure out. In our organization we find ourselves building projects and distributing them to a heterogeneous set of machines remotely for execution ( such as to dynamicly generated

Re: Recommended practices for managing/distributing dependencies for maven built jars outside the build lifecycle

Simply put, given a jar file that has an effective pom in its META-INF, is there a way to tell maven to download all the necessary dependencies ? On Mon, Oct 10, 2011 at 4:22 PM, Arun Ramakrishnan sinchronized.a...@gmail.com wrote: For lack of better articulation in the subject line, let me

dependency mechanism ( overriding transitive version )

I am trying to explicitly override a transitive dependencies version, but dosent seem to work. I have this in my projects pom 1.!-- use no-commons-logging -- 2. dependency 3. groupIdcommons-logging/groupId 4. artifactIdcommons-logging/artifactId 5.

dependency conflict issue ( dummy commons logging libs/repo )

I am not sure a lower version dependency seems to be trumping a higher version. Here is the POM http://pastebin.com/TBP0YTZs Here is the dependency tree http://pastebin.com/VBdjiVcL Whats going on here ? I was attempting to avoid transitive dependency of commons-logging. I followed the