[
https://issues.jboss.org/browse/JBIDE-13830?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-13830:
-------------------------------------
If anything, number 2 is a new bug in wtp behavior. WTP now ignores meta files like
.project whereas it did not used to. So a custom virtual component which explicitly
exposes a .project file will have this ignored against their wishes.
However, the unit test was made after SR1, and SR1 included this change in behaviour. The
difference in behaviour is only noticable when running tests against pre-SR1, which the
test was never designed to run against.
So... if anything, the new behavior in wtp is a bug, and this should not be documented as
a reason to use sr2 for 2 reasons: first, the change was made in sr1, so there's no
change between sr1 and sr2, and the second reason is that hte new behaviour is kinda crap
;)
document reasons for using Eclipse Juno SR2 instead of earlier
version on
www.jboss.org install page for JBT 4.0.1
------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13830
URL:
https://issues.jboss.org/browse/JBIDE-13830
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite, website
Affects Versions: 4.0.1.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.0.1.Final
When we release JBT 4.0.1, we should update
https://www.jboss.org/tools/download/installation/update_4_0#installon420421 to include a
blurb about why we encourage users to use Juno SR2 instead of R or SR1.
Reasons include:
a) performance patch, JBIDE-13326 / JBIDE-13335
b) WTP bug / behaviour change between WTP 3.3.0 & 3.3.1: JBIDE-13821
--
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