Re: Strange behaviour on resource plugin

2010-10-20 Thread Søren Krum
Hi!

fond it by myself: The -X helps a lot in between. The properties were
specified in a profile which was not active when running from the
command line.

Sorry for bothering you!

On 10/19/2010 04:09 PM, Søren Krum wrote:
> Hi!
> 
> I have detected a strange bahaviour of the maven resource plugin, and i
> am wondering if someone can give me a hint, what is going wrong here.
> 
> One of my maven projects uses the resource plugin to copy some
> configuration files with some placeholders in them.
> 
> When running maven from eclipse, the placeholders are nicely replaced
> with some values from the pom file, but when starting maven from the
> console, this replacement does not take place.
> 
> My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0
> from the command line, both not eager to do the replacement.
> 
> To make this behaviour even stranger, i detected this failing
> replacement after i updated my os from ubuntu 8/04 to 10/04, but i have
> no idea if that is really connected. I did not touch the maven
> installations at all, so it is a bit confusing
> 
> Any idea is highly welcome :-)
> 


-- 
Med vennlig hilsen

Søren D. Krum
Systemutvikler/system developer
UNINETT FAS
+ 47 73557859

There are 10 different kind of people in the world, those who understand
binary and those who don't

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Strange behaviour on resource plugin

2010-10-19 Thread Søren Krum
Hi!

I have detected a strange bahaviour of the maven resource plugin, and i
am wondering if someone can give me a hint, what is going wrong here.

One of my maven projects uses the resource plugin to copy some
configuration files with some placeholders in them.

When running maven from eclipse, the placeholders are nicely replaced
with some values from the pom file, but when starting maven from the
console, this replacement does not take place.

My eclipse uses a maven 3.0 snapshot, while i tried maven 2.2.1 and 3.0
from the command line, both not eager to do the replacement.

To make this behaviour even stranger, i detected this failing
replacement after i updated my os from ubuntu 8/04 to 10/04, but i have
no idea if that is really connected. I did not touch the maven
installations at all, so it is a bit confusing

Any idea is highly welcome :-)

-- 
Med vennlig hilsen

Søren D. Krum
Systemutvikler/system developer
UNINETT FAS
+ 47 73557859

There are 10 different kind of people in the world, those who understand
binary and those who don't

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org