Hi All,
I've been leaving this issue as it had less priority than others on my plate,
but
it's now been elevated. I've still not been able to resolve my problem of
being able to build this app on my development machine within Eclipse, but
not being able to build it from the console on the same machine, or from any
other machine.
The crux of the problem is that while the Eclipse-maven plugin builds my
application happily, when I run maven from a command-line (either on the
original windows box or another linux box) all my tests fail because the build
process is including the appfuse-data-common jars and ignoring my
modified core classes.
I'd followed the tutorial on core class modifications and had originally made
some mistakes in my POM configuration, but I believe I've fixed all those,
but it hasn't fixed my problem.
See further comments below.
On 31 Oct 2007 at 10:05, Matt Raible wrote:
> On 10/31/07, Rob Hills <[EMAIL PROTECTED]> wrote:
> > 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.
>
> The exclusion you added should fix this, I'm stumped as to why it doesn't.
>
> >
> > 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>
>
> Make sure your maven-warpath-plugin uses ${appfuse.version} for it's
> <version> element.
I'd actually had this hard-coded to "1.0-SNAPSHOT" for some reason, but
changing it to:
<plugin>
<groupId>org.appfuse</groupId>
<artifactId>maven-warpath-plugin</artifactId>
<version>${appfuse.version}</version>
[..]
<plugin>
hasn't made any difference to the problem. Incidentally, I notice that this
plugin has a <warpathExcludes> tag which lists a number of resource files.
Should that include a reference to the appfuse-data-common jars? If so,
how would I reference that?
TIA,
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]
