Re: exclude entries in MANIFEST.MF
Why are you doing all of this? What are you building that is so far outside the normal way to build EARs that it requires that you do this? Why do you need hibernate to compile but not to run? If hibernate is being provided at run-time then scope "provided" should handle this properly. I may be off base but it looks like you are trying to do something that should be very easy but have tried to make it too complex Fiddling with the Manifest is a not a normal activity as far as I know but I am not building EARs - only WARs and JARs. As a side note, Eclipse and its plug-ins do not use Maven to get everything done. They keep an eye on your pom.xml and try to set up their parameters to match what they think you are trying to do with the POM. You still have to look at the properties of your project to see how your Eclipse configuration has been adjusted to match your pom. That is the first thing to do if you are having trouble deploying and running through some Eclipse feature. You may have to manually adjust the properties if Eclipse misinterprets your pom. Once that works, you can go back and see if you can fix your pom or some plug-in to make it easier for Eclipse to figure it out, if possible. Free advice and worth every penny! Ron On 06/11/2013 9:15 AM, brandenber...@commcity.ch wrote: Try to define a filter, similar to the following snippet: lib true true true src/main/resources/ **/*application.xml,**/*MANIFEST.MF From: Surendran D To: Maven Users List Date: 06.11.2013 10:04 Subject: exclude entries in MANIFEST.MF Hi, I am currently building and EAR file using maven-ear-plugin I have a requirement to exclude some of the Class-Path: entries from MANIFEST.MF file. For example I have 3 dependencies hibernate-core.jar, quartz-1.6.5.jar and poi-3.7.jar in my class path (in my dependency of pom.xml) When I build my EAR file all these entries will be automatically added to Class-Path entry of my MANIFEST.MF file. My maven build looks as follows MyEAR org.apache.maven.plugins maven-ear-plugin false true src/main/resources/META-INF/MANIFEST.MF . . In the above build file true is responsible for adding the MANIFEST.MF entries. My requirement is to add only 2 jars in dependency quartz-1.6.5.jar and poi-3.7.jar and exlcude the remaning. If I give false all the entries are excluded from the MANIFEST.MF classpath. If the remove the depependecy entries from pom I get compilation errors. how can I achieve the above scenario. thanks, -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: exclude entries in MANIFEST.MF
Try to define a filter, similar to the following snippet: lib true true true src/main/resources/ **/*application.xml,**/*MANIFEST.MF From: Surendran D To: Maven Users List Date: 06.11.2013 10:04 Subject:exclude entries in MANIFEST.MF Hi, I am currently building and EAR file using maven-ear-plugin I have a requirement to exclude some of the Class-Path: entries from MANIFEST.MF file. For example I have 3 dependencies hibernate-core.jar, quartz-1.6.5.jar and poi-3.7.jar in my class path (in my dependency of pom.xml) When I build my EAR file all these entries will be automatically added to Class-Path entry of my MANIFEST.MF file. My maven build looks as follows MyEAR org.apache.maven.plugins maven-ear-plugin false true src/main/resources/META-INF/MANIFEST.MF . . In the above build file true is responsible for adding the MANIFEST.MF entries. My requirement is to add only 2 jars in dependency quartz-1.6.5.jar and poi-3.7.jar and exlcude the remaning. If I give false all the entries are excluded from the MANIFEST.MF classpath. If the remove the depependecy entries from pom I get compilation errors. how can I achieve the above scenario. thanks,
Re: exclude entries in MANIFEST.MF
Why do you need the Class-Path entry for an ear? JEE containers have other means to create the classpath. /Anders On Wed, Nov 6, 2013 at 9:54 AM, Surendran D wrote: > Hi, > I am currently building and EAR file using maven-ear-plugin > > I have a requirement to exclude some of the Class-Path: entries from > MANIFEST.MF file. > > For example I have 3 dependencies hibernate-core.jar, quartz-1.6.5.jar and > poi-3.7.jar in my class path (in my dependency of pom.xml) > > When I build my EAR file all these entries will be automatically added to > Class-Path entry of my MANIFEST.MF file. > > My maven build looks as follows > > > MyEAR > > > org.apache.maven.plugins > maven-ear-plugin > > > false > > true > > > > src/main/resources/META-INF/MANIFEST.MF > > > . > . > > > > > In the above build file > > true > is responsible for adding the MANIFEST.MF entries. > > My requirement is to add only 2 jars in dependency quartz-1.6.5.jar and > poi-3.7.jar and exlcude the remaning. > > If I give false all the entries are excluded from the MANIFEST.MF > classpath. If the remove the depependecy entries from pom I get compilation > errors. > > how can I achieve the above scenario. > > thanks, >
exclude entries in MANIFEST.MF
Hi, I am currently building and EAR file using maven-ear-plugin I have a requirement to exclude some of the Class-Path: entries from MANIFEST.MF file. For example I have 3 dependencies hibernate-core.jar, quartz-1.6.5.jar and poi-3.7.jar in my class path (in my dependency of pom.xml) When I build my EAR file all these entries will be automatically added to Class-Path entry of my MANIFEST.MF file. My maven build looks as follows MyEAR org.apache.maven.plugins maven-ear-plugin false true src/main/resources/META-INF/MANIFEST.MF . . In the above build file true is responsible for adding the MANIFEST.MF entries. My requirement is to add only 2 jars in dependency quartz-1.6.5.jar and poi-3.7.jar and exlcude the remaning. If I give false all the entries are excluded from the MANIFEST.MF classpath. If the remove the depependecy entries from pom I get compilation errors. how can I achieve the above scenario. thanks,
