If you add an exclusion to appfuse-${dao.framework} instead of
appfuse-service, does it fix the problem? Maybe we just need to update
our instructions. Also, if you're using Hibernate, you don't need to
exclude/include appfuse-${dao.framework} in your pom.xml - it's only
needed if you want to switch to JPA or iBATIS.
Matt
On 5/24/07, Tobias Vogel <[EMAIL PROTECTED]> wrote:
Hello,
I just tried to migrate from M4 to M5, and had some problems with
modified core classes. In M4 you had to add an exclusion of
"appfuse-data-common" to the dependency "appfuse-service". In my M5
archetype i did the same, but even after a full rebuild, the
appfuse-data-common package still gets included in the webapp and the
original core classes and hibernate.cfg get loaded. This leads to a
breaking application, as it depends on the modified classes and
configuration.
The only difference I could see between the two pom.xml files is the
foolowing part:
<dependency>
<groupId>org.appfuse</groupId>
<artifactId>appfuse-${dao.framework}</artifactId>
<version>${appfuse.version}</version>
</dependency>
I looked at the pom.xml of this dependency (in my case hibernate), and
it has appfuse-data-common as dependency, so it's clear why the package
still makes it into the full build.
I removed the dependency "appfuse-${dao.framework}" from the
core/pom.xml, and now all tests were successful. Shall i open an issue
and propose this solution, or may this cause other unwanted behaviour
i'm not aware of?
Kind regards,
Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://raibledesigns.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]