dion 2004/05/07 02:14:37
Modified: eclipse/xdocs properties.xml changes.xml
Log:
Document the eclipse.dependency property of the dependency element
PR: MPECLIPSE-23
Obtained from: Miguel Griffa
Submitted by: Miguel Griffa
Reviewed by: dIon
Revision Changes Path
1.9 +32 -11 maven-plugins/eclipse/xdocs/properties.xml
Index: properties.xml
===================================================================
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/properties.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- properties.xml 6 May 2004 05:43:12 -0000 1.8
+++ properties.xml 7 May 2004 09:14:37 -0000 1.9
@@ -33,17 +33,17 @@
<td>maven.eclipse.workspace</td>
<td>Yes</td>
<td>
- 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>.
- </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.
+ 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>.
+ </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.
</p>
</td>
</tr>
@@ -106,6 +106,27 @@
then Classpath Variables. Create a new variable named
<code>MAVEN_REPO</code> that points to your local Maven repository.
</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>
</section>
</body>
</document>
1.18 +3 -0 maven-plugins/eclipse/xdocs/changes.xml
Index: changes.xml
===================================================================
RCS file: /home/cvs/maven-plugins/eclipse/xdocs/changes.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- changes.xml 6 May 2004 05:43:13 -0000 1.17
+++ changes.xml 7 May 2004 09:14:37 -0000 1.18
@@ -25,6 +25,9 @@
</properties>
<body>
<release version="1.7-SNAPSHOT" date="in CVS">
+ <action dev="dion" type="update" issue="MPECLIPSE-23" due-to="Miguel Griffa">
+ Document the eclipse.dependency property of the dependency element
+ </action>
<action dev="dion" type="update" issue="MPECLIPSE-25" due-to="Miguel Griffa">
Add maven.eclipse.buildcommands and maven.eclipse.projectnatures
properties, docs
and test cases
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
