RE: how to 'point' to another properties file
Maven does allow you to override properties defined in the properties
files. In fact, the properties files have a well defined processing
order that's described here:
http://maven.apache.org/reference/user-guide.html#Properties_Processing
So, if you have a standard set of properties for one environment,
perhaps dev, you might define them in the project.properties file. You
could then override any or all of those properties with definitions in
${project.home}/build.properties, or ${user.home}/build.properties, or
even at the command line using the -Dproperty=value syntax.
Hope this helps.
..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 the property value in Maven.xml (the current solution only
enable change to properties to plugin, which is not good enough in my
case).
I had been working on creating a process to use Maven in our production.
But there are few properties are different from dev environment to
stage/ft/production.
I cannot find way to change properties after defined in the property
files. This might be a blocker if cannot be solved. I had tried to setup
different project.xml for different environment. But this is an
expensive solution. Any suggestion?
-David
On Tue, 2005-02-22 at 16:39, Hal Arnold wrote:
> Sorry if this has been asked and answered, but I searched to no avail:
>
>
>
> I'm autogenerating hibernate mappings and so I have my usual
> project.properties file with the following:
>
>
>
> maven.xdoclet.hibernatedoclet.fileset.0=true
>
> maven.xdoclet.hibernatedoclet.fileset.0.dir=${maven.src.dir}/java
>
> maven.xdoclet.hibernatedoclet.fileset.0.include=**/*.java
>
> maven.xdoclet.hibernatedoclet.hibernate.0.Version=2.0
>
>
>
> I noted somewhere that you should be able to do something like this in
> the project.properties:
>
> maven.hibernate.properties=conf/hibernate.properties
>
>
>
> This would allow you to remove the maven.xdoclet.hibernatedoclet.xx
> lines
>
> and move them into the new hibernate.properties
>
> located in conf. this doesn't seem to work
>
>
>
> I've also tried the usual (in the project.xml):
>
>
>
>
>
>conf
>
>
>
> hibernate.properties
>
>
>
>
>
>
>
> And even:
>
> conf/hibernate.properties
>
>
>
> Nada, zip, bupkis,
>
>
>
> Any help?
>
>
>
> /hba
>
>
--
David -- Powered by Thinking
Lead Java Engineer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How to display ALL values?
Is there some way to display all "variable" names and their values for a given scope point? I guess it's more than just variables. I'm interested in dumping, for debugging and learning purposes, the list of all name/value pairs, regardless of their source, that are defined and available to me (whether read-only or modifiable) at a given point. So, for example, within a given maven.xml file, I'd like to be able to dump all names and values of anything that is defined through any *.properties files, project.xml files, maven.xml files, plugins, etc., etc., ideally including an indication of the value's source, and whether it overrides an inherited value. This would help enormously in debugging problems, as well as in knowing what values I can leverage within my scripts, rather than re-inventing them. (I've been through the Maven documentation, and have come across some lists 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 # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: Question on accessing user-defined properties in maven.xml
It seems to be a problem in using the == comparison. If you use the
variable alone as the boolean expression, things seem to work:
build.properties:
myProp=true
Maven.xml:
...
myProp is ${myProp}
Yup, myProp is true!
Hmm, seems myProp is false!
Yup, myProp is true if you don't use an ==
comparison!
...
Results:
talkJellyToMe:
[echo] myProp is true
[echo] Hmm, seems myProp is false!
[echo] Yup, myProp is true if you don't use an == comparison!
-Original Message-
From: Qian Su [mailto:[EMAIL PROTECTED]
Sent: February 9, 2005 15:50
To: Maven Users List
Subject: RE: Question on accessing user-defined properties in maven.xml
Hi Russ,
Thanks for the quick reply. I don't think I have the same property
declared anywhere else. I believe it is a matter of correct syntax for
accessing the value of a user defined property. Below is portion of my
maven.xml file and the prints out for it:
hibernate.doclet.xxx: ${hibernate.doclet.xxx}
>> hibernate.doclet.xxx: true
...
>> never gets inside the if statement.
Can you please point it out to me as for how to access the value of '
hibernate.doclet.xxx' in the 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 defined with different values in
multiple property files? Properties defined in project.properties get
overridden by those in almost any other property file. (The only ones
with lower priority are those in plug-ins).
>From the user guide (http://maven.apache.org/reference/user-guide.html):
The properties files in Maven are processed in the following order:
* ${project.home}/project.properties
* ${project.home}/build.properties
* ${user.home}/build.properties
Where the last definition wins. So, Maven moves through this sequence of
properties files overridding any previously defined properties with
newer definitions. In this sequence your ${user.home}/build.properties
has the final say in the list of properties files processed. We will
call the list of properties files that Maven processes the standard
properties file set.
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:[EMAIL PROTECTED]
Sent: February 9, 2005 15:32
To: users@maven.apache.org
Cc: Qian Su
Subject: Question on accessing user-defined properties in maven.xml
Hi,
I declared a property of my own in project.properties file, but failed
to access the value of this property in maven.xml. Below is my sample
code in project.properties and maven.xml:
(project.properties)
hibernate.doclet.generate=true
(maven.xml)
...
It seems that the property set in project.properties is not visible in
maven.xml, however, if I run maven with
-Dhibernate.doclet.generate=true, then the 'if' statement does evaluate
to true. I tried to look for online resources to see how to access
user-defined properties in maven.xml but failed. I would really
appreciate any help here since it is a very commonly desired feature.
Qian
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Vir
RE: Question on accessing user-defined properties in maven.xml
Do you perhaps have the same property defined with different values in
multiple property files? Properties defined in project.properties get
overridden by those in almost any other property file. (The only ones
with lower priority are those in plug-ins).
>From the user guide (http://maven.apache.org/reference/user-guide.html):
The properties files in Maven are processed in the following order:
* ${project.home}/project.properties
* ${project.home}/build.properties
* ${user.home}/build.properties
Where the last definition wins. So, Maven moves through this sequence of
properties files overridding any previously defined properties with
newer definitions. In this sequence your ${user.home}/build.properties
has the final say in the list of properties files processed. We will
call the list of properties files that Maven processes the standard
properties file set.
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:[EMAIL PROTECTED]
Sent: February 9, 2005 15:32
To: users@maven.apache.org
Cc: Qian Su
Subject: Question on accessing user-defined properties in maven.xml
Hi,
I declared a property of my own in project.properties file, but failed
to access the value of this property in maven.xml. Below is my sample
code in project.properties and maven.xml:
(project.properties)
hibernate.doclet.generate=true
(maven.xml)
...
It seems that the property set in project.properties is not visible in
maven.xml, however, if I run maven with
-Dhibernate.doclet.generate=true, then the 'if' statement does evaluate
to true. I tried to look for online resources to see how to access
user-defined properties in maven.xml but failed. I would really
appreciate any help here since it is a very commonly desired feature.
Qian
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: remote repository must speak HTTP ??
No, the remote repository isn't _supposed_ to require http, but we've
had mixed results with this as well.
We've found that in some cases changing it to 3 slashes clears things
up: file:///localhost/... Unfortunately, it doesn't always seem to
work...in some cases 2 slashes are required, in other cases 3. I
haven't spent enough time on the problem to nail down the
differentiating criteria...hopefully someone else on this list can solve
the mystery. We're intending to host our local repository to an http
hosted one to avoid the problem entirely.
If you run into the same problem, where 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. Hansen [mailto:[EMAIL PROTECTED]
Sent: February 9, 2005 09:44
To: Maven User (E-mail)
Subject: remote repository must speak HTTP ??
I'm not having any luck with this:
maven.repo.remote = file://localhost/${basedir}/repository
Is that because a remote repository has to have an "http://"; URL ??
Thanks,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: installing different named artifact...
If I understand correctly, using this approach the client will have its version number before the "_client" in its name, i.e.: ejb:foo-1.0.jar client: foo-1.0_client.jar If so, given Maven's default expectation that version numbers immediately precede the extension, I presume the appropriate way for other projects to express a dependency on the client would be something like: foo 1.0_client Is this right? Thanks. ..Russ Jubenville -Original Message- From: Tom Bostelmann [mailto:[EMAIL PROTECTED] Sent: January 27, 2005 13:09 To: Maven Users List Subject: RE: installing different named artifact... So, I ended up with a bit of a hack for a solution. I ended up writing an ArtifactTypeHandler to handle 'ejb-client' type artifacts, which makes sure it copies it with the correct name. I also overrode the ejb:ejb-client and ejb:install-client goals so that they use the new type handler. Suggestions? Any better ideas? -Original Message- From: Tom Bostelmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 10:06 PM To: Maven Users List Subject: RE: installing different named artifact... Actually, in addition to that bug it also doesn't work well with a multi-project. In a multi-project it executes ejb:ejb, however, if I want to include the ejb:install-client, I end up having to do ejb:ejb again because the ejb:ejb-client has a prereq of "ejb:ejb". So, there are two problems: 1.) ejb:install-client doesn't install the client jar in your local repository with a name that ends with '-client' (it uses the same name as the ejb-jar artifact which is confusing). 2.) You can't have the project build both the client and the ejb-jar without building the ejb-jar twice (because ejb:install-client 'prereqs' ejb:ejb). How have others solved this?? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 5:47 PM To: Maven Users List Subject: Re: installing different named artifact... looks like a bug then, though I'll defer to someone with more knowledge of the ejb plugins as I don't use them directly. - Brett On Wed, 26 Jan 2005 17:40:20 -0800, Tom Bostelmann <[EMAIL PROTECTED]> wrote: > It copies it to the repository under jars using the same name, > unfortunately. > > Here's the end of the output of 'maven ejb:install-client' > > ejb:ejb: > [echo] Building ejb qpass_nextel_outbound-1.0 > [jar] Building jar: > /home/tbostelm/views/tbostelm_cnextel_bnd_2/vobs/Cnextel/ejb-jars/outbou > nd/target/qpass_nextel_outbound-1.0.jar > > ejb:ejb-client: > [jar] Building jar: > /home/tbostelm/views/tbostelm_cnextel_bnd_2/vobs/Cnextel/ejb-jars/outbou > nd/target/qpass_nextel_outbound-1.0-client.jar > Copying: from > '/home/tbostelm/views/tbostelm_cnextel_bnd_2/vobs/Cnextel/ejb-jars/outbo > und/target/qpass_nextel_outbound-1.0-client.jar' to: > '/home/tbostelm/.maven/repository/qpass_nextel/jars/qpass_nextel_outboun > d-1.0.jar' > Copying: from > '/home/tbostelm/views/tbostelm_cnextel_bnd_2/vobs/Cnextel/ejb-jars/outbo > und/project.xml' to: > '/home/tbostelm/.maven/repository/qpass_nextel/poms/qpass_nextel_outboun > d-1.0.pom' > BUILD SUCCESSFUL > Total time: 19 seconds > Finished at: Wed Jan 26 17:38:00 PST 2005 > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 26, 2005 5:29 PM > To: Maven Users List > Subject: Re: installing different named artifact... > > doesn't the ejb plugin already do this for you? > > - Brett > > On Wed, 26 Jan 2005 17:03:05 -0800, Tom Bostelmann <[EMAIL PROTECTED]> > wrote: > > I'm sure this question has been asked several times but I'm not sure > > what the 'best-practice' is at this point. My problem is that I'm > > generating an ejb-jar and would like the same project to generate the > > client-jar. So, the ejb-jar would have the name outbound-1.0.jar, and > > would be of type 'ejb', and the client would be > outboud_client-1.0.jar, > > which would be of type 'jar'. How do I do this using the same Maven > > project? > > > > I've tried fiddling with 'maven.final.name' and setting the > > 'pom.artifactId' but they both ultimately get installed using the same > > name (just different types). > > > > What's the best practice here? > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Create a J2EE application client?
Is there a plugin that creates a J2EE Application Client, i.e. creates the jar file along with the embedded application-client.xml file? (I'm sure I can use the jar plugin to get it done, but I expect it's already there somewhere, eluding my search at the moment.) Thanks. ..Russ Jubenville # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: Plugin version dependencies?
I was under the impression that this would work for a *project* within my build, where that project's artifact might be included in generated jar classpaths, bundled into ears, etc., of other projects. But here I'm talking about a *plugin* that participates in the building of those other 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 -Original Message- From: Haile, Mussie [mailto:[EMAIL PROTECTED] Sent: January 25, 2005 11:21 To: Maven Users List Subject: RE: Plugin version dependencies? Why don't you use SNAPSHOT for your Dev and the correct version for your production? This way, your developers would get the least version of the build as a SNAPSHOT. L8r. -M- -Original Message----- From: Russ Jubenville [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 25, 2005 10:37 AM To: users@maven.apache.org Subject: Plugin version dependencies? Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version 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 # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
Plugin version dependencies?
Is there a way to declare a project's dependency on a specific version of a Maven (or custom, for that matter) plugin? For example, assume that I felt the need to modify the jar plugin, which is currently at version 1.6 in my local repository, so I create a version 1.6.1. I want developers on the team to automatically get my new version, but I want the production build to still use the old version. I envision a declared dependency in my top project's project.xml file, indicating maven-jar-plugin version 1.6.1, the effect of which would be to automatically download the new version 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 # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: executing scripts from Maven
Not sure if Maven has a plugin for this (I'm sure someone else will step in with the proper Maven approach), but you can certainly run them via Ant tags in your maven scripts. Here's an example from a Windows environment: ... ... 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 Currently on-site at SOLCORP: 177 Lakeshore Blvd. E. * Toronto, ON M5A 1B7 (416) 673-6210 ext. 5338 [EMAIL PROTECTED] -Original Message- From: Tate Austin [mailto:[EMAIL PROTECTED] Sent: January 24, 2005 10:13 To: users@maven.apache.org Subject: executing scripts from Maven I'm still new to maven, but looking through the documentation I don't see the capabilities to execute scripts or *nix commands. Is maven not built to do that, is it simply something for the java-centric world or did I just not see that capability? We are attempting to use it as the principle part in migrating an old application to java and I am looking to see if it can execute some of the commands necessary for making a build happen. I can't really find a maven lexicon of commands aside from the plugins(or did are the plugins the source of command infrastructure?) # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal # # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: remove dependencies from classpath
If you're asking if you can prevent dependencies from being added to the classpath in a generated manifest within a jar, ejb or war, each of the related plugins looks for a corresponding property to be set to true in order to include it in the classpath: Jar plugin: jar.manifest.classpath Ejb plugin: ejb.manifest.classpath War plugin: war.manifest.classpath For example, in your jar project's project.xml file you might have: ... log4j 1.2.8 http://jakarta.apache.org/log4j/ true true ... 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 ext. 5338 [EMAIL PROTECTED] -Original Message- From: Charles-Alexandre Sabourdin [mailto:[EMAIL PROTECTED] Sent: January 24, 2005 05:01 To: users@maven.apache.org Subject: remove dependencies from classpath Hello, I wonder if there was a properties to set for dependencies to not be set into the classpath ? -- Charles-Alexandre SABOURDIN - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal # # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
Bundling dependents' dependencies?
I'm still feeling my way around Maven, and I'm sure I'm overlooking something obvious I have two projects: - jarProj whose artifact is a jar, and which has dependencies on external jars, such as extJar.jar - earProj whose artifact is an ear, and which lists jarProj as a bundled dependency I need to ensure that extJar.jar gets bundled within earProj.ear. Of course, I could just add extJar.jar as a bundled dependency in earProj. But this will quickly get out of control, ultimately leading me to have a super project listing every dependency I have in any possible subproject, which smells wrong. Since earProj is dependent on jarProj, and jarProj is dependent on extJar, the information seems available to make the connection. In fact, if I "install" jarProj.jar into my local repository, it publishes its pom. I'm not sure why it would do that except to facilitate navigating 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 Lakeshore Blvd. E. * Toronto, ON M5A 1B7 > (416) 673-6210 ext. 5338 > [EMAIL PROTECTED] > > # This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal #
RE: any examples on testing a TCP connection?
How about something like this:
http://localhost:8000"/>
Russ Jubenville
-Original Message-
From: Tim Brazil [mailto:[EMAIL PROTECTED]
Sent: January 21, 2005 10:26
To: Maven Users List
Subject: any examples on testing a TCP connection?
Hi
I have a goal that performs functional testing. I have a preGoal that
starts my product's daemon process (which initializes a TCP socket).
Since it takes several seconds for this daemon to get up to speed, I
need to sleep for a period of time prior to starting the tests. The
required sleep time can vary between machines and/or potential code
instrumentation.
I would like to perform a 1 second sleep interval loop while checking
for a successful connection to the daemon's TCP port; then break out
upon success. I too am a newbie. Does anyone have a snippet of script
that smells something like this?
Thanks for all your wonderful help in the past.
Tim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
RE: any examples on testing a TCP connection?
How about something like this:
http://localhost:8000"/>
Russ Jubenville
-Original Message-
From: Tim Brazil [mailto:[EMAIL PROTECTED]
Sent: January 21, 2005 10:26
To: Maven Users List
Subject: any examples on testing a TCP connection?
Hi
I have a goal that performs functional testing. I have a preGoal that
starts my product's daemon process (which initializes a TCP socket).
Since it takes several seconds for this daemon to get up to speed, I
need to sleep for a period of time prior to starting the tests. The
required sleep time can vary between machines and/or potential code
instrumentation.
I would like to perform a 1 second sleep interval loop while checking
for a successful connection to the daemon's TCP port; then break out
upon success. I too am a newbie. Does anyone have a snippet of script
that smells something like this?
Thanks for all your wonderful help in the past.
Tim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
#
This e-mail message has been scanned for Viruses and Content and cleared
by NetIQ MailMarshal
#
