Author: vsiveton
Date: Sat Aug 1 12:18:27 2009
New Revision: 799850
URL: http://svn.apache.org/viewvc?rev=799850&view=rev
Log:
o fixed links due to linkcheck report
o added some license header
o added netbeans images from website
Added:
maven/site/trunk/src/site/resources/guides/mini/
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Context_Menu.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Generate_Site.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Open_Project.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Project_Opened.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refresh_Project.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refreshed_Context_Menu.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Build_Main_Project.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Clean_Main_Project.png
(with props)
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Window_Files.png
(with props)
Modified:
maven/site/trunk/src/site/apt/guides/development/guide-building-m2.apt
maven/site/trunk/src/site/apt/guides/index.apt
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-resolution.apt
maven/site/trunk/src/site/apt/guides/mini/guide-encryption.apt
maven/site/trunk/src/site/apt/release-notes.apt.vm
maven/site/trunk/src/site/xdoc/docs-required.xml
Modified: maven/site/trunk/src/site/apt/guides/development/guide-building-m2.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/development/guide-building-m2.apt?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/development/guide-building-m2.apt
(original)
+++ maven/site/trunk/src/site/apt/guides/development/guide-building-m2.apt Sat
Aug 1 12:18:27 2009
@@ -4,9 +4,29 @@
Brett Porter
Jason van Zyl
------
- January 2008
+ 2009-08-01
------
+~~ Licensed to the Apache Software Foundation (ASF) under one
+~~ or more contributor license agreements. See the NOTICE file
+~~ distributed with this work for additional information
+~~ regarding copyright ownership. The ASF licenses this file
+~~ to you under the Apache License, Version 2.0 (the
+~~ "License"); you may not use this file except in compliance
+~~ with the License. You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing,
+~~ software distributed under the License is distributed on an
+~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+~~ KIND, either express or implied. See the License for the
+~~ specific language governing permissions and limitations
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/doxia/references/apt-format.html
+
Building Maven
* Why would I want to build Maven?
@@ -158,7 +178,7 @@
directory you specified as <<<M2_HOME>>> above.
If you have any problems or get any failures during the run, please report
them to the
- {{{/mail-lists.html} Maven Developers List}}.
+ {{{../../mail-lists.html} Maven Developers List}}.
For more information, consult the project help in the Ant build file.
Modified: maven/site/trunk/src/site/apt/guides/index.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/index.apt?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/index.apt (original)
+++ maven/site/trunk/src/site/apt/guides/index.apt Sat Aug 1 12:18:27 2009
@@ -4,9 +4,29 @@
Jason van Zyl
Eric Redmond
------
- 18 October 2006
+ 2009-08-01
------
+~~ Licensed to the Apache Software Foundation (ASF) under one
+~~ or more contributor license agreements. See the NOTICE file
+~~ distributed with this work for additional information
+~~ regarding copyright ownership. The ASF licenses this file
+~~ to you under the Apache License, Version 2.0 (the
+~~ "License"); you may not use this file except in compliance
+~~ with the License. You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing,
+~~ software distributed under the License is distributed on an
+~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+~~ KIND, either express or implied. See the License for the
+~~ specific language governing permissions and limitations
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/doxia/references/apt-format.html
+
Documentation
* Getting Started with Maven
@@ -113,13 +133,13 @@
* {{{./mini/guide-webapp.html}Webapps}}
* {{{./mini/guide-using-extensions.html}Using Extensions}}
-
+
* {{{./mini/guide-building-for-different-environments.html}Building For
Different Environments with Maven 2}}
* {{{./mini/guide-using-toolchains.html}Using Toolchains}}
-
+
* {{{./mini/guide-encryption.html} Encrypting passwords in settings.xml}}
-
+
** Testing
@@ -180,8 +200,6 @@
* {{{../settings.html}Settings Overview}}
({{{../ref/current/maven-settings/settings.html}Technical Settings Descriptor}})
- * {{{../encryption.html}Password Encryption}}
-
* {{{../plugins/index.html}Core Plug-ins List}}
* {{{../developers/mojo-api-specification.html}Mojo API}}
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
---
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt
(original)
+++
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-prefix-mapping.apt
Sat Aug 1 12:18:27 2009
@@ -3,8 +3,28 @@
---
John Casey
---
- 30-July-2005
- ---
+ 2009-08-01
+ ------
+
+~~ Licensed to the Apache Software Foundation (ASF) under one
+~~ or more contributor license agreements. See the NOTICE file
+~~ distributed with this work for additional information
+~~ regarding copyright ownership. The ASF licenses this file
+~~ to you under the Apache License, Version 2.0 (the
+~~ "License"); you may not use this file except in compliance
+~~ with the License. You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing,
+~~ software distributed under the License is distributed on an
+~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+~~ KIND, either express or implied. See the License for the
+~~ specific language governing permissions and limitations
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/doxia/references/apt-format.html
Introduction to Plugin Prefix Resolution
@@ -139,7 +159,7 @@
of <<<clean>>>, I can override the usage of the <<<maven-clean-plugin>>> when
<<<clean:clean>>> is invoked.
- <<NOTE2:>> For more information on <<<settings.xml>>>, see \[{{{1}1}}\].
+ <<NOTE2:>> For more information on <<<settings.xml>>>, see \[{{{a1}1}}\].
*Resources
Modified:
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-resolution.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-resolution.apt?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
---
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-resolution.apt
(original)
+++
maven/site/trunk/src/site/apt/guides/introduction/introduction-to-plugin-resolution.apt
Sat Aug 1 12:18:27 2009
@@ -3,8 +3,28 @@
---
John Casey
---
- 14-Nov-2005
- ---
+ 2009-08-01
+ ------
+
+~~ Licensed to the Apache Software Foundation (ASF) under one
+~~ or more contributor license agreements. See the NOTICE file
+~~ distributed with this work for additional information
+~~ regarding copyright ownership. The ASF licenses this file
+~~ to you under the Apache License, Version 2.0 (the
+~~ "License"); you may not use this file except in compliance
+~~ with the License. You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing,
+~~ software distributed under the License is distributed on an
+~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+~~ KIND, either express or implied. See the License for the
+~~ specific language governing permissions and limitations
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/doxia/references/apt-format.html
Introduction: How Maven Resolves Plugins
@@ -15,9 +35,9 @@
provides the implicit ability to instantly take advantage of new plugin
releases.
However, it also means that plugin information must be resolved at build
time, which
can be a complex task.
-
+
This document will detail the mechanism used to resolve plugin information.
-
+
*Referencing Plugins
Maven 2.0 brings with it added flexibility for referencing plugins and their
mojos.
@@ -26,28 +46,28 @@
in addition to the original mechanism of referencing a plugin by its
shorthand prefix
and a goal, Maven can also process plugin and mojo references that
concretely specify
groupId, artifactId, and optionally, version.
-
+
Most users will have little difficulty using Maven as before, referencing
plugins by
their prefix. However, with the introduction of the build lifecycle - and
mojo bindings
to that lifecycle - it is critical that lifecycle mappings be able to refer
to a mojo
in an unambiguous way. In fact, when dealing with lifecycle mappings, it's
illegal to
specify a mojo using its plugin-prefix. This helps Maven avoid the case
where the 'jar'
- lifecycle behaves differently on two users' machines, simply due to their
local Maven
+ lifecycle behaves differently on two users' machines, simply due to their
local Maven
configurations. As a side effect of this requirement, users also have the
option to
specify plugins and mojos in this way from the command line.
-
+
For clarity, the following are the three ways to reference a mojo from the
command line.
These will all result in the clean mojo of the maven-clean-plugin being
invoked:
-
+
+---+
mvn org.apache.maven.plugins:maven-clean-plugin:2.0:clean
mvn org.apache.maven.plugins:maven-clean-plugin:clean
mvn clean:clean
+---+
- By contrast, only the following are valid mojo references from inside a
lifecycle mapping
+ By contrast, only the following are valid mojo references from inside a
lifecycle mapping
definition:
-
+
+---+
org.apache.maven.plugins:maven-clean-plugin:2.0:clean
org.apache.maven.plugins:maven-clean-plugin:clean
@@ -56,44 +76,44 @@
<<NOTE:>> It's probably bad form to pin a plugin reference to a specific
version inside
a lifecycle mapping definition, since this prevents the user from taking
advantage of
plugin updates.
-
+
*Resolving Plugin Information
- Since users have the ability to reference a plugin by its groupId and
artifactId <<without>>
- a version, Maven must have the ability to resolve the plugin's version given
these other
- two attributes. However, since users can also refer to a plugin by its
prefix, Maven must
- also have the ability to resolve a plugin by this prefix alone - including
resolution of
- the plugin's version. To handle these two scenarios, Maven employs a
two-stage process for
+ Since users have the ability to reference a plugin by its groupId and
artifactId <<without>>
+ a version, Maven must have the ability to resolve the plugin's version given
these other
+ two attributes. However, since users can also refer to a plugin by its
prefix, Maven must
+ also have the ability to resolve a plugin by this prefix alone - including
resolution of
+ the plugin's version. To handle these two scenarios, Maven employs a
two-stage process for
resolving plugin information.
-
+
**Resolving <<<groupId>>> and <<<artifactId>>> for a Plugin
Maven's approach to resolving a plugin's groupId and artifactId given its
prefix is actually
- relatively simple. The user can specify a set of plugin groupId's to be
searched. Using
+ relatively simple. The user can specify a set of plugin groupId's to be
searched. Using
repository metadata for each configured groupId, Maven will search for
plugin prefix mappings
- using the process detailed in \[{{{1}1}}\].
-
+ using the process detailed in \[{{{a1}1}}\].
+
**Resolving a Plugin's Version
-
- When a plugin's groupId and artifactId are known, but its version is still
unknown,
+
+ When a plugin's groupId and artifactId are known, but its version is still
unknown,
Maven will resolve that plugin's version using a variety of sources. It will
check,
in order, the following:
-
+
[[1]] <the project's POM>
-
+
This includes all plugins specified in the \<build\> section; this is
intuitive.
However, since all plugin specifications in the POM are still
generally a better
source of information than reverting to external sources, <<the
\<pluginManagement\>
- section will also be searched.>>
-
+ section will also be searched.>>
+
<<NOTE:>> Checking of the \<pluginManagement\> section is new for
Maven 2.0.1.
-
+
[[2]] <the plugin registry>
-
+
This configuration file, usually located in <<<plugin-registry.xml>>>
within the
$HOME/.m2 directory, is disabled by default. To enable it, add the
following
section to the <<<settings.xml>>> file (also within $HOME/.m2):
-
+
+---+
<settings>
...
@@ -105,39 +125,39 @@
The plugin registry will maintain a mapping of {groupId, artifactId}
for a plugin
to the version to be used. It will also maintain a record of the last
time the
plugin was checked for updated versions; the configuration for when to
check
- for updated versions; and a list of rejected versions of the plugin
which are not
+ for updated versions; and a list of rejected versions of the plugin
which are not
to be used. If an updated version is found which has not yet been
rejected, the
plugin version manager will ask the user whether to use this version.
The user
can reject the version for now or always, or accept it for now or
always. If
prompting is disabled (batch mode), the plugin registry can be
configured with
a default answer to this question.
-
- See \[{{{2}2}}\] for more information on the plugin registry.
-
- See \[{{{3}3}}\] for more information on the <<<settings.xml>>> file.
+
+ See \[{{{a2}2}}\] for more information on the plugin registry.
+
+ See \[{{{a3}3}}\] for more information on the <<<settings.xml>>> file.
[[3]] <LATEST version metadata>
-
+
This is published each time a Maven plugin is deployed or installed.
It is simply
- a pointer to the latest published version of the plugin. It differs
from the
+ a pointer to the latest published version of the plugin. It differs
from the
SNAPSHOT metadata in that it is always present, regardless of the
project's version.
-
+
If you use the plugin registry, you can disable this check.
-
+
[[4]] <RELEASE version metadata>
-
- Since the LATEST metadata is always published, it obsoletes this check
when #3 is
- enabled. However, RELEASE metadata checking is still important in
order to support
+
+ Since the LATEST metadata is always published, it obsoletes this check
when #3 is
+ enabled. However, RELEASE metadata checking is still important in
order to support
legacy plugin-releases, where the LATEST metadata has not been
published. This check
can also be useful if the LATEST metadata check has been disabled.
This might be used
instead of LATEST metadata if the user only wants to use supported,
released plugin
versions.
-
+
[]
-
+
If all of the above resolution methods fail, the plugin cannot be located
and an exception
is thrown, stopping the build.
-
+
*Resources
{1}. {{{./introduction-to-plugin-prefix-mapping.html}Introduction to the
Plugin Prefix Mapping}}.
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-encryption.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-encryption.apt?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-encryption.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-encryption.apt Sat Aug 1
12:18:27 2009
@@ -3,64 +3,84 @@
-----
Oleg Gusakov
-----
- 10 February 2009
- -----
+ 2009-08-01
+ ------
+
+~~ Licensed to the Apache Software Foundation (ASF) under one
+~~ or more contributor license agreements. See the NOTICE file
+~~ distributed with this work for additional information
+~~ regarding copyright ownership. The ASF licenses this file
+~~ to you under the Apache License, Version 2.0 (the
+~~ "License"); you may not use this file except in compliance
+~~ with the License. You may obtain a copy of the License at
+~~
+~~ http://www.apache.org/licenses/LICENSE-2.0
+~~
+~~ Unless required by applicable law or agreed to in writing,
+~~ software distributed under the License is distributed on an
+~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+~~ KIND, either express or implied. See the License for the
+~~ specific language governing permissions and limitations
+~~ under the License.
+
+~~ NOTE: For help with the syntax of this file, see:
+~~ http://maven.apache.org/doxia/references/apt-format.html
{Password Encryption}
[[1]] {{{Introduction}Introduction}}
- [[2]] {{{How_to_create_master_password}How to create a master password}}
+ [[2]] {{{How_to_create_a_master_password}How to create a master password}}
[[3]] {{{How_to_encrypt_server_passwords}How to encrypt server passwords}}
- [[4]] {{{How_to_keep_master_password_on_removable_drive}How to keep the
master password on removable drive}}
-
+ [[4]] {{{How_to_keep_the_master_password_on_removable_drive}How to keep the
master password on removable drive}}
+
[[5]] {{{Tips}Tips}}
-
+
* {Introduction}
Maven 2.1.0+ now supports server password encryption. The main use case,
addressed by this solution is:
* multiple users share the same build machine (server, CI box)
-
+
* some users have the privilege to deploy Maven artifacts to repositories,
some don't.
-
+
** this applies to any server operations, requiring authorization, not
only deployment
-
+
* <<<settings.xml>>> is shared between users
The implemented solution adds the following capabilities:
* authorized users have an additional <<<settings-security.xml>>> file in
their <<<~/.m2>>> folder
-
+
** this file either contains encrypted <<master password>>, used to
encrypt other passwords
-
+
** or it can contain a <<relocation>> - reference to another file,
possibly on removable storage
-
+
** this password is created first via CLI for now
-
+
* server entries in the <<<settings.xml>>> have passwords and/or keystore
passphrases encrypted
-
+
** for now - this is done via CLI <<after>> master password has been
created and stored in appropriate location
* {How to create a master password}
Use the following command line:
-
+
+------------------------------------+
mvn --encrypt-master-password <password>
+------------------------------------+
This command will produce an encrypted version of the password, something like
-
+
+------------------------------------+
{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}
+------------------------------------+
- Store this password in the <<<~/.m2/settings-security.xml>>>; it should look
like
-
+ Store this password in the <<<~/.m2/settings-security.xml>>>; it should look
like
+
+------------------------------------+
<settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
@@ -72,19 +92,19 @@
* {How to encrypt server passwords}
You will have to use the following command line:
-
+
+------------------------------------+
mvn --encrypt-password <password>
+------------------------------------+
This command will produce an encrypted version of it, something like
-
+
+------------------------------------+
{COQLCE6DU6GtcS5P=}
+------------------------------------+
Cut-n-paste it into your <<<settings.xml>>> file in the server section. This
will look like:
-
+
+------------------------------------+
<settings>
...
@@ -102,7 +122,7 @@
+------------------------------------+
Please note that password can contain any information outside of the curly
brackets, so that the following will still work:
-
+
+------------------------------------+
<settings>
...
@@ -120,7 +140,7 @@
+------------------------------------+
Then you can use, say, deploy plugin, to write to this server:
-
+
+------------------------------------+
mvn deploy:deploy-file -Durl=https://maven.corp.com/repo \
-DrepositoryId=my.server \
@@ -131,10 +151,10 @@
* {How to keep the master password on removable drive}
- Create the master password exactly as described above, and store it on a
- removable drive, for instance on OSX, my USB drive mounts as
<<</Volumes/mySecureUsb>>>,
- so I store
-
+ Create the master password exactly as described above, and store it on a
+ removable drive, for instance on OSX, my USB drive mounts as
<<</Volumes/mySecureUsb>>>,
+ so I store
+
+------------------------------------+
<settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
@@ -144,38 +164,38 @@
in the file <<</Volumes/mySecureUsb/secure/settings-security.xml>>>
And then I create <<<~/.m2/settings-security.xml>>> with the following
content:
-
+
+------------------------------------+
<settingsSecurity>
<relocation>/Volumes/mySecureUsb/secure/settings-security.xml</relocation>
</settingsSecurity>
+------------------------------------+
- This assures that encryption will only work when the usb drive is mounted by
OS.
- This addresses a use case where only certain people are authorized to deploy
and
+ This assures that encryption will only work when the usb drive is mounted by
OS.
+ This addresses a use case where only certain people are authorized to deploy
and
are issued these devices.
* {Tips}
** Escaping curly-brace literals in your password <(Since: Maven 2.2.0)>
- At times, you might find that your password (or the encrypted form of it)
may
+ At times, you might find that your password (or the encrypted form of it) may
actually contain '{' or '}' as a literal value. If you added such a password
as-is
to your settings.xml file, you would find that Maven does strange things
with it.
Specifically, Maven will treat all the characters preceding the '{' literal,
and
all the characters after the '}' literal, as comments. Obviously, this is
not the
behavior you want in such a situation. What you really need is a way of
<<escaping>>
the curly-brace literals in your password.
-
+
Starting in Maven 2.2.0, you can do just this, with the widely used '\'
escape character.
If your password looks like this:
-
+
+---+
jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=
+---+
Then, the value you would add to your settings.xml would look like this:
-
+
+---+
{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}
+---+
Modified: maven/site/trunk/src/site/apt/release-notes.apt.vm
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/release-notes.apt.vm?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/release-notes.apt.vm (original)
+++ maven/site/trunk/src/site/apt/release-notes.apt.vm Sat Aug 1 12:18:27 2009
@@ -46,7 +46,7 @@
* the web site: {{http://maven.apache.org/}}
* the maven-user mailing list: {{http://maven.apache.org/mail-lists.html}}
-
+
* 2.2.0 Release Notes
Maven 2.2.0 contains a few important changes that justify the version
upgrade, instead of simply naming it 2.1.1. First, the Java requirement for
Maven 2.2.0 has been upgraded to 1.5 or later. This upgrade was planned for
2.1.0, but that release still contained binaries that were compatible with JDK
1.4. In addition, due to some serious flaws in the version-expression POM
transformation included in 2.1.0, this feature has been removed for the time
being. Finally, some new default execution IDs have been added to Maven to
enable the separation of configuration for plugins bound by the default
lifecycle mappings, and for those invoked directly from the command line. All
of these issues have been described below with their associated JIRA tickets.
@@ -55,7 +55,7 @@
** Changes that may affect existing builds
- * MNG-4143 - Starting in 2.2.0, Maven will run only on Java 1.5 and later.
You can still build projects for JDK1.4 and earlier using the approach
documented in the {{{/guides/mini/guide-building-jdk14-on-jdk15.html}Guide to
Building JDK 1.4 Projects on JDK 1.5}}.
+ * MNG-4143 - Starting in 2.2.0, Maven will run only on Java 1.5 and later.
You can still build projects for JDK1.4 and earlier using the approach
documented in the {{{./guides/mini/guide-building-jdk14-on-jdk15.html}Guide to
Building JDK 1.4 Projects on JDK 1.5}}.
* MNG-3401 - Executions with an id equal to <<<default->>><phase> (where
<phase> is a valid lifecycle phase) may have unexpected results as it will be
merged into the default lifecycle.
@@ -63,14 +63,14 @@
** Noteworthy changes and improvements
- * MNG-3401 - Starting in Maven 2.2.0, goals invoked directly from the
command line can be configured in the POM separately from other plugin
invocations using a special executionId called <<<default-cli>>>. Where
previously, all configurations for command-line goals had to go in the
plugin-level configuration, Maven 2.2.0 allows command-line-specific
configurations to be separated into their own <<<\<execution\>>>>. For more
information, see the {{{/guides/mini/guide-default-execution-ids.html}Guide to
Default Execution IDs}}.
-
- * MNG-3203 - Similar to MNG-3401, previous to Maven 2.2.0 it was
impossible to separate configurations for different goals from a single plugin
that were bound to the lifecycle by the default mappings for a given packaging.
Beginning in Maven 2.2.0, it is possible to separate configurations for
<<<compiler:compile>>> from those for <<<compiler:testCompile>>> using
executions with IDs <<<default-compile>>> and <<<default-testCompile>>>
respectively. In the case of the compiler plugin, this allows the separation of
include and exclude patterns that are applied during the two compiler
activities in the <<<jar>>> build. For more information, see the
{{{/guides/mini/guide-default-execution-ids.html}Guide to Default Execution
IDs}}.
-
+ * MNG-3401 - Starting in Maven 2.2.0, goals invoked directly from the
command line can be configured in the POM separately from other plugin
invocations using a special executionId called <<<default-cli>>>. Where
previously, all configurations for command-line goals had to go in the
plugin-level configuration, Maven 2.2.0 allows command-line-specific
configurations to be separated into their own <<<\<execution\>>>>. For more
information, see the {{{./guides/mini/guide-default-execution-ids.html}Guide to
Default Execution IDs}}.
+
+ * MNG-3203 - Similar to MNG-3401, previous to Maven 2.2.0 it was
impossible to separate configurations for different goals from a single plugin
that were bound to the lifecycle by the default mappings for a given packaging.
Beginning in Maven 2.2.0, it is possible to separate configurations for
<<<compiler:compile>>> from those for <<<compiler:testCompile>>> using
executions with IDs <<<default-compile>>> and <<<default-testCompile>>>
respectively. In the case of the compiler plugin, this allows the separation of
include and exclude patterns that are applied during the two compiler
activities in the <<<jar>>> build. For more information, see the
{{{./guides/mini/guide-default-execution-ids.html}Guide to Default Execution
IDs}}.
+
* MNG-4179 - <<Regression:>> In Maven 2.1.0, artifact downloads hang when
a transfer failure occurred. This has been corrected.
-
+
* MNG-4184 - <<Regression:>> Maven 2.1.0 failed with a cyclic dependency
in cases where a dependency for a report plugin is build as part of the current
reactor. This has been corrected.
-
+
* MNG-4167 - <<Regression:>> Version-expression resolution for POMs in
Maven 2.1.0 took place as a transformation phase during artifact installation
and deployment. However, this caused the deployed POM to be different from the
one signed by the GPG plugin. Because of this and other use-case problems,
version-expression resolution has been removed from Maven 2.2.0 pending a more
comprehensive design review. MNG-4223 provides tracking for this review.
* MNG-4140 - <<Regression:>> Version-expression resolution for POMs in
Maven 2.1.0 was too aggressive, replacing not only version expressions in
artifact coordinates, but also in plugin configurations and POM properties. As
mentioned above, version-expression resolution has been removed pending further
review.
@@ -80,76 +80,76 @@
*** Sub-task
* MNG-4144 - document escape character for curly braces in clear-text
passwords for settings.xml password security
-
+
* MNG-4145 - switch to released versions of plexus-sec-dispatcher (and by
ext. plexus-cipher) once they're available
*** Bug
* MNG-2258 - Wrong execution order of plugins in same phase
-
+
* MNG-3401 - Plugin parameters must be specified outside an execution
block when they are invoked from the command line
-
+
* MNG-3553 - cannot resolve dependency with scope import
-
+
* MNG-3776 - Namespace misspelled in settings.xml
-
+
* MNG-4074 - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10
-
+
* MNG-4082 - Encryption is triggered if passwords merely contain curly
braces
-
+
* MNG-4126 - regression Properties defined in profiles.xml of parent are
not inherited during multimodule build
-
+
* MNG-4137 - NPE in DefaultLIfecycleExecutor when run from within Hudson
builds
-
+
* MNG-4140 - Properties incorrectly replaced in pom
-
+
* MNG-4146 - password security doesn't work with custom password providers
-
+
* MNG-4147 - very long passwords cause LightweightHTTP wagon to line-wrap
the Base64-encoded Authorization header
-
+
* MNG-4165 - http session cookies rejected with non-lightweight http wagon
(maybe with lightweight one too)
-
+
* MNG-4166 - Problem parsing command-line options in release:perform
-
+
* MNG-4167 - version-expression transformation interferes with plugins
like GPG
-
+
* MNG-4168 - String index out of range: 43807
-
+
* MNG-4179 - regression Artifact download hangs upon transfer failure
-
+
* MNG-4184 - regression maven2.1 fails with cyclic dependency in case of
extension/dependency for report-plugin to reactor-project
-
+
* MNG-4207 - Plugins that use ArtifactResolver with http repositories AND
depend on log4j run into ExceptionInInitializerError
-
+
* MNG-4213 - preemptive auth in non-lightweight http wagon causes
Unauthorized responses from some servers
-
+
* MNG-4219 - update plexus-utils to avoid leaking processes in
CommandLineUtils.getSystemEnvars()
*** Improvement
* MNG-2979 - Cross module dependencies for multi-module site
-
+
* MNG-3203 - maven should execute compiler:compile and :test-compile in
separate executions, to allow separate configuration
-
+
* MNG-3834 - Improve error message when dependency with classifier is
missing version
-
+
* MNG-4210 - Remove log4j configuration warning
*** Task
* MNG-4143 - Update Java requirement to 1.5
-
+
* MNG-4169 - Remove invocation of maven-plugin-plugin:updatePluginRegistry
from default lifecycle bindings
*** Wish
-
+
* MNG-4139 - avoid the schema location in generated maven-metadata*.xml
* Release notes for earlier versions
* {{{./release-notes-2.1.x.html}Maven ${current21xVersion} Release Notes}}
-
+
* {{{./release-notes-2.0.x.html}Maven ${current20xVersion} Release Notes}}
* {{{./release-notes-older.html}Release Notes for earlier versions}}
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Context_Menu.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Context_Menu.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Context_Menu.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Generate_Site.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Generate_Site.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Generate_Site.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Open_Project.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Open_Project.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Open_Project.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Project_Opened.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Project_Opened.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Project_Opened.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refresh_Project.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refresh_Project.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refresh_Project.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refreshed_Context_Menu.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refreshed_Context_Menu.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Refreshed_Context_Menu.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Build_Main_Project.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Build_Main_Project.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Build_Main_Project.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Clean_Main_Project.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Clean_Main_Project.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Run_Clean_Main_Project.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Window_Files.png
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Window_Files.png?rev=799850&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
maven/site/trunk/src/site/resources/guides/mini/guide-ide-netbeans/Window_Files.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Modified: maven/site/trunk/src/site/xdoc/docs-required.xml
URL:
http://svn.apache.org/viewvc/maven/site/trunk/src/site/xdoc/docs-required.xml?rev=799850&r1=799849&r2=799850&view=diff
==============================================================================
--- maven/site/trunk/src/site/xdoc/docs-required.xml (original)
+++ maven/site/trunk/src/site/xdoc/docs-required.xml Sat Aug 1 12:18:27 2009
@@ -1,5 +1,27 @@
<?xml version="1.0"?>
-<document>
+
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+<document xmlns="http://maven.apache.org/XDOC/2.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/XDOC/2.0
http://maven.apache.org/xsd/xdoc-2.0.xsd";>
<!-- TODO: include back into site, after checking which are complete, add to
instructions on how to contribute docs -->
<properties>
<title>Documentation Required</title>
@@ -10,7 +32,7 @@
<p>
This page lists some of the most pressing documentation needs. If you
feel something is missing, please be sure
to let us know at the
- <a href="/mail-lists.html">Maven Users Mailing List</a>.
+ <a href="./mail-lists.html">Maven Users Mailing List</a>.
</p>
<h4>Documentation for users</h4>
<ul>
@@ -98,7 +120,7 @@
- overriding central repo
- using POM info in applications: the POM is packaged so there is
acccess
continuum example to get the version.
- - quick description of scm,wagon,continuum
+ - quick description of scm,wagon,continuum
</pre>
<h4>Profiles Example</h4>
<pre><
