Bug 779410 (SOA-1798) - JBDS - Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)
Summary: JBDS - Full Publish of ESB projects does not redeploy and also can't deploy a...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1798
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling
Version: 5.0.0 ER6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.0 GA
Assignee: Brian Fitzpatrick
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-06 19:32 UTC by Len DiMaggio
Modified: 2010-07-21 12:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-21 12:40:26 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1798 0 Major Closed JBDS - Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (dep... 2013-02-16 16:04:11 UTC

Description Len DiMaggio 2010-01-06 19:32:05 UTC
Date of First Response: 2010-02-09 00:42:00
project_key: SOA

Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)

Comment 1 Len DiMaggio 2010-01-06 19:32:36 UTC
Link: Added: This issue depends JBIDE-5597


Comment 2 David Le Sage 2010-02-09 05:42:00 UTC
Here is the draft comment for the Release Notes:


Using the Full Publish option in the JBossAS view to republish a jboss-esb.xml project does
not work.

To work around this issue, remove the project from the server and then add it again.


Comment 3 Brian Fitzpatrick 2010-02-10 15:08:04 UTC
Perfect

Comment 4 Brian Fitzpatrick 2010-03-09 15:04:21 UTC
Bumping to unscheduled. Didn't make it into SOA-P 5 tooling.

Comment 5 Brian Fitzpatrick 2010-07-21 12:40:25 UTC
This was resolved with  JBIDE-5597 back in January with JBT 3.1/JBDS 3.


Note You need to log in before you can comment on or make changes to this bug.