Re: Manifest classpath entry
As far as I am aware, no. You will need to install/deploy all of your Weblogic jars and use the Maven method to build up your classpath. Wayne On 1/23/08, robcon <[EMAIL PROTECTED]> wrote: > > Wayne, > > You are correct in what you are saying and I need to re-word my question. > > The Jars I actually need for the build are referenced by the classpath > structure within the weblogic.jar and so when I perform a build in eclipse > it finds these jar using the classpath hierarchy. > > Is there anyway to get Maven to utilise the classpath hierarchy within the > weblogic.jar rather than having to determine the actual jar(s) that are > required for the build (given that using this classpath requires the > weblogic.jar to be in the weblogic folder structure) ? > > Regards, > > Robert > > > > Wayne Fay wrote: > > > > What makes you think that Maven is "trying to reference some of the > > jars... but is unable to find them"? Do you have something interesting > > from mvn -X to show or just a general feeling in your gut about what > > it is doing? > > > > As far as I know (and I reserve the right to be proven wrong), Maven > > definitely does not look at the Manifest.MF files in Jars in your repo > > and then monkey around with dependencies etc. It only looks at the > > dependencies declared in the various pom.xml files. > > > > Wayne > > > > On 1/23/08, robcon <[EMAIL PROTECTED]> wrote: > >> > >> In our Maven POM we have a dependancy on a jar (Weblogic.jar) which has > >> many > >> Jars listed in the classpath Entry in its Manifest.MF file. > >> > >> When doing a Maven install maven appears to be trying to reference some > >> of > >> the jars in the classpath but is unable to find them because the > >> weblogic.jar is in the Maven repository folder and the jars referenced in > >> the classpath are in the bea-weblogic folder. Resolving the classpath > >> jars > >> appears to rely on all of the jars living in the standard weblogic folder > >> structure. > >> > >> This must be a common problem. How do I get around this ? > >> -- > >> View this message in context: > >> http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15039656.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] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15054435.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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manifest classpath entry
Wayne, You are correct in what you are saying and I need to re-word my question. The Jars I actually need for the build are referenced by the classpath structure within the weblogic.jar and so when I perform a build in eclipse it finds these jar using the classpath hierarchy. Is there anyway to get Maven to utilise the classpath hierarchy within the weblogic.jar rather than having to determine the actual jar(s) that are required for the build (given that using this classpath requires the weblogic.jar to be in the weblogic folder structure) ? Regards, Robert Wayne Fay wrote: > > What makes you think that Maven is "trying to reference some of the > jars... but is unable to find them"? Do you have something interesting > from mvn -X to show or just a general feeling in your gut about what > it is doing? > > As far as I know (and I reserve the right to be proven wrong), Maven > definitely does not look at the Manifest.MF files in Jars in your repo > and then monkey around with dependencies etc. It only looks at the > dependencies declared in the various pom.xml files. > > Wayne > > On 1/23/08, robcon <[EMAIL PROTECTED]> wrote: >> >> In our Maven POM we have a dependancy on a jar (Weblogic.jar) which has >> many >> Jars listed in the classpath Entry in its Manifest.MF file. >> >> When doing a Maven install maven appears to be trying to reference some >> of >> the jars in the classpath but is unable to find them because the >> weblogic.jar is in the Maven repository folder and the jars referenced in >> the classpath are in the bea-weblogic folder. Resolving the classpath >> jars >> appears to rely on all of the jars living in the standard weblogic folder >> structure. >> >> This must be a common problem. How do I get around this ? >> -- >> View this message in context: >> http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15039656.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] >> >> > > ----- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15054435.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 classpath entry
What makes you think that Maven is "trying to reference some of the jars... but is unable to find them"? Do you have something interesting from mvn -X to show or just a general feeling in your gut about what it is doing? As far as I know (and I reserve the right to be proven wrong), Maven definitely does not look at the Manifest.MF files in Jars in your repo and then monkey around with dependencies etc. It only looks at the dependencies declared in the various pom.xml files. Wayne On 1/23/08, robcon <[EMAIL PROTECTED]> wrote: > > In our Maven POM we have a dependancy on a jar (Weblogic.jar) which has many > Jars listed in the classpath Entry in its Manifest.MF file. > > When doing a Maven install maven appears to be trying to reference some of > the jars in the classpath but is unable to find them because the > weblogic.jar is in the Maven repository folder and the jars referenced in > the classpath are in the bea-weblogic folder. Resolving the classpath jars > appears to rely on all of the jars living in the standard weblogic folder > structure. > > This must be a common problem. How do I get around this ? > -- > View this message in context: > http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15039656.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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manifest classpath entry
In our Maven POM we have a dependancy on a jar (Weblogic.jar) which has many Jars listed in the classpath Entry in its Manifest.MF file. When doing a Maven install maven appears to be trying to reference some of the jars in the classpath but is unable to find them because the weblogic.jar is in the Maven repository folder and the jars referenced in the classpath are in the bea-weblogic folder. Resolving the classpath jars appears to rely on all of the jars living in the standard weblogic folder structure. This must be a common problem. How do I get around this ? -- View this message in context: http://www.nabble.com/Manifest-classpath-entry-tp15039656s177p15039656.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 classpath
The former, and thanks for the link. I'll bring the issue there (if it hasn't been raised already). Robert Egan "Wayne Fay" <[EMAIL PROTECTED]> 16-Aug-2007 11:27 AM Please respond to "Maven Users List" To "Maven Users List" cc Subject Re: manifest classpath Are you asking about a Maven2 pom configuration entry, or the actual Class-Path line in your MANIFEST.MF file generated by Maven? If you're asking about Maven, please file a RFE in JIRA and someone will take a look at your issue. I'd suggest filing under MJAR: http://jira.codehaus.org/browse/MJAR If you're asking about the MANIFEST.MF file itself, you are welcome to take this up with Sun and/or the JCP. Until then, the Jar specification requires that we continue to use the current formatting of the classpath: http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html Wayne On 8/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I've looked through the examples for this and it seems simple enough. > However, I'd really like to have my classpath as a series of path elements > for the sake of legibility and future maintnance, i.e. > > >path1 >path2 >path3 > > > instead of > > >path1 path2 path3 > > > It may not seem like much in the simple example given here, but here's a > class path from one of our production jars: > > Class-Path: plugins/framework plugins/checkservices plugins/transferse > rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap > ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar > securityUtil.jar wcmCache-hotfix.jar wcmCache.jar lib/apache/jakart > a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll > ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib > /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo > ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1. > 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu > /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu > s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec- > 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp > ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc- > 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1. > 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar > lib/apache/log4j/log4j-1.2.8.jar > > So I'm sure you can see why I'd like the former approach. Any ideas would > be welcome. > > > Thanks > Robert Egan > > This email message and any attachments may contain confidential, > proprietary or non-public information. The information is intended solely > for the designated recipient(s). If an addressing or transmission error > has misdirected this email, please notify the sender immediately and > destroy this email. Any review, dissemination, use or reliance upon this > information by unintended recipients is prohibited. Any opinions > expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: manifest classpath
Are you asking about a Maven2 pom configuration entry, or the actual Class-Path line in your MANIFEST.MF file generated by Maven? If you're asking about Maven, please file a RFE in JIRA and someone will take a look at your issue. I'd suggest filing under MJAR: http://jira.codehaus.org/browse/MJAR If you're asking about the MANIFEST.MF file itself, you are welcome to take this up with Sun and/or the JCP. Until then, the Jar specification requires that we continue to use the current formatting of the classpath: http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html Wayne On 8/16/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I've looked through the examples for this and it seems simple enough. > However, I'd really like to have my classpath as a series of path elements > for the sake of legibility and future maintnance, i.e. > > >path1 >path2 >path3 > > > instead of > > >path1 path2 path3 > > > It may not seem like much in the simple example given here, but here's a > class path from one of our production jars: > > Class-Path: plugins/framework plugins/checkservices plugins/transferse > rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap > ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar > securityUtil.jar wcmCache-hotfix.jar wcmCache.jar lib/apache/jakart > a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll > ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib > /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo > ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1. > 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu > /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu > s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec- > 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp > ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc- > 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1. > 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar > lib/apache/log4j/log4j-1.2.8.jar > > So I'm sure you can see why I'd like the former approach. Any ideas would > be welcome. > > > Thanks > Robert Egan > > This email message and any attachments may contain confidential, > proprietary or non-public information. The information is intended solely > for the designated recipient(s). If an addressing or transmission error > has misdirected this email, please notify the sender immediately and > destroy this email. Any review, dissemination, use or reliance upon this > information by unintended recipients is prohibited. Any opinions > expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
manifest classpath
I've looked through the examples for this and it seems simple enough. However, I'd really like to have my classpath as a series of path elements for the sake of legibility and future maintnance, i.e. path1 path2 path3 instead of path1 path2 path3 It may not seem like much in the simple example given here, but here's a class path from one of our production jars: Class-Path: plugins/framework plugins/checkservices plugins/transferse rvices plugins/alerts plugins/pr plugins/pr/achapps plugins/pr/wireap ps wcmPrincipals-hotfix.jar wcmPrincipals.jar securityUtil-hotfix.jar securityUtil.jar wcmCache-hotfix.jar wcmCache.jar lib/apache/jakart a-commons/commons-cli-1.0.jar lib/apache/jakarta-commons/commons-coll ections-3.1.jar lib/apache/jakarta-commons/commons-dbcp-1.2.1.jar lib /apache/jakarta-commons/commons-lang-2.1.jar lib/apache/jakarta-commo ns/commons-pool-1.2.jar lib/apache/jakarta-commons/commons-logging-1. 0.4/commons-logging.jar lib/apache/JCS/jcs-1.2.6.8.jar lib/oswego.edu /util-concurrent-1.3.4.jar lib/jradius/jradius.jar lib/jradius/jradiu s-dictionary.jar lib/gnu/gnu-crypto.jar lib/httpclient/commons-codec- 1.3.jar lib/httpclient/commons-httpclient-3.0.jar lib/emory.edu/backp ort-util-concurrent-2.2/backport-util-concurrent.jar lib/oracle/jdbc- 10.2.0.1.0/ojdbc14.jar lib/oracle/jdbc-10.2.0.1.0/jdbc_rowset_tiger1. 0.1mrel-ri/rowset.jar lib/jdom/jdom-1.0/jdom.jar lib/rsa/authapi.jar lib/apache/log4j/log4j-1.2.8.jar So I'm sure you can see why I'd like the former approach. Any ideas would be welcome. Thanks Robert Egan This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Problems with manifest classpath
Hi,
I am having a problem where a dependent jar(the jar is called nlsorm
and is in the ipeservice jar) is being added to the manifest classpath
of one ejb(the mdb in this case) and not the other...the ejb in this
case: I am a bit puzzled as I have the ejb plugin configured the same
way in both.. I have enclosed the pom for ipeservice, the two ejbs
and the pom for the ear:
The ipeservice jar with nlsorm:
4.0.0
com.nls.ca.ast
1.0-SNAPSHOT
ipe
ipeservice
IPE Util Jar
com.nls.zion.comp
processlogging
utilities
utilities
com.nls.ca.ast
nlsorm
${version}
com.nls.ca.ast
prfservice
${version}
src
srcTest
../IpeResources/common
../IpeResources/test
../../../Resources/common
../../../Resources/test
---
The mdb ejb:
4.0.0
com.nls.ca.ast
1.0-SNAPSHOT
ipe
ipe-mdb
IPE MDB
ejb
com.nls.zion.comp
processlogging
utilities
utilities
${groupId}
ipeservice
${version}
compile
src
srcTest
Resources
org.apache.maven.plugins
maven-ejb-plugin
false
true
development
whatever
---
The ejb:
4.0.0
com.nls.ca.ast
1.0-SNAPSHOT
ipe
ipe-ejb
IPE EJB
ejb
com.nls.zion.comp
processlogging
utilities
utilities
${groupId}
ipeservice
${version}
compile
src
srcTest
Resources
org.apache.maven.plugins
maven-ejb-plugin
false
true
development
whatever
Re: WARs: Including a dependency in WEB-INF/lib but not in the manifest classpath
What manifest classpath are you referring to? The war plugin does not add a classpath to the manifest - it only adds dependencies to WEB-INF/lib. It's the jar plugin that will add classpaths to manifests. Then the ear plugin will copy any jars in the manifest classpaths of each of its modules into the ear. If you don't want a dep to get added to the manifest classpath, for jars, or to WEB-INF, for wars, set its scope to provided. Please be more specific about exactly what you want you end product to look like (i.e. the ear and its contents). Ryan Nelson wrote: Hello everyone, I'm trying to build an EAR with multiple "skinny" WARs that look to the EAR for their common libraries. The maven-war-plugin site has some good examples on how to do this, but there is one use case that I need, that apparently is not supported. The manifest guide says: "Note that no way is shown to include a dependency in WEB-INF/lib but not the manifest classpath." I don't know when this example was last updated, but does anyone know if this has been changed? Or if there is an easy way around it, short of modifying the plugin code myself? I'm using the latest snapshot (2.0.3-SNAPSHOT). Thanks, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WARs: Including a dependency in WEB-INF/lib but not in the manifest classpath
Hello everyone, I'm trying to build an EAR with multiple "skinny" WARs that look to the EAR for their common libraries. The maven-war-plugin site has some good examples on how to do this, but there is one use case that I need, that apparently is not supported. The manifest guide says: "Note that no way is shown to include a dependency in WEB-INF/lib but not the manifest classpath." I don't know when this example was last updated, but does anyone know if this has been changed? Or if there is an easy way around it, short of modifying the plugin code myself? I'm using the latest snapshot (2.0.3-SNAPSHOT). Thanks, Ryan
WARs: Including a dependency in WEB-INF/lib but not in the manifest classpath
Hello everyone, I'm trying to build an EAR with multiple "skinny" WARs that look to the EAR for their common libraries. The maven-war-plugin site has some good examples on how to do this, but there is one use case that I need, that apparently is not supported. The manifest guide says: "Note that no way is shown to include a dependency in WEB-INF/lib but not the manifest classpath." I don't know when this example was last updated, but does anyone know if this has been changed? Or if there is an easy way around it, short of modifying the plugin code myself? I'm using the latest snapshot (2.0.3-SNAPSHOT). Thanks, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WARs: Including a dependency in WEB-INF/lib but not in the manifest classpath
Hello everyone, I'm trying to build an EAR with multiple "skinny" WARs that look to the EAR for their common libraries. The maven-war-plugin site has some good examples on how to do this, but there is one use case that I need, that apparently is not supported. The manifest guide says: "Note that no way is shown to include a dependency in WEB-INF/lib but not the manifest classpath." I don't know when this example was last updated, but does anyone know if this has been changed? Or if there is an easy way around it, short of modifying the plugin code myself? I'm using the latest snapshot (2.0.3-SNAPSHOT). Thanks, Ryan
Add Maven ear properties file to war manifest classpath
I am trying to add an additional classpath element to the manifest created by the war plugin. Is it possible to do this? I see how to add a manifest entry and I see how to specify the war classpath should be generated, but how to get this: Manifest-Version: 1.0 Class-Path: customerEjb_client.jar <-- Dependency inventoryEjb_client.jar <-- Dependency mailerEjb_client.jar<-- Dependency ../foobar.properties
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
Jerome Lacoste schreef: On 4/23/07, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: I also have a dependency on spring-core: /repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar So I need a different classpathPrefix depending on the dependency. what is your use case ? I am not sure that the repository-like structure allowed by the assembly plugin was designed to allow you to run your app from the generated repository. Some suggestions: 1- don't assemble as a maven repository (do you really need it ?) For the sake of namespacing, yes: /org/foo/bar-1.0.jar /org/doo/bar-1.0.jar are 2 different jars, with different classes. 2- don't depend on the generated classpath (e.g. use a wrapper to start your app) You mean a shell script? Then we need to keep 2 verions in sync: wrapper.bat and wrapper.sh. Or do you mean a wrapper jar? We have separate processes that reuse the same jars and want to minimize network traffic. How can we avoid having to rewrite the classpath with each dependency change in this case? 3- rewrite the generated classpath once your repository has been created. In the jar? Problem is we need the groupId of each artifact. 4- patch the jar plugin to accept a classpath generator that matches your requirement That would be the full solution. I would pick option 1 or 3. Cheers, J With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
On 4/23/07, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: I also have a dependency on spring-core: /repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar So I need a different classpathPrefix depending on the dependency. what is your use case ? I am not sure that the repository-like structure allowed by the assembly plugin was designed to allow you to run your app from the generated repository. Some suggestions: 1- don't assemble as a maven repository (do you really need it ?) 2- don't depend on the generated classpath (e.g. use a wrapper to start your app) 3- rewrite the generated classpath once your repository has been created. 4- patch the jar plugin to accept a classpath generator that matches your requirement I would pick option 1 or 3. Cheers, J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
I also have a dependency on spring-core: /repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar So I need a different classpathPrefix depending on the dependency. With kind regards, Geoffrey De Smet Ian Springer schreef: Hi, Add: ../../../../org/ggg/ggg-core/1.0/ as a child element of the element. Ian Geoffrey De Smet wrote: Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
Hi, Add: ../../../../org/ggg/ggg-core/1.0/ as a child element of the element. Ian Geoffrey De Smet wrote: Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dynamic jar manifest classpath based on groupId, artifactId and version in repository
Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to generate manifest ClassPath entries for a web project?
See http://jira.codehaus.org/browse/MEAR-60 for a suggested improvement to the 'downside' of this solution. Please vote for this issue if you want it fixed. Regards, Marcel - Original Message From: Manos Batsis <[EMAIL PROTECTED]> To: Maven Users List <[EMAIL PROTECTED]> Sent: Thursday, April 12, 2007 6:50:09 PM Subject: Re: How to generate manifest ClassPath entries for a web project? Johan Eltes wrote: > I'd like have all dependent jars of all modules of my enterprise > application bundled in the ear - not in WEB-INF/lib directories of my > war files. Is this possible with maven 2? I would also like maven to > generate the required ClassPath entries in the war manifest file. I've > found out how to accomplish the same tasks for ejb projects, but haven't > found any hints on war projects. md4j-quickstarter does that for it's ejb and war modules. The downside is you have to duplicate deps in the ear pom. See the ear and war pom in [1] and [2] respectively. [1] http://md4j.cvs.sourceforge.net/md4j/md4j-quickstarter-mvn/ear/pom.xml?view=markup [2] http://md4j.cvs.sourceforge.net/md4j/md4j-quickstarter-mvn/web/pom.xml?view=markup hth, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to generate manifest ClassPath entries for a web project?
Johan Eltes wrote: I'd like have all dependent jars of all modules of my enterprise application bundled in the ear - not in WEB-INF/lib directories of my war files. Is this possible with maven 2? I would also like maven to generate the required ClassPath entries in the war manifest file. I've found out how to accomplish the same tasks for ejb projects, but haven't found any hints on war projects. md4j-quickstarter does that for it's ejb and war modules. The downside is you have to duplicate deps in the ear pom. See the ear and war pom in [1] and [2] respectively. [1] http://md4j.cvs.sourceforge.net/md4j/md4j-quickstarter-mvn/ear/pom.xml?view=markup [2] http://md4j.cvs.sourceforge.net/md4j/md4j-quickstarter-mvn/web/pom.xml?view=markup hth, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to generate manifest ClassPath entries for a web project?
Good day, If you have a war project and you want some of its dependencies not to be included in your WEB-INF/lib, add ... ... ... provided Cheers, Franz Johan Eltes-3 wrote: > > Thanks. > Now that Maven is generating my manifest ClassPath entry for all my > dependencies - how do I avoid having the dependent jars copied into > the WEB-INF/lib directory of my war? > > Johan Eltes > Callista Enterprise AB > Mobil: +46 (0)708-22 41 86 > [EMAIL PROTECTED] > http://www.callistaenterprise.se > > > On 12 apr 2007, at 17.05, Jerome Lacoste wrote: > >> On 4/12/07, Johan Eltes <[EMAIL PROTECTED]> wrote: >>> >>> I'd like have all dependent jars of all modules of my enterprise >>> application bundled in the ear - not in WEB-INF/lib directories of my >>> war files. Is this possible with maven 2? I would also like maven to >>> generate the required ClassPath entries in the war manifest file. >>> I've found out how to accomplish the same tasks for ejb projects, but >>> haven't found any hints on war projects. >> >> >> >> Read >> >> http://maven.apache.org/plugins/maven-war-plugin/examples/war- >> manifest-guide.html >> >> J > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/ERROR-%22The-plugin-%27org.apache.maven.plugins%3Amaven-resources-plugin%27-does-not-exist%22-tf3564721s177.html#a9962532 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: How to generate manifest ClassPath entries for a web project?
Thanks. Now that Maven is generating my manifest ClassPath entry for all my dependencies - how do I avoid having the dependent jars copied into the WEB-INF/lib directory of my war? Johan Eltes Callista Enterprise AB Mobil: +46 (0)708-22 41 86 [EMAIL PROTECTED] http://www.callistaenterprise.se On 12 apr 2007, at 17.05, Jerome Lacoste wrote: On 4/12/07, Johan Eltes <[EMAIL PROTECTED]> wrote: I'd like have all dependent jars of all modules of my enterprise application bundled in the ear - not in WEB-INF/lib directories of my war files. Is this possible with maven 2? I would also like maven to generate the required ClassPath entries in the war manifest file. I've found out how to accomplish the same tasks for ejb projects, but haven't found any hints on war projects. Read http://maven.apache.org/plugins/maven-war-plugin/examples/war- manifest-guide.html J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to generate manifest ClassPath entries for a web project?
On 4/12/07, Johan Eltes <[EMAIL PROTECTED]> wrote: I'd like have all dependent jars of all modules of my enterprise application bundled in the ear - not in WEB-INF/lib directories of my war files. Is this possible with maven 2? I would also like maven to generate the required ClassPath entries in the war manifest file. I've found out how to accomplish the same tasks for ejb projects, but haven't found any hints on war projects. Read http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html J
How to generate manifest ClassPath entries for a web project?
I'd like have all dependent jars of all modules of my enterprise application bundled in the ear - not in WEB-INF/lib directories of my war files. Is this possible with maven 2? I would also like maven to generate the required ClassPath entries in the war manifest file. I've found out how to accomplish the same tasks for ejb projects, but haven't found any hints on war projects. Johan Eltes Callista Enterprise AB Mobil: +46 (0)708-22 41 86 [EMAIL PROTECTED] http://www.callistaenterprise.se - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Add Directory to Jar Manifest Classpath
Oh, I'm sorry, I thought you were saying that the Class-Path entry in the manifest couldn't refer to non-jar items. It's very easy to set the Class-Path entry using either the jar plugin or the assembly plugin. In the section, specify an element. The jar plugin has pretty good docs for this. If you want maven to include your dependencies, say this: com.example.App true To give your own classpath (or prepend to what maven writes), do this: ... config/ classes/ But note that currently the assembly plugin has a bug and ignores . The jar plugin does not have this bug. Paul berndq wrote: > > Hi, > >> Are you sure that documentation wasn't talking about applets? I've run >> executable jars with Class-Path manifest entries referencing the >> filesystem >> many times. > > I looked it up again: > > http://java.sun.com/j2se/1.3/docs/tooldocs/win32/java.html > goto -jar option, there it says > "When you use this option [Main-Class:classname], the JAR file is the > source of all user classes, and other user class path settings are > ignored." > > I was trying to extend the classpath from outside the jar (-cp xxx) > and this is what does not work according to the specs. > > I did not try to extend the classpath in the manifest inside the jar. > Is this possible at all when using the assembly plugin the create the > classpath entry in the manifest? > > thanks for you info! > > Bernd > >> Paul >> >> >> berndq wrote: >>> SingleShot wrote: >>>> I am building an executable JAR that depends on a handful of other JARs >>>> and a >>>> few config files being on the classpath. I want the config files to be >>>> editable by the end user, so did not add them as internal JAR >>>> resources. >>>> I've configured the maven-jar-plugin to generate a manifest and add the >>>> dependencies to its classpath (and create a mainclass entry), but >>>> cannot >>>> figure out how to configure it to add my config directory (containing >>>> the >>>> config files) to the classpath. >>>> >>>> Is it possible to add a directory to the classpath of a Maven-generated >>>> Manifest? >>> Hi, >>> >>> I had exactly the same problem. This is not a maven but a (sun?) Java >>> problem: >>> >>> Executable jars use a classloader that can only load resources/classes >>> from other jars and not from the file system. I found this documented >>> somewhere under java.sun.com. >>> >>> >>> So I had to stop using executable jars :-( >>> >>> best regards >>> Bernd >>> >>> - >>> 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] > > > -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7031994 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: Add Directory to Jar Manifest Classpath
Hi, Are you sure that documentation wasn't talking about applets? I've run executable jars with Class-Path manifest entries referencing the filesystem many times. I looked it up again: http://java.sun.com/j2se/1.3/docs/tooldocs/win32/java.html goto -jar option, there it says "When you use this option [Main-Class:classname], the JAR file is the source of all user classes, and other user class path settings are ignored." I was trying to extend the classpath from outside the jar (-cp xxx) and this is what does not work according to the specs. I did not try to extend the classpath in the manifest inside the jar. Is this possible at all when using the assembly plugin the create the classpath entry in the manifest? thanks for you info! Bernd Paul berndq wrote: SingleShot wrote: I am building an executable JAR that depends on a handful of other JARs and a few config files being on the classpath. I want the config files to be editable by the end user, so did not add them as internal JAR resources. I've configured the maven-jar-plugin to generate a manifest and add the dependencies to its classpath (and create a mainclass entry), but cannot figure out how to configure it to add my config directory (containing the config files) to the classpath. Is it possible to add a directory to the classpath of a Maven-generated Manifest? Hi, I had exactly the same problem. This is not a maven but a (sun?) Java problem: Executable jars use a classloader that can only load resources/classes from other jars and not from the file system. I found this documented somewhere under java.sun.com. So I had to stop using executable jars :-( best regards Bernd - 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]
Re: Add Directory to Jar Manifest Classpath
Are you sure that documentation wasn't talking about applets? I've run executable jars with Class-Path manifest entries referencing the filesystem many times. Paul berndq wrote: > > SingleShot wrote: >> I am building an executable JAR that depends on a handful of other JARs >> and a >> few config files being on the classpath. I want the config files to be >> editable by the end user, so did not add them as internal JAR resources. >> I've configured the maven-jar-plugin to generate a manifest and add the >> dependencies to its classpath (and create a mainclass entry), but cannot >> figure out how to configure it to add my config directory (containing the >> config files) to the classpath. >> >> Is it possible to add a directory to the classpath of a Maven-generated >> Manifest? > > Hi, > > I had exactly the same problem. This is not a maven but a (sun?) Java > problem: > > Executable jars use a classloader that can only load resources/classes > from other jars and not from the file system. I found this documented > somewhere under java.sun.com. > > > So I had to stop using executable jars :-( > > best regards > Bernd > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7019847 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: Add Directory to Jar Manifest Classpath
SingleShot wrote: I am building an executable JAR that depends on a handful of other JARs and a few config files being on the classpath. I want the config files to be editable by the end user, so did not add them as internal JAR resources. I've configured the maven-jar-plugin to generate a manifest and add the dependencies to its classpath (and create a mainclass entry), but cannot figure out how to configure it to add my config directory (containing the config files) to the classpath. Is it possible to add a directory to the classpath of a Maven-generated Manifest? Hi, I had exactly the same problem. This is not a maven but a (sun?) Java problem: Executable jars use a classloader that can only load resources/classes from other jars and not from the file system. I found this documented somewhere under java.sun.com. So I had to stop using executable jars :-( best regards Bernd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Add Directory to Jar Manifest Classpath
That's a very handy command! You're right, it says 2.1. Yesterday I tried running with -X, and I thought it said it was getting 2.2, but now -X also says 2.1, so I must have made a mistake. My apologies! But the trailing slash still works on my system. :-) But I'm running linux, and the bug is filed against windows Paul Syvalta wrote: > > > pjungwir wrote: >> >> I don't understand. 2.2 is the plugin version, not the maven version, >> right? That appears to be released. For me, it's what maven just uses; I >> didn't do anything special. >> > > Yes, the version of jar-plugin. To my knowledge 2.1 is the latest version > (see > http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/). > Jira lists both 2.1 and 2.2 unreleased ( which is wrong for the latter). > Are you sure you have checked the version of the correct plugin? Yuo can > check the version with command "mvn -Dplugin=jar help:describe". > > > -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7016303 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: Add Directory to Jar Manifest Classpath
pjungwir wrote: > > I don't understand. 2.2 is the plugin version, not the maven version, > right? That appears to be released. For me, it's what maven just uses; I > didn't do anything special. > Yes, the version of jar-plugin. To my knowledge 2.1 is the latest version (see http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/). Jira lists both 2.1 and 2.2 unreleased ( which is wrong for the latter). Are you sure you have checked the version of the correct plugin? Yuo can check the version with command "mvn -Dplugin=jar help:describe". -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7016118 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: Add Directory to Jar Manifest Classpath
I don't understand. 2.2 is the plugin version, not the maven version, right? That appears to be released. For me, it's what maven just uses; I didn't do anything special. Paul Syvalta wrote: > > > pjungwir wrote: >> >> >> Syvalta wrote: >>> >>> But that doesn't work for me, see: >>> http://jira.codehaus.org/browse/MJAR-60. >>> >> I didn't get any error with a trailing slash inside . JIRA >> says this is fixed against 2.2. I'm not sure why the bug is still open in >> that case. . . . >> > > There isn't snapshot of 2.2 yet, so I didn't test with that, so I can't > confirm. However, as I understand it, "fix for" means that is should be > fixed before that release, not that it's fixed. > -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7014719 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: Add Directory to Jar Manifest Classpath
pjungwir wrote: > > > Syvalta wrote: >> >> But that doesn't work for me, see: >> http://jira.codehaus.org/browse/MJAR-60. >> > I didn't get any error with a trailing slash inside . JIRA > says this is fixed against 2.2. I'm not sure why the bug is still open in > that case. . . . > There isn't snapshot of 2.2 yet, so I didn't test with that, so I can't confirm. However, as I understand it, "fix for" means that is should be fixed before that release, not that it's fixed. -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7006293 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: Malformed manifest classpath entry
Wayne, that seems like a different error. You shouldn't have Class-Path entries in the EAR's manifest (including Java EE 1.4) These entries belong in the modules within the ear, i.e. the EJB JAR's, etc. Though Max is technically right, its still ugly!!! :D! Alex On 10/25/06, Wayne Fay <[EMAIL PROTECTED]> wrote: Glassfish's application verifier (SJAS 9.1) actually complains about any Class-Path entry in your EAR MANIFEST... Apparently the most recent J2EE spec disallows this, haven't looked into it much myself, we're finally targeting JEE5 for our next release so I'm sure I'll learn a lot of new things. Test Name : tests.app.EARFileUsesClassPath Test Assertion : Manifest file of an EAR file should not contain Class-Path entries. Wayne On 10/25/06, Max Cooper <[EMAIL PROTECTED]> wrote: > I agree that it is ugly, but the Jar Specification requires the > wrapping, see "Line length" in this section: > > http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files > > The plugin is doing the right thing. > > -Max > > pjungwir wrote: > > Yeah, I wish maven wouldn't wrap the Class-Path entry, too. > > > > - > 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] -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
Re: Malformed manifest classpath entry
Glassfish's application verifier (SJAS 9.1) actually complains about any Class-Path entry in your EAR MANIFEST... Apparently the most recent J2EE spec disallows this, haven't looked into it much myself, we're finally targeting JEE5 for our next release so I'm sure I'll learn a lot of new things. Test Name : tests.app.EARFileUsesClassPath Test Assertion : Manifest file of an EAR file should not contain Class-Path entries. Wayne On 10/25/06, Max Cooper <[EMAIL PROTECTED]> wrote: I agree that it is ugly, but the Jar Specification requires the wrapping, see "Line length" in this section: http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files The plugin is doing the right thing. -Max pjungwir wrote: > Yeah, I wish maven wouldn't wrap the Class-Path entry, too. > - 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]
Re: Malformed manifest classpath entry
I agree that it is ugly, but the Jar Specification requires the wrapping, see "Line length" in this section: http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files The plugin is doing the right thing. -Max pjungwir wrote: Yeah, I wish maven wouldn't wrap the Class-Path entry, too. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Malformed manifest classpath entry
Yeah, I did a lot of mail-archive.com searching and its a common issue. Transitive dependency tracking can be fantastic (especially for Java applications building), but for EARs its VERY dangerous since you are left with runtime exceptions to debug (treaded cast class exceptions etc.) instead of a compile time errors which defeats the whole purpose of Maven2! :D -aps On 10/25/06, pjungwir <[EMAIL PROTECTED]> wrote: Yeah, I wish maven wouldn't wrap the Class-Path entry, too. I'm pretty new to maven myself, so I haven't tried out multi-module builds or J2EE builds. But I think you have the right idea. Marking things provided is the surest way I know to keep transitive dependencies out of your artifacts. There is also the tag, but then you have to catch every path from which the dependency is coming. A lot of people seem to get bit by your problem, so perhaps a flag to exclude transitive dependencies would be a good idea. You could override it on a per-dependency basis. Paul -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7002290 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
Re: Malformed manifest classpath entry
Yeah, I wish maven wouldn't wrap the Class-Path entry, too. I'm pretty new to maven myself, so I haven't tried out multi-module builds or J2EE builds. But I think you have the right idea. Marking things provided is the surest way I know to keep transitive dependencies out of your artifacts. There is also the tag, but then you have to catch every path from which the dependency is coming. A lot of people seem to get bit by your problem, so perhaps a flag to exclude transitive dependencies would be a good idea. You could override it on a per-dependency basis. Paul -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7002290 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: Malformed manifest classpath entry
Hi Paul, Sorry, yea, I've been a little frustrated dealing with manifest entries and transitive dependencies (last post). I've solved my problems for the most part. For the below issue what was happening is Maven2 (Plexutils I think) is generating the manifest file and not copying the EXACT string between my tags. It is formatting it which I found very odd, I would get: Class-Path: lib/mylib1.jar .. lib/mylib 1.jar lib/mylib2.jar... lib/mylib3. jar etc. it actually works during runtime, its looks ugly as sin. I'm using addClassPath now so I don't have the generated manifest to post (again sorry) which led me to my other post about transitive dependencies and best practices (I now have a duplicate dependency entries in the parent and transitive dependencies explicilty listed in order to give them a scope of provided so they don't appear in my EAR). FYI, I really think the transitive dependencies should be completely optional. In my case I had like 4-5 that crept in which would royally screw up a JBoss deploy (like log4j, commons-logging, xerces, etc.). Thanks! -aps On 10/25/06, pjungwir <[EMAIL PROTECTED]> wrote: Hello, Could you please post your MANIFEST.MF file so we can see what "royally screwed up" means? Thanks, Paul Alexander Sack-3 wrote: > > Hi Everybody, > > I did check the email archives on this one and I'm not sure what's what... > > If I specify a manifest entry such as: > > > > lib/some1.jar lib/some2.jar lib/some3.jar lib/some4.jar > lib/some5.jar > > --> > > The actual manifest entry is royally screwed up in terms of formatting. > I'm > porting projects so I realize I need to play around with dependencies so I > can just use the addClassPath entry, but shouldn't this work regardless? > > Also, can someone tell me the difference between compile, runtime, and > provided with respect to the tag? Its not very obvious from > the doc (or I'm looking at the wrong doc). > > Thanks! > > -aps > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7001669 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
Re: Add Directory to Jar Manifest Classpath
Syvalta wrote: > > But that doesn't work for me, see: > http://jira.codehaus.org/browse/MJAR-60. > I didn't get any error with a trailing slash inside . JIRA says this is fixed against 2.2. I'm not sure why the bug is still open in that case. . . . Paul -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a7001786 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: Malformed manifest classpath entry
Hello, Could you please post your MANIFEST.MF file so we can see what "royally screwed up" means? Thanks, Paul Alexander Sack-3 wrote: > > Hi Everybody, > > I did check the email archives on this one and I'm not sure what's what... > > If I specify a manifest entry such as: > > > > lib/some1.jar lib/some2.jar lib/some3.jar lib/some4.jar > lib/some5.jar > > --> > > The actual manifest entry is royally screwed up in terms of formatting. > I'm > porting projects so I realize I need to play around with dependencies so I > can just use the addClassPath entry, but shouldn't this work regardless? > > Also, can someone tell me the difference between compile, runtime, and > provided with respect to the tag? Its not very obvious from > the doc (or I'm looking at the wrong doc). > > Thanks! > > -aps > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7001669 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: Add Directory to Jar Manifest Classpath
SingleShot wrote: > > Is it possible to add a directory to the classpath of a Maven-generated > Manifest? > In theory, yes: org.apache.maven.plugins maven-jar-plugin org.foo.mainclass true lib config/ But that doesn't work for me, see: http://jira.codehaus.org/browse/MJAR-60. Another limitation (in java, not in maven) is that you can't access higher level directories, so something like ../config/ won't work. -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a6987252 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Add Directory to Jar Manifest Classpath
I am building an executable JAR that depends on a handful of other JARs and a few config files being on the classpath. I want the config files to be editable by the end user, so did not add them as internal JAR resources. I've configured the maven-jar-plugin to generate a manifest and add the dependencies to its classpath (and create a mainclass entry), but cannot figure out how to configure it to add my config directory (containing the config files) to the classpath. Is it possible to add a directory to the classpath of a Maven-generated Manifest? Thanks in advance. -- View this message in context: http://www.nabble.com/Add-Directory-to-Jar-Manifest-Classpath-tf2504507.html#a6982645 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Malformed manifest classpath entry
Hi Everybody, I did check the email archives on this one and I'm not sure what's what... If I specify a manifest entry such as: lib/some1.jar lib/some2.jar lib/some3.jar lib/some4.jar lib/some5.jar --> The actual manifest entry is royally screwed up in terms of formatting. I'm porting projects so I realize I need to play around with dependencies so I can just use the addClassPath entry, but shouldn't this work regardless? Also, can someone tell me the difference between compile, runtime, and provided with respect to the tag? Its not very obvious from the doc (or I'm looking at the wrong doc). Thanks! -aps -- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
Re: EJB Manifest Classpath
On Jul 8, 2006, at 11:40 PM, Markus Wolf wrote:
Hi,
I've wondering if there is something similar like in Maven 1.x and the
WAR-Plugins to have dependencies added to the JARs Classpath entry.
For
the WAR-plugin this is somewhat documented, but there are no docs for
the EJB-plugin. Any idea how this could work?
This works just like for the jar plugin as documented here: http://
maven.apache.org/guides/mini/guide-manifest.html except specifying
maven-ejb-plugin instead of maven-jar-plugin.
e.g.
org.apache.maven.plugins
maven-ejb-plugin
true
org.apache.geronimo.itest
jar
${pom.version}
true
Hope this helps,
david jencks
Thanks
Markus Wolf
--
emedia-solutions wolf
Wedeler Landstrasse 63
22559 Hamburg
(040) 550 083 70
web: http://www.emedia-solutions-wolf.de
mail: [EMAIL PROTECTED]
pgp: http://wwwkeys.de.pgp.net
-
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]
EJB Manifest Classpath
Hi, I've wondering if there is something similar like in Maven 1.x and the WAR-Plugins to have dependencies added to the JARs Classpath entry. For the WAR-plugin this is somewhat documented, but there are no docs for the EJB-plugin. Any idea how this could work? Thanks Markus Wolf -- > > emedia-solutions wolf > Wedeler Landstrasse 63 > 22559 Hamburg > (040) 550 083 70 > >> web: http://www.emedia-solutions-wolf.de >> mail: [EMAIL PROTECTED] >> pgp: http://wwwkeys.de.pgp.net > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 enterprise application package WAR and WEB-INF/lib and manifest classpath
Title: Maven 2 enterprise application package WAR and WEB-INF/lib and manifest classpath Problem description : In Maven 2, controlling dependencies within pom.xml files to control packaging within ear file plus controlling entries in the Manifest.mf file within the war file and the contents of WEB-INF/lib within the war Example project : - Ear file wrapping a jar, and a war file which in turn has a jar in it's WEB-INF/lib plus a manifest file class path referencing the jar held within ear file. This is useful for multiple war's in 1 ear. - -EAR - - - - frmw.jar - - - - ## - - # WebApp1 # - - # WEB-INF/lib # - - # x.jar # - - # # - - # # - - # Manifest.mf # - - # Class-Path: # - - # frmw.jar # - - ## - - - - Projects: - WebApp1 - frmw.jar - x.jar WebApp1 has dependency on frwm.jar and x.jar want to have frmw.jar appear as entry in Manifest.mf within war Class-Path: want to have x.jar appear in WEB-INF/lib but not as entry in manifest.mf Class-Path: Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 enterpise packaging wars, ears, manifest classpath and WEB-INF/lib
Title: M2 enterpise packaging wars, ears, manifest classpath and WEB-INF/lib Problem description : In Maven 2, controlling dependencies within pom.xml files to control packaging within ear file plus controlling entries in the Manifest.mf file within the war file and the contents of WEB-INF/lib within the war Example project : - Ear file wrapping a jar, and a war file which in turn has a jar in it's WEB-INF/lib plus a manifest file class path referencing the jar held within ear file. This is useful for multiple war's in 1 ear. - -EAR - - - - frmw.jar - - - - ## - - # WebApp1 # - - # WEB-INF/lib # - - # x.jar # - - # # - - # # - - # Manifest.mf # - - # Class-Path: # - - # frmw.jar # - - ## - - - - Projects: - WebApp1 - frmw.jar - x.jar WebApp1 has dependency on frwm.jar and x.jar want to have frmw.jar appear as entry in Manifest.mf within war Class-Path: want to have x.jar appear in WEB-INF/lib but not as entry in manifest.mf Class-Path: Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Manifest CLASSPATH line wraps?
That's what it's meant to do to long lines. It's in the jar spec, somewhere. JBoss understands wrapped lines just fine. > -Original Message- > From: Mike Cantrell [mailto:[EMAIL PROTECTED] > Sent: 09 May 2005 15:34 > To: users@maven.apache.org > Subject: Manifest CLASSPATH line wraps? > > > Hello, > > > > I'm testing out maven (1.0.2) for the first time. I think I > have everything > working except my Manifest.mf Classpath. It's wrapping/truncating the > entries. > > > > Example: > > > > Class-Path: commons-beanutils-1.7.0.jar commons-collections-2.1.1.jar > > commons-dbcp-1.2.1.jar commons-digester-1.6.jar commons-fileupload-1 > > .0.jar commons-lang-2.0.jar commons-logging-1.0.4.jar commons-pool-1. > > 2.jar commons-validator-1.1.4.jar log4j-1.2.8.jar spring-1.2-rc2.jar > > spring-aop-1.2-rc2.jar spring-beans-1.2-rc2.jar spring-context-1.2-rc > > 2.jar spring-core-1.2-rc2.jar spring-dao-1.2-rc2.jar spring-hibernate > > -1.2-rc2.jar spring-jdbc-1.2-rc2.jar spring-mock-1.2-rc2.jar spring-o > > rm-1.2-rc2.jar spring-remoting-1.2-rc2.jar spring-support-1.2-rc2.jar > > spring-web-1.2-rc2.jar spring-webmvc-1.2-rc2.jar ehcache-1.1.jar swa > > rmcache-1.0rc2.jar jboss-cache-1.2.2alpha.jar jgroups-2.2.7.jar jta-u > > nknown.jar xml-apis-unknown.jar c3p0-0.8.5.2.jar connector-unknown.ja > > r jboss-system-unknown.jar asm-attrs-unknown.jar asm-unknown.jar jacc > > -1.0-fr.jar dom4j-1.6.jar antlr-2.7.5H3.jar cglib-2.1.jar jboss-commo > > n-unknown.jar oscache-2.1.jar jdbc-stdext-2.0.jar jboss-jmx-unknown.j > > ar xerces-2.6.2.jar jaxen-1.1-beta-4.jar proxool-0.8.3.jar concurrent > > -1.3.2.jar msbase-2000.jar mssqlserver-2000.jar msutil-2000.jar > > > > See how it's cutting off file names when it does a line wrap? > Is this the > intended behavior? My application server (jboss-4.0.1sp1) > can't find the > dependant jars inside my EAR for my EJB jar. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manifest CLASSPATH line wraps?
Hello, I'm testing out maven (1.0.2) for the first time. I think I have everything working except my Manifest.mf Classpath. It's wrapping/truncating the entries. Example: Class-Path: commons-beanutils-1.7.0.jar commons-collections-2.1.1.jar commons-dbcp-1.2.1.jar commons-digester-1.6.jar commons-fileupload-1 .0.jar commons-lang-2.0.jar commons-logging-1.0.4.jar commons-pool-1. 2.jar commons-validator-1.1.4.jar log4j-1.2.8.jar spring-1.2-rc2.jar spring-aop-1.2-rc2.jar spring-beans-1.2-rc2.jar spring-context-1.2-rc 2.jar spring-core-1.2-rc2.jar spring-dao-1.2-rc2.jar spring-hibernate -1.2-rc2.jar spring-jdbc-1.2-rc2.jar spring-mock-1.2-rc2.jar spring-o rm-1.2-rc2.jar spring-remoting-1.2-rc2.jar spring-support-1.2-rc2.jar spring-web-1.2-rc2.jar spring-webmvc-1.2-rc2.jar ehcache-1.1.jar swa rmcache-1.0rc2.jar jboss-cache-1.2.2alpha.jar jgroups-2.2.7.jar jta-u nknown.jar xml-apis-unknown.jar c3p0-0.8.5.2.jar connector-unknown.ja r jboss-system-unknown.jar asm-attrs-unknown.jar asm-unknown.jar jacc -1.0-fr.jar dom4j-1.6.jar antlr-2.7.5H3.jar cglib-2.1.jar jboss-commo n-unknown.jar oscache-2.1.jar jdbc-stdext-2.0.jar jboss-jmx-unknown.j ar xerces-2.6.2.jar jaxen-1.1-beta-4.jar proxool-0.8.3.jar concurrent -1.3.2.jar msbase-2000.jar mssqlserver-2000.jar msutil-2000.jar See how it's cutting off file names when it does a line wrap? Is this the intended behavior? My application server (jboss-4.0.1sp1) can't find the dependant jars inside my EAR for my EJB jar.
Re: Generate manifest classpath entry?
Yes it is Take a look at the jar plugin properties: http://maven.apache.org/reference/plugins/jar/properties.html In short, you must set the property: maven.jar.manifest.classpath.add=true And in your project.xml, in each dependency, add the following property: true That should do the trick. Hope it helps. Eric. Wim Deblauwe wrote: Hi, is it possible to generate a Class-Path entry in the generated manifest file that includes all dependend jars? See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Main%20Attributes for more info regards, Wim - 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]
Generate manifest classpath entry?
Hi, is it possible to generate a Class-Path entry in the generated manifest file that includes all dependend jars? See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Main%20Attributes for more info regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[war-plugin] Include dependency as manifest-classpath
Hi. Just getting started with Maven, and I must say I like it! Kudos to the developers! To the question: One nice feature for the war plugin would be to make it possible to specify that a dependency should be included in the manifest classpath of the war. Is is this something that is considered? The jelly-code is in the ejb-plugin, so I suppose it would be pretty easy to implement (I'd be happy to write a patch). The reason is that when you have an ejb module and one or many web-modules in a J2EE-project (as we have) you often have common dependencies between these modules. Let's say you need commons-logging in all modules then you'd probably want to include commons-logging-x.x.x.jar in the EAR-file, and reference it from all other modules as manifest classpath entries. In the project.xml of a webapplication you would thus have: commons-logging commons-logging 1.0.3 true webwork webwork 1.3 true Thoughts, comments? //Anders -- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Anders Engström [EMAIL PROTECTED] . http://www.gnejs.netPGP-Key: ED010E7F . [Your mind is like an umbrella. It doesn't work unless you open it.] pgp0.pgp Description: PGP signature
Re: Question: How to create a manifest classpath
We had to tackle the same thing and did the following: Then in your project.properties file you need to include this: maven.jar.mainclass=com.evnt.eve.Eve maven.jar.manifest=target/conf/manifest.mf Hope that helps, Brent Siegfried Göschl wrote: Hi Michal, I had a look at uberjar a few months ago but encountered performance problems due to the URLClassloader - it takes ages to pull in my JARs :-). Orginale Mail Snippet >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> But it is too slow - my JAR is about 11.5 MByte and starting it takes now 150 seconds instead of 3 seconds. After loading all the classes there is still a performance degration of the factor 5 - my tests runs now in 19.5 sec instead of 3.8 seconds. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< As a workaround I'm using the javaapp plugin hosted on http://maven- plugins.sourceforge.net/ ... the most recent version for Maven B10 is actually found within the CVS since I had no time to upload a new release of it. Cheers, Siegfried Goeschl On 31 Jul 2003 at 22:26, Michal Maczka wrote: take a look what uberjar plugin does. Michal -Original Message- From: Erik Husby [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 10:21 PM To: Maven Users List Subject: Re: Question: How to create a manifest classpath Quoting Siegfried Göschl <[EMAIL PROTECTED]>: Hi Erik, I'm not quite sure if I'm qualified to answer your question since this is the first time that I heard of a manifest classpath ... :-) ... but I asked Google. And Google knows a few things about it - you might find the relevant code it the maven.ejb-plugin ... Hope this helps, Siegfried Goeschl That is exactly what I am looking for -- thanks. FYI a manifest classpath allows one easily package an application so that you can do the following: cd somedirectory java -jar application.jar Assuming that the application jar and all its related jar files are in the directory "somedirectory". On Windows this means you can double click on a jar file to launch the application. -- Erik Husby Team Lead for Software Quality Automation Whitehead Institute/MIT Center for Genome Research Rm 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669 office: 617.258.9227 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Portal INTERIA.PL zaprasza... >>> http://link.interia.pl/f174b - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question: How to create a manifest classpath
Hi Michal, I had a look at uberjar a few months ago but encountered performance problems due to the URLClassloader - it takes ages to pull in my JARs :-). >>> Orginale Mail Snippet >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> But it is too slow - my JAR is about 11.5 MByte and starting it takes now 150 seconds instead of 3 seconds. After loading all the classes there is still a performance degration of the factor 5 - my tests runs now in 19.5 sec instead of 3.8 seconds. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< As a workaround I'm using the javaapp plugin hosted on http://maven- plugins.sourceforge.net/ ... the most recent version for Maven B10 is actually found within the CVS since I had no time to upload a new release of it. Cheers, Siegfried Goeschl On 31 Jul 2003 at 22:26, Michal Maczka wrote: > take a look what uberjar plugin does. > > Michal > > > -Original Message- > > From: Erik Husby [mailto:[EMAIL PROTECTED] > > Sent: Thursday, July 31, 2003 10:21 PM > > To: Maven Users List > > Subject: Re: Question: How to create a manifest classpath > > > > > > Quoting Siegfried Göschl <[EMAIL PROTECTED]>: > > > > > Hi Erik, > > > > > > I'm not quite sure if I'm qualified to answer your question since > > > this is the first time that I heard of a manifest classpath ... > > > :-) ... but I asked Google. > > > > > > And Google knows a few things about it - you might find the > > > relevant code it the maven.ejb-plugin ... > > > > > > > > > Hope this helps, > > > > > > Siegfried Goeschl > > > > That is exactly what I am looking for -- thanks. > > > > FYI a manifest classpath allows one easily package an application so > > that you can do the following: > > > > > cd somedirectory > > > java -jar application.jar > > > > Assuming that the application jar and all its related jar files are > > in the directory "somedirectory". > > > > On Windows this means you can double click on a jar file to > > launch the application. > > -- > > Erik Husby > > Team Lead for Software Quality Automation > > Whitehead Institute/MIT Center for Genome Research > > Rm 2192 > > 320 Charles St > > Cambridge, MA 02141-2023 > > mobile: 781.354.6669 > > office: 617.258.9227 > > [EMAIL PROTECTED] > > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- Portal INTERIA.PL zaprasza... >>> http://link.interia.pl/f174b > > > > > > > > > > - > 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]
RE: Question: How to create a manifest classpath
take a look what uberjar plugin does. Michal > -Original Message- > From: Erik Husby [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 31, 2003 10:21 PM > To: Maven Users List > Subject: Re: Question: How to create a manifest classpath > > > Quoting Siegfried Göschl <[EMAIL PROTECTED]>: > > > Hi Erik, > > > > I'm not quite sure if I'm qualified to answer your question since > > this is the first time that I heard of a manifest classpath ... :-) > > ... but I asked Google. > > > > And Google knows a few things about it - you might find the relevant > > code it the maven.ejb-plugin ... > > > > > > Hope this helps, > > > > Siegfried Goeschl > > That is exactly what I am looking for -- thanks. > > FYI a manifest classpath allows one easily package an application > so that you > can do the following: > > > cd somedirectory > > java -jar application.jar > > Assuming that the application jar and all its related jar files are in the > directory "somedirectory". > > On Windows this means you can double click on a jar file to > launch the application. > -- > Erik Husby > Team Lead for Software Quality Automation > Whitehead Institute/MIT Center for Genome Research > Rm 2192 > 320 Charles St > Cambridge, MA 02141-2023 > mobile: 781.354.6669 > office: 617.258.9227 > [EMAIL PROTECTED] > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- > Portal INTERIA.PL zaprasza... >>> http://link.interia.pl/f174b > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question: How to create a manifest classpath
Quoting Siegfried Göschl <[EMAIL PROTECTED]>: > Hi Erik, > > I'm not quite sure if I'm qualified to answer your question since > this is the first time that I heard of a manifest classpath ... :-) > ... but I asked Google. > > And Google knows a few things about it - you might find the relevant > code it the maven.ejb-plugin ... > > > Hope this helps, > > Siegfried Goeschl That is exactly what I am looking for -- thanks. FYI a manifest classpath allows one easily package an application so that you can do the following: > cd somedirectory > java -jar application.jar Assuming that the application jar and all its related jar files are in the directory "somedirectory". On Windows this means you can double click on a jar file to launch the application. -- Erik Husby Team Lead for Software Quality Automation Whitehead Institute/MIT Center for Genome Research Rm 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669 office: 617.258.9227 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question: How to create a manifest classpath
Hi Erik, I'm not quite sure if I'm qualified to answer your question since this is the first time that I heard of a manifest classpath ... :-) ... but I asked Google. And Google knows a few things about it - you might find the relevant code it the maven.ejb-plugin ... Hope this helps, Siegfried Goeschl On 31 Jul 2003 at 13:49, Erik Husby wrote: > > I am trying to convert from Ant to Maven. > > One of the things that my Ant script did was to create a manifest > classpath that referred to all the jars in my /lib directory. I was > able to create a jar:jar pregoal that does that as well. But what I'd > like to do would be to create the classpath using the dependencies > that are listed in the project.xml. > > Would someone give me a hint on how that would be done in Maven/Jelly? > > -- > Erik Husby > Team Lead for Software Quality Automation > Whitehead Institute/MIT Center for Genome Research > Rm 2192 > 320 Charles St > Cambridge, MA 02141-2023 > mobile: 781.354.6669 > office: 617.258.9227 > [EMAIL PROTECTED] > > > > - > 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]
Question: How to create a manifest classpath
I am trying to convert from Ant to Maven. One of the things that my Ant script did was to create a manifest classpath that referred to all the jars in my /lib directory. I was able to create a jar:jar pregoal that does that as well. But what I'd like to do would be to create the classpath using the dependencies that are listed in the project.xml. Would someone give me a hint on how that would be done in Maven/Jelly? -- Erik Husby Team Lead for Software Quality Automation Whitehead Institute/MIT Center for Genome Research Rm 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669 office: 617.258.9227 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
