Using mvm 3.1.1 with a pom.xml with a dependency on log4j version [1.2.8] - it will not resolve Similar for required versions up to and including [1.2.15]
It¹s not an option for us to just go to the later log4j like [1.2.17] What¹s going on here? If we request an open ended 1.2.8 then it resolves ok ! Here¹s an example session i836228@SJCM00561975A> mvn dependency:tree [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building testlog4j 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ Downloading: http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml Downloaded: http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml (352 B at 0.7 KB/sec) Downloaded: http://repo.maven.apache.org/maven2/log4j/log4j/maven-metadata.xml (352 B at 0.6 KB/sec) [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.025s [INFO] Finished at: Fri Mar 07 12:31:54 PST 2014 [INFO] Final Memory: 6M/81M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project testlog4j: Could not resolve dependencies for project ariba.testlog4j:testlog4j:jar:1.0-SNAPSHOT: Failed to collect dependencies at log4j:log4j:jar:[1.2.8,1.2.8]: No versions available for log4j:log4j:jar:[1.2.8,1.2.8] within specified range -> [Help 1] Here is a pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>ariba.testlog4j</groupId> <artifactId>testlog4j</artifactId> <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <dependencies> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>[1.2.8]</version> </dependency> </dependencies> </project> Here is a .m2/settings.xml <?xml version="1.0" encoding="UTF-8"?> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <proxies> <proxy> <id>sap</id> <active>true</active> <protocol>http</protocol> <host>proxy.ariba.com</host> <port>8080</port> </proxy> </proxies> <profiles> <profile> <id>alwaysActiveProfile</id> <repositories> <repository> <id>MavenCentralRepo1</id> <name>maven Central Repo1</name> <url>http://repo1.maven.org/maven2</url> <layout>default</layout> </repository> </repositories> </profile> </profiles> <activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> </activeProfiles> </settings> On 3/6/14, 9:16 AM, "Venkata Suresh Kumar Pamidipati" <suresh.pamidip...@oracle.com> wrote: >Hi mgainty, > >Thanks for the response and information. I will contact the number given >below. > >Thanks & Regards, >Suresh > > >----- Original Message ----- >From: mgai...@hotmail.com >To: users@maven.apache.org, suresh.pamidip...@oracle.com >Sent: Thursday, March 6, 2014 6:39:54 PM GMT +05:30 Chennai, Kolkata, >Mumbai, New Delhi >Subject: RE: Invalid signature file digest for Manifest main attributes > >Hi Suresh > > > >Your best solution will come from Oracle Support India >They are supposed to know this information and will be able to assist you >with your problem >Oracle India Support Line number is +91.22.66796200 >If Oracle India is unable to assist you ..we can find a resource on this >side of the planet to help you > > >Warm Regards > > > > > >> Date: Wed, 5 Mar 2014 19:19:44 -0800 >> From: suresh.pamidip...@oracle.com >> To: users@maven.apache.org >> Subject: Invalid signature file digest for Manifest main attributes >> >> Hi, >> >> I am trying to build our project using maven. I have included multiple >>dependency jars in pom.xml and I am trying to build distribution jar >>using assembly:assembly goal. The command "mvn assembly:assembly" >>resulted in the below error. >> >> [ERROR] Failed to execute goal >>org.apache.maven.plugins:maven-assembly-plugin:2.4:assembly >>(default-cli) on project my-plugin: Execution default-cli of goal >>org.apache.maven.plugins:maven-assembly-plugin:2.4:assembly failed: >>Invalid signature file digest for Manifest main attributes -> [Help 1] >> >> Two of the dependency jars when present together was causing this >>issue. I tried commenting one of them and mvn assembly:assembly command >>worked fine. To make it work with both the jars present together, I >>tried by adding excludes in dependency, assembly and even shade plugin >>configuration in pom.xml to exclude MANIFEST files of one of those two >>jars as shown below, but still the same error exists. >> >> <configuration> >> <filters> >> <filter> >> <artifact>MyJar1:MyJar1</artifact> >> <excludes> >> <exclude>META-INF/*.SF</exclude> >> <exclude>META-INF/*.DSA</exclude> >> <exclude>META-INF/*.RSA</exclude> >> </excludes> >> </filter> >> </filters> >> </configuration> >> >> Please let me know how to resolve this error. I am not sure if the >>exclude statements were being ignored or I am missing some thing here. >>Any information on this will be really helpful. >> >> Thanks & Regards, >> Suresh >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org