[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8508) Creating new BPEL project with an existing bpelContent dir = Facet error, the .settings dir is not created for the project
[
https://issues.jboss.org/browse/JBIDE-8508?page=com.atlassian.jira.plugin...
]
Len DiMaggio updated JBIDE-8508:
--------------------------------
Summary: Creating new BPEL project with an existing bpelContent dir = Facet error,
the .settings dir is not created for the project (was: BPEL Facet should not error
because of directories already exists when importing existing projects from disk)
Issue Type: Bug (was: Feature Request)
Description:
Screen shot and .log for the error are attached - the error was seen importing SOA-P
5.1's bpel_hello_world_header_ode quickstart.
As a result, the project is not deployable in JBDS.
Workaround:
The user must delete the project, create an empty project and import the exusting
projects files into that empty project.
was:
Screen shot and .log for the error are attached - the error was seen importing SOA-P
5.1's bpel_hello_world_header_ode quickstart.
Can the error display be made less alarming looking? Can it be a WARNING?
Creating new BPEL project with an existing bpelContent dir = Facet
error, the .settings dir is not created for the project
--------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-8508
URL: https://issues.jboss.org/browse/JBIDE-8508
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel
Affects Versions: 3.2.0.Final
Environment: Version: 4.0.0.GA Build id: v20110216-1930-H239-GA Build date:
20110216-1930
SOA-P 5.1 GA
JBoss Tools
http://download.jboss.org/jbosstools/updates/nightly/trunk/ (BPEL editor)
1.0.0.v20110217-0324-H60-Alpha1
Reporter: Len DiMaggio
Assignee: Robert (Bob) Brodt
Fix For: 3.2.1, 3.3.x
Attachments: log, Screenshot.png
Screen shot and .log for the error are attached - the error was seen importing SOA-P
5.1's bpel_hello_world_header_ode quickstart.
As a result, the project is not deployable in JBDS.
Workaround:
The user must delete the project, create an empty project and import the exusting
projects files into that empty project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira