I wanted to give you an update as to where I am with this as what you
included seems exactly like my problem. However, when I included the
plugins directive in the project.xml from where I build my webapp,
build
plugins
plugin
artifactIdmaven-war-plugin/artifactId
You have to wrap plugins in pluginManagement. The examples in the
documentation doesn't seem to mention this either, so it's a common
mistake for me as well. Ex:
build
pluginManagement
plugins
plugin
.
/plugin
You are mixing up the maven 2 pom with maven 1's project.xml, the maven 1 model
description is here:
http://maven.apache.org/maven-1.x/reference/maven-model/3.0.2/maven.html
In maven 1 you don't specify the plugins in the build section of your pom, you
either install them with 'maven
I did as you suggested, but got the parse error ...
maven war:war
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1
---
Error parsing project.xml
Thanks. I'm getting closer. I now have this in my dependency list ...
dependency
groupIdmaven-war-plugin/groupId
artifactIdmaven-war-plugin/artifactId
version1.6.3/version
typeplugin/type
configuration
attachClassestrue/attachClasses
Are you referring to this entry:
classpathentry kind=src
path=/myco-oit-governor-citizen-assistanceUtility-webapp/classpathentry
If so, try changing it to reference:
/myco-oit-governor-citizen-assistanceUtility-webapp/WEB-INF/classes
Unless Maven notices it's a WAR, and transforms the classpath
Hey,
This might help:
http://is.gd/4bPYH
If you have 2.1 of the WAR maven plugin, then it would work. Otherwise
you can just use the SNAPSHOT (all described on the thread).
Then, when you build it, the WAR will be installed into your local
repo, as well as an additional JAR (which only has the
Hi,
I'm using Maven 1.1. I have this dependency in my project.xml file ...
dependency
groupIdmyco.oit.governor.citizen.assistanceUtility/groupId
artifactIdmyco-oit-governor-citizen-assistanceUtility-webapp/artifactId
version${currentVersion}/version
typewar/type
Perhaps you meant ${project.version} instead of ${currentVersion} ?
Quintin Beukes
On Fri, Oct 9, 2009 at 5:43 PM, laredotornado laredotorn...@gmail.com wrote:
Hi,
I'm using Maven 1.1. I have this dependency in my project.xml file ...
dependency
Thanks, for now, I hard-coded the version to make this error go away.
Problem now is that it doesn't seem the dependency is getting included in my
classpath, because I get compilation errors (for classes that are included
in the dependency in question) now when I try to run, such as ...
maven
In your classpath, is that in fact where the files are put? Can you
confirm, from your project root, whether or not you can access those
classes using the relative/absolute paths specified in your classpath.
Specifically, when in your project's root, type: ls -ld
First off, thanks so much for taking the time to respond. To answer your
questions ...
In your classpath, is that in fact where the files are put? Can you
confirm, from your project root, whether or not you can access those
classes using the relative/absolute paths specified in your classpath.
12 matches
Mail list logo