Update/Refactor documentation
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@481133 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
aheritier
parent
14d371108c
commit
198d9404c2
@ -24,6 +24,7 @@
|
||||
</properties>
|
||||
<body>
|
||||
<release version="1.11.1-SNAPSHOT" date="In SVN">
|
||||
<action dev="aheritier" type="add" issues="MPECLIPSE-127">Add basic support (jar,war) for WTP 1.5</action>
|
||||
<action dev="aheritier" type="fix">WTP configuration : tld dependencies weren't deployed in ${maven.war.tld.dir} but in WEB-INF/lib</action>
|
||||
<action dev="aheritier" type="add">New goal eclipse:multiclean</action>
|
||||
<action dev="aheritier" type="add">New goal eclipse:multiproject</action>
|
||||
|
||||
@ -1,98 +1,122 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!--
|
||||
/*
|
||||
* Copyright 2001-2004 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
/*
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
|
||||
<faqs title="Frequently Asked Questions">
|
||||
<faqs title="FAQs">
|
||||
|
||||
<part id="general">
|
||||
<title>General</title>
|
||||
|
||||
|
||||
<faq id="junit">
|
||||
<question>
|
||||
I can't seem to get JUnit to show up in the classpath. What gives?
|
||||
</question>
|
||||
<question>I can't seem to get JUnit to show up in the classpath. What gives?</question>
|
||||
<answer>
|
||||
<p>
|
||||
You must have some unit tests for your project, otherwise JUnit
|
||||
is ignored.
|
||||
</p>
|
||||
<p>You must have some unit tests for your project, otherwise JUnit is ignored.</p>
|
||||
</answer>
|
||||
</faq>
|
||||
|
||||
<faq id="project dependencies">
|
||||
<question>How can I define dependencies as eclipse projects ?</question>
|
||||
<answer>
|
||||
<p>The dependencies defined in the POM don't need to be jars strictly. They can be projects in the eclipse workspace. If a dependency is an eclipse project a property needs to be added to that dependency to indicate so.</p>
|
||||
<source>
|
||||
<![CDATA[
|
||||
<dependency>
|
||||
<groupId>group</groupId>
|
||||
<artifactId>artifact</artifactId>
|
||||
<version>version</version>
|
||||
<properties>
|
||||
<eclipse.dependency>true</eclipse.dependency>
|
||||
</properties>
|
||||
</dependency>
|
||||
]]>
|
||||
</source>
|
||||
<p>This indicates that the dependency is another project in the workspace. Note that the name of the referenced project is the artifactId.</p>
|
||||
<p>The inverse also works. If you have included extra jars that shouldn't be in the eclipse classpath then you can set <code>eclipse.dependency=false</code></p>
|
||||
</answer>
|
||||
</faq>
|
||||
</part>
|
||||
|
||||
<part id="source">
|
||||
<title>Source Code Integration w/ Eclipse</title>
|
||||
|
||||
<faq id="source-dep">
|
||||
<question>How can I attach source code to libraries defined in dependencies ?</question>
|
||||
<answer>
|
||||
<p>Frequently you will want to include for compiled jars the source .java files to help with debugging.</p>
|
||||
<p>The plugin is able to download sources archive at <code>${groupId}/java-sources/${artifactId}-${version}-sources.jar</code> from the repository. This behavior can be disabled by configuring the <code>maven.eclipse.src.download</code> property. As an example, the source archive for the dependency <code>MAVEN_REPO/eclipse/<em>jars</em>/eclipse-ui-3.0.0<em>.jar</em></code> will be mapped to <code>MAVEN_REPO/eclipse/<em>java-sources</em>/eclipse-ui-3.0.0<em>-sources.jar</em></code> </p>
|
||||
<p>For backward compatibility the plugin still accepts source archives located at <code>MAVEN_REPO/${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension}</code> but it won't download them from the repository. </p>
|
||||
</answer>
|
||||
</faq>
|
||||
|
||||
<faq id="generated-sources">
|
||||
<question>How must I setup generated source code ?</question>
|
||||
<answer>
|
||||
<p>When Eclipse is not generating source code for you there is a conflict between Maven generating the source code and then Eclipse treating it as compiled code. Typically when generating code using Maven the code ends up in the target/classes directory. This is fine as long as Maven is doing the build. However, if Eclipse is then setup to do the build, when Eclipse performs a clean build all the generated code in target/classes will be removed.</p>
|
||||
<p>The alternatives typically are to place the generated code in the /src/java directory and allow Maven and Eclipse to treat it the same. However, this leads to a tendency to check generated code into source control, which typically is not appropriate for generated code. Alternatively, it can be placed in some sort of /src/generated or target/generated directory. In Maven2, generated code lives in target/generated-sources, in a manner similiar to generated xdoc's live in target/generated-xdocs. Within the target/generated-sources would be each type of generated code.</p>
|
||||
<p>By default, the plugin will load as seperate source folders any directory found in <code>${maven.build.dir}/generated-sources</code>. So, if you generate your mock objects into <code>${maven.build.dir}/generated-sources/mocks</code> and your wsdl classes into <code>${maven.build.dir}/generated-sources/wsdl</code> then each of these directories will be mounted as source folders. Note: You must have already created these directories, otherwise the plugin won't know to add them as source folders. Before running <code>maven eclipse</code> just ensure you have already generated all of your source code.</p>
|
||||
<p>For example, if you used the XDoclet Plugin for Maven to generate Hibernate mapping files, they would be placed in <code>/target/generated-sources/xdoclet/</code>. While, if you used the Hibernate Plugin for Maven to generate the SQL scripts for generating a database then that would be placed in <code>/target/generated-sources/schema/</code>.<br />Settings in project.properties:</p>
|
||||
<source>
|
||||
maven.xdoclet.hibernatedoclet.destDir=${maven.build.dir}/generated-sources/xdoclet
|
||||
maven.hibernate.output.dir=${maven.build.dir}/generated-sources/schema
|
||||
</source>
|
||||
</answer>
|
||||
</faq>
|
||||
|
||||
</part>
|
||||
|
||||
<part id="project-organization">
|
||||
<faq id="eclipse-multiproject">
|
||||
<question>
|
||||
Eclipse doesn't support hierarchical project structure. How am i supposed to organize my multiproject ?
|
||||
</question>
|
||||
<part id="eclipse-multiproject">
|
||||
<title>Multiproject support</title>
|
||||
<faq id="hierarchical">
|
||||
<question>Eclipse doesn't support hierarchical project structure. How am i supposed to organize my multiproject ?</question>
|
||||
<answer>
|
||||
<p>
|
||||
If you use Eclipse, you may already have encountered the Infamous Layout Issue:
|
||||
Eclipse doesn't handle (yet ?) overlapping projects. Thus if you work in a
|
||||
multiproject context with a classical non flat layout, Eclipse integration becomes
|
||||
quite problematic. You surely don't want to use one big Eclipse project because
|
||||
you'll then lose visibility on dependencies (inter-project dependencies as well
|
||||
as library dependencies) and this will quickly become quite hard to manage - and
|
||||
promotes cycles.
|
||||
</p>
|
||||
<p>
|
||||
Best solution found so far is to refactor your project structure to rather
|
||||
use a flat layout, as described below:
|
||||
<source>
|
||||
<pre>
|
||||
<p>If you use Eclipse, you may already have encountered the Infamous Layout Issue: Eclipse doesn't handle (yet ?) overlapping projects. Thus if you work in a multiproject context with a classical non flat layout, Eclipse integration becomes quite problematic. You surely don't want to use one big Eclipse project because you'll then lose visibility on dependencies (inter-project dependencies as well as library dependencies) and this will quickly become quite hard to manage - and promotes cycles.</p>
|
||||
<p>Best solution found so far is to refactor your project structure to rather use a flat layout, as described below:</p>
|
||||
<source>
|
||||
<pre>
|
||||
/project-root | /project-root
|
||||
+- subproject1 | +- project.xml
|
||||
+- project.xml ===> /subproject1
|
||||
+- subproject2 | +- project.xml
|
||||
+- project.xml | /subproject2
|
||||
+- project.xml | +- project.xml
|
||||
|
||||
</pre>
|
||||
</source>
|
||||
</p>
|
||||
<p>
|
||||
And alter your properties in a similar way than the example below:
|
||||
<source>
|
||||
maven.multiproject.basedir=${basedir}/..
|
||||
maven.multiproject.includes=*/project.xml
|
||||
maven.multiproject.excludes=project-root/project.xml
|
||||
</source>
|
||||
</p>
|
||||
<p>
|
||||
If you really can't (or don't want to) flatten your layout, the only solutions that are offered to you are a few tricks, each with its own drawback.
|
||||
<ul>
|
||||
<li>
|
||||
Edit root files outside Eclipse - almost safe but implies switching between tools.
|
||||
Note that initial checkout must be done through command line in this case, because
|
||||
parent project shouldn't be in the workspace folder.
|
||||
</li>
|
||||
<li>
|
||||
Create a virtual project which contains links to root files - doesn't
|
||||
support refactoring well, and implies identical paths on every developer machines.
|
||||
</li>
|
||||
</ul>
|
||||
<i>Use those tricks at your own risk</i>
|
||||
</p>
|
||||
<p>
|
||||
if this issue really annoys you, then please vote for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973">https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973</a>
|
||||
</p>
|
||||
</pre>
|
||||
</source>
|
||||
<p>And alter your properties in a similar way than the example below:</p>
|
||||
<source>
|
||||
maven.multiproject.basedir=${basedir}/..
|
||||
maven.multiproject.includes=*/project.xml
|
||||
maven.multiproject.excludes=project-root/project.xml
|
||||
</source>
|
||||
<p>If you really can't (or don't want to) flatten your layout, the only solutions that are offered to you are a few tricks, each with its own drawback.</p>
|
||||
<ul>
|
||||
<li>
|
||||
Edit root files outside Eclipse - almost safe but implies switching between tools. Note that initial
|
||||
checkout must be done through command line in this case, because parent project shouldn't be in the
|
||||
workspace folder.
|
||||
</li>
|
||||
<li>
|
||||
Create a virtual project which contains links to root files - doesn't support refactoring well, and
|
||||
implies identical paths on every developer machines.
|
||||
</li>
|
||||
</ul>
|
||||
<p><i>Use those tricks at your own risk</i></p>
|
||||
<p>if this issue really annoys you, then please vote for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973">https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973</a></p>
|
||||
</answer>
|
||||
</faq>
|
||||
</part>
|
||||
</faqs>
|
||||
</faqs>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<!--
|
||||
/*
|
||||
* Copyright 2001-2004 The Apache Software Foundation.
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed under the Apache License, Version 2.0 (the "License");
|
||||
* you may not use this file except in compliance with the License.
|
||||
@ -20,7 +20,7 @@
|
||||
<document>
|
||||
|
||||
<properties>
|
||||
<title>Eclipse Plugin Goals</title>
|
||||
<title>Plugin Goals</title>
|
||||
<author email="dion@apache.org">dIon Gillard</author>
|
||||
</properties>
|
||||
|
||||
|
||||
@ -1,26 +1,26 @@
|
||||
<?xml version="1.0"?>
|
||||
<!--
|
||||
/*
|
||||
* Copyright 2001-2004 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
/*
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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>
|
||||
|
||||
<properties>
|
||||
<title>Maven Eclipse Plugin</title>
|
||||
<title>About</title>
|
||||
<author email="vmassol@octo.com">Vincent Massol</author>
|
||||
<author email="dion@apache.org">dIon Gillard</author>
|
||||
</properties>
|
||||
@ -28,104 +28,24 @@
|
||||
<body>
|
||||
<section name="Maven Eclipse Plugin">
|
||||
<p>
|
||||
This plug-in provides the ability to generate Eclipse project files
|
||||
(<code>.classpath</code> and <code>.project</code> files), as well as
|
||||
configure Eclipse to use Maven as an <i>External Tool</i>.
|
||||
This plug-in provides the ability to generate Eclipse project files (
|
||||
<code>.classpath</code>
|
||||
and
|
||||
<code>.project</code>
|
||||
files), as well as configure Eclipse to use Maven as an
|
||||
<i>External Tool</i>
|
||||
.
|
||||
</p>
|
||||
<p>
|
||||
For more information on the functionality provided by this plugin,
|
||||
please see the <a href="goals.html">Goals</a> document.
|
||||
For more information on the functionality provided by this plugin, please see the
|
||||
<a href="goals.html">Goals</a>
|
||||
document.
|
||||
</p>
|
||||
<p>
|
||||
For more information on how to customise the functionality provided
|
||||
by this plugin, please see the <a href="properties.html">properties</a>
|
||||
For more information on how to customise the functionality provided by this plugin, please see the
|
||||
<a href="properties.html">properties</a>
|
||||
document.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
<section name="Defining dependencies as eclipse projects">
|
||||
<p>
|
||||
The dependencies defined in the POM need not to be jars strictly. They can
|
||||
be projects in the eclipse workspace. If a dependency is an eclipse project
|
||||
a property needs to be added to that dependency to indicate so.
|
||||
</p>
|
||||
<source><![CDATA[
|
||||
<dependency>
|
||||
<groupId>group</groupId>
|
||||
<artifactId>artifact</artifactId>
|
||||
<version>version</version>
|
||||
<properties>
|
||||
<eclipse.dependency>true</eclipse.dependency>
|
||||
</properties>
|
||||
</dependency>
|
||||
]]></source>
|
||||
<p>
|
||||
This indicates that the dependency is another project in the workspace.
|
||||
Note that the name of the referenced project is the artifactId.
|
||||
</p>
|
||||
<p>
|
||||
The inverse also works. If you have included extra jars that shouldn't be
|
||||
in the eclipse classpath then you can set <code>eclipse.dependency=false</code>
|
||||
</p>
|
||||
</section>
|
||||
<section name="Source Code Integration w/ Eclipse">
|
||||
<subsection name="Artifact Sources">
|
||||
<p>
|
||||
Frequently you will want to include for compiled jars the source .java files to help
|
||||
with debugging.
|
||||
</p>
|
||||
<p>
|
||||
The plugin is able to download sources archive at <code>${groupId}/java-sources/${artifactId}-${version}-sources.jar</code>
|
||||
from the repository. This behavior can be disabled by configuring the <code>maven.eclipse.src.download</code> property.
|
||||
As an example, the source archive for the dependency <code>MAVEN_REPO/eclipse/<em>jars</em>/eclipse-ui-3.0.0<em>.jar</em></code>
|
||||
will be mapped to <code>MAVEN_REPO/eclipse/<em>java-sources</em>/eclipse-ui-3.0.0<em>-sources.jar</em></code>
|
||||
</p>
|
||||
<p>
|
||||
For backward compatibility the plugin still accepts source archives located at
|
||||
<code>MAVEN_REPO/${groupId}/src/${artifactId}-${version}.${maven.eclipse.src.extension}</code> but it won't
|
||||
download them from the repository.
|
||||
</p>
|
||||
</subsection>
|
||||
<subsection name="Generated Source Code">
|
||||
<p>
|
||||
When Eclipse is not generating source code for you there is a conflict between
|
||||
Maven generating the source code and then Eclipse treating it as compiled code.
|
||||
Typically when generating code using Maven the code ends up in the target/classes
|
||||
directory. This is fine as long as Maven is doing the build. However, if Eclipse
|
||||
is then setup to do the build, when Eclipse performs a clean build all the generated
|
||||
code in target/classes will be removed.
|
||||
</p>
|
||||
<p>
|
||||
The alternatives typically are to place the generated code in the /src/java directory
|
||||
and allow Maven and Eclipse to treat it the same. However, this leads to a tendency
|
||||
to check generated code into source control, which typically is not appropriate for
|
||||
generated code. Alternatively, it can be placed in some sort of /src/generated or
|
||||
target/generated directory. In Maven2, generated code lives in target/generated-sources,
|
||||
in a manner similiar to generated xdoc's live in target/generated-xdocs. Within the
|
||||
target/generated-sources would be each type of generated code.
|
||||
</p>
|
||||
<p>
|
||||
By default, the plugin will load as seperate source folders any directory found in
|
||||
<code>${maven.build.dir}/generated-sources</code>. So, if you generate your mock objects into
|
||||
<code>${maven.build.dir}/generated-sources/mocks</code> and your wsdl classes into
|
||||
<code>${maven.build.dir}/generated-sources/wsdl</code> then each of these directories will be mounted
|
||||
as source folders. Note: You must have already created these directories, otherwise the
|
||||
plugin won't know to add them as source folders. Before running <code>maven eclipse</code>
|
||||
just ensure you have already generated all of your source code.
|
||||
</p>
|
||||
<p>
|
||||
For example, if you used the XDoclet Plugin for Maven to generate Hibernate mapping files,
|
||||
they would be placed in <code>/target/generated-sources/xdoclet/</code>. While, if you used the
|
||||
Hibernate Plugin for Maven to generate the SQL scripts for generating a database then that
|
||||
would be placed in <code>/target/generated-sources/schema/</code>.
|
||||
<br/>
|
||||
Settings in project.properties:
|
||||
</p>
|
||||
<source>
|
||||
maven.xdoclet.hibernatedoclet.destDir=${maven.build.dir}/generated-sources/xdoclet
|
||||
maven.hibernate.output.dir=${maven.build.dir}/generated-sources/schema
|
||||
</source>
|
||||
</subsection>
|
||||
</section>
|
||||
</body>
|
||||
</body>
|
||||
</document>
|
||||
|
||||
@ -1,38 +1,39 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<!--
|
||||
/*
|
||||
* Copyright 2001-2004 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
/*
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
<project name="Maven Eclipse Plugin">
|
||||
<title>Maven Eclipse Plugin</title>
|
||||
<body>
|
||||
<breadcrumbs>
|
||||
<item name="Apache" href="http://www.apache.org"/>
|
||||
<item name="Maven" href="http://maven.apache.org/"/>
|
||||
<item name="Maven 1.x" href="http://maven.apache.org/maven-1.x/"/>
|
||||
<item name="Plugins" href="http://maven.apache.org/maven-1.x/plugins/"/>
|
||||
<item name="Bundled" href="http://maven.apache.org/maven-1.x/plugins/bundled/"/>
|
||||
<item name="Apache" href="http://www.apache.org" />
|
||||
<item name="Maven" href="http://maven.apache.org/" />
|
||||
<item name="Maven 1.x" href="http://maven.apache.org/maven-1.x/" />
|
||||
<item name="Plugins" href="http://maven.apache.org/maven-1.x/plugins/" />
|
||||
<item name="Bundled" href="http://maven.apache.org/maven-1.x/plugins/bundled/" />
|
||||
</breadcrumbs>
|
||||
<links>
|
||||
<item name="Eclipse" href="http://www.eclipse.org/"/>
|
||||
<item name="Eclipse" href="http://www.eclipse.org/" />
|
||||
</links>
|
||||
<menu name="Overview">
|
||||
<item name="Goals" href="/goals.html"/>
|
||||
<item name="Properties" href="/properties.html"/>
|
||||
<item name="FAQ" href="/faq.html"/>
|
||||
<menu name="Maven 1.x Eclipse Plugin">
|
||||
<item name="About" href="/index.html" />
|
||||
<item name="Goals" href="/goals.html" />
|
||||
<item name="Properties" href="/properties.html" />
|
||||
<item name="FAQs" href="/faq.html"/>
|
||||
</menu>
|
||||
</body>
|
||||
</project>
|
||||
|
||||
@ -1,49 +1,58 @@
|
||||
<?xml version="1.0" encoding="ISO-8859-1"?>
|
||||
<!--
|
||||
/*
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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.
|
||||
*/
|
||||
-->
|
||||
/*
|
||||
* Copyright 2001-2006 The Apache Software Foundation.
|
||||
*
|
||||
* Licensed 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>
|
||||
|
||||
<properties>
|
||||
<title>Eclipse Properties</title>
|
||||
<title>Plugin Properties</title>
|
||||
<author email="vmassol@octo.com">Vincent Massol</author>
|
||||
<author email="dion@apache.org">dIon Gillard</author>
|
||||
</properties>
|
||||
|
||||
<body>
|
||||
<section name="Eclipse Settings">
|
||||
<section name="Plugin Properties">
|
||||
<table>
|
||||
<tr><th>Property</th><th>Optional?</th><th>Description</th></tr>
|
||||
<tr>
|
||||
<th>Property</th>
|
||||
<th>Optional?</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.workspace</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Location of the <a href="http://www.eclipse.org">Eclipse</a>
|
||||
Location of the
|
||||
<a href="http://www.eclipse.org">Eclipse</a>
|
||||
workspace that holds your configuration and source.
|
||||
<p>
|
||||
On Windows, this will be the <code>workspace</code> directory
|
||||
under your eclipse installation. For example, if you installed
|
||||
eclipse into <code>c:\eclipse</code>, the workspace is
|
||||
<code>c:\eclipse\workspace</code>.
|
||||
On Windows, this will be the
|
||||
<code>workspace</code>
|
||||
directory under your eclipse installation. For example, if you installed eclipse into
|
||||
<code>c:\eclipse</code>
|
||||
, the workspace is
|
||||
<code>c:\eclipse\workspace</code>
|
||||
.
|
||||
</p>
|
||||
<p>
|
||||
If this parameter is specified, the <a href="goals.html#eclipse:external-tools">
|
||||
external-tools</a> goal will use it as the destination to copy the generated file.
|
||||
If this parameter is specified, the
|
||||
<a href="goals.html#eclipse:external-tools">external-tools</a>
|
||||
goal will use it as the destination to copy the generated file.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -52,13 +61,13 @@
|
||||
<td>Yes (default=plugins)</td>
|
||||
<td>
|
||||
<p>
|
||||
Generate Eclipse external tools mappings for the specified goals.
|
||||
This accepts two values: 'all' for all the goals,
|
||||
and 'plugins' to generate only the plugins' default goals.
|
||||
Generate Eclipse external tools mappings for the specified goals. This accepts two values: 'all' for all
|
||||
the goals, and 'plugins' to generate only the plugins' default goals.
|
||||
</p>
|
||||
<p>
|
||||
If this parameter is specified, the <a href="goals.html#eclipse:external-tools">
|
||||
external-tools</a> goal will use it as the destination to copy the generated file.
|
||||
If this parameter is specified, the
|
||||
<a href="goals.html#eclipse:external-tools">external-tools</a>
|
||||
goal will use it as the destination to copy the generated file.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -66,50 +75,47 @@
|
||||
<td>maven.eclipse.junit</td>
|
||||
<td>Yes (default=3.8.1)</td>
|
||||
<td>
|
||||
The version of JUnit you want added to your project. If this
|
||||
property is set to <code>none</code> then JUnit will not be added to your
|
||||
build classpath.
|
||||
The version of JUnit you want added to your project. If this property is set to
|
||||
<code>none</code>
|
||||
then JUnit will not be added to your build classpath.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.output.dir</td>
|
||||
<td>Yes (default=${maven.build.dest)</td>
|
||||
<td>
|
||||
The directory to which Eclipse should output its classes.
|
||||
By default this is the same directory as Maven generates its code
|
||||
however this can be changed so that <code>maven clean</code>
|
||||
The directory to which Eclipse should output its classes. By default this is the same directory as Maven
|
||||
generates its code however this can be changed so that
|
||||
<code>maven clean</code>
|
||||
does not interfere with Eclipse's build.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.test.output.dir</td>
|
||||
<td>Yes (default=${maven.test.dest} defined in test plugin)</td>
|
||||
<td>
|
||||
The directory to which Eclipse should output its test classes.
|
||||
</td>
|
||||
<td>The directory to which Eclipse should output its test classes.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.classpath.include</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Comma delimited list of additional source directories to include in
|
||||
the classpath, like <code>src/conf</code>.
|
||||
Comma delimited list of additional source directories to include in the classpath, like
|
||||
<code>src/conf</code>
|
||||
.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.resources.addtoclasspath</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Specify whether to include the resources defined in the POM in the
|
||||
Eclipse classpath. Defaults to false.
|
||||
Specify whether to include the resources defined in the POM in the Eclipse classpath. Defaults to false.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.conclasspath</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Comma delimited list of additional kind "con" path
|
||||
to include in the classpath description file like
|
||||
Comma delimited list of additional kind "con" path to include in the classpath description file like
|
||||
<code>org.eclipse.pde.core.requiredPlugins</code>
|
||||
</td>
|
||||
</tr>
|
||||
@ -117,17 +123,15 @@
|
||||
<td>maven.eclipse.buildcommands</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Comma delimited list of additional build commands
|
||||
to include in the project description file. The java builder will automatically be added if a java source
|
||||
dir is set (if not already specified in the list).
|
||||
Comma delimited list of additional build commands to include in the project description file. The java
|
||||
builder will automatically be added if a java source dir is set (if not already specified in the list).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.projectnatures</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Comma delimited list of additional project natures
|
||||
to include in the project description file. These natures
|
||||
Comma delimited list of additional project natures to include in the project description file. These natures
|
||||
will be added after the java nature (if the java nature is not already specified in the list).
|
||||
</td>
|
||||
</tr>
|
||||
@ -135,56 +139,69 @@
|
||||
<td>maven.eclipse.project.name</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
Name of the generated project on Eclipse.
|
||||
Defaults to <code>${artifactId}</code>.
|
||||
Name of the generated project on Eclipse. Defaults to
|
||||
<code>${artifactId}</code>
|
||||
.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.gen.src</td>
|
||||
<td>Yes (default=${maven.build.dir}/generated-sources)</td>
|
||||
<td>
|
||||
The directory that generated source code is placed. Maven will select
|
||||
any directories under this as source code. This prevents the generated
|
||||
source from being removed whenever Eclipse does a clean build, and allows
|
||||
The directory that generated source code is placed. Maven will select any directories under this as source
|
||||
code. This prevents the generated source from being removed whenever Eclipse does a clean build, and allows
|
||||
the generated code to be clearly in the build directory.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.src.extension</td>
|
||||
<td>Yes (default=<code>zip</code>)</td>
|
||||
<td>
|
||||
The extension used for source attachments.
|
||||
Deprecated, source attachment are expected now at
|
||||
Yes (default=
|
||||
<code>zip</code>
|
||||
)
|
||||
</td>
|
||||
<td>
|
||||
The extension used for source attachments. Deprecated, source attachment are expected now at
|
||||
<code>MAVEN_REPO${groupId}/java-sources/${artifactId}-${version}-sources.jar</code>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.src.download</td>
|
||||
<td>Yes (default=<code>true</code>)</td>
|
||||
<td>
|
||||
Specify if java sources archives need to be downloaded from the configured
|
||||
remote repositories. Defaults to true.
|
||||
Yes (default=
|
||||
<code>true</code>
|
||||
)
|
||||
</td>
|
||||
<td>
|
||||
Specify if java sources archives need to be downloaded from the configured remote repositories. Defaults to
|
||||
true.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>maven.eclipse.javadoc.download</td>
|
||||
<td>Yes (default=<code>true</code>)</td>
|
||||
<td>
|
||||
Specify if javadocs archives need to be downloaded from the configured
|
||||
remote repositories, when no source archive is available. Defaults to true.
|
||||
Yes (default=
|
||||
<code>true</code>
|
||||
)
|
||||
</td>
|
||||
<td>
|
||||
Specify if javadocs archives need to be downloaded from the configured remote repositories, when no source
|
||||
archive is available. Defaults to true.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td>maven.eclipse.multiproject.basedir</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
This is the base directory that the plugin will use when searching for
|
||||
projects to be processed. It is also the 'current directory' for relative paths
|
||||
This is the base directory that the plugin will use when searching for projects to be processed. It is
|
||||
also the 'current directory' for relative paths
|
||||
</p>
|
||||
<p>
|
||||
Default value is <code>${maven.multiproject.basedir}</code>.
|
||||
Default value is
|
||||
<code>${maven.multiproject.basedir}</code>
|
||||
.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -192,12 +209,11 @@
|
||||
<td>maven.eclipse.multiproject.ignoreFailures</td>
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>Set this to true to allow the plugin to continue when any project fails during processing.</p>
|
||||
<p>
|
||||
Set this to true to allow the plugin to continue
|
||||
when any project fails during processing.
|
||||
</p>
|
||||
<p>
|
||||
Default value is <code>${maven.multiproject.ignoreFailures}</code>.
|
||||
Default value is
|
||||
<code>${maven.multiproject.ignoreFailures}</code>
|
||||
.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -206,15 +222,18 @@
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
This is the list of file specifications to be included when searching for
|
||||
projects to be processed by the plugin.
|
||||
This is the list of file specifications to be included when searching for projects to be processed by the
|
||||
plugin.
|
||||
</p>
|
||||
<strong>
|
||||
The 'top-level' project that you use to run <code>maven eclipse:multiproject</code>
|
||||
The 'top-level' project that you use to run
|
||||
<code>maven eclipse:multiproject</code>
|
||||
must not be included in the set of projects to be processed.
|
||||
</strong>
|
||||
<p>
|
||||
Default value is <code>${maven.multiproject.includes}</code>.
|
||||
Default value is
|
||||
<code>${maven.multiproject.includes}</code>
|
||||
.
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
@ -223,19 +242,24 @@
|
||||
<td>Yes</td>
|
||||
<td>
|
||||
<p>
|
||||
This is the list of file specifications to be excluded when searching for
|
||||
projects to be processed by the plugin
|
||||
This is the list of file specifications to be excluded when searching for projects to be processed by the
|
||||
plugin
|
||||
</p>
|
||||
<p>
|
||||
Default value is
|
||||
<code>${maven.multiproject.excludes}</code>
|
||||
.
|
||||
</p>
|
||||
<p>Default value is <code>${maven.multiproject.excludes}</code>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
<p>
|
||||
Note that you will need to defined a <code>MAVEN_REPO</code> Java
|
||||
Classpath variable in Eclipse. This is done by selecting the Window
|
||||
menu, then Preferences. In the dialog box, select the Java node and
|
||||
then Classpath Variables. Create a new variable named
|
||||
<code>MAVEN_REPO</code> that points to your local Maven repository.
|
||||
Note that you will need to defined a
|
||||
<code>MAVEN_REPO</code>
|
||||
Java Classpath variable in Eclipse. This is done by selecting the Window menu, then Preferences. In the dialog
|
||||
box, select the Java node and then Classpath Variables. Create a new variable named
|
||||
<code>MAVEN_REPO</code>
|
||||
that points to your local Maven repository.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user