[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1047) Publishing cross different filesystems doesn't appear to work

Publishing cross different filesystems doesn't appear to work ------------------------------------------------------------- Key: JBIDE-1047 URL: http://jira.jboss.com/jira/browse/JBIDE-1047 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Environment: Linux Reporter: Darryl Miles Assigned To: Rob Stryker Fix For: 2.0.0.CR1 Publishing cross different filesystems doesn't appear to work. I have my workspace in /home/myuser/workspace and my jboss runtime in /opt/jboss-4.2.1.GA these are on different unix file systems a /home and a /opt. I was trying to publish an EAR which contained one JAR (Utility JAR for classpath purpose) and an EJB implementation (based on an "EJB Project"). The Utility JAR was published correctly to the target runtime (this is because of the way Eclipse IDE achieve that, there is a different method for publish contributing Utility JARs). The entire tree was creately created in the deploy directory but none of the .class or .xml files (infact no other files) were published. I'd like to ask that since I saw no error in the UI about a publishing failure if you are checking the return values for all file operations and signaling their failure in the UI, this is something the Eclipse Tomcat driver was not even going circa WTP 1.0. I'm also unable to track down a page explaining where the source code is to the project to be able to audit it, and labs.jboss.org website drives me potty as I end up going around in circles never getting to what I'm looking for. You really should have a link right next to the binary download for the source download for that release, while this is done for some packages (on sourceforge) it does not appear to be done for all and certainly pages like http://labs.jboss.com/jbosside/download/index.html should have a link right next to each download to obtain the related source. I believe there is even a legal precedent over that constitutes your obligations in regards to LGPL in this matter.