I don't want to go for creation of maven assembly and packing things
together. Please suggest me if there are any other approaches
There is nothing stopping you from making another Maven project that
only contains your config files (in src/main/resources, perhaps) and
then publishing that to
Thanks Wayne,
If I do this and create a new .zip or some other artifact for my
configuration files, is it possible to deploy this by extracting the config
files to specific location using Cargo plugin?
Regards,
Tirumal Reddy M
-Original Message-
From: Wayne Fay [mailto:wayne
If I do this and create a new .zip or some other artifact for my
configuration files, is it possible to deploy this by extracting the config
files to specific location using Cargo plugin?
I haven't used Cargo in a while so I have no idea. It seems like
asking the Cargo folks directly would
configuration files, is it possible to deploy this by extracting the
config
files to specific location using Cargo plugin?
I haven't used Cargo in a while so I have no idea. It seems like
asking the Cargo folks directly would be the most efficient method to
get this answered.
Wayne
Hi,
I have a doubt regarding distributing configuration files which needs to be
deployed in application server. But these files needs to be separated from the
web achieve. I am publishing the web archive and other artifacts to remote
repository, from where I am picking up and deploying them
Hello,
I am new to this list and may just missed this topic discussion.
I have a web application that I need to compile and package into
war/ear/tar.
This app need to be packaged with different configuration files (server
names/IP addresses) for Dev/QA/Prod environments.
However I don't want
2010/11/22 ilya.may...@ubs.com:
This app need to be packaged with different configuration files (server
names/IP addresses) for Dev/QA/Prod environments.
This kind of info are better put in the server. For example, for
JBoss, you can create a .properties file and put it inside:
jboss/server
JNDI will do the job on Tomcat.
Ron
On 22/11/2010 1:47 PM, Antonio Petrelli wrote:
2010/11/22ilya.may...@ubs.com:
This app need to be packaged with different configuration files (server
names/IP addresses) for Dev/QA/Prod environments.
This kind of info are better put in the server
the appropriate files into
place. Then to build a dev environment you might do something like mvn -P dev
package. Of course, you can use any other plugin config within a profile
other than the ant plugin, such as having separate assembler plugin configs and
include different configuration files
assembler plugin configs and include different configuration files that way.
There's lots of way to do it; I'm not sure what the best one is.
eric
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: Monday, November 22, 2010 1:03 PM
To: users@maven.apache.org
: Haszlakiewicz, Eric [mailto:ehas...@transunion.com]
Sent: Monday, November 22, 2010 3:38 PM
To: Maven Users List
Subject: RE: Multiple packages with different configuration files
Well those are some rather useless answers.
JNDI will only do the job if you configure it that way. You need to
get
Email : ilya.may...@ubs.com
-Original Message-
From: Haszlakiewicz, Eric [mailto:ehas...@transunion.com]
Sent: Monday, November 22, 2010 3:38 PM
To: Maven Users List
Subject: RE: Multiple packages with different configuration files
Well those are some rather useless answers.
JNDI
Message-
From: ilya.may...@ubs.com [mailto:ilya.may...@ubs.com]
Sent: Monday, November 22, 2010 6:19 PM
To: users@maven.apache.org
Subject: RE: Multiple packages with different configuration files
Eric,
Let me elaborate on the issue. I cannot use profiles as it
will create only one
here.
The operations team need to keep their copies of the configuration
files up to date with any dev changes (like new configuration
variables).
Ideally you want to make this file as small as possible (i.e
production passwords and ip, port, url values)
Any values that are configurable, but dont
Once again, thank you to everyone who answered. I will investigate these
proposals.
About slf4j complaining about multiple configuration files present in
the CP, I suppose it must be possible to overcome this complaining. But
what is annoying to me is that these redundant files are included
About slf4j complaining about multiple configuration files present in
the CP, I suppose it must be possible to overcome this
complaining. But what is annoying to me is that these redundant files
are included when they should not, because from a logical point of
view project C does not need
sees two or more
configuration files on the class path, it emits a warning:
Hey, I see N different copies of logback.xml on your class path. The
copies are located at path1, path2, ..., pathN. I am picking the first
one. (It's just a warning...)
Lobgack-classic is noticing an ambiguity
Olivier,
Since projects A and B seem to be just artifacts, I am still wondering
why projects A and B need a configuration file for logging. If it is
for testing purposes, why not use logback-text.xml and place it under
/src/test/resources/ directory?
--
Ceki Gülcü
Logback: The reliable,
Ceki Gulcu a écrit :
Olivier,
Since projects A and B seem to be just artifacts, I am still wondering
why projects A and B need a configuration file for logging. If it is
for testing purposes, why not use logback-text.xml and place it under
/src/test/resources/ directory?
Indeed, it appears to
On 27 Apr 2009, at 21:32, Frédéric Camblor wrote:
This is only a point of view but...
Isn't the problem coming from the slf4f framework ?
I don't really know this logging framework, but it astonishes me
that it
complains about multiple configuration in the classpath.
Generally, framework
problem as the project C has) ;
- it does not solve the question of the log configuration file not being
integrated in the jar for easily modification by the end-user after
deployment ;
- the problem I face is a general problem, as I always use log
configuration files in my projects, so I
in the classpath (the
ones from A and B and C) when I would like it to find only the one from
project C.
I am thus wondering how to avoid this duplication of configuration files
(or avoid exposure of the A and B configuration files /for dependent
projects/). (Naturally completely excluding
it to find only the one from project C.
I am thus wondering how to avoid this duplication of configuration files
(or avoid exposure of the A and B configuration files /for dependent
projects/). (Naturally completely excluding logback.xml in A and B
wouldn't solve my problem as it would also
If A and B are only utility modules (not runnable), and you only use
the log configuration files for unit testing, I would have moved them
to src/test/resources in A and B. That way they are not made available
to C. C will have the log configuration file in src/main/resources, at
least
of configuration
files (or avoid exposure of the A and B configuration files /for
dependent projects/). (Naturally completely excluding logback.xml in
A and B wouldn't solve my problem as it would also exclude the
configuration file when running A or B themselves.)
More generally
project would have the same problem as the project C has) ;
- it does not solve the question of the log configuration file not
being integrated in the jar for easily modification by the end-user
after deployment ;
- the problem I face is a general problem, as I always use log
configuration files
the question of the log configuration file not
being integrated in the jar for easily modification by the end-user
after deployment ;
- the problem I face is a general problem, as I always use log
configuration files in my projects, so I would like to find a good
solution once and for all.
You can
of the log configuration file not being
integrated in the jar for easily modification by the end-user after
deployment ;
- the problem I face is a general problem, as I always use log
configuration files in my projects, so I would like to find a good solution
once and for all.
You can unpack
Thanks Brett!
It turns out that the jalopy plug-in does support multi-module projects ...
http://mojo.codehaus.org/jalopy-maven-plugin/examples/multimodule.html
Sorry for not looking at the docs a bit closer before firing off
questions on the mailing
list. But thanks anyway for drawing my
Hello group,
I have a multi-module project and I want to use the same jalopy (code
formatting)
settings for all the modules. I tried to add the following to the main pom.xml:
plugins
...
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjalopy-maven-plugin/artifactId
Sorry, for the confusing message, I hit a gmail shortcut that sent the
mail out prematurely.
So, again: I tried adding the following configuration to the main pom.xml:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjalopy-maven-plugin/artifactId
version1.0-alpha-1/version
The general approach used here can be seen in the checkstyle plugin - the
configuration is able to be provided at either a file, URL, or within a
repository artifact. The last option is the best since it makes advantage of
Maven's resolution and local caching but also makes it referencable from
I have a rather simple, common problems, that probably was solved
before. I looked at both jar and assembly plug-in and did not find the
answer.
I have to produce an executable jar with dependencies and with
configuration files that I'd like to be stored outside of the jar, like
the following
.
_
From: Naftulin, Henry BGI SF
Sent: Friday, March 14, 2008 12:10 PM
To: 'users@maven.apache.org'
Subject: Executable jar with extra directory for configuration
files [ASGI]
I have a rather simple, common problems, that probably
Message-
From: youhaodeyi [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 24, 2008 2:54 AM
To: users@maven.apache.org
Subject: Why is there two configuration files for Maven, settings.xml
and pom.xml
Can I put the configurations in settings.xml to pom.xml? Why does maven
use
two configuration
Subject: Why is there two configuration files for Maven, settings.xml
and pom.xml
Can I put the configurations in settings.xml to pom.xml? Why does maven
use
two configuration files?
--
This message may contain confidential, proprietary, or legally privileged
information. No confidentiality
On Sat, 2008-02-23 at 23:53 -0800, youhaodeyi wrote:
Can I put the configurations in settings.xml to pom.xml? Why does maven use
two configuration files?
The pom.xml is meant to be checked in to your version control system,
and will be published to the maven repository. This should produce
Can I put the configurations in settings.xml to pom.xml? Why does maven use
two configuration files?
--
View this message in context:
http://www.nabble.com/Why-is-there-two-configuration-files-for-Maven%2C-settings.xml-and-pom.xml-tp15661726s177p15661726.html
Sent from the Maven - Users mailing
Kalle, Thanks a lot!
-邮件原件-
发件人: Kalle Korhonen [mailto:[EMAIL PROTECTED]
发送时间: 2008年1月7日 11:47
收件人: Maven Users List
主题: Re: how to use maven project properties in other configuration files?
On 1/6/08, Fred Zhang [EMAIL PROTECTED] wrote:
My project is a multi-module project which
module or from
the project root pom in maven?
Best Regards
Fred Zhang
-Original message---
From: Kalle Korhonen [mailto:[EMAIL PROTECTED]
Sent: Jan.04.2008 16:31
To: Maven Users List
Subject: Re: how to use maven project properties in other configuration files?
Make your configuration
the properties and both ear and war are using them.
Kalle
-Original message---
From: Kalle Korhonen [mailto:[EMAIL PROTECTED]
Sent: Jan.04.2008 16:31
To: Maven Users List
Subject: Re: how to use maven project properties in other configuration
files?
Make your configuration file a filtered
files (not pom.xml or settings.xml). For
example, when I build an ear file with the name EAR-${project.version}.ear,
I need to use this ear name in some configuration file for JNDI-lookup.
But how can I use the maven property ${project.version} in configuration
files? Is there any plug-in that can
Hi there,
Sometimes I need to use maven project properties, e.g. ${project.version} etc
in some configuration files (not pom.xml or settings.xml). For example, when I
build an ear file with the name EAR-${project.version}.ear, I need to use
this ear name in some configuration file for JNDI
Where's the best place in the standard Maven layout to place configuration
files - I don't mean resources that end up bundled with the classes and
which are available on the final classpath, like property files.
By configuration files, I mean things like development-time web server
scripts
layout to place configuration
files - I don't mean resources that end up bundled with the classes and
which are available on the final classpath, like property files.
By configuration files, I mean things like development-time web server
scripts that are colocated with the project - but which
Hello,
This question is quite common. In fact, in my opinion, the documentation is
not enough clear for this point.
Have a look to nabble :
http://www.nabble.com/Default-location-of-config-files--%3E-Maven-Standard-Directroy-Layo-ut--tf3466078s177.html#a9672316
HTH,
Rémy
Hello,
I found a wiki page best practices: the location of configuration files
vs resources , but it is empty.
Can somebody define this best practice and explain what the standard way
is to use the src/main/config. This dir is a part of the standard
directory structure of maven 2 but nowhere
On 5/31/07, Tom Lambrechts [EMAIL PROTECTED] wrote:
Hello,
I found a wiki page best practices: the location of configuration files
vs resources , but it is empty.
Can somebody define this best practice and explain what the standard way
is to use the src/main/config. This dir is a part
/build
Cheers,
Sudheendra N Singh
-Original Message-
From: Cristian D. Romanescu [mailto:[EMAIL PROTECTED]
Sent: 11 April 2007 17:25
To: [EMAIL PROTECTED]
Subject: Newbie: running mvn test problem with configuration files and
current directory
Hello,
I
Hello,
I just downloaded maven and played a little bit with it.
I have the following problem (maven 2.0.6):
project structure
.
|
src
| main
| |
| java
| test
|java
| |src
| |resources
| |myconfig.xml
pom.xml
When I run mvn test, everything works fine, sources are
D. Romanescu [mailto:[EMAIL PROTECTED]
Sent: 11 April 2007 17:25
To: users@maven.apache.org
Subject: Newbie: running mvn test problem with configuration files and
current directory
Hello,
I just downloaded maven and played a little bit with it.
I have the following problem (maven 2.0.6
: 11 April 2007 17:25
To: users@maven.apache.org
Subject: Newbie: running mvn test problem with configuration files and
current directory
Hello,
I just downloaded maven and played a little bit with it.
I have the following problem (maven 2.0.6):
project structure
.
|
src
| main
| |
| java
with the
classloading of surefire.
My test configuration files are stored under the directory
src/test/resources. They are named as applicationContext-**-test.xml
When I start mvn test, Spring doesn t load the right directory:
[DEBUG] PathMatchingResourcePatternResolver - Looking for matching
resources
Hello,
I programmed some testcases which run perfectly under M1.x . I moved
them to M2 recently. Unfortunately, I have some troubles with the
classloading of surefire.
My test configuration files are stored under the directory
src/test/resources. They are named as applicationContext
when the app is
deployed into production I can change the settings. So basically check in a
directory structure to the repository.
Thanks
Naz
--
View this message in context:
http://www.nabble.com/Configuration-files-t1396714.html#a3766267
Sent from the Maven - Users forum at Nabble.com
directory
with all the config files that the users can change at will will. Thanks
--
View this message in context:
http://www.nabble.com/Configuration-files-t1396714.html#a3756335
Sent from the Maven - Users forum at Nabble.com
can change at will will. Thanks
--
View this message in context:
http://www.nabble.com/Configuration-files-t1396714.html#a3756335
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: lundi 24 octobre 2005 04:01
To: Maven Users List
Subject: RE: Where should configuration files go?
[snip]
We might want to align our notions:
http://maven.apache.org/guides/introduction/introduction
All,
I decided to keep the context configuration for Tomcat 5.5 external (vs. in
META-INF).
That brought up the question, where to keep external configuration files in the
Maven-suggested directory layout?
Any ideas?
Thx,
Janek
On Sat, 2005-10-22 at 14:05 +0200, Vincent Massol wrote:
Hi Robert,
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]
Sent: samedi 22 octobre 2005 14:03
To: users@maven.apache.org
Subject: Where should configuration files go?
Greetings,
I'm a recent
Greetings,
I'm a recent Ant-to-Maven 2.0 convert and am trying to mavenize some
existing greenfield projects.
In the past I have usually kept my Hibernate *.hbm.xml files in the same
directory as their corresponding .java files because it facilitates
referencing. Should I still keep them
Hi Robert,
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]
Sent: samedi 22 octobre 2005 14:03
To: users@maven.apache.org
Subject: Where should configuration files go?
Greetings,
I'm a recent Ant-to-Maven 2.0 convert and am trying to mavenize some
existing
Vincent, thanks for advice. I'll put it to good use.
/robert
Vincent Massol wrote:
Hi Robert,
-Original Message-
From: Robert Taylor [mailto:[EMAIL PROTECTED]
Sent: samedi 22 octobre 2005 14:03
To: users@maven.apache.org
Subject: Where should configuration files go?
Greetings,
I'm
-editable text configuration files (which CANNOT be included inside the
jar). This project utilised by several other projects in our organisation
and is listed as a Maven dependency in each of the latter's project.xml
files.
As a result, it's very easy to update the messaging jar in the other
We had a problem similar to this, but I don't think it's quite
identical. We have a project that builds a jar that also has external
configuration files that, when installed, may be updated by the
installer to fit the user's situation (so the configuration can't be in
the jar).
For the project
What is the maven.conf.dir property for? The user guide says, The directory
that holds configuration files. Configuration files for what?? Are they
included as a 'source directory' of sorts?? What does Maven do with the
config files?
I would like Maven to slurp up my configuration files
Hi Peter,
What is the maven.conf.dir property for? The user guide says, The directory
that holds configuration files. Configuration files for what?? Are they
included as a 'source directory' of sorts?? What does Maven do with the
config files?
Looks like maven itself doesn't use that property
build our project and create a zip containing the project's JAR, the
dependencies, and configuration files
3 deploy our project to the webapp
I'm stuck on 2. I have it done but the only problem is all my dependencies
are in the binary distribution:
postGoal
name=dist:prepare-bin-filesystem
I'm using Maven to create distributions for several of our projects. I'm
curious how people are including dependencies and configuration files in
their distributions? So far I'm using a postGoal on the
prepare-bin-filesystem goal with a copy dependencies (I forgot the tag).
This copies ALL my
69 matches
Mail list logo
