[
https://issues.apache.org/jira/browse/OPENJPA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-341.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The Codehaus plugin from the report
is gone, replaced by openjpa-tools/openjpa-maven-plugin, and PCEnhancer.run now
handles a class with no metadata without failing (PCEnhancer.java:583-596 only
enhances when _meta != null). The cited commit 5d0162381 is about logging
skipped classes in the runtime and metamodel, not the enhancer, so it is the
wrong evidence. Please reopen if this still happens with OpenJPA 4.x.
> Maven build exits with non-null exit code when new class is added
> -----------------------------------------------------------------
>
> Key: OPENJPA-341
> URL: https://issues.apache.org/jira/browse/OPENJPA-341
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 1.0.0
> Environment: Using maven 2
> Reporter: Sudhakar Ramasamy
> Priority: Major
> Attachments: brazos.voter.lib.zip
>
>
> Attached is a sample eclipse maven project. In this sample project, if you
> issue a mvn package, the OpenJPA enhance goal will exit with a non-null exit
> code.
> If you were to delete the brazos.voter.lib.dao.Test.java class the code
> compiles just fine with the OpenJPA enhance goal. You will notice that
> Test.java is POJO with nothing in it.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
