[jbosstools-issues] [JBoss JIRA] (JBIDE-12585) remote publishing gives weird error when not pointing to exact expected directory layout
[
https://issues.jboss.org/browse/JBIDE-12585?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12585:
-------------------------------------
I've discovered the cause of the strange error message. IT's simply bad code up in
RSE. The method throwing the exception passes in empty strings:
//TODO better throw SENFE at the place where we know what element and operation is
done
messageException = new SystemElementNotFoundException("", "");
//$NON-NLS-1$ //$NON-NLS-2$
This is clearly very useful ;) I can try to improve this to at least indicate that the
file is not found in some way.
remote publishing gives weird error when not pointing to exact
expected directory layout
----------------------------------------------------------------------------------------
Key: JBIDE-12585
URL: https://issues.jboss.org/browse/JBIDE-12585
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
setup an ASx server to deploy remotely (i.e. on openshift) and point to a directory that
*does not* have standalone/deployments already in it - then at publish time you get errors
like:
"failed to copy to
/home/max/work/standalone/deployments/test.war/META-INF/MANIFEST.MF on host
neo6.gva.redhat.com
Missing element for : ''"
Not very informative.
If you fix the server to point to a directory that have standalone/deployments already
things starts working again.
The error should be more informative - optimally ask the user if the missing directories
should be made ?
Didnt we at some point have a "verify" button for the remote setup to check if
directories were present?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira