diff --git a/eclipse/xdocs/changes.xml b/eclipse/xdocs/changes.xml index 628aed14..17f78eb5 100644 --- a/eclipse/xdocs/changes.xml +++ b/eclipse/xdocs/changes.xml @@ -25,7 +25,7 @@ - Add property maven.eclipse.resources.addtoclasspath to control whether to add pom.resources etc or not. Provide backwards compatiblity. + Add property maven.eclipse.resources.addtoclasspath to control whether to add pom.resources etc or not. Provide backwards compatiblity. Set proper cactus.src.dir Fixed duplicated source entry issue. add property maven.eclipse.addResources=false to prevent the build resources from breaking old Eclipse builds. diff --git a/eclipse/xdocs/index.xml b/eclipse/xdocs/index.xml index 7c02aa24..df4e4927 100644 --- a/eclipse/xdocs/index.xml +++ b/eclipse/xdocs/index.xml @@ -107,10 +107,19 @@ target/generated-sources would be each type of generated code.

+ By default, the plugin will load as seperate source folders any directory found in + ${maven.build.dir}/generated-sources. So, if you generate your mock objects into + ${maven.build.dir}/generated-sources/mocks and your wsdl classes into + ${maven.build.dir}/generated-sources/wsdl 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 maven eclipse + just ensure you have already generated all of your source code. +

+

For example, if you used the XDoclet Plugin for Maven to generate Hibernate mapping files, - they would be placed in /target/generated-sources/xdoclet/. While, if you used the + they would be placed in /target/generated-sources/xdoclet/. While, if you used the Hibernate Plugin for Maven to generate the SQL scripts for generating a database then that - would be placed in /target/generated-sources/schema/. + would be placed in /target/generated-sources/schema/.
Settings in project.properties: