I already use them and i didn't have problems. Did you check the case of the filename and the directories as it is wrote in the exception ?
Arnaud On 2/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Any feedback on this one? Are symbolic links in the repository generally a > bad idea? > > _ __ _ _ > //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com > `- ` > Andreas Ebbert-Karroum > Software Design Engineer - Nokia Networks Services / Middleware > phone: +49-211-94123928, fax: +49-211-9412-3838 > Heltorfer Straße 1, 40472 Düsseldorf, Germany > > ---------------------------------------------------------------------- > This message is confidential. If you have received this message in error, > please delete it from your system. You should not copy it for any purpose, > or disclose its contents to any other person. Internet communications are > not secure and therefore Nokia GmbH does not accept legal responsibility > for the contents of this message as it has been transmitted over a public > network. Thank you. > Nokia GmbH, Nokia Networks is a German Company. Further information > about the Company is available from its principal offices at > Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the > website at http://www.nokia.com/ > ---------------------------------------------------------------------- > > >-----Original Message----- > >From: Ebbert-Karroum Andreas (Nokia-NET/Dusseldorf) > >Sent: 14 February, 2006 13:08 > >To: 'users@maven.apache.org' > >Subject: ear:ear and symbolic links in repository > > > >Hi, > > > >I am trying to assemble an ear file with maven 1.0.2 on linux. > >The problem is that I have a lot of dependencies, which have > >to go into the ear file as libraries, which have to be > >downloaded from the web and manually added to the repository. > >I did this with symbolic links under linux, and this is > >causing problems for the ear:ear goal. The below mentioned > >oss_common_spec-1.2.jar is copied to the repository for > >testing purposes (it was a link previously), the > >oss_cbe_service_spec is a symbolic link. I couldn't find any > >open bug report for this behaviour. The problem is - as far as > >I can tell - that the test > > > ><j:if > >test="${!(checkFile.getAbsolutePath().equals(checkFile.getCanon > >icalPath()))}"> > > > >Doesn't work for symbolic links. > > > >Here's the output from the build: > > > >ear:ear: > > [echo] Building EAR oss_sa_ri_ear-1.2 with appxml > >"/home/andreas/Documents/Development/java.net/ossj/service_acti > >vation/root/../ri/app/target/application.xml" > > [echo] Bundling: jar - ossj:oss_common_spec - 1.2 > > [echo] Dependency oss_common_spec-1.2.jar will be bundled > >as /oss_common_spec-1.2.jar > > [copy] Copying 1 file to > >/home/andreas/Documents/Development/java.net/ossj/service_activ > >ation/ri/app/target/tmpEarDeps > > > >BUILD FAILED > >File...... > >/home/andreas/Documents/Development/java.net/ossj/service_activ > >ation/root/maven.xml > >Element... m:reactor > >Line...... 28 > >Column.... 131 > >Unable to obtain goal [ear:ear] -- > >/home/andreas/.maven/cache/maven-ear-plugin-1.6/plugin.jelly:99:24: > ><ant:fail> Case-sensitive issue: The dependency > >ossj:oss_cbe_service_spec has a case problem. The dependency > >was either retrieved in the past with the wrong case or has > >been specified with the wrong case in your project.xml file. > >Fix your project.xml or update your local repository with the > >properly-cased file and try again. > >Total time: 10 seconds > >Finished at: Wed Feb 08 09:37:32 CET 2006 > > > > --------------------------------------------------------------------- > 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]
