RE: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid
David did you check the Junit test that ojdbc6 is listed as a dependency? dependencies dependency groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0.1/version /dependency /dependencies Martin- Date: Sat, 8 Mar 2014 13:30:59 -0800 Subject: Re: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid From: davek1...@gmail.com To: users@maven.apache.org In the log, there is a reference to 'no dependency information available', but the POM for com.oracle:ojdbc6:jar:11.2.0.1 exists. Any help/suggestions on how to resolve this issue would be appreciated. Verifying availability of C:\Users\david.kennedy\.m2\repository\com\oracle\ojdbc6\11.2.0.1\ojdbc6-11.2.0.1.pom from [eclipselink (http://download.eclipse.org/rt/eclipselink/maven.repo/, releases+snapshots), central (http://repo.maven.apache.org/maven2, releases)] The POM for com.oracle:ojdbc6:jar:11.2.0.1 is missing, no dependency information available C:\Users\david.kennedy\.m2\repository\com\oracle\ojdbc6\11.2.0.1\ojdbc6-11.2.0.1.pom ?xml version=1.0 encoding=UTF-8? 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/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0.1/version nameOracle JDBC Driver/name descriptionOracle JDBC driver classes for use with JDK1.7/description url http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html /url licenses license nameOracle Technology Network Development and Distribution License Terms/name url http://www.oracle.com/technology/software/htdocs/distlic.html/url /license /licenses organization nameOracle Corporation/name urlhttp://www.oracle.com/url /organization /project On Sat, Mar 8, 2014 at 12:13 PM, Dave Kennedy davek1...@gmail.com wrote: I'm not sure where I need to add a dependency declaration for the ojdbc driver These are the references to oracle pom.xml dependency groupIdcom.oracle/groupId artifactIdojdbc6/artifactId version11.2.0.1/version scopeprovided/scope /dependency src/test/resources/jdbcproperties jdbc.driverClassName=oracle.jdbc.OracleDriver jdbc.url=oracle:thin:@database.com:1521:dbname jdbc.username=name jdbc.password=pass src/test/resources/testingContext.xml bean id=jpaVendorAdapter class=org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter p:showSql=true p:databasePlatform=org.eclipse.persistence.platform.database.OraclePlatform / On Sat, Mar 8, 2014 at 11:55 AM, Wayne Fay wayne...@gmail.com wrote: I updated the ojdbc6-11.2.0.1.pom file (see below) and the 'invalid' message did not appear. Good. Now there is an error running JUnit tests: No suitable driver found for oracle:thin:@dataserver.com:1521:dbname Most likely you are missing a dependency declaration for the ojdbc driver in the module that threw this error during the JUnit execution. I can PING the database in GlassFish Domain Admin Console and view the Tables and data in Netbeans | Services | Databases What makes you think this has ANYTHING to do Netbeans or Glassfish...? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fail assembly plugin if symbols are unknown
Hello,
I think using the enforcer is generally possible, but I am looking for an
option I can configure in the parent POM. For requireProperty I would have
to have a list of all the properties used in the assembly descriptors
(which means i have to maintain 2 times).
My goal is to find mismatch automatically and early without additional
manual steps.
I havent seen somewhere a general maven concept about handling unexpanded
properties, so I think about providing patches to some specific components
(if it has a chance to be included?).
Greetings
Bernd
Am 08.03.2014 09:57 schrieb Mirko Friedenhagen mfriedenha...@gmail.com:
Bernd,
what about using enforcer's requireProperty rule?
Regards
Mirko
--
Sent from my mobile
On Mar 7, 2014 10:20 PM, Bernd Eckenfels e...@zusammenkunft.net wrote:
Hello,
we use in a lot of projects special assembly descriptors, which
typically use the following pattern:
assembly
...
iddistribution/id
baseDirectory/baseDirectory
files
file
outputDirectory${dist.x}/${dist.base.software.lib}/outputDirectory
source${project.build.directory}/x.jar/source
/file
/files
/assembly
We are currently cleaning up some POMs and there is a risk that some of
the properties are no longer defined. This produces ZIP files which
have directory or file names in there with unexpanded ${dist*} symbols
(file name not filters).
Is it possible to make the assembly (archiver?) plugin (and
others) fail in a situation where ${} cannot be interpolated?
The same would be nice for manifest headers in the maven archiver
(filter in this case)?
Greetings
Bernd
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid
Martin,
I'm not sure where you mean to check that ojdbc6 is listed as a dependency.
I am trying to convert the project from using MySql to Oracle,
so I might not have configured everything correctly.
This is in the testingContext.xml file:
bean id=jpaVendorAdapter
class=org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter
p:showSql=true
p:databasePlatform=org.eclipse.persistence.platform.database.OraclePlatform
/
pom.xml:
dependency
groupIdcom.oracle/groupId
artifactIdojdbc6/artifactId
version11.2.0.1/version
/dependency
testingContext.xml:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
xmlns:p=http://www.springframework.org/schema/p;
xmlns:context=http://www.springframework.org/schema/context;
xmlns:tx=http://www.springframework.org/schema/tx;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd;
bean id=propertyConfigurer
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
p:location=classpath:jdbc.properties /
bean id=ahmDataSource
class=org.springframework.jdbc.datasource.DriverManagerDataSource
p:driverClassName=${jdbc.driverClassName}
p:url=${jdbc.url}
p:username=${jdbc.username}
p:password=${jdbc.password}
/
bean id=loadTimeWeaver
class=org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver
/
bean id=jpaVendorAdapter
class=org.springframework.orm.jpa.vendor.EclipseLinkJpaVendorAdapter
p:showSql=true
p:databasePlatform=org.eclipse.persistence.platform.database.OraclePlatform
/
bean id=entityManagerFactory
class=org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean
p:dataSource-ref=ahmDataSource
p:jpaVendorAdapter-ref=jpaVendorAdapter
p:persistenceXmlLocation=test-persistence.xml
/
!-- Transaction manager for a single JPA EntityManagerFactory
(alternative to JTA) --
bean id=transactionManager
class=org.springframework.orm.jpa.JpaTransactionManager
p:dataSource-ref=ahmDataSource
p:entityManagerFactory-ref=entityManagerFactory/
!-- checks for annotated configured beans --
context:annotation-config/
!-- Scan for Repository/Service annotations --
context:component-scan base-package=dao /
!-- enable the configuration of transactional behavior based on
annotations --
tx:annotation-driven /
/beans
On Sun, Mar 9, 2014 at 5:14 AM, Martin Gainty mgai...@hotmail.com wrote:
David
did you check the Junit test that ojdbc6 is listed as a dependency?
dependencies
dependency
groupIdcom.oracle/groupId
artifactIdojdbc6/artifactId
version11.2.0.1/version
/dependency
/dependencies
Martin-
Date: Sat, 8 Mar 2014 13:30:59 -0800
Subject: Re: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1
is invalid
From: davek1...@gmail.com
To: users@maven.apache.org
In the log, there is a reference to 'no dependency information
available',
but the POM for com.oracle:ojdbc6:jar:11.2.0.1 exists.
Any help/suggestions on how to resolve this issue would be appreciated.
Verifying availability of
C:\Users\david.kennedy\.m2\repository\com\oracle\ojdbc6\11.2.0.1\ojdbc6-11.2.0.1.pom
from [eclipselink (
http://download.eclipse.org/rt/eclipselink/maven.repo/,
releases+snapshots), central (http://repo.maven.apache.org/maven2,
releases)]
The POM for com.oracle:ojdbc6:jar:11.2.0.1 is missing, no dependency
information available
C:\Users\david.kennedy\.m2\repository\com\oracle\ojdbc6\11.2.0.1\ojdbc6-11.2.0.1.pom
?xml version=1.0 encoding=UTF-8?
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/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.oracle/groupId
artifactIdojdbc6/artifactId
version11.2.0.1/version
nameOracle JDBC Driver/name
descriptionOracle JDBC driver classes for use with
JDK1.7/description
url
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
/url
licenses
license
nameOracle Technology Network Development and Distribution
License Terms/name
url
http://www.oracle.com/technology/software/htdocs/distlic.html/url
/license
/licenses
organization
nameOracle Corporation/name
urlhttp://www.oracle.com/url
/organization
/project
On Sat, Mar 8, 2014 at 12:13 PM, Dave
maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
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; modelVersion4.0.0/modelVersion groupIdariba.testlog4j/groupId artifactIdtestlog4j/artifactId version1.0-SNAPSHOT/version packagingjar/packaging dependencies dependency groupIdlog4j/groupId artifactIdlog4j/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 idsap/id activetrue/active protocolhttp/protocol hostproxy.ariba.com/host port8080/port /proxy /proxies profiles profile idalwaysActiveProfile/id repositories repository idMavenCentralRepo1/id namemaven Central Repo1/name urlhttp://repo1.maven.org/maven2/url layoutdefault/layout /repository /repositories /profile /profiles activeProfiles activeProfilealwaysActiveProfile/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
Best way for packaging maven plugin
Hello, I have a maven project with many modules, some of them use a maven plugin into the goal compile. This plugin is also a module. When I clean then package the parent project everything is OK, the plugin is well executed into child module. But when I clean - compile the parent project, the first module that need to execute the plugin throw an error : No plugin descriptor found at META-INF/maven/plugin.xml Indeed, the file plugin.xml seems to be generated during the packaging, that's why I have an error on the goal compile. Please, Do you know I could resolve that ? How do you package your plugin with the rest of the project ? Thanks for your helps. Alex -- View this message in context: http://maven.40175.n5.nabble.com/Best-way-for-packaging-maven-plugin-tp5787233.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven-shade-plugin Class Overlap
I'm trying to use maven shade to overlay all of my changes to a jar on top of another in a manner similar to a jar overlay. However there are some classes that overlap in my source files with the jar I wish to overlap. After I build, the ones that overlap are replaced by what is in the jar's i'm overlaying. I want to know if it's possible to either chose the order the jars are added or to tell it to skip any classes that overlap. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-shade-plugin-Class-Overlap-tp5787056.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Invalid signature file digest for Manifest main attributes
Hi, 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 artifactMyJar1:MyJar1/artifact excludes excludeMETA-INF/*.SF/exclude excludeMETA-INF/*.DSA/exclude excludeMETA-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
Re: Best way for packaging maven plugin
I have a maven project with many modules, some of them use a maven plugin into the goal compile. This plugin is also a module. Best practice (IMO IME) is to have the plugin as its own, independent project. Then depend on the plugin in your other projects. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven won't resolve from central log4j:log4j:1.2.8 through 1.2.15
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) Where did this repo.maven.apache.org url come from? It is invalid as far as I know. I suspect your troubles are related to this. Or possibly related to the proxy you have defined. The correct URL to central is repo1.maven.org: http://repo1.maven.org/maven2/log4j/log4j/ which shows these versions under that GA coordinate: 1.1.3/ 04-Jan-2007 19:21 - 1.2.11/04-Jan-2007 19:21 - 1.2.12/04-Jan-2007 19:21 - 1.2.13/04-Jan-2007 19:21 - 1.2.14/08-Jan-2007 15:56 - 1.2.15/30-Aug-2007 17:41 - 1.2.16/08-Jan-2011 14:24 - 1.2.17/28-May-2012 10:46 - 1.2.4/ 04-Jan-2007 19:21 - 1.2.5/ 04-Jan-2007 19:21 - 1.2.6/ 04-Jan-2007 19:21 - 1.2.7/ 04-Jan-2007 19:21 - 1.2.8/ 04-Jan-2007 19:21 - 1.2.9/ 04-Jan-2007 19:21 - Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven-shade-plugin Class Overlap
I'm trying to use maven shade to overlay all of my changes to a jar on top of another in a manner similar to a jar overlay. However there are some classes that overlap in my source files with the jar I wish to overlap. After I build, the ones that overlap are replaced by what is in the jar's i'm overlaying. I want to know if it's possible to either chose the order the jars are added or to tell it to skip any classes that overlap. I use shade but won't pretend to be an expert on all the configuration options. I will assume you RTFM already. Did you consider using class relocation to move the overlapping classes to com.dontuse? Or perhaps an artifact filter to just eliminate them entirely? Just thinking out loud, I'm not sure what the order is/should be. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
