classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Thalmeiner Zsolt
Hello, I'm building a Java project using Maven 2.0.9 and JVM 1.5.0_14 on Windows XP. My project depends on runtime from some jar files that are resides in the same directory with my jar so I put this configuration to my pom.xml: plugin groupIdorg.apache.maven.plugins/groupId

Re: classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Paolo Compieta
- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/classpath-fileseparator-problem-in-generated-manifest-file-under-winxp-tp17312374p17313594.html Sent from the Maven

Re: classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Thalmeiner Zsolt
Using the classpathPrefix.\/classpathPrefix tag I want to get .\ (backslash) as prefix but the manifest file contains ./ (slash) prefixes. Unfortunatelly running the jar under WinXP doesn't recognizes paths with slashes :( I wrote to the list because I didn't found any information in doc pages

Re: classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Paolo Compieta
this problem. Regards, th - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/classpath-fileseparator-problem-in-generated

Re: classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Thalmeiner Zsolt
Can you send me a simple working example? Thank you in advance. th Paolo Compieta írta: This is not a Maven problem. The classpath entry in the manifest file is platform independent, and all paths are relative to the containing jar - you shouldn't even need the ./ prefix. see

Re: classpath fileseparator problem in generated manifest file under winxp

2008-05-19 Thread Tim Kettler
What do you mean by working example? you project build is behaving exactly as it should. Class-path entries in a jar manifest are ...relative URLS .. [1] and a file URL per definition [2] (section 3.10) contains forward slashes. If your library-jars are located in the same directory as the