[
https://issues.jboss.org/browse/FORGE-700?page=com.atlassian.jira.plugin....
]
George Gastaldi commented on FORGE-700:
---------------------------------------
The problem lies in the BSC maven processor plugin. The latest version (2.1.0-beta1)
ignores the <dependency> setting. Use the 2.0.5 as a workaround.
{code:xml}
<plugin>
<groupId>org.bsc.maven</groupId>
<artifactId>maven-processor-plugin</artifactId>
<version>2.0.5</version>
<extensions>false</extensions>
<executions>
<execution>
<id>process</id>
<phase>generate-sources</phase>
<goals>
<goal>process</goal>
</goals>
<configuration>
<processors>
<processor>org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor</processor>
</processors>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-jpamodelgen</artifactId>
<version>1.2.0.Final</version>
</dependency>
</dependencies>
</plugin>
{code}
Annotation processor
'org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor' not found
--------------------------------------------------------------------------------------
Key: FORGE-700
URL:
https://issues.jboss.org/browse/FORGE-700
Project: Forge
Issue Type: Bug
Components: Java EE APIs
Reporter: George Gastaldi
Fix For: 1.1.2.Final
When choosing a JPA Model gen (Hibernate) the following error occurs:
{code}
[INFO] javac option: -proc:only
[INFO] javac option: -processor
[INFO] javac option: org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor
[INFO] javac option: -d
[INFO] javac option:
/Downloads/workspace/forge-core/dist/target/forge-distribution-1.1.2-SNAPSHOT/bin/my3rdForgeApp/target/classes
[INFO] javac option: -s
[INFO] javac option:
/Downloads/workspace/forge-core/dist/target/forge-distribution-1.1.2-SNAPSHOT/bin/my3rdForgeApp/target/generated-sources/apt
[INFO] diagnostic error: Annotation processor
'org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor' not found
[ERROR] error on execute: error during compilation
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira