| Milestone release OTDT 1.4.0 M2 [message #566921] |
Mon, 14 December 2009 15:03 |
 Stephan Herrmann
Messages: 1853
Registered: July 2009 |
Senior Member |
|
|
(cross-post to otj-users (old) and eclipse.objectteams (new))
A new milestone release has been uploaded to the server:
Object Teams Development Tooling 1.4.0 Milestone 2
This release matches the very recent Eclipse 3.6.0 Milestone 4,
which is available from this update site:
http://download.eclipse.org/eclipse/updates/3.6milestones
or as a full download from:
http://download.eclipse.org/eclipse/downloads/drops/S-3.6M4- 200912101301/index.php
The matching OTDT update site is:
http://www.objectteams.org/distrib/otdt-updates-1.4
The headlines for this release are
* Significant improvements in standard refactorings to respect OT/J rules
When performing standard JDT refactorings the OTDT additionally
checks whether OT/J specific rules would be violated or whether
unwanted behavioral changes may result due to the OT/J semantics.
Some of these enhancements had been lost when moving from Eclipse
3.0 to 3.2, due to a lack of maintainability of the copy&pasted
based solution.
Now Johannes Gebauer has re-implemented the adaptation of JDT
refactorings using OT/Equinox, resulting in a solution that is
much more complete *and* better maintainable.
These improvements are witnessed by approx. 70 additional JUnit
test (passing).
* First OT/J specific refactorings Extract Callin and Inline Callin
In addition to the adaptation of existing refactorings Johannes
has implemented the first OT/J specific refactorings. Similar to
how PullUp/PushDown refactorings can be used to move code along
the inheritance hierarchy Extract-/Inline Callin can be used for
moving code along the playedBy axis. His thesis sketches some more
refactorings which in concert will provide comprehensive support
for morphing POJOs into teams/roles and back again.
Documentation for these brand new refactorings will be published
shortly.
* Remote debugging of OT/J applications
In order to debug an OT/J application that was launched outside
Eclipse, the debugger has to be told that OT/J extensions should
be applied. This is done using a new checkbox in the launch
configuration tab for connecting to a remote application. It
consistently resembles the way how OT/J is enabled when launching
applications from within Eclipse.
This improvement is documented in the cumulative New&Noteworthy at
http://www.objectteams.org/distrib/new_in_1.4.html#debug
A few more enhancements and bug fixes are listed here:
http://www.objectteams.org/distrib/tickets_OTDT_1.4.0M2.html
Updating using p2 is gradually becoming routine, except that shared
installations using the -configuration switch require a 2-step update
1. update the base installation
2. update the specific configuration.
This process appears to be somewhat fragile. Please post here if you
have convenient and reliable steps how to perform such an update.
Thanks.
cheers,
Stephan
|
|
|
Powered by
FUDForum. Page generated in 0.03003 seconds
] 
Search
Help
Register
Login
Home
