Today "Make Deployable" seem to only be stored locally in workspace data or together with a server.
This causes problems when importing an existing project from svn, filesystem, project examples etc. that the files that already have been marked as deployable
does not continue to be so.
Shouldn't the status of being "Deployable" be something we persist per resource/project and then pick it up when you import such a project?
(not sure if this is a duplicate, but couldn't find it)
- relates to
-
JBIDE-5856 No possibility to deploy seam examples datasource directly from JBT
- Closed