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

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

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

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

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

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

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

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

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:

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