Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
Values for the outputDirectory property are ignored.
This POM snippet:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>openjpa-maven-plugin</artifactId>
<version>LATEST</version>
<configuration>
<includes>*/jpa/.class</includes>
<addDefaultConstructor>true</addDefaultConstructor>
<enforcePropertyRestrictions>true</enforcePropertyRestrictions>
<outputDirectory>$
/openjpa-enhance</outputDirectory>
</configuration>
<executions>
<execution>
<id>enhancer</id>
<phase>process-classes</phase>
<goals>
<goal>enhance</goal>
</goals>
</execution>
</executions>
</plugin>
...does not result in, e.g. target/openjpa-enhance being created.
a few answers:
a) for the use canse you asked (enhancement)
Since openjpa only enhances the currently compiled classes and doesn't create a different output directory for them, we don't evaluate the outputDirectory for this mojo.
b) for the sql creation
see the <sqlFile> tag of the sql OpenJpaSqlMojo
c) for schema creation
see the <schemaFile> tag of the OpenJpaSchemaMojo