Hi all,
summary
-------
I have noticed a regression from appfuse version 2.0 to version 2.0.1.
I use struts modular + jpa.
Basically, version 2.0.1 now introduce (how? why? no idea ...) the
following dependency in the web app
my app
(...)
+- org.appfuse:appfuse-struts:warpath:2.0.1:compile
(...)
+- org.appfuse:appfuse-service:jar:2.0.1:compile
(...)
+- org.appfuse:appfuse-hibernate:jar:2.0.1:compile
(output from 'mvn dependency:tree')
Which eventually results in the war file containing both
appfuse-hibernate and appfuse-jpa jars, which is bad.
how to reproduce
----------------
generate struts modular artifact
mvn clean install gives [INFO] BUILD SUCCESSFUL
Change pom.xml, core/pom.xml and remove/rename hibernate config file as
documented in http://appfuse.org/display/APF/Using+JPA,
mvn clean install gives [ERROR] BUILD ERROR
A quick look at the WEB-INF/lib dir shows :
(...)
appfuse-data-common-2.0.1.jar
appfuse-hibernate-2.0.1.jar
appfuse-jpa-2.0.1.jar
(...)
removing appfuse-hibernate-2.0.1.jar fixes the issue.
Same workflow in 2.0 works fine.
workaround
----------
I have been able to workaround the issue by setting
<dao.framework>jpa</dao.framework>
in <M2_REPO>/org/appfuse/appfuse/2.0.1/appfuse-2.0.1.pom
which I do not feel like a good idea.
fix
---
I do not understand how this dependency gets into the web app.
What could be a cleaner solution than patching appfuse pom ?
Thanks
Christophe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
