Re: classpath entries in maven-archiver generated MANIFEST.MF cannot be referenced

2008-05-14 Thread aldana

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

2008-05-14 Thread aldana

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

2008-05-14 Thread [EMAIL PROTECTED]
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]