.
..Russ Jubenville
-Original Message-
From: David Cao [mailto:[EMAIL PROTECTED]
Sent: February 23, 2005 13:35
To: Maven Users List
Subject: Re: how to 'point' to another properties file
Hi, this is a real need. I need:
1 Change the property file name by command line;
2 Or, change
of variables, but nowhere have I seen a comprehensive list,
and especially the ability to display all names, values and inheritance
status within the present scope.)
Is this a pipe dream? Or is there some special plugin / tag / sweet bit
of script that will do the trick?
Thanks in advance!
Russ Jubenville
sometimes it's 2, other times
it's 3, you may find using the following (less-than-ideal) trick of some
help:
maven.repo.remote = file:///localhost/${basedir}/repository, \
file://localhost/${basedir}/repository
..Russ Jubenville
-Original Message-
From: Mark D
.
In addition, System properties are processed after the above chain of
properties files are processed. So, a property specified on the CLI
using the -Dproperty=value convention will override any previous
definition of that property.
..Russ Jubenville
-Original Message-
From: Qian Su [mailto
' in the j:if tag using correct syntax?
Thanks!
Qian
-Original Message-
From: Russ Jubenville [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 12:41 PM
To: Maven Users List
Subject: RE: Question on accessing user-defined properties in maven.xml
Do you perhaps have the same property
way for
other projects to express a dependency on the client would be something
like:
dependency
idfoo/id
version1.0_client/version
/dependency
Is this right?
Thanks.
..Russ Jubenville
-Original Message-
From: Tom Bostelmann [mailto:[EMAIL PROTECTED]
Sent: January 27, 2005 13:09
to developers' machines and use that
version in their builds. Meanwhile, the old version would remain in the
repository, and since the production build's project.xml would still show
version 1.6, it would continue to use that version for its build.
Any help is greatly appreciated!
..Russ Jubenville
projects themselves. It's not that those other project's
classes, etc., are dependant on the new version of the plugin, but rather
the build process itself is dependent on the new version of the plugin.
Can I still use the SNAPSHOT approach in this case?
Thanks in advance!
..Russ Jubenville
/jar.manifest.classpath
ejb.manifest.classpathtrue/ejb.manifest.classpath
/properties
/dependency
...
Hope this helps.
Russ Jubenville, Senior Technical Consultant
Consulting Services, EDS Canada
Currently on-site at SOLCORP:
177 Lakeshore Blvd. E. * Toronto, ON M5A 1B7
(416) 673-6210
/
arg line=${db2commandfile}/
arg line=${db2args}/
arg line=${db2logfile} 2amp;1/
/exec
...
Doco for the exec tag in Ant:
http://ant.apache.org/manual/CoreTasks/exec.html
Hope this helps.
Russ Jubenville, Senior Technical Consultant
Consulting Services, EDS Canada
://localhost:8000/
and whatever other multiple conditions you might
care about/
/and
/waitfor
fail if=launchFailed message=*** ERROR: J2EE Server failed to
start ***/
/goal
Russ Jubenville
-Original Message-
From: Tim Brazil [mailto
://localhost:8000/
and whatever other multiple conditions you might
care about/
/and
/waitfor
fail if=launchFailed message=*** ERROR: J2EE Server failed to
start ***/ /goal
Russ Jubenville
-Original Message-
From: Tim Brazil [mailto
the jar's
inheritance hierarchy.
Have I just missed an option I need to set? Or is it not currently possible
for a project to automatically bundle its dependents' dependencies?
Thanks!
Russ Jubenville, Senior Technical Consultant
Consulting Services, EDS Canada
Currently on-site at SOLCORP:
177
13 matches
Mail list logo
