blob: be57d726bc1485f195560652ef5c22c9007379e6 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" name="Project Name" xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<release projectid="tools.ajdt" version="2.0" />
<introduction>
<html:div>
<html:p>
AJDT released 2.0.0 to coincide with Eclipse's Galileo release in late June. There are two streams,
of this version, one for Eclipse 3.4, with version 2.0.0.e34x-*, and one for Eclipse 3.5 with version 2.0.0.e35x-*.
These two streams are maintained as separate branches in CVS. Because of AJDT's tight integration with JDT,
the Eclipse 3.4 stream will not install in Eclipse 3.5 and vice versa. Excepting these differences,
the two streams use the same code base and have the same feature set. The recent 2.0.1 release is the last
scheduled version targeting the Eclipse 3.4 stream. There will be no more changes to this stream unless a
critical bug is discovered and fixed. We are planning to release an AJDT version for the Eclipse 3.6 stream
to coincide with the Helios release in June 2010, and we will begin to release development snapshots of this
stream in early 2010.
</html:p>
</html:div>
</introduction>
<release_deliverables>
<html:div>
<html:p>
AJDT includes 6 plugins from two other EPL Eclipse.org projects:
<html:ul>
<html:li>
The
<html:a
href="http://www.eclipse.org/projects/project-plan.php?projectid=tools.aspectj">AspectJ project</html:a>
contributes three plugins.
These plugins are
<html:em>org.aspectj.runtime</html:em>
, which contains the AspectJ runtime,
<html:em>org.aspectj.ajde</html:em>
, which contains AspectJ support for integrating with a
development environment,
and
<html:em>org.aspectj.weaver</html:em>
, which contains the AspectJ weaver and compiler.
</html:li>
<html:li>
The
<html:a
href="http://www.eclipse.org/equinox/incubator/aspects/index.php">Equinox Aspects project</html:a>
, part of the Eqinox Incubator also contributes three plugins.
These are
<html:em>org.eclipse.equinox.weaving.aspectj
</html:em>
, which contains the equinox weaving service,
<html:em>org.eclipse.equinox.weaving.hook
</html:em>
, which contains the OSGi framework extension for the weaving
service to plug in, and
<html:em>org.eclipse.equinox.weaving.source
</html:em>
, which contains Equinox Aspects source code.
</html:li>
</html:ul>
</html:p>
</html:div>
</release_deliverables>
<release_milestones>
<preamble>
<html:div>Service releases of AJDT are released on an approximately 3 month schedule.</html:div>
</preamble>
<milestone date="01/05/2010" milestone="2.0.2">
<html:div>Service refresh of AJDT for the 3.5 stream</html:div>
</milestone>
<milestone date="03/20/2010" milestone="2.0.3">
<html:div>Service refresh of AJDT for the 3.5 stream.
First stable development release targeting Eclipse 3.6. This is meant for early adopters,
specifically for those at EclipseCon. The 3.5 and 3.6 streams will be largely similar
although some functionality in the 3.6 may not be available yet.</html:div>
</milestone>
<milestone date="06/30/2010" milestone="2.0.4">
<html:div>First public release of the 3.6 stream and service refresh of the 3.5 stream.</html:div>
</milestone>
<milestone date="09/30/2010" milestone="2.0.4">
<html:div>Final scheduled release of the 3.5 stream and service refresh of the 3.6 stream.</html:div>
</milestone>
<postamble>
<html:div></html:div>
</postamble>
</release_milestones>
<target_environments>
<html:div>AJDT 2.0.0.e34x-* requires Eclipse 3.4 and AJDT 2.0.0.e35x-* requires Eclipse 3.5. As such, AJDT has the same JRE requirements as Eclipse.</html:div>
<internationalization>
<html:div>English language bundles are available for many AJDT messages, but they have not been translated.
</html:div>
</internationalization>
</target_environments>
<compatibility_with_previous_releases>
<html:div>ADJT versions are designed to be backwards compatible with older versions of the same stream. However, since different streams
run on different Eclipse versions, there is no compatibility between streams, even though the feature sets are largely the same.</html:div>
</compatibility_with_previous_releases>
<themes_and_priorities>
<preamble>
<html:div>Our current focus is three-fold: Intertype declaration
support, IDE support for load-time weaving, and crosscutting model
support across projects and binaries. These themes are generated
from user requests in the community. As such, we want
to maintain flexibility and put effort into new themes if they are
coherently generated from the community.
</html:div>
</preamble>
<theme name="Intertype Declaration support (ITD)">
<description>
<html:p>
Third party projects such as <html:a href="http://sringsource.org/roo">ROO</html:a> are pushing the
limits of ITD functionality both in the compiler and the editor. Since this is a highly visible project
with many potential users, we would like to encourage its adoption by facilitating the ITD editor support
that it requires. This include facility for ITD-aware content assist, reconciling, refactoring, searching
and navigation.
</html:p>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwords&amp;short_desc=[itd]+[plan]&amp;product=AJDT&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</committed>
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=256312%2C262969%2C273334%2C273335%2C273914%2C274608&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</proposed>
</theme>
<theme name="IDE support for Load Time Weaving (LTW)">
<description>
<html:p>
Currently, aspects applied to a project through LTW are not visible in the
editor in the standard ways that compile time aspects are. These
include
gutter annotations and entries in the crosscutting view. Because there is
no editing support, using LTW can be time consuming and
error-prone. We will
explore ways to gather and display LTW information to the programmer while
editing.
</html:p>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwords&amp;short_desc=[ltw]+[plan]&amp;product=AJDT&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</committed>
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwords&amp;short_desc=[ltw]+[plan]&amp;product=AJDT&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</proposed>
</theme>
<theme
name="Crosscutting model support across projects and binaries (model)">
<description>
<html:p>
Provide support for navigation and across the aspect path and in path.
</html:p>
</description>
<committed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwords&amp;short_desc=[handles]+[plan]&amp;product=AJDT&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;bug_status=VERIFIED&amp;bug_status=CLOSED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</committed>
<proposed
bugzilla="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwords&amp;short_desc=[handles]+[plan]&amp;product=AJDT&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;status_whiteboard_type=allwordssubstr&amp;status_whiteboard=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">
</proposed>
</theme>
</themes_and_priorities>
</plan>