Hi Matt,
On 31 Oct 2007 at 8:39, Matt Raible wrote:
> You need to exclude it on the warpath dependency, not on the war dependency.
That was well spotted! Unfortunately, moving my exclusion down to the correct
dependency hasn't changed anything :-(
In my pom.xml, I now have:
<dependency>
<groupId>org.appfuse</groupId>
<artifactId>appfuse-${web.framework}</artifactId>
<version>${appfuse.version}</version>
<type>warpath</type>
<!-- This exclusion and the dependency following this
one allow DAO framework switching. -->
<!-- You only need these if you want to use JPA or
iBATIS. See APF-565 for more information. -->
<!-- It does no harm to leave it in for Hibernate, but
it's not needed. -->
<exclusions>
<exclusion>
<groupId>org.appfuse</groupId>
<artifactId>appfuse-data-common</artifactId>
</exclusion>
<exclusion>
<groupId>org.appfuse</groupId>
<artifactId>appfuse-hibernate</artifactId>
</exclusion>
</exclusions>
</dependency>
However, I still get all tests failing because of the same User class problems.
In my mvn -X output, I'm still seeing
"org.appfuse:appfuse-data-common:jar:2.0:compile (selected for compile)" in
various places.
I've also noticed the following early in the output from mvn -X and wondered if
it was relevant:
22:56:30.922 [DEBUG] Retrieving parent-POM: org.appfuse:appfuse::2.0-SNAPSHOT
for project: org.appfuse:maven-warpath-
plugin:maven-plugin:1.0-SNAPSHOT from the repository.
In my pom.xml properties, I have:
<appfuse.version>2.0</appfuse.version>
So I'm not sure why 2.0-SNAPSHOT is being used here. I had used 2.0-SNAPSHOT
early in this project, but moved up to FINAL as
soon as it was released. Could that be causing this problem?
Cheers,
Rob Hills
Waikiki, Western Australia
Mobile +61 (412) 904-357
Fax: +61 (8) 9529-2137
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
