in the classpath?
Rolf
On 2/8/06, Jay H. Hartley [EMAIL PROTECTED] wrote:
Rolf,
If you are using Maven 2, set the executable parameter for the
compile:compile goal:
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
http://maven.apache.org/plugins/maven-compiler-plugin/compile
Rolf,
If you are using Maven 2, set the executable parameter for the
compile:compile goal:
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
For a description of how to set compiler parameters, see
http://maven.apache.org/plugins/maven-compiler-plugin/howto.html
For Maven
Alternatively, if the mock objects are intended for use in multiple
projects, define them in their own project. They can then be deployed like
any other project artifact and can be used in test cases for multiple other
projects. When deploying the final application, exclude this jar in the same
It sounds to me like two types of documentation are needed. One is the/an
ideal Maven Way of setting up a consultant's multi-client project,
assuming you are starting fresh and know you will be using Maven. I
personally think that Maven is ideal for exactly that kind of environment,
but then I'm
In Maven 1 properties:
maven.scm.tag=BRANCH_TAG_NAME
See:
http://maven.apache.org/reference/plugins/scm/properties.html
In Maven 2 POM:
scm
...
tagBRANCH_TAG_NAME/tag
...
/scm
See:
http://maven.apache.org/maven2/maven-model/maven.html#class_Scm
I haven't used Maven 2
that just happen to
share the same codebase.
Good luck,
Jay
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 10:40 AM
To: Maven Users List
Subject: Re: [m1] Conditional dependencies
From: Jay H. Hartley [EMAIL PROTECTED]
2) Create two
Wendy,
I can't say I've had this exact problem, but I can think of two approaches
I'd consider:
1) Create a separate project, let's call it jsf. Have all the RI/MyFaces
jars listed in its dependency list. No code is involved, but the build
produces two artifacts, both uberjars (not that you'd
Our approach is to have a dedicated documentation sub-project, with just
xdocs. The multiproject parent project has little if anything in it, so the
default navigation is fine. One of the links then leads to Documentation.
That project then has a customized navigation.xml linking together all the
I'm a bit confused by the initial problem posed in this thread. This may
expose a fundamental misunderstanding of Java on my part, but if so I'd like
it cleared up by this fine group sooner rather than later.
I routinely build a project for a CDC target using a Sun J2SE 1.3 boot class
path,
