Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739405#739405 -------------------------------------------------------------- The location of the tmp and deployment directories are on the same filesystem. However, the location of the JBoss AS *installation* and the user instance (where the tmp and deployment folders are located) are different filesystems. In other words, / and /home are two different filesystems (they are different logical volumes). -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739405#739405] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739419#739419 -------------------------------------------------------------- Same exact error. Only directories are copied, files fail to copy. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739419#739419] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739458#739458 -------------------------------------------------------------- I think I've narrowed down the issue. I don't know how to solve it yet, but I at least know the precise circumstances that cause the problem. First, I ruled out any issue with the JBoss Tools install or a discrepancy with what the Fedora package installs by working with a zip download from jboss.org. I extracted the zip file, setup a new runtime and server, started it and successfully deployed the helloworld application. So that works as expected. My suspicion is that the problem occurs when JBoss Tools can't write to the JBoss AS installation. To prove this, I followed these steps: * I changed the ownership of the entire JBoss AS installation to root (both user and group permission) * I created a management user (admin / admin123) and verified I could use jboss-cli -c as non-root to connect to it * I started the server as the root user * I setup a new runtime and server for this installation, marked it as externally managed and set the management user to admin / admin123 * I configured the server to use a custom deploy folder (both deployments and tmp) that are owned by my user (i.e., not owned by root) * I started the server in JBoss Tools, effectively connecting to the server, and verified that the deployment scanner was updated to scan the custom deploy folder * I attempted to deploy the helloworld application by dragging the project folder to the server Once again, the deployment failed. It created the directories in the custom deploy folder, but reported the same error as above when attempting to write the files. My hypothesis is that the error message we are seeing is a veil. It's possible the failure is coming from an operation further up the chain. From changing the ownership of the installation to root, it's pretty clear that JBoss Tools is attempting to write something into the installation directory when it shouldn't be. So, the problem isn't that JBoss Tools is trying to put the files in the wrong place. The problem is that it's trying to perform a write operation in the installation sometime between when it creates the directories and when it moves the files into them. It may have something to do with the manifest file, though that's just a stab in the dark. You should be able to reproduce this on OSX since it's also a *nix operation system (though I suppose Windows also has file permission controls). -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739458#739458] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739510#739510 -------------------------------------------------------------- Btw, I think solving this problem would also solve the problem where Eclipse can't rename a file across a file system boundary (as described in this forum thread: https://community.jboss.org/thread/196086 'Publishing to JBoss 7.1 Runtime Server...' has encountered a problem). Eclipse should not be touching the root file system where JBoss AS is installed, so there would be no file system crossing. It should only be writing to the deploy locations specified in the user's home directory. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739510#739510] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739558#739558 -------------------------------------------------------------- Oh, duh. You're right, it's not m2e. The META-INF/MANIFEST.MF (from target/m2e-wtp/web-resources) just happens to be the first file the publisher is attempting to copy to the deployment directory. Anyway, I found the bug. Just as I suspected, somewhere in the org.jboss.ide.eclipse.as.core plugin, the custom tempDeployDirectory is not being respected. I found it in the worst of places, the generic copyFile() method, which is responsible for copying all the web resources to the deployment folder. copyFile() calls writeToTempFile(), which calls getTempFolder() and that's where the wrong temp folder is choosen. Here's the offending code in http://anonsvn.jboss.org/repos/jbosstools/trunk/as/plugins/org.jboss.ide.... org.jboss.ide.eclipse.as.core.server.xpl.LocalCopyCallback: protected File getTempFolder() {     File f = null;     if (tmpDeployRootFolder != null) {         f = tmpDeployRootFolder.toFile();     }     // ^^^ Bad logic     else if (server != null) {         String path = ServerConverter.getDeployableServer(server).getTempDeployFolder();         f = new File(path);     }     else {         return tempDir;     }     if (!f.exists())         f.mkdirs();     return f; } Notice that the method +first+ looks to see if the server has a temp deploy folder in the installation root (e.g., JBOSS_HOME/standalone/tmp). Of course, the JBoss AS 7 installation *does* have this folder, but it +should not+ be used if a custom tempDeployDir is specified. Only if this folder is missing (which it never will be) does this existing code honor the tempDeployDir setting. That's a bug. That explains why the JBoss Tools server is attempting to write to /usr/share/jboss-as/standalone/tmp and thus why the deployment is failing. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739558#739558] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Rob Stryker [https://community.jboss.org/people/rob.stryker] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739650#739650 -------------------------------------------------------------- I have traced it even further back, howerver, and discovered the problem lives in JBoss71Server...  That's the class where it should be returning different values for metadata vs server vs custom deployment location, and that's the file where it wasn't doing it.  The class you mention is functioning exactly as desired, but JBoss71Server was the one ignoring what should be happening. https://issues.jboss.org/browse/JBIDE-12090 https://issues.jboss.org/browse/JBIDE-12090 tracks the bug, and its progress -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739650#739650] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Dan Allen [https://community.jboss.org/people/dan.j.allen] created the discussion "Re: How do we use JBoss Tools with the JBoss AS 7 Fedora package?" To view the discussion, visit: https://community.jboss.org/message/739767#739767 -------------------------------------------------------------- Hooray!!!!!! Mission accomplished. Great job hunting this down Rob and Max. This is a nice win. I'm definitely going to showcase this integration at JAX. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/739767#739767] Start a new discussion in JBoss Tools at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]