RE: maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
Thanks, exactly what I was looking for.
-Original Message-
From: Thomas Broyer
Sent: donderdag 18 februari 2021 11:44
To: jean-pierre.urk...@devoteam.com.invalid
Cc: Maven Users List
Subject: Re: maven-assembly-plugin v3.3.0 - how to modify generated
MANIFEST.MF
Use the 'archive' property of the assembly plugin itself (not in the
assembly descriptor):
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#archive
Le jeu. 18 févr. 2021 à 11:23, Jean-Pierre Urkens
a écrit :
> Hi all,
>
>
>
> I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’
> in the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
> generating its own (plexus archiver) MANIFEST file with contents:
>
>Manifest-Version: 1.0
>
> Created-By: Plexus Archiver 4.2.1
>
>
>
> My idea was to include via a my own MANIFEST.MF file
> specifying the Main-Class and ‘append’ this to the generated MANIFEST
> using the ‘file-aggregator’ containerDescriptorHandler in my descriptor
> file:
>
>
>
>
>
>
>
> file-aggregator
>
>
>
> .*/MANIFEST.MF
>
> META-INF/MANIFEST.MF
>
>
>
>
>
>
>
>
>
> This didn’t work so I was wondering whether it found my manifest file.
> So I adjusted the above configuration to write to ‘test/
> META-INF/MANIFEST.MF’.
>
> My own manifest file resides under ‘db/MANIFEST.MF’ and should be
> picked up
> by:
>
>
>
>
>
>
>
>
> ${project.build.directory}/classes
>
>
>
> false
>
>
>
> db/**
>
>
>
>
>
>
>
>
>
> Now it does generate an ‘test/META-INF/MANIFEST.MF’ but with following
> contents:
>
># Aggregated on Thu Feb 18 11:18:39 CET 2021 from:
>
>
>
> So it looks that the content of my ‘db/MANIFEST.MF’ isn’t included.
> What am I missing? How can I add my own content to the generated
> manifest file of this plugin?
>
>
>
> Tanks for any hints,
>
>
>
> J.P.
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
Use the 'archive' property of the assembly plugin itself (not in the
assembly descriptor):
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#archive
Le jeu. 18 févr. 2021 à 11:23, Jean-Pierre Urkens
a écrit :
> Hi all,
>
>
>
> I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’ in
> the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
> generating its own (plexus archiver) MANIFEST file with contents:
>
>Manifest-Version: 1.0
>
> Created-By: Plexus Archiver 4.2.1
>
>
>
> My idea was to include via a my own MANIFEST.MF file specifying
> the Main-Class and ‘append’ this to the generated MANIFEST using the
> ‘file-aggregator’ containerDescriptorHandler in my descriptor file:
>
>
>
>
>
>
>
> file-aggregator
>
>
>
> .*/MANIFEST.MF
>
> META-INF/MANIFEST.MF
>
>
>
>
>
>
>
>
>
> This didn’t work so I was wondering whether it found my manifest file. So I
> adjusted the above configuration to write to ‘test/
> META-INF/MANIFEST.MF’.
>
> My own manifest file resides under ‘db/MANIFEST.MF’ and should be picked up
> by:
>
>
>
>
>
>
>
> ${project.build.directory}/classes
>
>
>
> false
>
>
>
> db/**
>
>
>
>
>
>
>
>
>
> Now it does generate an ‘test/META-INF/MANIFEST.MF’ but with following
> contents:
>
># Aggregated on Thu Feb 18 11:18:39 CET 2021 from:
>
>
>
> So it looks that the content of my ‘db/MANIFEST.MF’ isn’t included. What am
> I missing? How can I add my own content to the generated manifest file of
> this plugin?
>
>
>
> Tanks for any hints,
>
>
>
> J.P.
>
maven-assembly-plugin v3.3.0 - how to modify generated MANIFEST.MF
Hi all,
I am trying to generate a ‘jar’ assembly that contains a ‘Main-Class’ in
the META-INF/MANIFEST.MF. Now it looks like the assembly plugin is
generating its own (plexus archiver) MANIFEST file with contents:
Manifest-Version: 1.0
Created-By: Plexus Archiver 4.2.1
My idea was to include via a my own MANIFEST.MF file specifying
the Main-Class and ‘append’ this to the generated MANIFEST using the
‘file-aggregator’ containerDescriptorHandler in my descriptor file:
file-aggregator
.*/MANIFEST.MF
META-INF/MANIFEST.MF
This didn’t work so I was wondering whether it found my manifest file. So I
adjusted the above configuration to write to ‘test/
META-INF/MANIFEST.MF’.
My own manifest file resides under ‘db/MANIFEST.MF’ and should be picked up
by:
${project.build.directory}/classes
false
db/**
Now it does generate an ‘test/META-INF/MANIFEST.MF’ but with following
contents:
# Aggregated on Thu Feb 18 11:18:39 CET 2021 from:
So it looks that the content of my ‘db/MANIFEST.MF’ isn’t included. What am
I missing? How can I add my own content to the generated manifest file of
this plugin?
Tanks for any hints,
J.P.
maven-archetype extension produces jar without Manifest.mf
Hi, looking at current maven-archetype extension it doesn't extends fully the maven-jar-plugin as it cannot produce or setup to include a Manifest.mf file into resulting archetype jar. Is that intention, omission or I just wasn't able to configure it properly? Any help is welcome. Ps. I generated as tryout maven-archetype-quickstart and tried to add into plugin configuration the following: maven-archetype-plugin 3.0.1 -- Marek Novotny signature.asc Description: OpenPGP digital signature
Re: Custom MANIFEST.MF maven-ejb-plugin
Still not sure that you need to do this. Assuming that you can not alter the manifest.mf, what would you do? What are you trying to do that is so bizarre that no one else would need such a feature? See below. On 08/11/2013 4:03 PM, Surendran D wrote: Couldn't find any way to achieve the previous scenario. resolved my adding custom manifest.mf inside src/resources/ and copying it... instead of generating one. On Fri, Nov 8, 2013 at 9:30 AM, Surendran Duraisamy wrote: Hi, How can I generate custom class-path: entries in my maven-ejb-plugin. I have 3 jar A.jar, B.jar and C.jar in my maven dependency pom.xml. I need to put only B.jar and C.jar in my Class-Path: entries of my MANIFEST. I cannot use dependency scope provided as my project is referred by another project which require dependency scope compile. The other project can have a compile dependency on C. If you don't provide C in your jar, where does it come from? Is there any filters in maven-ejb-plugin or I exclude only specific entries in my maven-ejb-plugin. 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: Custom MANIFEST.MF maven-ejb-plugin
Couldn't find any way to achieve the previous scenario. resolved my adding custom manifest.mf inside src/resources/ and copying it... instead of generating one. On Fri, Nov 8, 2013 at 9:30 AM, Surendran Duraisamy wrote: > Hi, > How can I generate custom class-path: entries in my maven-ejb-plugin. > > I have 3 jar A.jar, B.jar and C.jar in my maven dependency pom.xml. I need > to put only B.jar and C.jar in my Class-Path: entries of my MANIFEST. > > I cannot use dependency scope provided as my project is referred by > another project which require dependency scope compile. > > Is there any filters in maven-ejb-plugin or I exclude only specific > entries in my maven-ejb-plugin. > > Thanks, > >
Custom MANIFEST.MF maven-ejb-plugin
Hi, How can I generate custom class-path: entries in my maven-ejb-plugin. I have 3 jar A.jar, B.jar and C.jar in my maven dependency pom.xml. I need to put only B.jar and C.jar in my Class-Path: entries of my MANIFEST. I cannot use dependency scope provided as my project is referred by another project which require dependency scope compile. Is there any filters in maven-ejb-plugin or I exclude only specific entries in my maven-ejb-plugin. Thanks, - 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
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,
Re: MANIFEST.MF into assembly plugin
The Maven war plugin can handle exploded. Even if you need some distribution, having then generated by the Maven WAR plugin will make sure users of the WAR will benefit from it Jeff On Fri, Jun 28, 2013 at 1:34 PM, adrien ruffie wrote: > Because I don't use warm aven plugin, my webapp is exploded in my > distribution packaging (it is one of directories located in my main > distribution), so that's why I doesn't generate a war. > Therefore Maven doesn't pass through the war packaging phase where it is > supposed to generate the manifest > > -Message d'origine- > De : jeffma...@gmail.com [mailto:jeffma...@gmail.com] De la part de Jeff > MAURY > Envoyé : vendredi 28 juin 2013 11:04 > À : Maven Users List > Objet : Re: MANIFEST.MF into assembly plugin > > Why don't you use the maven war plugin to generate the MANIFEST.MF with > your > entries ? > > Jeff > > > On Fri, Jun 28, 2013 at 10:31 AM, adrien ruffie > wrote: > > > Hello all, > > > > ** ** > > > > I have a problem, Perhaps you know a solution. > > > > ** ** > > > > I have the following (in attached file) plugin to build a > > distribution, with unpackaged war, and several jars (built to from the > > webapp). I search to place a manifest with several information in my > > unpackaged war directory into /classes/META-INF but I doesn’t find how > > I can generate a MANIFEST.MF and place it at this Location. I have try > > to use + + … into > > maven-assembly-plugin 2.4 but doesn’t work … > > > > > > Do you know a solution ? > > > > ** ** > > > > I think jar manifest as far as war manifest is generated and > > integrated into jar/war archive during its packaging/zip but, we > > cannot exporte get it before, to extract it to another location. > > > > ** ** > > > > ** ** > > > > Thank and best regards, > > > > ** ** > > > > adrien > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
RE: MANIFEST.MF into assembly plugin
Because I don't use warm aven plugin, my webapp is exploded in my distribution packaging (it is one of directories located in my main distribution), so that's why I doesn't generate a war. Therefore Maven doesn't pass through the war packaging phase where it is supposed to generate the manifest -Message d'origine- De : jeffma...@gmail.com [mailto:jeffma...@gmail.com] De la part de Jeff MAURY Envoyé : vendredi 28 juin 2013 11:04 À : Maven Users List Objet : Re: MANIFEST.MF into assembly plugin Why don't you use the maven war plugin to generate the MANIFEST.MF with your entries ? Jeff On Fri, Jun 28, 2013 at 10:31 AM, adrien ruffie wrote: > Hello all, > > ** ** > > I have a problem, Perhaps you know a solution. > > ** ** > > I have the following (in attached file) plugin to build a > distribution, with unpackaged war, and several jars (built to from the > webapp). I search to place a manifest with several information in my > unpackaged war directory into /classes/META-INF but I doesnt find how > I can generate a MANIFEST.MF and place it at this Location. I have try > to use + + into > maven-assembly-plugin 2.4 but doesnt work > > > Do you know a solution ? > > ** ** > > I think jar manifest as far as war manifest is generated and > integrated into jar/war archive during its packaging/zip but, we > cannot exporte get it before, to extract it to another location. > > ** ** > > ** ** > > Thank and best regards, > > ** ** > > adrien > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MANIFEST.MF into assembly plugin
Why don't you use the maven war plugin to generate the MANIFEST.MF with your entries ? Jeff On Fri, Jun 28, 2013 at 10:31 AM, adrien ruffie wrote: > Hello all, > > ** ** > > I have a problem, Perhaps you know a solution. > > ** ** > > I have the following (in attached file) plugin to build a distribution, > with unpackaged war, and several jars (built to from the webapp). I search > to place a manifest with several information in my unpackaged war directory > into /classes/META-INF but I doesn’t find how I can generate a MANIFEST.MF > and place it at this Location. I have try to use + > + … into maven-assembly-plugin 2.4 but doesn’t work … > > > Do you know a solution ? > > ** ** > > I think jar manifest as far as war manifest is generated and integrated > into jar/war archive during its packaging/zip but, we cannot exporte get it > before, to extract it to another location. > > ** ** > > ** ** > > Thank and best regards, > > ** ** > > adrien > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
MANIFEST.MF into assembly plugin
Hello all,
I have a problem, Perhaps you know a solution.
I have the following (in attached file) plugin to build a distribution, with
unpackaged war, and several jars (built to from the webapp). I search to
place a manifest with several information in my unpackaged war directory
into /classes/META-INF but I doesn't find how I can generate a MANIFEST.MF
and place it at this Location. I have try to use +
+ . into maven-assembly-plugin 2.4 but doesn't work .
Do you know a solution ?
I think jar manifest as far as war manifest is generated and integrated into
jar/war archive during its packaging/zip but, we cannot exporte get it
before, to extract it to another location.
Thank and best regards,
adrien
distribution-packaging
postgresql
${postgresql.provider.artifactId}
${postgresql.provider.version}
provided
com.oracle
${oracle.provider.artifactId}
${oracle.provider.version}
provided
false
org.codehaus.mojo
buildnumber-maven-plugin
1.1
generate-build-date
validate
create
false
true
{0,date,-MM-dd HH:mm:ss}
timestamp
buildDate
generate-timestamp
validate
create
false
true
{0}
timestamp
validate
create
org.apache.maven.plugins
maven-jar-plugin
2.4
${basedir}/${packaging.directory}
true
${project.url}
${project.name}
E-DEAL
${project.version}
${timestamp}
${buildDate}
${os.name}
build-myapp-base-jar
prepare-package
jar
com/myapp/frontline/*.class
com/myapp/frontline/automation/*.class
com/myapp/frontline/grid/**
com/myapp/frontline/display/**
com/myapp/frontline/helper/**
com/myapp/frontline/navigation/**
com/myapp/frontline/partition/**
${distribution.prefix}-base
build-myapp-controller-jar
prepare-package
jar
com/myapp/frontline/controller/**
com/myapp/frontline/initializers/**
com/myapp/frontline/grid/**
com/myapp/frontline/display/**
com/myapp/frontline/helper/**
com/myapp/frontline/navigation/**
com/myapp/frontline/controller/actions/custom/notused/**
${distribution.prefix}-controller
build-myapp-custom-jar
prepare-package
jar
com/myapp/frontline/custom/*.class
${distribution.prefix}-custom
build-myapp-dashboard-jar
prepare-package
jar
com/myapp/frontline/dashboard/*.class
${distribution.prefix}-dashboard
build-myapp-transfer-jar
prepare-package
jar
com/myapp/frontline/transfer/**
${distribution.prefix}-transfer
build-myapp-fulltextsearch-jar
prepare-package
jar
com/myapp/frontline/fulltextsearch/**
${distribution.prefix}-fulltextsearch
build-myapp-fusion-jar
prepare-package
jar
com/myapp/frontline/fusion/**
${distribution.prefix}-fusion
build-myapp-infobar-jar
prepare-package
jar
com/myapp/frontline/infobar/**
${distribution.prefix}-infobar
build-myapp-netbusiness-jar
prepare-package
jar
com/myapp/frontline/netbusiness/**
com/myapp/frontline/publication/**
${distribution.prefix}-netbusiness
build-myapp-ofcgraphs-jar
prepare-package
jar
com/myapp/frontline/ofcgraphs/**
${distribution.prefix}-ofcgraphs
build-myapp-tasks-jar
prepare-package
jar
com/myapp
Maven Shade Plugin: v1.7.1 creating a lower-case meta-inf/manifest.mf file?
We are using maven 3.0.3 and the 1.7.1 shade plugin to create an executable jar. We recently noticed that the shaded jar has a lower-case meta-inf/manifest.mf file in it. The original jar does not have the lowercasing, so it seems to be an issue with the shade plugin? I can't see anything in the code I browsed...anyone else having this issue? We are building on linux... -- Jeffrey D. Brekke Wisconsin, USA ekke...@gmail.com jbre...@wi.rr.com bre...@apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-ear-plugin - How to manipulate Manifest.MF of webModule and ejbModule?
I'm not sure about different behaviors. But I would normally get the JAR and
WAR plugins to edit respected modules' MANIFEST files.
-Original Message-
From: Mauricio
Sent: July-09-12 12:55 PM
Subject: maven-ear-plugin - How to manipulate Manifest.MF of webModule and
ejbModule?
Hello,
I have a multimodule maven project with the following structure:
| app (parent)
-- pom.xml
-- app-ear
-- pom.xml
-- app-ejb
-- src
-- pom.xml
-- app-web
-- src
-- pom.xml
|
This is my *app/pom.xml* (parent project) where I put all my application
dependencies:
|
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";>
4.0.0
com.mycompany
app
0.0.1-SNAPSHOT
pom
app
http://maven.apache.org
app-ejb
app-web
app-ear
javax.ejb
ejb-api
3.0
provided
javaee
javaee-api
5
provided
org.glassfish
javax.faces
2.0.9
provided
org.richfaces.ui
richfaces-components-ui
org.richfaces.core
richfaces-core-impl
org.richfaces
richfaces-bom
4.2.0.Final
import
pom
org.apache.maven.plugins
maven-compiler-plugin
2.4
1.6
1.6
|
This is my *app-ejb/pom.xml*:
|
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";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-ejb
ejb
org.apache.maven.plugins
maven-ejb-plugin
2.3
3.0
|
This is my *app-web/pom.xml*:
|
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";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-web
war
${project.groupId}
app-ejb
${project.version}
provided
app-web
org.apache.maven.plugins
maven-war-plugin
2.2
|
And finally this is my *app-ear/pom.xml* where I have the detais about how
generate my app.ear file:
|
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";>
4.0.0
app
com.mycompany
0.0.1-SNAPSHOT
app-ear
ear
${project.groupId}
app-ejb
ejb
${project.version}
provided
${project.groupId}
app-web
war
${project.version}
provided
app
maven-ear-plugin
2.7
5
war
lib
true
com.mycompany
app-web
app-web.war
/app
com.mycompany
app-ejb
app-ejb.jar
org.glassfish
javax.faces
org.richfaces.core
richfaces-core-api
maven-ear-plugin - How to manipulate Manifest.MF of webModule and ejbModule?
org.w3c.css
sac
com.google.guava
guava
|
My problem is that /app.ear/app-web.war!META-INF/MANIFEST.MF/ and
/app.ear/app-ejb.jar!META-INF/MANIFEST.MF/ looks like this:
| Manifest-Version: 1.0
Build-Jdk: 1.6.0_24
Class-Path: lib/javax.faces-2.0.9.jar lib/richfaces-core-api-4.2.0.Fin
al.jar lib/richfaces-core-impl-4.2.0.Final.jar lib/richfaces-componen
ts-api-4.2.0.Final.jar lib/richfaces-components-ui-4.2.0.Final.jar li
b/cssparser-0.9.5.jar lib/sac-1.3.jar lib/guava-10.0.1.jar lib/jsr305
-1.3.9.jar
Created-By: Apache Maven
Archiver-Version: Plexus Archiver
|
And I really have to remove the Class-Path entry from these MANIFEST.
Why? Because it seems that RichFaces is being loaded two times in
classpath of my application. (One from app.ear/lib folder and another
from app.ear/app-web.war!META-INF/MANIFEST.MF Class-Path entry). And
when I try to deploy app.ear in my Application Server (Oracle Weblogic
10.3.5) I get some errors like that:
| INFO: Unsanitized stacktrace from failed start...
java.lang.IllegalArgumentException: duplicate key: class
javax.faces.validator.RequiredValidator
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
at
com.google.common.collect.RegularImmutableMap.(RegularImmutableMap.java:72)
at
com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:221)
at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:207)
at
org.richfaces.javascript.ClientServiceConfigParser.parseConfig(ClientServiceConfigParser.java:53)
at
org.richfaces.application.ValidatorModule.createClientScriptService(ValidatorModule.java:65)
at org.richfaces.application.ValidatorModule.configure(ValidatorModule.java:60)
at
org.richfaces.application.ServicesFactoryImpl.init(ServicesFactoryImpl.java:27)
|
It's weird that if I run |mvn package| in my *app-web* project, the
Class-path entry does not go to app-web.war/META-INF/MANIFEST.MF. It
only occurs when I run |mvn package| in my *app* parent project.
So, how could I remove the Class-path entry of webModule and ejbModule
MANIFEST file?
I found a similar problem in this thread
<http://stackoverflow.com/questions/9237485/how-to-set-up-manifest-class-path-properly-in-maven-war-plugin>
but without a solution.
I appreciate any help.
Thanks,
Mauricio
Re: How to add additional info to the MANIFEST.MF
> I am using WID 7's serviceDeploy.bat to generate the EAR file from Maven. How > can I inject some build information into the MANIFEST.MF file inside the EAR > file? I want something like this: I have no idea about WID7 or serviceDeploy.bat but this is simple with plain-jane Maven: http://www.lmgtfy.com/?q=maven+manifest.mf+add+entry Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add additional info to the MANIFEST.MF
I am using WID 7's serviceDeploy.bat to generate the EAR file from Maven. How can I inject some build information into the MANIFEST.MF file inside the EAR file? I want something like this: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Build-Jdk: 1.6.0 Implementation-Title: CdiWebServicesEar Implementation-Vendor-Id: com.nbfg.cdi Built-By: NBFG Implementation-Version: 2.3.4-20120622.195932-29 But the default is as follows: Manifest-Version: 1.0 Created-By: 1.5.0 (IBM Corporation) DeployVersion: 7.0.0.0 I notice this command during the run: exec The CDIPubSubMgmtMedApp project is being created. and I believe it's using a default MANIFEST.MF, so how can I inject additional information here? INFO Running with /c call C:/IBM/WID7_WTE/runtimes/bi_v7/profiles/qesb/bin/serviceDeploy.bat C:\Sandbox\MDM\CDIPubSubM gmtMed\..\build\target\CDIPubSubMgmtMed/CDIPubSubMgmtMed-servicedeploy.zip -workingDirectory C:\Sandbox\MDM\CDIPubSubMgm tMed\..\build\target\CDIPubSubMgmtMed/servicedeploy -outputApplication C:\Sandbox\MDM\CDIPubSubMgmtMed\..\build\target\C DIPubSubMgmtMed/CDIPubSubMgmtMed-2.3.4-SNAPSHOT.ear -keep true -ignoreErrors false exec The workbench is starting in C:\Sandbox\MDM\build\target\CDIPubSubMgmtMed\servicedeploy\138442eb9e5. exec The workspace is initializing. exec CDIPubSubMgmtMed-servicedeploy.zip was successfully imported into the workspace. exec The CDIPubSubMgmtMedApp project is being created. exec The CDIPubSubMgmtMedWeb project is being created. exec The CDIPubSubMgmtMed project is building. exec CDIPubSubMgmtMed is being validated. exec The following 2 warning messages were reported during deployment: exec Severity: warning exec Description: CWSCA8095W: Unable to find class com.ibm.ws.sib.api.jmsra.JmsJcaManagedConnectionFactory , please make sure the classpath is properly set up. exec Resource: ClientInfoEventPublishImport.import exec Location: exec Severity: warning exec Description: CWZMU0044E: The fail terminal of the manageIndividualEvent : CDIServicePartner callout r esponse primitive is not connected. exec Resource: CDIPubSubMgmtMed.medflow exec Location: exec The C:\Sandbox\MDM\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\CDIPubSubMgmtMed-2.3.4-SNAPSHOT.ear app lication is being exported. exec Deployment has completed. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-add-additional-info-to-the-MANIFEST-MF-tp5662221p5712758.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
Re: glassfish gf-client.jar with dependencies in its MANIFEST.MF
Hi, I tried the latest 4.0-b33 from maven central and it build fine. I was having earlier problem at my end for same version but then those files which it failed for I deleted and then it resumed fine. Since had problem with 4.0 I without digging deep tried 3.* build and they had their problems and I went on to investigate them. Thanks for checking. Regards, Miten. -- View this message in context: http://maven.40175.n5.nabble.com/glassfish-gf-client-jar-with-dependencies-in-its-MANIFEST-MF-tp5708802p5708820.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
Re: glassfish gf-client.jar with dependencies in its MANIFEST.MF
Wayne Fay wrote: >> gf-client.jar in my local project level repo. I added with >> install:install-file gf-client.jar but now how to setup those >> ../modules.jar >> files in project level repo ? > > If you added gf-client.jar with install-file then you will most likely > need to do the same for all the others. and then specify the ones you > need via . > > The Glassfish team is pretty familiar with Maven so I'm surprised they > don't publish the gf-client artifact (with a proper pom file declaring > dependencies etc) that you could just depend on instead. I'd ask them > directly about it. They do publish it, Miten should just had a look into the jar itself, it contains its own Maven pom. Then he would know that the G:A:V is org.glassfish.main.appclient.client:gf-client:3.1.2 and therefore available at http://repo.maven.apache.org/maven2/org/glassfish/main/appclient/client/gf- client/3.1.2/ - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: glassfish gf-client.jar with dependencies in its MANIFEST.MF
> gf-client.jar in my local project level repo. I added with > install:install-file gf-client.jar but now how to setup those > ../modules.jar > files in project level repo ? If you added gf-client.jar with install-file then you will most likely need to do the same for all the others. and then specify the ones you need via . The Glassfish team is pretty familiar with Maven so I'm surprised they don't publish the gf-client artifact (with a proper pom file declaring dependencies etc) that you could just depend on instead. I'd ask them directly about it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
glassfish gf-client.jar with dependencies in its MANIFEST.MF
Hi, In glassfish app server there is gf-client.jar which in its MANIFEST.MF has lots of dependencies referring to ../modules/*.jar files. As per the file system of glassfish install it resolves fine but I want to setup gf-client.jar in my local project level repo. I added with install:install-file gf-client.jar but now how to setup those ../modules.jar files in project level repo ? Below is snippet of how the gf-client.jar manifest looks like (just few classpath entries pasted and its copy paste from dos terminal). C:\tmp\META-INF>type MANIFEST.MF Manifest-Version: 1.0 Ant-Version: Apache Ant 1.6.5 Created-By: Apache Maven Archiver-Version: Plexus Archiver Built-By: java_re Build-Jdk: 1.6.0_10 Package: org.glassfish.appclient.client.acc Main-Class: org.glassfish.appclient.client.AppClientFacade GlassFish-ServerExcluded: true PreMain-Class: org.glassfish.appclient.client.acc.agent.AppClientConta inerAgent Class-Path: ../modules/tools.jar ../modules/auto-depends.jar ../module s/config.jar ../modules/config-types.jar ../modules/hk2.jar ../module s/hk2-core.jar ../modules/osgi-adapter.jar ../modules/grizzly-comet.j ar ../modules/grizzly-config.jar ../modules/grizzly-framework.jar ../ modules/grizzly-http.jar ../modules/grizzly-http-ajp.jar ../modules/g rizzly-http-servlet.jar ../modules/grizzly-lzma.jar ../modules/grizzl Regards, Miten. -- View this message in context: http://maven.40175.n5.nabble.com/glassfish-gf-client-jar-with-dependencies-in-its-MANIFEST-MF-tp5708802.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
Re: How to add additional info to the MANIFEST.MF
Hi
You have not configured your project to be an EAR project.
You need to add the following line to your POM, otherwise
maven-ear-plugin is never run, as can be seen in the log you provided.
ear
On 2012-04-24 19:58, hujirong wrote:
> I tried, didn't work.
>
> Below is my POM and build output. There is no maven-ear-plugin definition in
> the parent POM.
>
>
>
> 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";>
> 4.0.0
>
>
> com.nbfg.max.maven
> max-wesb-pom
> 0.0.4-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtMed
> 0.0.1-SNAPSHOT
> CDIPubSubMgmtMed Mediation
>
>
>
>
> maven-ear-plugin
>
>
>
>
> true
>
>
>
> ${maven.build.timestamp}
>
> NBFG
>
>
>
>
>
>
>
>
>
>
> com.ibm.ws.sca.sdoplugins
> sdo_api
> ${wid.version}
> system
>
> ${was.home}/feature_packs/sca/sdoplugins/sdo_api.jar
>
>
>
>
> com.nbfg.max.wesb
> ClientServicesBOLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> ClientInfoMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIPubSubMgmtBOLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> CDIServiceMgmtLib
> 0.0.1-SNAPSHOT
>
>
> com.nbfg.max.wesb
> ClientInfoEventLib
> 0.0.1-SNAPSHOT
>
>
>
>
>
>
>
>
>
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building CDIPubSubMgmtMed Mediation 0.0.1-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ CDIPubSubMgmtMed
> ---
> [INFO] Deleting
> C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @
> CDIPubSubMgmtMed ---
> [INFO] Setting property 'portable.artifact.path' to
> 'C:/Workspace/WID/CDIPubSubMgmtMed/../build/target/CDIPubSubMgmtMed/CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear'.
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @
> CDIPubSubMgmtMed ---
> [INFO] Source directory: C:\Workspace\WID\CDIPubSubMgmtMed\gen\src added.
> [INFO]
> [INFO] --- build-helper-maven-plugin:1.7:add-resource (add-resource) @
> CDIPubSubMgmtMed ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
> CDIPubSubMgmtMed ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\Workspace\WID\CDIPubSubMgmtMed\src\main\resources
> [INFO] Copying 20 resources
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> CDIPubSubMgmtMed ---
> [WARNING] File encoding has not been set, using platform encoding Cp1252,
> i.e. build is platform dependent!
> [INFO] Compiling 2 source files to
> C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:testResources
> (default-testResources) @ CDIPubSubMgmtMed ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> C:\Workspace\WID\CDIPubSubMgmtMed\src\test\resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testC
Re: How to add additional info to the MANIFEST.MF
I tried, didn't work.
Below is my POM and build output. There is no maven-ear-plugin definition in
the parent POM.
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";>
4.0.0
com.nbfg.max.maven
max-wesb-pom
0.0.4-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtMed
0.0.1-SNAPSHOT
CDIPubSubMgmtMed Mediation
maven-ear-plugin
true
${maven.build.timestamp}
NBFG
com.ibm.ws.sca.sdoplugins
sdo_api
${wid.version}
system
${was.home}/feature_packs/sca/sdoplugins/sdo_api.jar
com.nbfg.max.wesb
ClientServicesBOLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
ClientInfoMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIPubSubMgmtBOLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
CDIServiceMgmtLib
0.0.1-SNAPSHOT
com.nbfg.max.wesb
ClientInfoEventLib
0.0.1-SNAPSHOT
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building CDIPubSubMgmtMed Mediation 0.0.1-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ CDIPubSubMgmtMed
---
[INFO] Deleting
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @
CDIPubSubMgmtMed ---
[INFO] Setting property 'portable.artifact.path' to
'C:/Workspace/WID/CDIPubSubMgmtMed/../build/target/CDIPubSubMgmtMed/CDIPubSubMgmtMed-0.0.1-SNAPSHOT.ear'.
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:add-source (add-source) @
CDIPubSubMgmtMed ---
[INFO] Source directory: C:\Workspace\WID\CDIPubSubMgmtMed\gen\src added.
[INFO]
[INFO] --- build-helper-maven-plugin:1.7:add-resource (add-resource) @
CDIPubSubMgmtMed ---
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @
CDIPubSubMgmtMed ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\Workspace\WID\CDIPubSubMgmtMed\src\main\resources
[INFO] Copying 20 resources
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
CDIPubSubMgmtMed ---
[WARNING] File encoding has not been set, using platform encoding Cp1252,
i.e. build is platform dependent!
[INFO] Compiling 2 source files to
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\classes
[INFO]
[INFO] --- maven-resources-plugin:2.4.3:testResources
(default-testResources) @ CDIPubSubMgmtMed ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
C:\Workspace\WID\CDIPubSubMgmtMed\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
CDIPubSubMgmtMed ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.7.2:test (default-test) @
CDIPubSubMgmtMed ---
[INFO] No tests to run.
[INFO] Surefire report directory:
C:\Workspace\WID\CDIPubSubMgmtMed\..\build\target\CDIPubSubMgmtMed\surefire-reports
---
T E S T S
Re: How to add additional info to the MANIFEST.MF
> The current EAR file only has the first three lines info. How can I add the > next four lines in BOLD? I am using a parent POM which is not created by me. Google for "maven manifest.mf" leads me to: http://maven.apache.org/guides/mini/guide-manifest.html With a link to: http://maven.apache.org/shared/maven-archiver/index.html Which tells the user how to add such data via . Since this is an ear, you will add configuration to the maven-ear-plugin entry in your pom. Here is an example if your project was a jar -- just adapt it slightly: http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html Google knows about all of this. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to add additional info to the MANIFEST.MF
Hi The current EAR file only has the first three lines info. How can I add the next four lines in BOLD? I am using a parent POM which is not created by me. Thanks Jirong Manifest-Version: 1.0 DeployVersion: 7.0.0.0 Created-By: 1.5.0 (IBM Corporation) *Implementation-Vendor: NBFG Built-By: NBFG Implementation-Version: 20120404_1130 Implementation-Title: CDIPubSubMgmtMed* -- View this message in context: http://maven.40175.n5.nabble.com/How-to-add-additional-info-to-the-MANIFEST-MF-tp5662221p5662221.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
Re: Adding a line in the MANIFEST.MF with maven3
got this fixed now: org.apache.felix maven-bundle-plugin 2.2.0 true org.dyndns.soundbox.mp3wrapper.Activator com.jcraft.jogg,com.jcraft.jorbis,javazoom.jl.converter,javazoom.jl.decoder,javazoom.jl.player,javazoom.jl.player.advanced,javazoom.spi,javazoom.spi.mpeg.sampled.convert,javazoom.spi.mpeg.sampled.file,javazoom.spi.mpeg.sampled.file.tag,javazoom.spi.vorbis.sampled.convert,javazoom.spi.vorbis.sampled.file,org.dyndns.soundbox.mp3wrapper,org.tritonus.lowlevel.lame,org.tritonus.midi.file,org.tritonus.sampled.convert,org.tritonus.sampled.convert.javalayer,org.tritonus.sampled.convert.lame,org.tritonus.sampled.file,org.tritonus.sampled.file.mpeg,org.tritonus.share,org.tritonus.share.midi,org.tritonus.share.sampled,org.tritonus.share.sampled.convert,org.tritonus.share.sampled.file,org.tritonus.share.sampled.mixer org.dyndns.soundbox.mp3wrapper.* * simply putting any value pairs into will put the line: "key: value" into the manifest.mf regards, oli Am 19.12.2011 13:16, schrieb Antonio Petrelli: 2011/12/19 Oliver Zemann I dont want to change so much in the pom.xml, because i am new to maven and dont want to "kill" it, so i hoped there is something like "just add this line and its done" ;) It's wrong. It's better to use the correct Maven plugin. There's a great probability that the IDE will recognize it (I am pretty sure of it in Eclipse, but NetBeans was one of the first adopters of Maven). Moreover I noticed that you are using Felix for a thing that, sincerely, I cannot be able to read. Did you try using the Felix Maven plugin? http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding a line in the MANIFEST.MF with maven3
> I cannot be able to read i dont understand that. Netbeans uses the felix-maven-plugin by default. And yes, i am using it too. But what has this to do with my problem in adding a line to the manifest.mf? On the site you posted, i only found that: If you have an existing manifest, you can add this to the Bnd instructions, like so: <_include>src/main/resources/META-INF/MANIFEST.MF Should i create a manifest.mf with content: SPI-Provider: ... And use the include statement for that? I did not post the whole pom.xml, only the relevant parts of it. Am 19.12.2011 13:16, schrieb Antonio Petrelli: > 2011/12/19 Oliver Zemann > >> I dont want to change so much in the pom.xml, because i am new to maven >> and dont want to "kill" it, so i hoped there is something like "just add >> this line and its done" ;) >> > It's wrong. It's better to use the correct Maven plugin. There's a great > probability that the IDE will recognize it (I am pretty sure of it in > Eclipse, but NetBeans was one of the first adopters of Maven). > Moreover I noticed that you are using Felix for a thing that, sincerely, I > cannot be able to read. Did you try using the Felix Maven plugin? > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html > > Antonio > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding a line in the MANIFEST.MF with maven3
2011/12/19 Oliver Zemann > I dont want to change so much in the pom.xml, because i am new to maven > and dont want to "kill" it, so i hoped there is something like "just add > this line and its done" ;) > It's wrong. It's better to use the correct Maven plugin. There's a great probability that the IDE will recognize it (I am pretty sure of it in Eclipse, but NetBeans was one of the first adopters of Maven). Moreover I noticed that you are using Felix for a thing that, sincerely, I cannot be able to read. Did you try using the Felix Maven plugin? http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html Antonio
Re: Adding a line in the MANIFEST.MF with maven3
Because Netbeans created it that way... and in the netbeans created
pom.xml there's no usage of the maven-jar-plugin. Also the statement:
"Starting with version 2.1, the maven-jar-plugin uses Maven Archiver
2.1. This means that it no longer creates the Specification and
Implementation details in the manifest by default."
I dont want to change so much in the pom.xml, because i am new to maven
and dont want to "kill" it, so i hoped there is something like "just add
this line and its done" ;)
thanks,
oli
Am 19.12.2011 12:01, schrieb Anders Hammar:
> Why aren't you using the standard Maven way for a jar project and
> configure the jar plugin?
> http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
>
> /Anders
>
> On Mon, Dec 19, 2011 at 11:56, Oliver Zemann
> wrote:
>> Hi,
>>
>> i would like to add a line into my manifest.mf when the .jar is created
>> with netbeans 7.0.1.
>> This is my pom.xml:
>>
>>
>>
>>build-for-felix
>>
>>
>>org.apache.felix
>>org.apache.felix.main
>>3.0.7
>>provided
>>
>>
>>
>>
>>
>>
>>org.apache.maven.plugins
>>maven-antrun-plugin
>>1.6
>>
>>
>>compile
>>package
>>
>>run
>>
>>
>>
>>> property="plugins.jars" pathsep="${path.separator}">
>>> refid="maven.runtime.classpath"/>
>>> from="${project.build.directory}${file.separator}classes" to=""/>
>>
>>> property="bundles">
>>
>>
>>
>>
>>> to="file:modules/*" casesensitive="no"/>
>>
>>
>>
>>> file="${project.build.directory}/config.properties">
>>> key="felix.auto.start" value="${bundles}
>> file:modules/${project.build.finalName}.jar"/>
>>> key="org.osgi.framework.bootdelegation" value="*"/>
>>
>>> file="${maven.dependency.org.apache.felix.org.apache.felix.main.jar.path}"
>> tofile="${project.build.directory}/felix.jar"/>
>>
>>
>>
>>
>>
>>
>>org.apache.maven.plugins
>>maven-assembly-plugin
>>2.2
>>
>>
>>create-executable-jar
>>package
>>
>>single
>>
>>
>>
>>
>> ${basedir}/src/main/assembly/felix.xml
>>
>>
>> ${project.build.finalName}
>>
>>
>>
>>
>> javax.sound.sampled.AudioSystem#getAudioInputStream
>>
>>
>>
>>
>>
>&g
Re: Adding a line in the MANIFEST.MF with maven3
Why aren't you using the standard Maven way for a jar project and
configure the jar plugin?
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
/Anders
On Mon, Dec 19, 2011 at 11:56, Oliver Zemann
wrote:
> Hi,
>
> i would like to add a line into my manifest.mf when the .jar is created
> with netbeans 7.0.1.
> This is my pom.xml:
>
>
>
> build-for-felix
>
>
> org.apache.felix
> org.apache.felix.main
> 3.0.7
> provided
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-antrun-plugin
> 1.6
>
>
> compile
> package
>
> run
>
>
>
> property="plugins.jars" pathsep="${path.separator}">
> refid="maven.runtime.classpath"/>
> from="${project.build.directory}${file.separator}classes" to=""/>
>
> property="bundles">
>
>
>
>
> to="file:modules/*" casesensitive="no"/>
>
>
>
> file="${project.build.directory}/config.properties">
> key="felix.auto.start" value="${bundles}
> file:modules/${project.build.finalName}.jar"/>
> key="org.osgi.framework.bootdelegation" value="*"/>
>
> file="${maven.dependency.org.apache.felix.org.apache.felix.main.jar.path}"
> tofile="${project.build.directory}/felix.jar"/>
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 2.2
>
>
> create-executable-jar
> package
>
> single
>
>
>
>
> ${basedir}/src/main/assembly/felix.xml
>
>
> ${project.build.finalName}
>
>
>
>
> javax.sound.sampled.AudioSystem#getAudioInputStream
>
>
>
>
>
>
>
>
>
> org.codehaus.mojo
>
> exec-maven-plugin
> 1.1
>
>
>
>
> verify
>
>
>
> exec
>
>
>
>
>
>
> java
>
> ${project.build.dir}
>
>
>
> -jar
>
> org.apache.aries.spifly.static.tool-0.4-SNAPSHOT-jar-with-dependencies.jar
>
> target/${project.build.finalName}.jar
>
>
>
>
>
> org.apache.maven.plugins
> maven-clean-plugin
> 2.2
>
>
> true
>
>
> ${basedir}/target
>
>
> ${project.build.finalName}.jar
>
>
Adding a line in the MANIFEST.MF with maven3
Hi,
i would like to add a line into my manifest.mf when the .jar is created
with netbeans 7.0.1.
This is my pom.xml:
build-for-felix
org.apache.felix
org.apache.felix.main
3.0.7
provided
org.apache.maven.plugins
maven-antrun-plugin
1.6
compile
package
run
org.apache.maven.plugins
maven-assembly-plugin
2.2
create-executable-jar
package
single
${basedir}/src/main/assembly/felix.xml
${project.build.finalName}
javax.sound.sampled.AudioSystem#getAudioInputStream
org.codehaus.mojo
exec-maven-plugin
1.1
verify
exec
java
${project.build.dir}
-jar
org.apache.aries.spifly.static.tool-0.4-SNAPSHOT-jar-with-dependencies.jar
target/${project.build.finalName}.jar
org.apache.maven.plugins
maven-clean-plugin
2.2
true
${basedir}/target
${project.build.finalName}.jar
Re: How to merge the manifest.mf
Hi，
I try it, but the result is not my expected.My Directory like this:
---
-src
-main
-java
-‘sources’
-resources
-‘other resource files’
-META-INF
-MANIFEST.MF
-spring
-‘some configuration files’
-target
-pom.xml
---
My MANIFEST.MF is :
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Runtime
Bundle-SymbolicName: ${user.project.symbolicName}
Bundle-Version: 1.0.0.qualifier
Import-Package: org.eclipse.osgi.framework.console;version="1.1.0",
org.osgi.framework;version="1.3.0",
org.slf4j
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Require-Bundle: org.springframework.osgi.core;bundle-version="1.2.1"
Now i want to modify the 'Bundle-Version' use .
My POM fragment like this :
maven-jar-plugin
2.3
META-INF/MANIFEST.MF
false
./
META-INF/**/*
**/*/.svn
Can you tell me the JIRA's url?
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-merge-the-manifest-mf-tp5058051p5060921.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
Re: How to merge the manifest.mf
Thank you very much. -- View this message in context: http://maven.40175.n5.nabble.com/How-to-merge-the-manifest-mf-tp5058051p5060817.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
Re: How to merge the manifest.mf
> But, when the operation completed, the manifest.mf is not changed.How to > merge?Thanks First off, the usual location for this file is src/main/resources/META-INF/MANIFEST.MF. So my first try would be to move the file there and change the configuration to see if that does anything. Then I would wonder where you are coming up with the idea that the manifest file is not changing? Where exactly are you seeing that? Try running "mvn package", then unzipping the resulting jar file and looking at that manifest file (directly from the jar). That file should have the Bundle-Version you specified in it. The manifest file in /target may or may not, depending on where (and when) you are looking at it. If you're doing all this and still not seeing the results you expect, I would create a sample project that demonstrates this issue and attach it to a JIRA so someone can look at it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to merge the manifest.mf
Hi,
I use my own manifest.mf in the POM.xml like this:
maven-jar-plugin
2.3.2
META-INF/MANIFEST.MF
${project.version}
But, when the operation completed, the manifest.mf is not changed.How to
merge?Thanks
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-merge-the-manifest-mf-tp5058051p5058051.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
Re: Error assembling WAR: MANIFEST.MF does not exist.
> Why are you setting outputDirectory manually?
I have no good answer to your question. I have found the similar project
like my one. And I do copy and paste.
> that means in war/WEB-INF/classes/META-INF/ just as it says in the error
> message.
I've understood this, and therefore I've said sorry.
dennisl wrote:
>
> On 2011-05-01 01:31, sipungora wrote:
>> Sorry, it was my error. pom says:
>>
>>
>> war/WEB-INF/classes
>
> This is not good. You should alway use a directory under target/ as your
> output directory. Why are you setting outputDirectory manually?
>
>> ...
>> and
>> ...
>>
>> org.apache.maven.plugins
>> maven-war-plugin
>>
>>
>> war
>>
>> src/main/webapp/WEB-INF/web.xml
>>
>> WEB-INF/lib/*
>>
>>
>>
>> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>>
>
> Here you are telling the plugin to use your own custom MANIFEST.MF that
> is located in ${project.build.outputDirectory}/META-INF/ and with your
> current outputDirectory that means in war/WEB-INF/classes/META-INF/ just
> as it says in the error message.
>
>>
>>
>>
>> ...
>>
>>
>> Now I've corrected it and build is successful.
>>
>> Thank you for hint. Sorry. --
>> View this message in context:
>> http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361959.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
>>
>>
>
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
--
View this message in context:
http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4363196.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
Re: Error assembling WAR: MANIFEST.MF does not exist.
On 2011-05-01 01:31, sipungora wrote:
> Sorry, it was my error. pom says:
>
>
> war/WEB-INF/classes
This is not good. You should alway use a directory under target/ as your
output directory. Why are you setting outputDirectory manually?
> ...
> and
> ...
>
> org.apache.maven.plugins
> maven-war-plugin
>
>
> war
>
> src/main/webapp/WEB-INF/web.xml
>
> WEB-INF/lib/*
>
>
>
> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
Here you are telling the plugin to use your own custom MANIFEST.MF that
is located in ${project.build.outputDirectory}/META-INF/ and with your
current outputDirectory that means in war/WEB-INF/classes/META-INF/ just
as it says in the error message.
>
>
>
> ...
>
>
> Now I've corrected it and build is successful.
>
> Thank you for hint. Sorry. --
> View this message in context:
> http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361959.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
>
>
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Error assembling WAR: MANIFEST.MF does not exist.
Sorry, it was my error. pom says:
war/WEB-INF/classes
...
and
...
org.apache.maven.plugins
maven-war-plugin
war
src/main/webapp/WEB-INF/web.xml
WEB-INF/lib/*
${project.build.outputDirectory}/META-INF/MANIFEST.MF
...
Now I've corrected it and build is successful.
Thank you for hint. Sorry. --
View this message in context:
http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361959.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
Re: Error assembling WAR: MANIFEST.MF does not exist.
Do you mean this part?
org.apache.maven.plugins
maven-war-plugin
war
src/main/webapp/WEB-INF/web.xml
WEB-INF/lib/*
${project.build.outputDirectory}/META-INF/MANIFEST.MF
--
View this message in context:
http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361951.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
Re: Error assembling WAR: MANIFEST.MF does not exist.
What does your POM say? On Sat, Apr 30, 2011 at 6:43 PM, sipungora wrote: > Hi, > > can somebody explain me why get I this error: > > "Error assembling WAR: myproject\war\WEB-INF\classes\META-INF\MANIFEST.MF > does not exist." > > Why is it looking for MANIFEST.MF in WEB-INF\classes? > > Thanks in advance. > Best Regards. > -sipungora-- > View this message in context: > http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361924.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Error assembling WAR: MANIFEST.MF does not exist.
Hi, can somebody explain me why get I this error: "Error assembling WAR: myproject\war\WEB-INF\classes\META-INF\MANIFEST.MF does not exist." Why is it looking for MANIFEST.MF in WEB-INF\classes? Thanks in advance. Best Regards. -sipungora-- View this message in context: http://maven.40175.n5.nabble.com/Error-assembling-WAR-MANIFEST-MF-does-not-exist-tp4361924p4361924.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
Re: Maven generated MANIFEST.MF: Commit or ignore?
In some cases, if you're strongly relying on your IDE (this is the case for me with eclipse RSA & websphere integration), it can be useful to commit this on your SCM. But generally, everything generated should be ignored :-) Frédéric On Fri, Oct 8, 2010 at 2:03 PM, Yanko, Curtis wrote: > They get packaged into the artifact itself. No need to commit > > > > > Curt Yanko | Continuous Integration Services | UnitedHealth Group IT > Making IT Happen, one build at a time > > -Original Message- > From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] > On Behalf Of Paul Benedict > Sent: Thursday, October 07, 2010 8:31 PM > To: Maven Users List > Subject: Maven generated MANIFEST.MF: Commit or ignore? > > Can anyone recommend whether to SCM commit the generated MANIFEST.MF > files? Or should they just be ignored? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > This e-mail, including attachments, may include confidential and/or > proprietary information, and may be used only by the person or entity > to which it is addressed. If the reader of this e-mail is not the intended > recipient or his or her authorized agent, the reader is hereby notified > that any dissemination, distribution or copying of this e-mail is > prohibited. If you have received this e-mail in error, please notify the > sender by replying to this message and delete this e-mail immediately. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
RE: Maven generated MANIFEST.MF: Commit or ignore?
They get packaged into the artifact itself. No need to commit Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, October 07, 2010 8:31 PM To: Maven Users List Subject: Maven generated MANIFEST.MF: Commit or ignore? Can anyone recommend whether to SCM commit the generated MANIFEST.MF files? Or should they just be ignored? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven generated MANIFEST.MF: Commit or ignore?
Aren't they generated into target usually, and rebuilt on each build? Doesn't sound like something to check in. On 08/10/2010, at 11:31 AM, Paul Benedict wrote: > Can anyone recommend whether to SCM commit the generated MANIFEST.MF > files? Or should they just be ignored? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven generated MANIFEST.MF: Commit or ignore?
In general, you shouldn't commit any generated file to SCM. On Oct 7, 2010, at 8:31 PM, Paul Benedict wrote: > Can anyone recommend whether to SCM commit the generated MANIFEST.MF > files? Or should they just be ignored? > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven generated MANIFEST.MF: Commit or ignore?
Can anyone recommend whether to SCM commit the generated MANIFEST.MF files? Or should they just be ignored? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: dependencyManagement and Manifest.MF issue
Hi Torsten, torsten.reinh...@gi-de.com wrote at Dienstag, 23. Februar 2010 15:24: > Hi, > > in our build, we have a module C with a dependeny to module B, having a > dependency to module A in version A-4.0.14, but managed to version > A-4.0.15. > Thus, this version and dependency is build into Manifest.MF of module C: > > Class-Path: B-1.0.0-SNAPSHOT.jar A-4.0.15.jar > > Later on, we pick up module C, and copy all dependencies of it into a > directory structure - assuming, that a complete classpath will result. > When copying dependencies, not version A-4.0.15 is copied, but A-4.0.14 > (coming from module B´s dependencies). > > => We now have a runtime problem, because in Manifest.MF A-4.0.15 is > stated, but A-4.0.14 was copied. > > Any suggestions how to handle this? Use a dependencyManagement section in a shared parent POM where you define the versions of your direct and transitive deps. NOte, that such a parent POM does not have to be in the parent directory, but can be an artifact on its own right with own release cycle. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
dependencyManagement and Manifest.MF issue
Hi, in our build, we have a module C with a dependeny to module B, having a dependency to module A in version A-4.0.14, but managed to version A-4.0.15. Thus, this version and dependency is build into Manifest.MF of module C: Class-Path: B-1.0.0-SNAPSHOT.jar A-4.0.15.jar Later on, we pick up module C, and copy all dependencies of it into a directory structure - assuming, that a complete classpath will result. When copying dependencies, not version A-4.0.15 is copied, but A-4.0.14 (coming from module B´s dependencies). => We now have a runtime problem, because in Manifest.MF A-4.0.15 is stated, but A-4.0.14 was copied. Any suggestions how to handle this? Thanx, Torsten
Re: Error in assembly - META-INF/MANIFEST.MF not found
Just a gentle ping if anyone has any insight on why this would occur. Its wreaking havoc with my builds and any help is much appreciated. I checked the archives and saw one other person with this issue but the only response I saw was someone mentioning running an ls command. I can provide any additional info necessary if this issue is unclear. Hopefully someone knows what I'm doing wrong :) Thanks Mike Key On Jan 5, 2010, at 1:07 PM, Mike Key wrote: > I am building an assembly from a war and when I build locally with maven it > works fine, however when I build on a CentOS machine through Hudson I get the > following error on initial build, if I restart the build it clears itself up, > but on each checkin this error occurs. I have checked the war and > META-INF/MANIFEST.MF DOES exist. > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to create assembly: Error creating assembly archive > distribution: Problem creating war: JAR entry META-INF/MANIFEST.MF not found > in > <http://myhost/job/live-ensure-trunk/ws/trunk/services/live-identity-ws/target/live-identity-ws-3.0.0-SNAPSHOT.war> > > Any help on clearing this up is much appreciated. > > Thanks in advance. > > Mike Key
Error in assembly - META-INF/MANIFEST.MF not found
I am building an assembly from a war and when I build locally with maven it works fine, however when I build on a CentOS machine through Hudson I get the following error on initial build, if I restart the build it clears itself up, but on each checkin this error occurs. I have checked the war and META-INF/MANIFEST.MF DOES exist. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to create assembly: Error creating assembly archive distribution: Problem creating war: JAR entry META-INF/MANIFEST.MF not found in <http://myhost/job/live-ensure-trunk/ws/trunk/services/live-identity-ws/target/live-identity-ws-3.0.0-SNAPSHOT.war> Any help on clearing this up is much appreciated. Thanks in advance. Mike Key
Re: maven-jar-plugin version 2.3 MANIFEST.MF SNAPSHOT problem
Stephen Duncan Jr wrote:
> I see that http://jira.codehaus.org/browse/MJAR-28 was "fixed" in the 2.3
> release. From my perspective, this seems to have broken things, including a
> viable working system I had using 2.2.
>
> In 2.3 I have several SNAPSHOT dependencies, but when I build a jar with
> addClasspath, only one of those is getting a timestamp version, the rest
> still say -SNAPSHOT. In 2.2 all would say -SNAPSHOT. By adding:
>
>
>
> ${artifact.artifactId}-${artifact.baseVersion}.${artifact.extension}
>
>
> to my dependency-set config for the assembly plugin, the assembly plugin
> would also always use -SNAPSHOT.
>
> In 2.3 the versions in the MANIFEST still do not match up to the assembly
> (after removing the outputFileNameMapping), as in that case all the versions
> in the assembly are timestamped, but many are not in the manifest.
>
> Should I reopen MJAR-28?
>
Hi Stephen,
Please create a new issue if you are still having problems. We can add a
link to the old issue later, but I prefer not to reopen issues when the
version they were "fixed" in have been released. It messes up the
changes reports.
Also, please attach a sample project that we can use to reproduce the issue.
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-jar-plugin version 2.3 MANIFEST.MF SNAPSHOT problem
I see that http://jira.codehaus.org/browse/MJAR-28 was "fixed" in the 2.3
release. From my perspective, this seems to have broken things, including a
viable working system I had using 2.2.
In 2.3 I have several SNAPSHOT dependencies, but when I build a jar with
addClasspath, only one of those is getting a timestamp version, the rest
still say -SNAPSHOT. In 2.2 all would say -SNAPSHOT. By adding:
${artifact.artifactId}-${artifact.baseVersion}.${artifact.extension}
to my dependency-set config for the assembly plugin, the assembly plugin
would also always use -SNAPSHOT.
In 2.3 the versions in the MANIFEST still do not match up to the assembly
(after removing the outputFileNameMapping), as in that case all the versions
in the assembly are timestamped, but many are not in the manifest.
Should I reopen MJAR-28?
--
Stephen Duncan Jr
www.stephenduncanjr.com
maven jar plugin not including all the jars in the manifest.mf
I am trying to build jar, where i would need all the classpath entries in the manifest.mf, but the manifest.mf is not inlcluding the jars in the classpath (like testng.jar ). is there anything wrong in my configuration ? org.apache.maven.plugins maven-jar-plugin true true org.testng.TestNG /export/home/webdriver/lib test-jar -- View this message in context: http://www.nabble.com/maven-jar-plugin-not-including-all-the-jars-in-the-manifest.mf-tp25190308p25190308.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
Re: How to add a directory to the Class-Path in the MANIFEST.MF.
Hello, The matter of title was self-solved. If you add the directory './' to the Class-Path in the MANIFEST.MF, you only have to write the below to the pom.xml of your project. ・ ・ ./ ・ ・ ・ The directory './' will be added to the head of the Class-Path. Takeshi Katayama wrote: >Hello, > >Please teach me to add a directory to the Class-Path in the MANIFEST.MF. > >I would like to put the property files on the outside of the created jar-file. >(Not to build every changing settings.) >But, by default, if there are the property files under >/src/main/resources, >those files are put in the created jar-file. > >Or, usually in the Maven projects, >aren't the property files put on the outside of the created jar-file ? >(In short, is it the correct usage that there are always the property files >under /src/main/resources ?) > >Someone who knows, please teach me. > > >- >To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: include current direcory path into jar classpath in manifest.mf file
> I am getting FileNotFoundException while reading resource files in > current directory . > Can u please help me to include current directory path apart from > library jar files path in manifest.mf file of a jar. Why don't you provide a few lines of code that aren't working and/or a few lines out of your pom file so that people can help in more concrete terms rather than speaking about things so generally? Ultimately, what are you trying to achieve, what have you tried so far, and what is or is not working? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
include current direcory path into jar classpath in manifest.mf file
Hi, I am getting FileNotFoundException while reading resource files in current directory . Can u please help me to include current directory path apart from library jar files path in manifest.mf file of a jar. Thanks & Regards Polireddy Reddem VOIP: 6917 Access Identity Management Team ITS - NCG -Security Services Bank of America -Hyderabad The information contained in this transmission may contain privileged and confidential information and is intended only for the use of the person(s) named above. If you are not the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you received this email in error, please contact the sender immediately by reply e-mail and destroy all copies of the original message. This email is not intended as an offer or solicitation for the purchase or sale of any financial instruments.
Re: How to add a directory to the Class-Path in the MANIFEST.MF.
> Please teach me to add a directory to the Class-Path in the MANIFEST.MF. http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html http://maven.apache.org/shared/maven-archiver/index.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to add a directory to the Class-Path in the MANIFEST.MF.
Hello, Please teach me to add a directory to the Class-Path in the MANIFEST.MF. I would like to put the property files on the outside of the created jar-file. (Not to build every changing settings.) But, by default, if there are the property files under /src/main/resources, those files are put in the created jar-file. Or, usually in the Maven projects, aren't the property files put on the outside of the created jar-file ? (In short, is it the correct usage that there are always the property files under /src/main/resources ?) Someone who knows, please teach me. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to set outputFileNameMapping for generated Class-Path in MANIFEST.MF?
Hi,
I specify the following outputFileNameMapping option in the assembly
descriptor to cut off version number from jar names. This is because
the produced jars are used in another project, and I don't want to
change the naming convention there.
...
...
${module.artifactId}.${module.extension}
I also want to add a Class-Path entry to the main jar:
maven-jar-plugin
true
What I get is a Class-Path entry in manifest that contains jars with
version number, e.g.
Class-Path: jdom-1.1.jar.
I searched but I was not able to find the way to specify jar file name
format for Class-Path in manifest either for maven-jar-plugin or for
for jar format of maven-assembly-plugin.
I was able to suppress version number for jars which are build by this
maven build:
${artifactId}
...
In this case maven-jar-plugin generates correct Class-Path entry. But
external jars like jdom are still included with their extension.
Is there a solution for this?
--Vova
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Excluding Manifest.MF when generating jar-files
On Thu, Feb 12, 2009 at 8:29 AM, Weichselbaumer Michael (MWE 4170) wrote: > Manifest.MF files are created dynamically, but I need to compare newly > built jar-artifacts to older ones in order to find out if they have > changed. This is done by simply checking md5 hashes. Those hashes are > modified by the manifest.mf ... therefore I need to get rid of it ... The jar file stores also the file date of the individual files. I am not sure I fully understand what you are trying to do, but the MANIFEST.MF file is probably not your only problem. Henry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Excluding Manifest.MF when generating jar-files
Manifest.MF files are created dynamically, but I need to compare newly built jar-artifacts to older ones in order to find out if they have changed. This is done by simply checking md5 hashes. Those hashes are modified by the manifest.mf ... therefore I need to get rid of it ... -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Mittwoch, 11. Februar 2009 18:55 To: Maven Users List Subject: Re: Excluding Manifest.MF when generating jar-files > I am currently trying to create jar-files without the MANIFEST.MF > included. > How can i tell Maven2 to not include those? What possible reason do you have for needing this functionality? I'm curious. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Excluding Manifest.MF when generating jar-files
> I am currently trying to create jar-files without the MANIFEST.MF > included. > How can i tell Maven2 to not include those? What possible reason do you have for needing this functionality? I'm curious. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Excluding Manifest.MF when generating jar-files
Hello list, I am currently trying to create jar-files without the MANIFEST.MF included. How can i tell Maven2 to not include those? I have already figured out that adding: org.apache.maven.plugins maven-jar-plugin false helps me removing that "maven" subfolder in "META-INF", which contains pom.properties and stuff. But now I would like to not include a MANIFEST.MF either. Anyway, I can't figure out how to configure that. Could anyone help me with this?!
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Hi Thank you for your reply. I used the following code inside the build element to make it possible to use my own manifest file but it is not including the file into the final archite. org.apache.maven.plugins maven-jar-plugin src/main/resources/META-INF/MANIFEST.MF Is there anything else which I should do? is there any way to ensure that maven execute tasks associated with these elements? Thanks Brett Randall-2 wrote: > > are covered in the Maven POM reference here > http://maven.apache.org/pom.html#Plugins . They are nested within a > . > > On Sun, Jan 4, 2009 at 11:00 AM, sarah.kho wrote: > >> >> Thank you for the link, unfortunately my build file has no tag >> inside it. An I can not find out where I should put those tags. dot hey >> goes inside the tag? >> >> Thanks >> >> >> >> >> >> Olivier Lamy wrote: >> > >> > Hi, >> > Maybe have a look here >> > >> http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html >> > . >> > >> > HTH, >> > -- >> > Olivier >> > >> > 2009/1/3 legolas : >> >> >> >> Hi >> >> Thank you for reading my post >> >> Can someone please let me know how I can ensure that Maven uses my own >> >> Manifest.MF instead of the one it generates? >> >> I tried to use **/*.MF to ensure that it will >> include >> >> my >> >> file but it uses its own generated file which is not what I need. I >> test >> >> the >> >> syntax of **/*.MF and it works for other files and >> not >> >> for the Manifest.mf >> >> >> >> Thanks. >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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 >> >> >> >> >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.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 >> >> > > -- View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21309292.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
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
are covered in the Maven POM reference here http://maven.apache.org/pom.html#Plugins . They are nested within a . On Sun, Jan 4, 2009 at 11:00 AM, sarah.kho wrote: > > Thank you for the link, unfortunately my build file has no tag > inside it. An I can not find out where I should put those tags. dot hey > goes inside the tag? > > Thanks > > > > > > Olivier Lamy wrote: > > > > Hi, > > Maybe have a look here > > http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html > > . > > > > HTH, > > -- > > Olivier > > > > 2009/1/3 legolas : > >> > >> Hi > >> Thank you for reading my post > >> Can someone please let me know how I can ensure that Maven uses my own > >> Manifest.MF instead of the one it generates? > >> I tried to use **/*.MF to ensure that it will include > >> my > >> file but it uses its own generated file which is not what I need. I test > >> the > >> syntax of **/*.MF and it works for other files and > not > >> for the Manifest.mf > >> > >> Thanks. > >> -- > >> View this message in context: > >> > http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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 > >> > >> > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > View this message in context: > http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.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 > >
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Thank you for the link, unfortunately my build file has no tag inside it. An I can not find out where I should put those tags. dot hey goes inside the tag? Thanks Olivier Lamy wrote: > > Hi, > Maybe have a look here > http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html > . > > HTH, > -- > Olivier > > 2009/1/3 legolas : >> >> Hi >> Thank you for reading my post >> Can someone please let me know how I can ensure that Maven uses my own >> Manifest.MF instead of the one it generates? >> I tried to use **/*.MF to ensure that it will include >> my >> file but it uses its own generated file which is not what I need. I test >> the >> syntax of **/*.MF and it works for other files and not >> for the Manifest.mf >> >> Thanks. >> -- >> View this message in context: >> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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 >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.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
Re: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Hi, Maybe have a look here http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html . HTH, -- Olivier 2009/1/3 legolas : > > Hi > Thank you for reading my post > Can someone please let me know how I can ensure that Maven uses my own > Manifest.MF instead of the one it generates? > I tried to use **/*.MF to ensure that it will include my > file but it uses its own generated file which is not what I need. I test the > syntax of **/*.MF and it works for other files and not > for the Manifest.mf > > Thanks. > -- > View this message in context: > http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?
Hi Thank you for reading my post Can someone please let me know how I can ensure that Maven uses my own Manifest.MF instead of the one it generates? I tried to use **/*.MF to ensure that it will include my file but it uses its own generated file which is not what I need. I test the syntax of **/*.MF and it works for other files and not for the Manifest.mf Thanks. -- View this message in context: http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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
Re: How to add snapshot dependency into MANIFEST.MF
youhaodeyi wrote: > > My project dependent on a snapshot dependency (test-1.0-snapshot). I added > this configuration in my jar-plugin: > > true > test.ui.Starter > UI DEMO > > All the dependencies will be written to manifest.mf file. So the final > manifest.mf will includes: > Class-Path: test-1.0-snapshot.jar > > But when I run the assembly, the version of the test-1.0 will be > inconsistent with the one in manifest file. How can I make them > consistent? I use Maven 2.0.9. > > Does anyone have me on this? thanks. -- View this message in context: http://www.nabble.com/How-to-add-snapshot-dependency-into-MANIFEST.MF-tp20171142p20655457.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to add snapshot dependency into MANIFEST.MF
My project dependent on a snapshot dependency (test-1.0-snapshot). I added this configuration in my jar-plugin: true test.ui.Starter UI DEMO All the dependencies will be written to manifest.mf file. So the final manifest.mf will includes: Class-Path: test-1.0-snapshot.jar But when I run the assembly, the version of the test-1.0 will be inconsistent with the one in manifest file. How can I make them consistent? I use Maven 2.0.9. -- View this message in context: http://www.nabble.com/How-to-add-snapshot-dependency-into-MANIFEST.MF-tp20171142p20171142.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly:assembly does not generate Main-class in MANIFEST.MF
Hello Maven gurus and users, I have a pom.xml to generate an executable jar-with-dependencies. The pom.xml creates everything expected except the MANIFEST.MF with Main-class: defined. The executable jar will work but I have to unjar the jar to a temporary directory, edit the MANIFEST.MF for the Main-class: definition and then re-jar. The element content follows along with the MANIFEST.MF it generates. Any and all ideas and suggestions welcomed. TIA and please advise, David. ** Expected MANIFEST.MF ** Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: 1.5.0_15-b04 (Sun Microsystems Inc.) Main-class: com.fds.ar.apps.util.fileupload.XSFileUploadApp.XSFileUploadApp * Generated MANIFEST.MF * Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: 1.5.0_15-b04 (Sun Microsystems Inc.) pom.xml maven-assembly-plugin jar-with-dependencies com.fds.ar.apps.util.fileupload.XSFileUploadApp.XSFileUploadApp com.fds.ar.apps.util.fileupload.XSFileUploadApp true Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last. Henry David Thoreau - Walden - 1845 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to set the JDK target used into MANIFEST.MF Build-Jdk
Hi all,
currently I am trying to set properly the JDK target used when jarring my
modules. What I have tried is:
org.apache.maven.plugins
maven-jar-plugin
false
test
${maven.compiler.compilerVersion}
${maven.compiler.target}
..
The problem seems to be that ${maven.compiler.compilerVersion} has not been
initialised yet neither the ${maven.compiler.target} expression, when it
should be set into the entry. When I open the MANIFEST.MF I see
that Build-Jdk is set to "test null".
I have read a JIRA related to this issue:
[jira] Created: (MPJAR-49) Incorrect jdk version in "Build JDK" in manifest
when maven.compile.executable is set
but it seems I can not fix it.
Could you advise me.
Thank you
Dobri
Re: classpath entries in maven-archiver generated MANIFEST.MF cannot be referenced
i tried different things and my guess is that the problems occur because the problematic module is a webapplication running in the lightweight jetty container. it seems that the jetty-classloader cannot cope with some classpath entries. all other non-webapp components i am using with the generated MANIFEST.MF are working fine. i heard already some issues about webcontainers and referencing classpaths, so i suspect the same problem with my app. - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/classpath-entries-in-maven-archiver-generated-MANIFEST.MF-cannot-be-referenced-tp17229567p17232146.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath entries in maven-archiver generated MANIFEST.MF cannot be referenced
no, i copy/pasted the Class-Path bit from my maven-jar-plugin generated MANIFEST.MF and it is a multi-liner. it follows the 72 bytes block. all lines have maximum 72 bytes length and each newline starts with a white space. maybe this seems more to be a java as a maven-jar-plugin issue. i am using jre1.6.0_02. will investigate further... [EMAIL PROTECTED] wrote: > > If this is all on one line, then that is a violation of the java > Manifest-file specification. > > See: > http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#Manifest%20Specification > > > >> * Line length: >> No line may be longer than 72 bytes (not characters), in its >> UTF8-encoded form. >> If a value would make the initial line longer than this, it should >> be continued on >> extra lines (each starting with a single SPACE). >> > - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/classpath-entries-in-maven-archiver-generated-MANIFEST.MF-cannot-be-referenced-tp17229567p17230602.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: classpath entries in maven-archiver generated MANIFEST.MF cannot be referenced
aldana schrieb: > hi, > > i got problems with the classpath entries MANIFEST.MF. some classes cannot > be found, though they exist as entry in MANIFEST.MF. weird thing is, that > some jars are included correctly (i get some basic startup, which needs some > dependency jars, but in the end all crashes). > > startup, which tells me it cannot find a certain type: > 'java -classpath .:mainJar.jar de..Main' > > startup, which gets further, but still crashes afterwards: > 'java -classpath .:mainJar.jar:../lib/myfaces-impl-1.1.5.jar de..Main' > > this tells me that not all class-path entries are included correctly. > > the weird thing is, that the generated class-path of MANIFEST.MF (see below) > looks fine. maybe there are too many entries (~80), which is causing > problems... has anybody faced similar symptoms when using maven-jar plugin > and option? > > ---Generated MANIFEST.MF CLASSPATH by maven-jar-plugin- > > Class-Path: ../lib/hibernate-commons-annotations-3.3.0.ga.jar ../lib/h > ibernate-3.2.5.ga.jar ../lib/ehcache-1.2.3.jar ../lib/commons-logging > -1.1.jar ../lib/commons-collections-3.1.jar ../lib/jta-1.0.1B.jar ../ > lib/asm-attrs-1.5.3.jar ../lib/dom4j-1.6.1.jar ../lib/antlr-2.7.6.jar > ../lib/cglib-2.1_3.jar ../lib/asm-1.5.3.jar ../lib/persistence-api-1 > .0.jar ../lib/tomahawk-1.1.5.jar ../lib/commons-validator-1.3.1.jar . > ./lib/commons-beanutils-1.7.0.jar ../lib/commons-digester-1.6.jar ../ > lib/xml-apis-1.0.b2.jar ../lib/commons-fileupload-1.0.jar ../lib/comm > ons-el-1.0.jar ../lib/commons-codec-1.3.jar ../lib/oro-2.0.8.jar ../l > ib/commons-lang-2.1.jar ../lib/jstl-1.1.0.jar ../lib/log4j-1.2.12.jar > ../lib/castor-0.9.5.4.jar ../lib/openjms-0.7.7.jar ../lib/openjms-co > mmon-0.7.7.jar ../lib/hibernate-annotations-3.3.0.ga.jar ../lib/myfac > es-api-1.1.5.jar ../lib/spring-2.0.6.jar ../lib/logkit-1.0.1.jar ../l > ib/avalon-framework-4.1.3.jar ../lib/common-konnektor-1.1-SNAPSHOT.ja > r ../lib/managementPersistence-1.0-SNAPSHOT.jar ../lib/commons-dbcp-1 > .2.1.jar ../lib/commons-pool-1.2.jar ../lib/hsqldb-1.8.0.7.jar ../lib > /baseUtilities-1.1-SNAPSHOT.jar ../lib/jaxb-api-2.1.jar ../lib/stax-a > pi-1.0-2.jar ../lib/activation-1.1.jar ../lib/jaxb-impl-2.1.jar ../li > b/xml-sec-1.3.jar ../lib/bcprov-1.35.jar ../lib/saaj-impl-1.3.jar ../ > lib/saaj-api-1.3.jar ../lib/xsom-1.0.1.jar ../lib/relaxngDatatype-200 > 20414.jar ../lib/xalan-2.7.0.jar ../lib/jcalendar-1.3.2.jar ../lib/co > mmons-httpclient-3.0.jar ../lib/common-gematik-1.1-SNAPSHOT.jar ../li > b/jaxws-rt-2.1.3.jar ../lib/axiom-api-1.2.2.jar ../lib/mail-1.4.jar . > ./lib/jaxen-1.1-beta-9.jar ../lib/xercesImpl-2.0.2.jar ../lib/stax-ap > i-1.0.1.jar ../lib/release-2.2.1-1.0-SNAPSHOT.jar ../lib/axiom-impl-1 > .2.2.jar ../lib/axis2-adb-1.1.1.jar ../lib/axis2-kernel-1.1.1.jar ../ > lib/wsdl4j-1.6.1.jar ../lib/jms-1.1.jar ../lib/openjms-net-0.7.7.jar > ../lib/jsp-2.1-6.1.7.jar ../lib/core-3.1.1.jar ../lib/jsp-api-2.1-6.1 > .7.jar ../lib/servlet-api-2.5-6.1.7.jar ../lib/ant-1.6.5.jar ../lib/m > yfaces-impl-1.1.5.jar ../lib/concurrent-1.3.4.jar ../lib/jetty-plus-6 > .1.7.jar ../lib/geronimo-spec-jta-1.0.1B-rc4.jar ../lib/jetty-6.1.7.j > ar ../lib/jetty-util-6.1.7.jar ../lib/spice-jndikit-1.2.jar ../lib/In > tegrityManager-1.0.0-SNAPSHOT.jar > > If this is all on one line, then that is a violation of the java Manifest-file specification. See: http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#Manifest%20Specification * Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
classpath entries in maven-archiver generated MANIFEST.MF cannot be referenced
hi, i got problems with the classpath entries MANIFEST.MF. some classes cannot be found, though they exist as entry in MANIFEST.MF. weird thing is, that some jars are included correctly (i get some basic startup, which needs some dependency jars, but in the end all crashes). startup, which tells me it cannot find a certain type: 'java -classpath .:mainJar.jar de..Main' startup, which gets further, but still crashes afterwards: 'java -classpath .:mainJar.jar:../lib/myfaces-impl-1.1.5.jar de..Main' this tells me that not all class-path entries are included correctly. the weird thing is, that the generated class-path of MANIFEST.MF (see below) looks fine. maybe there are too many entries (~80), which is causing problems... has anybody faced similar symptoms when using maven-jar plugin and option? ---Generated MANIFEST.MF CLASSPATH by maven-jar-plugin- Class-Path: ../lib/hibernate-commons-annotations-3.3.0.ga.jar ../lib/h ibernate-3.2.5.ga.jar ../lib/ehcache-1.2.3.jar ../lib/commons-logging -1.1.jar ../lib/commons-collections-3.1.jar ../lib/jta-1.0.1B.jar ../ lib/asm-attrs-1.5.3.jar ../lib/dom4j-1.6.1.jar ../lib/antlr-2.7.6.jar ../lib/cglib-2.1_3.jar ../lib/asm-1.5.3.jar ../lib/persistence-api-1 .0.jar ../lib/tomahawk-1.1.5.jar ../lib/commons-validator-1.3.1.jar . ./lib/commons-beanutils-1.7.0.jar ../lib/commons-digester-1.6.jar ../ lib/xml-apis-1.0.b2.jar ../lib/commons-fileupload-1.0.jar ../lib/comm ons-el-1.0.jar ../lib/commons-codec-1.3.jar ../lib/oro-2.0.8.jar ../l ib/commons-lang-2.1.jar ../lib/jstl-1.1.0.jar ../lib/log4j-1.2.12.jar ../lib/castor-0.9.5.4.jar ../lib/openjms-0.7.7.jar ../lib/openjms-co mmon-0.7.7.jar ../lib/hibernate-annotations-3.3.0.ga.jar ../lib/myfac es-api-1.1.5.jar ../lib/spring-2.0.6.jar ../lib/logkit-1.0.1.jar ../l ib/avalon-framework-4.1.3.jar ../lib/common-konnektor-1.1-SNAPSHOT.ja r ../lib/managementPersistence-1.0-SNAPSHOT.jar ../lib/commons-dbcp-1 .2.1.jar ../lib/commons-pool-1.2.jar ../lib/hsqldb-1.8.0.7.jar ../lib /baseUtilities-1.1-SNAPSHOT.jar ../lib/jaxb-api-2.1.jar ../lib/stax-a pi-1.0-2.jar ../lib/activation-1.1.jar ../lib/jaxb-impl-2.1.jar ../li b/xml-sec-1.3.jar ../lib/bcprov-1.35.jar ../lib/saaj-impl-1.3.jar ../ lib/saaj-api-1.3.jar ../lib/xsom-1.0.1.jar ../lib/relaxngDatatype-200 20414.jar ../lib/xalan-2.7.0.jar ../lib/jcalendar-1.3.2.jar ../lib/co mmons-httpclient-3.0.jar ../lib/common-gematik-1.1-SNAPSHOT.jar ../li b/jaxws-rt-2.1.3.jar ../lib/axiom-api-1.2.2.jar ../lib/mail-1.4.jar . ./lib/jaxen-1.1-beta-9.jar ../lib/xercesImpl-2.0.2.jar ../lib/stax-ap i-1.0.1.jar ../lib/release-2.2.1-1.0-SNAPSHOT.jar ../lib/axiom-impl-1 .2.2.jar ../lib/axis2-adb-1.1.1.jar ../lib/axis2-kernel-1.1.1.jar ../ lib/wsdl4j-1.6.1.jar ../lib/jms-1.1.jar ../lib/openjms-net-0.7.7.jar ../lib/jsp-2.1-6.1.7.jar ../lib/core-3.1.1.jar ../lib/jsp-api-2.1-6.1 .7.jar ../lib/servlet-api-2.5-6.1.7.jar ../lib/ant-1.6.5.jar ../lib/m yfaces-impl-1.1.5.jar ../lib/concurrent-1.3.4.jar ../lib/jetty-plus-6 .1.7.jar ../lib/geronimo-spec-jta-1.0.1B-rc4.jar ../lib/jetty-6.1.7.j ar ../lib/jetty-util-6.1.7.jar ../lib/spice-jndikit-1.2.jar ../lib/In tegrityManager-1.0.0-SNAPSHOT.jar - manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/classpath-entries-in-maven-archiver-generated-MANIFEST.MF-cannot-be-referenced-tp17229567p17229567.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manifest.mf maven2
On Wed, Apr 9, 2008 at 9:25 PM, Urooj Khan <[EMAIL PROTECTED]> wrote: > now i cant figure out how maven2 is generating this manifest.mf file so that > i can fiddle with it and try to get the right output Start here: http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html (... and if necessary, follow the link to the Archiver Reference.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
manifest.mf maven2
hi everyone... i am in the process of converting a project from maven 1 to maven 2. i have a three projects within one big project.. i figured just mvn one:convert on each project.xml would do the trick.. but its actually an extremely huge task.. so i'm starting bottom up and i've been able to complete one of the sub-modules to convert to maven2. now the problem i'm having is because of the manifest.mf file... when i compare the war files generated by maven 1 and maven 2.. the only difference i see is the manifest.mf file... now i cant figure out how maven2 is generating this manifest.mf file so that i can fiddle with it and try to get the right output thanks in advance! -- Urooj Khan
Re: Config MANIFEST.MF
Hi, You can have a look here http://maven.apache.org/shared/maven-archiver/index.html and here http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html. Maven Archiver is used to generate the MANIFEST.MF file. -- Olivier 2008/1/22, Arthur Rodrigues Stilben <[EMAIL PROTECTED]>: > How can I configure the MANIFEST.MF in the Maven ? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Config MANIFEST.MF
How can I configure the MANIFEST.MF in the Maven ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with MANIFEST.MF in maven-jar-plugin
Hi, guys! I have not known the rule of 72 character in Manifest file. My application was using more than 72 character in Manifest file. When I saw the file created by maven, I thought that will not work out I tested and work out with breaklines. Sorry and thanks for your help! Helio Wayne Fay escreveu: What do you mean "my jar does not work out"? How does it break? Please review the JAR spec -- I am reasonably certain the Maven-produced manifest.mf is correct: http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). Wayne On 11/27/07, helio <[EMAIL PROTECTED]> wrote: Hi, I am using maven-jar-plugin on maven 2.0.7. I added this in my pom.xml: org.apache.maven.plugins maven-jar-plugin src/main/resources/META-INF/MANIFEST.MF In src/main/resources/META-INF/MANIFEST.MF I have: Manifest-Version: 1.0 Class-Path: activation.jar commons-logging.jar getopt.jar javassist.jar jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jboss-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-client.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar Main-Class: com.Claudio But when I run mvn clean package, into jar´s MANIFEST.MF I got: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: claudior Build-Jdk: 1.5.0_06 Main-Class: com.Claudio Class-Path: activation.jar commons-logging.jar getopt.jar javassist.ja r jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jbos s-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-cl ient.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar The plugin maven-jar-plugin adds breaklines in Class-Path and my jar does not work out!!! Please, help me. Helio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- * Helio Marci de Oliveira * Departamento de Tecnologia [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> tel: + 55 11 3848 8700 ramal:8780 skype: helio.marci <http://www.buscape.com> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with MANIFEST.MF in maven-jar-plugin
On 28/11/2007, Wayne Fay <[EMAIL PROTECTED]> wrote: > > What do you mean "my jar does not work out"? How does it break? > > Please review the JAR spec -- I am reasonably certain the > Maven-produced manifest.mf is correct: > > http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files > > Line length: > No line may be longer than 72 bytes (not characters), in its > UTF8-encoded form. If a value would make the initial line longer than > this, it should be continued on extra lines (each starting with a > single SPACE). that's correct - you'll see the same effect when using plain old jar: jar cfm foo.jar src/main/resources/META-INF/MANIFEST.MF jar xf foo.jar and META-INF/MANIFEST.MF will be formatted with the 72 char limit as Wayne said, could you explain more about "does not work out"? do you see any exceptions / errors when using your jar? are those jarfiles listed in Class-Path, in the same directory as your jar. note Class-Path does not allow you to refer to embedded jars, see: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4648386 for the (long-running!) saga... Wayne > > On 11/27/07, helio <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am using maven-jar-plugin on maven 2.0.7. > > I added this in my pom.xml: > > > > > > > > > > org.apache.maven.plugins > > maven-jar-plugin > > > > > > > > src/main/resources/META-INF/MANIFEST.MF > > > > > > > > > > > > > > In src/main/resources/META-INF/MANIFEST.MF I have: > > > > Manifest-Version: 1.0 > > Class-Path: activation.jar commons-logging.jar getopt.jar javassist.jar > > jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar > > jboss-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar > > jbossws-client.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar > > log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar > > stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar > > Main-Class: com.Claudio > > > > But when I run mvn clean package, into jar´s MANIFEST.MF I got: > > > > Manifest-Version: 1.0 > > Archiver-Version: Plexus Archiver > > Created-By: Apache Maven > > Built-By: claudior > > Build-Jdk: 1.5.0_06 > > Main-Class: com.Claudio > > Class-Path: activation.jar commons-logging.jar getopt.jar javassist.ja > > r jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jbos > > s-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-cl > > ient.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar > > mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar > > wsdl4j.jar wstx.jar xercesImpl.jar > > > > The plugin maven-jar-plugin adds breaklines in Class-Path and my jar > > does not work out!!! > > > > Please, help me. > > > > Helio > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
Re: Problem with MANIFEST.MF in maven-jar-plugin
What do you mean "my jar does not work out"? How does it break? Please review the JAR spec -- I am reasonably certain the Maven-produced manifest.mf is correct: http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). Wayne On 11/27/07, helio <[EMAIL PROTECTED]> wrote: > Hi, > > I am using maven-jar-plugin on maven 2.0.7. > I added this in my pom.xml: > > > > > org.apache.maven.plugins > maven-jar-plugin > > > > src/main/resources/META-INF/MANIFEST.MF > > > > > > > In src/main/resources/META-INF/MANIFEST.MF I have: > > Manifest-Version: 1.0 > Class-Path: activation.jar commons-logging.jar getopt.jar javassist.jar > jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar > jboss-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar > jbossws-client.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar > log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar > stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar > Main-Class: com.Claudio > > But when I run mvn clean package, into jar´s MANIFEST.MF I got: > > Manifest-Version: 1.0 > Archiver-Version: Plexus Archiver > Created-By: Apache Maven > Built-By: claudior > Build-Jdk: 1.5.0_06 > Main-Class: com.Claudio > Class-Path: activation.jar commons-logging.jar getopt.jar javassist.ja > r jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jbos > s-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-cl > ient.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar > mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar > wsdl4j.jar wstx.jar xercesImpl.jar > > The plugin maven-jar-plugin adds breaklines in Class-Path and my jar > does not work out!!! > > Please, help me. > > Helio > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with MANIFEST.MF in maven-jar-plugin
Hi, I am using maven-jar-plugin on maven 2.0.7. I added this in my pom.xml: org.apache.maven.plugins maven-jar-plugin src/main/resources/META-INF/MANIFEST.MF In src/main/resources/META-INF/MANIFEST.MF I have: Manifest-Version: 1.0 Class-Path: activation.jar commons-logging.jar getopt.jar javassist.jar jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jboss-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-client.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar Main-Class: com.Claudio But when I run mvn clean package, into jar´s MANIFEST.MF I got: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: claudior Build-Jdk: 1.5.0_06 Main-Class: com.Claudio Class-Path: activation.jar commons-logging.jar getopt.jar javassist.ja r jaxb-api.jar jaxb-impl.jar jbossall-client.jar jboss-ejb3x.jar jbos s-j2ee.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar jbossws-cl ient.jar jbossws-spi.jar jboss-xml-binding.jar jtds-1.2.jar log4j.jar mail.jar mysql-connector-java-3.1.12-bin.jar policy.jar stax-api.jar wsdl4j.jar wstx.jar xercesImpl.jar The plugin maven-jar-plugin adds breaklines in Class-Path and my jar does not work out!!! Please, help me. Helio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: carriage return in the generated MANIFEST.MF file
On 13/11/2007, Kevin Du <[EMAIL PROTECTED]> wrote: > > Hi, > > Sorry if this is a duplicate message. I send this out before > subscribe. Just want to make sure that it can actually be send out after > subscribe. > > I am using my own manifest file by following > > > ... > > > > org.apache.maven.plugins > maven-jar-plugin > ... > > > > > src/main/resources/META-INF/MANIFEST.MF > > > ... > > > > ... > > > I specified my class path in my manifest.mf file in the format of > Class-Path: dir/xxx.jar dir/yyy.jar > > After mvn install, when I do java -jar myApp.jar it complains > 'NoClassFound' for the class I specified in the class path. It took me an > hour to find out the the MANIFEST.MF file in the generated jar has > carriage returns in it. > > The generated manifest.mf file looks like > > Class-Path: /home/xxx/.m2/repository/com/xxx/xxx/mod > el/1.0-SNAPSHOT/ model-1.0-SNAPSHOT.jar > > I guess that is why it complains NoClassFound, anybody any idea? no - manifests that have long lines will normally have carriage returns, with the continuing line marked with an initial space - see the line length description for the Jar manifest file: http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#JAR%20Manifest "No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE)." so this is actually valid - your problem seems to be that you're using an absolute path: /home/... whereas the Class-Path entry expects relative paths - again from the same Jar page: "The value of this attribute specifies the relative URLs of the extensions or libraries that this application or extension needs. URLs are separated by one or more spaces. The application or extension class loader uses the value of this attribute to construct its internal search path. so you should ensure that your classpath entries are relative to the location of the Jar. Thanks > > Kevin > > > > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ -- Cheers, Stuart
carriage return in the generated MANIFEST.MF file
Hi, I am using my own manifest file by following ... org.apache.maven.plugins maven-jar-plugin ... src/main/resources/META-INF/MANIFEST.MF ... ... I specified my class path in my manifest.mf file in the format of Class-Path: dir/xxx.jar dir/yyy.jar After mvn install, when I do java -jar myApp.jar it complains 'NoClassFound' for the class I specified in the class path. It took me an hour to find out the the MANIFEST.MF file in the generated jar has carriage returns in it. The generated manifest.mf file looks like Class-Path: /home/xxx/.m2/repository/com/xxx/xxx/mod el/1.0-SNAPSHOT/ model-1.0-SNAPSHOT.jar I guess that is why it complains NoClassFound, anybody any idea? Thanks Kevin __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
carriage return in the generated MANIFEST.MF file
Hi, Sorry if this is a duplicate message. I send this out before subscribe. Just want to make sure that it can actually be send out after subscribe. I am using my own manifest file by following ... org.apache.maven.plugins maven-jar-plugin ... src/main/resources/META-INF/MANIFEST.MF ... ... I specified my class path in my manifest.mf file in the format of Class-Path: dir/xxx.jar dir/yyy.jar After mvn install, when I do java -jar myApp.jar it complains 'NoClassFound' for the class I specified in the class path. It took me an hour to find out the the MANIFEST.MF file in the generated jar has carriage returns in it. The generated manifest.mf file looks like Class-Path: /home/xxx/.m2/repository/com/xxx/xxx/mod el/1.0-SNAPSHOT/ model-1.0-SNAPSHOT.jar I guess that is why it complains NoClassFound, anybody any idea? Thanks Kevin __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
[M2] how to generate manifest.mf file
Hello, In a mojo, I would like to generate the manifest.mf file as we can find it in the result jar (with the Class-Path entry). I tried to play with the MavenProject component but without success. Thanks Yann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: how to give change the path for jars in "manifest.mf " file in ejb.project
Hi Kiran, How about the following: true lib/ Regards, Misl - The Unguided One --- Today's code, is tomorrow's legacy --- -Oorspronkelijk bericht- Van: Kiran Kodlady [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 15 juni 2007 15:29 Aan: users@maven.apache.org Onderwerp: how to give change the path for jars in "manifest.mf " file in ejb.project Hello, when i add in pom.xml of ejb project, all the dependecy jars are listed in manifest.mf file as it is without any path. My question here is , is there any way to give customized path for all the jars in manifest.mf. For example can i get entry for a xyz.jar in manifest.mf file as "lib/xyz.jar". Thanks a lot in advance.. Kiran Kodlady. -- View this message in context: http://www.nabble.com/how-to-give-change-the-path-for-jars-in-%22manifes t.mf-%22-file-in-ejb.project-tf3927894s177.html#a11139534 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] DISCLAIMER De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken aan andere personen dan de geadresseerde. Indien u deze e-mail abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af voor en/of in verband met alle gevolgen en/of schade van een onjuiste of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het gebruik van Internet e-mail brengt zekere risico's met zich. Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium door de Politie Amsterdam-Amstelland van de hand gewezen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to give change the path for jars in "manifest.mf " file in ejb.project
Hello, when i add in pom.xml of ejb project, all the dependecy jars are listed in manifest.mf file as it is without any path. My question here is , is there any way to give customized path for all the jars in manifest.mf. For example can i get entry for a xyz.jar in manifest.mf file as "lib/xyz.jar". Thanks a lot in advance.. Kiran Kodlady. -- View this message in context: http://www.nabble.com/how-to-give-change-the-path-for-jars-in-%22manifest.mf-%22-file-in-ejb.project-tf3927894s177.html#a11139534 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin wraps manifest.mf line at wrong position
Hi Zhang, All MANIFEST.MF files that contain lines longer than 72 bytes are invalid, according to the Jar Manifest specification. That's why the plugin splits them, which is the only way to create a valid manifest. And no, AFAIK, you can not force the plugin to create invalid manifest files. Here is the specification extract: - Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). You can find the spec here: http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Notes on Manifest and Signature Files Cheers Jo On 6/8/07, 張旭 <[EMAIL PROTECTED]> wrote: Dear friends, I have encountered a strange problem when specify custom manifest file when using the maven-jar-plugin. I've a very very long line in the manifest file that maybe have hundreds columns. It seems that the plug-in will automatically wrap the line every 70 cols. Is there a parameter in configuration that can override the default behavior? Thanks in advance.
Re: maven-jar-plugin wraps manifest.mf line at wrong position
On Fri, 2007-06-08 at 16:21 +0800, 張旭 wrote: > Dear friends, > I have encountered a strange problem when specify custom manifest file when > using the maven-jar-plugin. > I've a very very long line in the manifest file that maybe have hundreds > columns. > It seems that the plug-in will automatically wrap the line every 70 cols. > Is there a parameter in configuration that can override the default > behavior? The plugin does the right thing and you really don't want to override that. From the Jar specification: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-jar-plugin wraps manifest.mf line at wrong position
Dear friends, I have encountered a strange problem when specify custom manifest file when using the maven-jar-plugin. I've a very very long line in the manifest file that maybe have hundreds columns. It seems that the plug-in will automatically wrap the line every 70 cols. Is there a parameter in configuration that can override the default behavior? Thanks in advance.
Re: Generating Class-Path: Entry in /META-INF/Manifest.mf for an EJB
This is documented on the plugin's website: http://maven.apache.org/plugins/maven-ejb-plugin/faq.html Wayne On 6/6/07, Artur Wystub <[EMAIL PROTECTED]> wrote: Hi NG, is there a way to let maven generate the Class-Path: Entry in /META-INF/Manifest.mf for an EJB? I have a multi-module project with an ear and an ejb as subprojects and have to put all the names of jars referenced by the ejb manually in the Manifest.mf in META-INF of the ejb. Is there a better way to do that? Thanks in advance Artur - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating Class-Path: Entry in /META-INF/Manifest.mf for an EJB
Hi NG, is there a way to let maven generate the Class-Path: Entry in /META-INF/Manifest.mf for an EJB? I have a multi-module project with an ear and an ejb as subprojects and have to put all the names of jars referenced by the ejb manually in the Manifest.mf in META-INF of the ejb. Is there a better way to do that? Thanks in advance Artur - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: generating pom.xml from MANIFEST.MF?
I'm not aware of any plugin or process that exists which would generate the pom.xml file from the MANIFEST.MF. You'll have to make them by hand, or create a tool. Wayne On 6/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hello, I have to add some not mavenized external projects as jars to my repository. This external projects are currently in developing-status and can not be mavenized. They all have an existing MANIFEST.MF where bundle-dependencies are defined. Is there a way to automatically create a pom.xml for these projects, which I can use to deploy them to the repository? I want this to use the projects for my own project builded with maven2 ant dependencies declared in my pom.xml. regards, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
generating pom.xml from MANIFEST.MF?
Hello, I have to add some not mavenized external projects as jars to my repository. This external projects are currently in developing-status and can not be mavenized. They all have an existing MANIFEST.MF where bundle-dependencies are defined. Is there a way to automatically create a pom.xml for these projects, which I can use to deploy them to the repository? I want this to use the projects for my own project builded with maven2 ant dependencies declared in my pom.xml. regards, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
