[
https://issues.apache.org/jira/browse/JUDDI-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689933#action_12689933
]
Tom Cunningham commented on JUDDI-166:
--------------------------------------
Removed all of the properties from the hibernate/openjpa persistence files that
we use for testing and added them to a pom. I would like to find a way to
pass them in from the pom -> maven surefire system properties through a
properties file, but the maven surefire plugin only seems to support passing
string values, not variables such as
${juddi.hibernate.maxRows}.
I've added a step into the juddi-core pom which then subsequently removes the
persistence.xml post-test but pre-package, which should ensure that the
persistence.xml is not put into the jar.
> Need review persistence.xml setup
> ---------------------------------
>
> Key: JUDDI-166
> URL: https://issues.apache.org/jira/browse/JUDDI-166
> Project: jUDDI
> Issue Type: Bug
> Reporter: Tom Cunningham
> Assignee: Tom Cunningham
> Fix For: 3.0beta
>
>
> Currently, our persistence.xml's are stored in
> juddi-core/src/main/resources/persistence. The user chooses the
> persistence framework they want using a property during the build :
> cd juddi-core
> mvn -Dpersistence=(hibernate|openjpa) clean install (where persistence= one
> of hibernate/openjpa)
> The persistence.xml then ends up in the built juddi-core.jar. Should we
> be shipping a persistence.xml inside of juddi-core.jar?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
