You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ep...@apache.org on 2004/10/26 10:12:25 UTC

cvs commit: maven-plugins/eclipse/xdocs index.xml changes.xml

epugh       2004/10/26 01:12:25

  Modified:    eclipse/xdocs index.xml changes.xml
  Log:
  Tweak docs to answer MPECLIPSE-55 entry maven.gen.src=${maven.build.dir}/generated-sources ignored
  better.
  
  Revision  Changes    Path
  1.4       +11 -2     maven-plugins/eclipse/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  RCS file: /home/cvs/maven-plugins/eclipse/xdocs/index.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- index.xml	15 Oct 2004 09:45:05 -0000	1.3
  +++ index.xml	26 Oct 2004 08:12:24 -0000	1.4
  @@ -107,10 +107,19 @@
         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 /target/generated-sources/xdoclet/.  While, if you used the 
  +      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 /target/generated-sources/schema/.
  +      would be placed in <code>/target/generated-sources/schema/</code>.
         <br/>
         Settings in project.properties:
         <source>
  
  
  
  1.39      +1 -1      maven-plugins/eclipse/xdocs/changes.xml
  
  Index: changes.xml
  ===================================================================
  RCS file: /home/cvs/maven-plugins/eclipse/xdocs/changes.xml,v
  retrieving revision 1.38
  retrieving revision 1.39
  diff -u -r1.38 -r1.39
  --- changes.xml	26 Oct 2004 07:57:06 -0000	1.38
  +++ changes.xml	26 Oct 2004 08:12:24 -0000	1.39
  @@ -25,7 +25,7 @@
     </properties>
     <body>
       <release version="1.9-SNAPSHOT" date="in cvs">
  -      <action dev="epugh" type="add">Add property <code>maven.eclipse.resources.addtoclasspath</code> to control whether to add pom.resources etc or not.  Provide backwards compatiblity.</action>        
  +      <action dev="epugh" type="fix" issue="MPECLIPSE-53">Add property <code>maven.eclipse.resources.addtoclasspath</code> to control whether to add pom.resources etc or not.  Provide backwards compatiblity.</action>        
         <action dev="felipeal" type="fix" issue="MPECLIPSE-52">Set proper <code>cactus.src.dir</code></action>        
         <action dev="felipeal" type="fix" issue="MPECLIPSE-51">Fixed duplicated source entry issue.</action>        
         <action dev="epugh" type="add">add property maven.eclipse.addResources=false to prevent the build resources from breaking old Eclipse builds.</action>        
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org