[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 added the following to our error generation due to the bad exception parameters
upstream:
{code}
+ String exceptionMsg = sme.getMessage();
+ if( "Missing element for : ''".equals(exceptionMsg)) {
+ sme = new Exception("The requested path is not found on the
remote system.", sme);
+ }
{code}
I thought we did have a verify button also but I can't seem to find a trace of it.
Will need to investigate further.
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
Affects Versions: 4.0.0.Alpha2
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 4.0.0.Beta1
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