[jbosstools-issues] [JBoss JIRA] (JBDS-2279) Investigate use of JRebel 5.0.1 in JBoss Central
Radim Hopp (JIRA)
jira-events at lists.jboss.org
Thu Oct 18 07:30:01 EDT 2012
[ https://issues.jboss.org/browse/JBDS-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radim Hopp resolved JBDS-2279.
------------------------------
Resolution: Done
Tried the scenario Max described here, changes in code were picked up by JRebel and all classes were reinitialized/reloaded.
Version of JRebel: 5.0.1.RELEASE-201207191833
JRebel also doesn't significantly interfere with other standard JBDS UI parts.
> Investigate use of JRebel 5.0.1 in JBoss Central
> ------------------------------------------------
>
> Key: JBDS-2279
> URL: https://issues.jboss.org/browse/JBDS-2279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central
> Affects Versions: 6.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Radim Hopp
> Priority: Blocker
> Fix For: 6.0.0.CR1
>
>
> Latest on update site (http://www.zeroturnaround.com/update-site/) is this:
> JRebel 5.0.1.RELEASE-201207191833
> We're not allowed to redistribute this, so when you're testing if this works with Eclipse 4.2 / JBT 4.0 / JBDS 6.0, please ensure that you record the version you're using to verify it's the same (or newer) than the version stated above.
> Should the major version change, please update the description of this JIRA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list