Bug 777650 (SOA-160) - Smooks console - remove console from SOA source tree
Summary: Smooks console - remove console from SOA source tree
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-160
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Tooling, JBossESB
Version: 4.2 IR6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 IR8
Assignee: tcunning
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-20 11:46 UTC by trev
Modified: 2007-12-05 03:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-12-05 03:11:00 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-160 0 None None None Never

Description trev 2007-11-20 11:46:06 UTC
Date of First Response: 2007-11-22 10:54:59
project_key: SOA

Console is tech preview - should be in the community release but not the platform release

Comment 1 Tom Fennelly 2007-11-22 15:54:59 UTC
Will do this as soon as I get write access to https://svn.corp.jboss.com/repos/soa/

Comment 2 Mark Little 2007-11-22 16:19:09 UTC
We'll obviously need a mechanism to prevent it being pulled across from the ESB CP branch every time there's an update too.

Comment 3 Tom Fennelly 2007-11-22 18:01:59 UTC
Not as straightforward as I'd first thought... that console also contains the management components added by TomC.  Will look more closely at it in the morning, but would like to hear from TomC too before I go making changes - might hold off on actually making any changes until then.

Comment 4 Tom Fennelly 2007-11-26 12:21:31 UTC
Tom is taking over this task.  He's more familiar with the build here (the libs etc) and is better positioned than me to extract the transformation console.  Thanks Tom :-)

Comment 5 tcunning 2007-11-26 20:08:01 UTC
Don't copy over the Smooks Console files.       This change should not go back into the CP branch.


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