fighting the plan
diff --git a/plan.xml b/plan.xml
index f035978..32c5173 100755
--- a/plan.xml
+++ b/plan.xml
@@ -2,38 +2,25 @@
<?xml-stylesheet type="text/xsl" href="project-plan-render.xsl"?>
<!--?xml-stylesheet type="text/xsl" href="project-plan-render.xsl"?-->
<p:plan xmlns:p="http://www.eclipse.org/project/plan" xmlns="http://www.w3.org/1999/xhtml">
- <p:release projectid="m2e" version="0.13.0"/>
+ <p:release projectid="m2e-wtp" version="0.16.0"/>
<p:introduction>
- <p>M2E provides both a framework for building Maven-centric Eclipse
- tools and set of tools and user interface elements directly
- consumable by Eclipse Users.</p>
+ <p>m2e-wtp aims at providing a tight integration between Apache Maven and Maven Integration for Eclipse (a.k.a m2e) on one hand and
+ and the Eclipse Web Tools Project (a.k.a WTP) on the other hand.
+ </p>
<div>
- <p>As a framework, M2E provides facilities to import and configure
- Maven projects in Eclipse workspace as well as APIs that allow
- m2e extensions to access Maven project metadata and participate in
- Maven project configuration and workspace build.</p>
- </div>
- <div>
- For the end user, M2E provides:
+ m2e-wtp provides a number of features designed to improve the productivity of Java EE developers using Apache Maven as their build tool :
<ul>
- <li>wizards to import existing and to create new Maven projects
- </li>
- <li>rich form-based and text-based pom.xml file editor</li>
- <li>launch configuration type to launch Maven build directly
- from Eclipse IDE
- </li>
- <li>access Maven repository index to browse repository contents
- and in various code-assist
- </li>
+ <li><strong>Project configurators :</strong> translate Maven plugin configuration to WTP settings for war, ejb, rar, app-client, ear packagings.</li>
+ <li><strong>Eclipse to Maven Project converters :</strong> maps WTP settings of existing Java EE projects to their maven plugin configuration equivalent</li>
+ <li><strong>Web resource filtering :</strong>Dynamically modifies the content of web resources at build time and instantly deploys them on a server</li>
+ <li><strong>War overlays :</strong>Shares the same web resources (images, css ...) across different web applications</li>
</ul>
</div>
- <p>Extensible JDT integration is provided by M2E as well.</p>
</p:introduction>
<p:release_deliverables>
<ul>
- <li>feature to be installed into an Eclipse IDE installation using
- an update site.
- </li>
+ <li>m2e-wtp feature</li>
+ <li>m2e-wtp SDK (source archive) feature</li>
</ul>
</p:release_deliverables>
<p:release_milestones>
@@ -41,132 +28,98 @@
<p>
Release milestones will be occurring at roughly 6 week
intervals, and will be aligned with the
- <a href="http://wiki.eclipse.org/Indigo_Simultaneous_Release">
- Indigo Simultaneous Release
+ <a href="http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan">
+ Kepler Simultaneous Release
</a>
train.
</p>
</p:preamble>
- <p:milestone date="02/07/2011" milestone="M5">
- <div>0.13.0 M5</div>
+ <p:milestone date="23/07/2012" milestone="0.16.0.M1">
+ <div>0.16.0.M1</div>
</p:milestone>
- <p:milestone date="03/14/2011" milestone="M6">
- <div>0.13.0 M6</div>
+ <p:milestone date="22/08/2012" milestone="0.16.0.RC1">
+ <div>0.16.0.RC1</div>
</p:milestone>
- <p:milestone date="05/02/2011" milestone="M7">
- <div>0.13.0 M7</div>
+ <p:milestone date="14/09/2012" milestone="0.16.0.RC2">
+ <div>0.16.0.RC2</div>
</p:milestone>
+
</p:release_milestones>
-
<p:target_environments>
- <p>M2E requires minimum Java SE 5 VM.</p>
- <p>M2E is compatible with Eclipse 3.5.2, Eclipse 3.6.2 and Eclipse
- 3.7 and is generally expected to work on each of these Eclipse
- releases respective referenced platforms with additional
- requirement of Java SE 5 or better VM.
+ <p>m2e-wtp is tested on Java 6 and Java 7, but in theory should run on Java 5 VMs,
+ as that is the highest version of Java assumed in the bundle's manifest.mf files (in the OSGi BREE heading)</p>
+ <p>m2e-wtp is compatible with Eclipse 3.6.2, 3.7.2, 3.8 and Eclipse
+ 4.2 and is generally expected to work on each of these Eclipse
+ platforms.
</p>
<p:internationalization>
- <p>All m2e user interface elements are externalized, but only
- English strings are provided as the default resource
- bundles.
+ <p>Internationalization and Localization will be supported in a future release.
+ The current user interface is displayed in English only.
</p>
</p:internationalization>
</p:target_environments>
-
<p:compatibility_with_previous_releases>
- <h3>Compatibility with Sonatype m2eclipse 0.10.x and earlier
- m2eclipse releases
- </h3>
+ <h3>Compatibility with Sonatype m2eclipse-wtp 0.15.x and previous releases</h3>
<p>
- <strong>API Contract Compatibility:</strong>
- To comply with Eclipse Foundation requirements, all m2e java package
- and extension points have been moved to org.eclipse.m2e
- namespace. No compatibility layer will be provided for consumers
- of earlier versions of m2eclipse.
+ <strong>API Contract Compatibility :</strong>
+ To comply with the Eclipse Foundation requirements, all the m2eclipse-wtp java packages
+ have been moved from org.maven.ide.eclipse.wtp to the org.eclipse.m2e.wtp
+ namespace.
+ However, all project configurator ids have been kept to ensure minimal disruption with 3rd party adopters and existing custom m2e lifecycle mappings.
</p>
<p>
<strong>Workspace Compatibility:</strong>
- No migration will be provided for workspaces created with earlier
- versions of m2eclipse. Sharing of the same workspace with m2e
- 0.13.0 and earlier versions of m2eclipse will not be supported.
- The users are expected to start with new workspace and import
- their projects using "Existing Maven Projects" import wizards.
+ No compatibility layer will be provided for non-default workspace preferences set in earlier versions of m2eclipse-wtp. However m2e-wtp default workspace settings behave the same as previous in m2eclipse-wtp.
+ </p>
+ <p>
+ <strong>Project Compatibility:</strong>
+ No compatibility layer will be provided for non-default project preferences set in earlier versions of m2eclipse-wtp. However m2e-wtp default project settings behave the same as in previous m2eclipse-wtp.
</p>
</p:compatibility_with_previous_releases>
-
<p:themes_and_priorities>
<p:preamble>
</p:preamble>
- <p:theme name="Robust build lifecycle mapping">
+ <p:theme name="Encourage community participation">
<p:committed>
<ul>
<li>
- <strong>Metadata driven lifecycle mapping.</strong>
- M2E will define lifecycle mapping metadata format and
- mechanisms to embed mapping metadata in project pom.xml
- files, share mapping metadata among multiple related
- projects and provide mapping metadata via Eclipse extension
- point.
+ <strong>Agile open source project</strong>
+ m2e-wtp, as a sub-project of m2e, is an agile open source project
+ and as such does not have feature and/or bugfix roadmap.
+ We encourage community members to come forward with ideas how to
+ improve m2e-wtp and generally plan to prioritize patches review over other m2e-wtp development activities.
</li>
</ul>
</p:committed>
- <p:proposed>
- <ul>
- <li>
- <strong>Public lifecycle mapping API.</strong>
- </li>
- </ul>
- </p:proposed>
</p:theme>
- <p:theme name="Discovery and installation of extensions">
- <p:committed>
- <ul>
- <strong>Find and install required extension.</strong>
- M2E will only support limited number of standard Maven plugins
- out of the box, while support for other Maven plugins is
- expected to be provided by thirdparty extension. M2E will
- provide discovery mechanism that will help users find and
- install extensions required to support their projects.
- </ul>
- </p:committed>
- </p:theme>
- <p:theme name="Better pom.xml editor">
- <p:committed>
- <p>TBD</p>
- </p:committed>
- </p:theme>
- <p:theme name="Stay current with Maven technologies">
+ <p:theme name="Close collaboration with the M2E and WTP projects">
<p:committed>
<ul>
<li>
- <strong>Include latest released Maven version</strong>
- Maven is an active opensource project with new release
- produced at roughly six weeks intervals. To maintain parity
- with bugfixes and new features available to command line
- Maven users, m2e will include latest Maven version available
- in time for Ingigo release. We will work with Maven core
- developers to align m2e and maven release schedules.
- </li>
+ <strong>Cross-project collaboration</strong>
+ In order to implement new maven features into m2e-wtp or fix bugs,
+ we continuously help improve both m2e's and WTP's APIs,
+ working closely with core developers of both projects,
+ by contributing patches, raising bug or enhancement requests.
+ </li>
</ul>
</p:committed>
- <p:proposed>
- <ul>
- <li>Mechanism to deliver Maven Core updates</li>
- </ul>
- </p:proposed>
</p:theme>
+ <!--
<p:theme name="Mature Eclipse.org project">
<p:committed>
<ul>
- <li>Move m2e project to Eclipse Foundation</li>
+ <li>Move m2e-wtp to Eclipse Foundation</li>
</ul>
</p:committed>
<p:proposed>
<ul>
- <li>Join "Java" eclipse distribution</li>
<li>Graduate from incubation</li>
+ <li>Join the "Java EE" Eclipse distribution for Kepler</li>
</ul>
</p:proposed>
</p:theme>
+ -->
+
</p:themes_and_priorities>
</p:plan>
