Re: SNAPSHOT handling not working??
Forgot to mention that I of course use the updatePolicyalways/updatePolicy setting for the repository. Regards Claus Hi, I'm having problems getting maven2 to update/download the latest snapshot version from a remote repository. The snapshot version is deployed with maven and I can see that the metadata information (with buildnummer etc.) is downloaded but the jar itself is not!! It this a bug with version 2.0.4 or what must I do to get the jar downloaded?? Regards Claus - 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]
properties in assembly descriptor.xml?
Hi, I have serveral assembly descriptor files. Is it possible to get properties (from pom,settings,filters) available in the assembly descriptor files? This would be useful for avoiding to much duplication in the descriptor files. Regards Claus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with filtering of property files
The files are under the same subdirectory:
resource
directory*${basedir}/src/conf*/directory
filteringtrue/filtering
includes
includecontext.xml/include
includeversion.properties/include
/includes
/resource
**/version.properties... doesn't seem to do the trick.
Claus
Bravo, Kris wrote:
Are the files underneath subdirectories? You may need to go from this:
includecontext.xml/include
includeversion.properties/include
To this:
includecontext.xml/include
include**/version.properties/include
kris bravo * Clarify Development * office: 678.893.1288 * mobile:
678.296.8723
-Original Message-
From: Claus Myglegaard Vagner [mailto:[EMAIL PROTECTED]
Sent: Friday, June 02, 2006 9:59 AM
To: Maven Users List
Subject: Problem with filtering of property files
Hi,
I have a problem filtering property files (using maven 2.0.4):
Setup:
...
build
finalNameplanb/finalName
sourceDirectorysrc/java/sourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
filters
filter${basedir}/context.properties/filter
/filters
resources
resource
directory${basedir}/src/conf/directory
filteringtrue/filtering
includes
includecontext.xml/include
includeversion.properties/include
/includes
/resource
...
/resources
...
/build
...
Filtering of the above context.xml works fine, but filtering of
version.properties dosn't seem to work?
If I create a version.xml file instead an replaces it with
version.properties again it works... (any difference for *.xml contra
*.properties filtering?)
Ideally I would like to use settings.xml as filter instead of
context.properties but it only seems to work with context.properties...
Can anybody please help me with
1. why isn't version.properties being filtered?
2. why can't I use settings.xml as a filter?
Best Regards,
Claus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with filtering of property files
I'm using ${} tokens and the specified properties are either from
settings.xml or a pom property from pom.xml.
(I will make sure to double check for typos)
Claus
Max Cooper wrote:
I am not precisely sure what the difference is, but from looking at
the filtering code in the maven-resources-plugin in the past, I know
that it does treat *.properties files differently than other files.
These things might make a difference, too:
1. What delimiters are you using for the tokens? ${} is probably more
likely to work than @@.
2. How are the properties specified? There is an issue with replacing
system properties (specified on the command line with -Dname=value).
Are you are using system properties in your token replacements?
3. Watch out for typos that might mess up the token replacement
engine. For example, an unmatched }, {, or @ character can mess up
replacement.
As a real-world example of #3, the jboss-service.xml file that ships
with JBoss 4.0.3SP1 has a typo in it, and my token replacements
weren't working properly until I resolved it. This was the offending
line (note the paren instead of curly brace after jboss.server.home):
scans ${jboss.server.home)/deploy, which is always local
-Max
Claus Myglegaard Vagner wrote:
Hi,
I have a problem filtering property files (using maven 2.0.4):
Setup:
...
build
finalNameplanb/finalName
sourceDirectorysrc/java/sourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
filters
filter${basedir}/context.properties/filter
/filters
resources
resource
directory${basedir}/src/conf/directory
filteringtrue/filtering
includes
includecontext.xml/include
includeversion.properties/include
/includes
/resource
...
/resources
...
/build
...
Filtering of the above context.xml works fine, but filtering of
version.properties dosn't seem to work?
If I create a version.xml file instead an replaces it with
version.properties again it works... (any difference for *.xml contra
*.properties filtering?)
Ideally I would like to use settings.xml as filter instead of
context.properties but it only seems to work with context.properties...
Can anybody please help me with
1. why isn't version.properties being filtered?
2. why can't I use settings.xml as a filter?
Best Regards,
Claus
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem with filtering of property files
Hi,
I have a problem filtering property files (using maven 2.0.4):
Setup:
...
build
finalNameplanb/finalName
sourceDirectorysrc/java/sourceDirectory
testSourceDirectorysrc/test/testSourceDirectory
filters
filter${basedir}/context.properties/filter
/filters
resources
resource
directory${basedir}/src/conf/directory
filteringtrue/filtering
includes
includecontext.xml/include
includeversion.properties/include
/includes
/resource
...
/resources
...
/build
...
Filtering of the above context.xml works fine, but filtering of
version.properties dosn't seem to work?
If I create a version.xml file instead an replaces it with
version.properties again it works... (any difference for *.xml contra
*.properties filtering?)
Ideally I would like to use settings.xml as filter instead of
context.properties but it only seems to work with context.properties...
Can anybody please help me with
1. why isn't version.properties being filtered?
2. why can't I use settings.xml as a filter?
Best Regards,
Claus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
