Re: Deploying archetypes

The archetype is packaging already. The only problem is the deploy. Maintaining the generated archetype by hand is out of the question and defeats the purpose of the archetype. This is a sample/base application that is in constant development. The archetype needs to be up-to-date with any

Re: Deploying archetypes

Wow - looks like I’m on the cutting edge. It seems the NPE is fixed in 2.9 of the deploy plugin which isn’t released yet: https://jira.codehaus.org/browse/MDEPLOY-174 From: Jordan Zimmerman jor...@jordanzimmerman.com Reply: Jordan Zimmerman jor...@jordanzimmerman.com Date: March 6, 2014 at

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

Re: Invalid signature file digest for Manifest main attributes

Look in the jar that the assembly created to see if the excludes actually worked. Ron On 06/03/2014 8:09 AM, Martin Gainty wrote: 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

Re: Maven Release Plugin throws Authentication Required error

Hi, First try do to that without using Jenkins at all. This is a pure maven configuration thing. You just seem to be missing the authentication part (see username and password parameters maybe). When you manage to release some dummy versions of your project, then and only then try doing it from

Re: Invalid signature file digest for Manifest main attributes

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,

Re: Invalid signature file digest for Manifest main attributes

Hi Ron, In the assembly distribution jar, only file present was MANIFEST.MF and there were no other files. But the jar created from packaging has the .SF and .RSA files which indicates that exclude configuration did not work. The dependency jar which I have mentioned in pom.xml is a signed jar

Re: Invalid signature file digest for Manifest main attributes

I just had a similar problem. I used the shade plugin with the following exclusion filter and it worked. Without the exclusion, I had .RSA and .DSA files in the resulting assembly and with the exclusions, they were omitted. You notice that my filter applies to *:* You might want to try that

Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid

When the project is built the following message is generated. The POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details The POM and repository look to be correct. Any suggestions on how to resolve this

Re: Netbeans 7.4 maven POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid

The POM for com.oracle:ojdbc6:jar:11.2.0.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Did you enable debug logging with -X to see more details? What does it say? Wayne