update towards the alpha-3 release

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@193099 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brett Leslie Porter 2005-06-23 07:26:53 +00:00
parent 9699c96631
commit 9ea44973f8
4 changed files with 82 additions and 80 deletions

View File

@ -1,20 +1,20 @@
------ ------
Release Notes - Maven 2.0 Alpha 2 Release Notes - Maven 2.0 Alpha 3
------ ------
Brett Porter Brett Porter
------ ------
13 May 2005 23 June 2005
------ ------
The Apache Maven team are proud to announce the second alpha release of Maven 2.0. The Apache Maven team are proud to announce the third alpha release of Maven 2.0.
Download it from {{http://maven.apache.org/maven2/download.html}} Download it from {{http://maven.apache.org/maven2/download.html}}
Maven is a software project management and comprehension tool. Based on the concept of a project object model Maven is a software project management and comprehension tool. Based on the concept of a project object model
(POM), Maven can manage a project's build, reporting and documentation from a central piece of information. (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
This release includes <<{{{http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&fixfor=11020} 76 bug fixes and enhancements}}>> since the This release includes <<{{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=11021} 83 bug fixes and enhancements}}>>
first release on 8 April. since the previous release on 13 May.
Maven 2.0 is a rewrite of the popular Maven application to achieve a number of goals, and to provide a stable Maven 2.0 is a rewrite of the popular Maven application to achieve a number of goals, and to provide a stable
basis to take it into the future. While it can be considered quite stable, and future versions are now expected to basis to take it into the future. While it can be considered quite stable, and future versions are now expected to
@ -23,18 +23,23 @@ Brett Porter
The main new features in this release are: The main new features in this release are:
* Basic site generation * Improved dependency management
* Improved error handling * Build profiles for environment specific settings and dependencies
* Automatic plugin updates * Finalised build lifecycle
* Published Mojo and Plugin API * Proper handling of derived dependency type such as sources, javadocs and ejb clients
* Inclusion of Ant tasks for Maven 2.0 * Beanshell plugin support
This release is expected to be much more architecturally stable, making early adoption * Improved reporting support, including internationalisation.
a possiblity. At this point, there are still only the core plugins available.
* Improvements to the Ant tasks
* Various plugin improvements
This release is very near to being feature complete, and the next release will be a feature complete beta-1.
We hope you enjoy using Maven! If you have any questions, please consult: We hope you enjoy using Maven! If you have any questions, please consult:

View File

@ -16,7 +16,8 @@
document. document.
</p> </p>
<p> <p>
Maven has also grown into a project that is building other products to help in the software development lifecycle<!--, Maven has also grown into a project that is building other products to help in the software development
lifecycle<!--,
such as the <a href="http://maven.apache.org/continuum">Continuum</a> continuous integration server -->. such as the <a href="http://maven.apache.org/continuum">Continuum</a> continuous integration server -->.
<a href="http://maven.apache.org/project/index.html">More information about the Maven Project</a>. <a href="http://maven.apache.org/project/index.html">More information about the Maven Project</a>.
</p> </p>
@ -32,13 +33,16 @@
<ul> <ul>
<li>Simple project setup that follows best practices - get a new project or module started in seconds</li> <li>Simple project setup that follows best practices - get a new project or module started in seconds</li>
<li>Consistent usage across all projects means no ramp up time for new developers coming onto a project</li> <li>Consistent usage across all projects means no ramp up time for new developers coming onto a project</li>
<li>Superior dependency management including automatic updating, dependency closures (also known as transitive dependencies)</li> <li>Superior dependency management including automatic updating, dependency closures (also known as transitive
dependencies)</li>
<li>Able to easily work with multiple projects at a time</li> <li>Able to easily work with multiple projects at a time</li>
<li>A large and growing repository of libraries and metadata to use out of the box, and arrangements in place <li>A large and growing repository of libraries and metadata to use out of the box, and arrangements in place
with the largest Open Source projects for real-time availability of their latest releases</li> with the largest Open Source projects for real-time availability of their latest releases</li>
<li>Extensible, with the ability to easily write plugins in Java or other scripting languages</li> <li>Extensible, with the ability to easily write plugins in Java or other scripting languages</li>
<li>Instant access to new features with little or no extra configuration</li> <li>Instant access to new features with little or no extra configuration</li>
<li><a href="ant-tasks.html">Ant tasks</a> for dependency management and deployment outside of Maven</li> <li>
<a href="ant-tasks.html">Ant tasks</a>for dependency management and deployment outside of Maven
</li>
</ul> </ul>
<p> <p>
The following features are available in Maven 1.0 and will be available and much improved in Maven 2.0 through The following features are available in Maven 1.0 and will be available and much improved in Maven 2.0 through
@ -57,7 +61,7 @@
<answer> <answer>
<p> <p>
You've seen You've seen
<a href="#what-is-maven">above</a> the goals that Maven aims to achieve, however there have also <a href="#what-is-maven">above</a>the goals that Maven aims to achieve, however there have also
been questions about why Maven 2.0 is rewritten from the successful Maven 1.0. In summary, the main goals of been questions about why Maven 2.0 is rewritten from the successful Maven 1.0. In summary, the main goals of
the new Maven 2.0 architecture are: the new Maven 2.0 architecture are:
</p> </p>
@ -112,7 +116,8 @@
release schedule so that new features can be obtained as they are ready and tested. release schedule so that new features can be obtained as they are ready and tested.
</p> </p>
<p> <p>
For more information, consult the <a href="roadmap.html">Road Map</a>. For more information, consult the
<a href="roadmap.html">Road Map</a>.
</p> </p>
</answer> </answer>
</faq> </faq>
@ -129,7 +134,8 @@
join the project. join the project.
</p> </p>
<p> <p>
For instructions on checking out and building Maven 2.0, see <a href="building.html">Building Maven 2.0</a>. For instructions on checking out and building Maven 2.0, see
<a href="building.html">Building Maven 2.0</a>.
</p> </p>
<p> <p>
For more information, please see For more information, please see
@ -138,6 +144,39 @@
</answer> </answer>
</faq> </faq>
<faq id="scripting-languages">
<question>What plugin languages will Maven 2.0 support? What about [insert language here]?</question>
<answer>
<p>
As of the current alpha-3 release, Maven supports pure Java, Beanshell and Marmalade. Java is the preferred
language for it's familiarity and speed, while Marmalade is preferred for porting Maven 1.x plugins, and
writing
plugins based on Ant tasks.
</p>
<p>
We get asked a lot whether Maven 2.0 will support other languages, in particular Groovy.
We will allow the use of Groovy - and virtually any other scripting
language if there is demand, or someone can commit a small amount of time to implementing a
factory for it.
</p>
<p>
We would recommend waiting for Groovy to have a 1.0 release so the API
(and language!) is stable. What we will not be doing is actively
supporting it (in terms of answering questions about how to use it)
like we currently do for Jelly in Maven 1.x.
</p>
<p>
Beanshell is more mature, and we want a language that users will find
answers for when they look, and that when they find bugs, it is
clearly defined where they actually are.
</p>
<p>
We may consider emphasising a different language if there are compelling technical reasons
for doing so - if you have a suggestion, feel free to contact the development list.
</p>
</answer>
</faq>
<faq id="get-help"> <faq id="get-help">
<question>Where do I get help with Maven 2.0?</question> <question>Where do I get help with Maven 2.0?</question>
<answer> <answer>
@ -148,13 +187,13 @@
</p> </p>
<p> <p>
You can also join us on IRC at You can also join us on IRC at
<code>irc.codehaus.org</code> on <code>irc.codehaus.org</code>on
<code>#maven2</code>. This is available both <code>#maven2</code>. This is available both
over over
<a href="irc://irc.codehaus.org/#maven2">IRC</a> and <a href="irc://irc.codehaus.org/#maven2">IRC</a>and
<a href="http://irc.codehaus.org/">HTTP</a> for those behind firewalls (enter <a href="http://irc.codehaus.org/">HTTP</a>for those behind firewalls (enter
<code>#maven2</code> in the <code>#maven2</code>in the
<i>Channel</i> box). <i>Channel</i>box).
</p> </p>
<p> <p>
Please remember that it is a preview release, so please be patient with features that are not yet implemented, Please remember that it is a preview release, so please be patient with features that are not yet implemented,

View File

@ -1,38 +1,18 @@
<?xml version="1.0"?> <?xml version="1.0"?>
<faqs id="General FAQ"> <faqs id="General FAQ">
<part id="General"> <part id="General">
<faq id="scripting-languages"> <faq id="scope-provided">
<question>What plugin languages will Maven 2.0 support? What about [insert language here]?</question> <question>How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</question>
<answer> <answer>
<p> <p>
As of the Technology Preview, Maven supports pure Java and Marmalade. Java is the preferred language The scope you should use for this is
for it's familiarity and speed, while Marmalade is preferred for porting Maven 1.x plugins, and writing <code>provided</code>. This indicates to Maven that the dependency will be
plugins based on Ant tasks. provided at run time by its container or the JDK, for example.
</p> </p>
<p> <p>
In alpha-2, Beanshell support is planned. We currently view this as the best candidate to be the primary Dependencies with this scope will not be passed on transitively, nor will they be bundled in an package such
plugin scripting language in Maven 2.0. as
</p> a WAR, or included in the runtime classpath.
<p>
We get asked a lot whether Maven 2.0 will support other languages, in particular Groovy.
We will allow the use of Groovy - and virtually any other scripting
language if there is demand, or someone can commit a small amount of time to implementing a
factory for it.
</p>
<p>
We would recommend waiting for Groovy to have a 1.0 release so the API
(and language!) is stable. What we will not be doing is actively
supporting it (in terms of answering questions about how to use it)
like we currently do for Jelly in Maven 1.x.
</p>
<p>
Beanshell is more mature, and we want a language that users will find
answers for when they look, and that when they find bugs, it is
clearly defined where they actually are.
</p>
<p>
We may consider emphasising a different language if there are compelling technical reasons
for doing so - if you have a suggestion, feel free to contact the development list.
</p> </p>
</answer> </answer>
</faq> </faq>

View File

@ -22,34 +22,12 @@
We will continue with the successful technique from Maven 1.0 of making plugins available on a separate We will continue with the successful technique from Maven 1.0 of making plugins available on a separate
release schedule so that new features can be obtained as they are ready and tested. release schedule so that new features can be obtained as they are ready and tested.
</p> </p>
<subsection name="Maven 2.0 alpha 3">
<p>
<i>Expected Release: </i> mid-June 2005
</p>
<p>
<i>Aims and features:</i> This release is aims to finalise the major features of Maven 2.0.
(<b>Note:</b> depending on the quality of this release, it may be labelled as beta 1, with the following
release being beta 2).
</p>
<ul>
<li>Remaining planned dependency management features - conflict management and version mediation</li>
<li>Outstanding issues for the build lifecycle</li>
<li>Build profiles for different environments</li>
<li>Improved site and report functionality</li>
<li>Multiple project aggregation features</li>
<li>Plugin development to meet Maven 1.0 functionality will be underway</li>
<li>Release assistance</li>
<li>Miscellaneous feature updates</li>
<li>Bugfixes</li>
<li>Preliminary Beanshell Mojo support</li>
</ul>
</subsection>
<subsection name="Maven 2.0 beta 1"> <subsection name="Maven 2.0 beta 1">
<p> <p>
<i>Expected Release: </i> mid-July 2005 <i>Expected Release:</i>mid-July 2005
</p> </p>
<p> <p>
<i>Aims and features:</i> This should be feature complete and mostly stable. There are expected to be <i>Aims and features:</i>This should be feature complete and mostly stable. There are expected to be
bug fixes and cosmetic changes, but no new major features beyond this release. bug fixes and cosmetic changes, but no new major features beyond this release.
</p> </p>
<ul> <ul>
@ -61,10 +39,10 @@
</subsection> </subsection>
<subsection name="Maven 2.0 Final"> <subsection name="Maven 2.0 Final">
<p> <p>
<i>Expected Release: </i> early August 2005, following a release candidate <i>Expected Release:</i>early August 2005, following a release candidate
</p> </p>
<p> <p>
<i>Aims and features:</i> Final release, a suitable replacement for Maven 1.1 as the stable release for new <i>Aims and features:</i>Final release, a suitable replacement for Maven 1.1 as the stable release for new
projects. projects.
</p> </p>
<ul> <ul>
@ -74,13 +52,13 @@
</subsection> </subsection>
<subsection name="Maven 2.0.x"> <subsection name="Maven 2.0.x">
<p> <p>
<i>Aims and features:</i> Bugfixes found in the Maven core will be released as interim updates leading up <i>Aims and features:</i>Bugfixes found in the Maven core will be released as interim updates leading up
to the Maven 2.1 development stream. to the Maven 2.1 development stream.
</p> </p>
</subsection> </subsection>
<subsection name="Maven 2.1"> <subsection name="Maven 2.1">
<p> <p>
<i>Aims and features:</i> Features to be added after the July freeze on Maven 2.0 will be slated for a 2.1 <i>Aims and features:</i>Features to be added after the July freeze on Maven 2.0 will be slated for a 2.1
release later in 2005. release later in 2005.
</p> </p>
</subsection> </subsection>