Issue with ManifestResourceTransformer and string length limit for main class

Hi, I've added a maven-shade-plugin for the infamous Spring issues when creating an uber jar. Anyway in my ManifestResourceTransformer I specify my executable class. When I run mvn clean/install and then try to execute the jar, I get a class not found issue. When I expand the jar file that

mvn2 structure design for a software product

Hi, I have a general design question on mvn2's project (directory) structure. I'm starting on a project which involves creating a software product to be used by a few clients, with each client having particular customizations on top of the product. I'm thinking of a structure design where I

profiles for separate projects on same build

I'm running into a situation where I need to build a project twice in the same run dependent on two or more separate projects. For example, say I have three subprojects under root set up like this: root -- subproject A -- subproject M -- config.xml -- subproject Z Projects A and Z

profiles / text substitution

I would like to use maven profiles in the pom but would like someway to combine this with text substitution. Basically I would like to have one generic hibernate configuration file that has a ${connection} ready for runtime text substitution. Then I would have 2 external files that contains the

Re: Correlation between tagging and versioning

/plugins/maven-release-plugin/ Tag version and POM version must indeed match. - Yann 2007/1/11, moraleslos [EMAIL PROTECTED]: I'm about to tag my code in my repository to the maven-recommended x.x.x-y-z format-- probably at 1.0.0-alpha-1. I was wondering how this correlates

Re: Correlation between tagging and versioning

release version is out of my control? -los Yann Le Du-4 wrote: Hi Los, maven-release-plugin is your friend : http://maven.apache.org/plugins/maven-release-plugin/ Tag version and POM version must indeed match. - Yann 2007/1/11, moraleslos [EMAIL PROTECTED]: I'm about to tag my code

Correlation between tagging and versioning

I'm about to tag my code in my repository to the maven-recommended x.x.x-y-z format-- probably at 1.0.0-alpha-1. I was wondering how this correlates to the version used in my POMs-- currently at 1.0-SNAPSHOT. Shouldn't they match, or are they suppose to be different? I'm new to the

Compilation failure for JSE 6 / maven2

I currently have a maven 2 (v 2.0.4) project set up and working until now. I don't recall changing any code but when I run a mvn compile on my project, I get this error: [ERROR] BUILD FAILURE [INFO]