diff --git a/eclipse/xdocs/changes.xml b/eclipse/xdocs/changes.xml index 7c19407b..719c281f 100644 --- a/eclipse/xdocs/changes.xml +++ b/eclipse/xdocs/changes.xml @@ -25,6 +25,9 @@ + + Document the eclipse.dependency property of the dependency element + Add maven.eclipse.buildcommands and maven.eclipse.projectnatures properties, docs and test cases diff --git a/eclipse/xdocs/properties.xml b/eclipse/xdocs/properties.xml index 23b6d672..e5075e41 100644 --- a/eclipse/xdocs/properties.xml +++ b/eclipse/xdocs/properties.xml @@ -33,17 +33,17 @@ maven.eclipse.workspace Yes - Location of the Eclipse - workspace that holds your configuration and source. -

- On Windows, this will be the workspace directory - under your eclipse installation. For example, if you installed - eclipse into c:\eclipse, the workspace is - c:\eclipse\workspace. -

-

- If this parameter is specified, the - external-tools goal will use it as the destination to copy the generated file. + Location of the Eclipse + workspace that holds your configuration and source. +

+ On Windows, this will be the workspace directory + under your eclipse installation. For example, if you installed + eclipse into c:\eclipse, the workspace is + c:\eclipse\workspace. +

+

+ If this parameter is specified, the + external-tools goal will use it as the destination to copy the generated file.

@@ -107,5 +107,26 @@ MAVEN_REPO that points to your local Maven repository.

+
+

+ 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. +

+ + group + artifact + version + + true + + +]]> +

+ This indicates that the dependency is another project in the workspace. + Note that the name of the referenced project is the artifactId. +

+