Apache
/
maven
mirror of https://github.com/apache/maven.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
maven-site/src/site/apt/release-notes.apt
View File

@ -1,20 +1,20 @@
------
Release Notes - Maven 2.0 Alpha 2
Release Notes - Maven 2.0 Alpha 3
------
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}}
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.
This release includes <<{{{http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&fixfor=11020} 76 bug fixes and enhancements}}>> since the
first release on 8 April.
This release includes <<{{{http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=11021} 83 bug fixes and enhancements}}>>
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
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:
* 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
a possiblity. At this point, there are still only the core plugins available.
* Improved reporting support, including internationalisation.
* 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:

49
maven-site/src/site/fml/about.fml
View File

@ -16,7 +16,8 @@
document.
</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 -->.
<a href="http://maven.apache.org/project/index.html">More information about the Maven Project</a>.
</p>
@ -32,13 +33,16 @@
<ul>
<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>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>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>
<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><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>
<p>
The following features are available in Maven 1.0 and will be available and much improved in Maven 2.0 through
@ -112,7 +116,8 @@
release schedule so that new features can be obtained as they are ready and tested.
</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>
</answer>
</faq>
@ -129,7 +134,8 @@
join the project.
</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>
For more information, please see
@ -138,6 +144,39 @@
</answer>
</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">
<question>Where do I get help with Maven 2.0?</question>
<answer>

36
maven-site/src/site/fml/general.fml
View File

@ -1,38 +1,18 @@
<?xml version="1.0"?>
<faqs id="General FAQ">
<part id="General">
<faq id="scripting-languages">
<question>What plugin languages will Maven 2.0 support? What about [insert language here]?</question>
<faq id="scope-provided">
<question>How do I prevent including JARs in WEB-INF/lib? I need a "compile only" scope!</question>
<answer>
<p>
As of the Technology Preview, Maven supports pure Java 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.
The scope you should use for this is
<code>provided</code>. This indicates to Maven that the dependency will be
provided at run time by its container or the JDK, for example.
</p>
<p>
In alpha-2, Beanshell support is planned. We currently view this as the best candidate to be the primary
plugin scripting language in Maven 2.0.
</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.
Dependencies with this scope will not be passed on transitively, nor will they be bundled in an package such
as
a WAR, or included in the runtime classpath.
</p>
</answer>
</faq>

22
maven-site/src/site/xdoc/roadmap.xml
View File

@ -22,28 +22,6 @@
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.
</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">
<p>
<i>Expected Release:</i>mid-July 2005