[
https://jira.jboss.org/jira/browse/JBIDE-3079?page=com.atlassian.jira.plu...
]
Denny Xu commented on JBIDE-3079:
---------------------------------
This issue is because when creating a ESB project, one property is saved as persistent
property into the workspace, so if we copy the project to another workspace and deploying,
the saved
persistent property is lost and can not the the "esbcontent" folder name, so the
error occur.
So far, the issue has not been completely resolved, if the user create an ESB project
without changing the "esbcontent" folder, and then import the project into other
workspace, the deployment works, but if the "esbcontent" folder is changed, the
deployment would not work, so more work need to be done for this issue, I will work on it
and try to resolved it completely.
Deployment does not work for the ESB project which is imported from
other workspace
-----------------------------------------------------------------------------------
Key: JBIDE-3079
URL:
https://jira.jboss.org/jira/browse/JBIDE-3079
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.alpha
Reporter: Denny Xu
Assignee: Denny Xu
Fix For: 3.0.0.beta1
When I launch jboss tools with a brand new workspace and import a ESB project from an old
workspace, then trying to deploy the project, it get a NullPointerException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira