continuum does not (or at least, didn't) support ClearCase and
> neither
> > > did
> > > > DamageControl.
> > > >
> > > > So we ended up with CruiseControl.
> > > > I'm fairly happy with it, but it's one big (underscored and ca
y happy with it, but it's one big (underscored and capital
> > letters) drawback is it's configuration.
> > But I gather there's work going on with that problem too.
> >
> > The nice thing about CruiseControl is it's flexibility - not it's
visual
&g
oing on with that problem too.
The nice thing about CruiseControl is it's flexibility - not it's visual
impact.
I'm *not* a GUI developer, so I'm capable of appreciating the things I do
not see ;-)
As always, the best way to determine the best solution for you - is to try
them
Hello.
We've been using Maven 1.0.x for about a year now, and I recently started
looking at Maven2 as we're going
to shuffle our build servers around a bit.
I've run into an issue:
When using Maven 1.0.x we've set up a list of repositories in
build.properties thus:
axx.repo.vob=${basedir}/../li
Hi'ya!
At our company I've got a build server running CruiseControl over Maven
without any Ant.
It just uses the Mavenbuilder plugin - works like a charm.
// Jan-Helge Bergesen, TMN Dept. AXXESSIT ASA | http://www.axxessit.no
- Reply to All the Original Message -
Author:
Hi all.
I'm getting the same exception, but using ClearCase.
Has the ClearCase connection string changed from the following:
scm:clearcase:
I assume the maven-changelog-plugin still reads this setting when
generating the
report?
Best regards.Mvh. Jan-Helge
--
Jan-
Hi all.
I'm just wondering... Have you ever attempted to create a dependency
without the or
tags?
Maybe I'm stupid, but I'd expect Maven to look for a jar
${dep.groupId}/jars/${dep.artifactId}.jar - but instead
it attempts to locate ${dep.groupId}/jars/${dep.artifactId}-.jar :-/
This is RC-1
${all_fail} div ${total_test}
Yields:
[echo] 5 div 107
[echo]
I.e.: the output of the j:expr is an empty string?
I'd expect something like 0.0467 - am I wrong?
Ah... this would be MPMULTIPROJECT-19.
Look at http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPMULTIPROJECT-19
"Glenn R. Golden" <[EMAIL PROTECTED]>
12.02.2004 01:21
Please respond to "Maven Users List"
To: "Maven Users List" <[EMAIL PROTECTED]>
cc:
Subject
I'm overriding one of "our own" properties which specifies the location of
where to copy the jar files to accomodate our legacy development env.
It would be nice if supported an "inherit (boolean)"
property.
I'll solve it with an . :-/
Jason van Zyl <[EMAIL PROTECTED]>
02.02.2004 19:42
P
Any idea anyone?
Is it possble to do this in the context?
Just to (attempt to) clarify:
I've got a property (a directory) set in a build.properties that is
shared among several
projects.
The projects "stage" their JAR files to this location for developer
"environment execution".
I'd like to b
Must the variables to be shared across a maven:maven invokation be placed
in a special context?
The following scenario behaves unexpectedly:
In one of the .properties files:
ext_jar_stage=[path A]
In my top-level maven.xml file within a goal:
Will use ${ext_jar_stage}
In the "sub_component
Hi all
I've seen that there has been a discussion regarding this before (at least
on the mailing list).
I gather one can circumvent this by modifying the appropriate
property/variable in a preGoal
(like maven.compile.src.set), but that would add to the maintenance
workload and really
it'd just
Duh! One prepends the property with ${basedir} (of course).
So that for the top-most property is "${basedir}/aDirectory" and the
sub-project property is "${basedir}/../aDirectory" :-}
[EMAIL PROTECTED]
07.01.2004 10:47
Please respond to "Maven Users List"
To: [EMAIL PROTECTED]
I'm having problems with properties in project.properties involving
relative paths:
For the top-most maven.xml/project it points to "./aDirectory"
For the subsequent directories i've for a shared project.properties that
has the property set to "../aDirectory".
When I use the reactor at the top i
Thanks for the advise, but it's Not An Option(tm).
I'm trying to analyze the "update" log from "cleartool update" on a
snapshot view.
This looks like:
New: sw\uml\FM.mdl \main\1
Updated:
sw\java\axxtmn\src\no\axxessit\client\appl\mapviewer\MapViewer.java
\main\tmn_1.1_pat
How does one get this to work?
${some.text}
won't work..?
Regards, Jan-Helge
Heh..
The example project.xml on the webpage files didn't include the
tag, and since I copied the template directly of the
website - it didn't work.
Added the tag in the project.xml files - presto!
Happy Hollidays one and all!
[EMAIL PROTECTED]
19.12.2003 13:56
Please respond to "Maven U
Nope. No work.
Maybe it's the hollidays..
Mikael Lundgren <[EMAIL PROTECTED]>
19.12.2003 13:35
Please respond to "Maven Users List"
To: Maven Users List <[EMAIL PROTECTED]>
cc:
Subject:Re: Regarding multiple projects and dependencies.
Hmm,
sometimes I
Hi, thanks for the tip.
The problem still that the order of processing is "file-system order", so
no
compilation/jar/install is performed in order to correct the "hole" in the
repository.
Takker så mye - God Jul og Godt Nyttår! (siste dag før ferie).
--
Jan-Helge
Mikael Lundgren <[EMAIL P
Continuing on the discussion driven by Nicolas;
I'm testing out Maven on three of our sub-components with the following
dependencies:
axxbs -> mediator -> common
(where the notation "a -> " means "a depends on b").
The directory layout is:
+- common
| +- src
| +- src_test
not resolve symbol" errors during "maven
java:compile".
Renaming the ZIP to a JAR (and relocating in the repository, as well as
updating project.xml) makes
the "maven java:compile" finish successfullly..
I'm sure it's something obvious I've overlooked
ry, as well as
updating project.xml) makes
the "maven java:compile" finish successfullly..
I'm sure it's something obvious I've overlooked - but if someone could
help me I'd appreciate it
greatly.
Regards, Jan-Helge Bergesen
Software Developer TMN Group, Axxessit ASA | http://www.axxessit.no
23 matches
Mail list logo
