Re: maven 2.0.9+ and windows absolute paths

2008-12-17 Thread Dmitry Beransky
On Tue, Dec 16, 2008 at 3:34 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
 Dmitry Beransky wrote:

 Hi,

 It seems that Maven 2.0.9 has introduced a bug where Windows absolute
 paths aren't being properly resolved.

 [snip]

 Are you running Maven under Cygwin?

Nope, pure unadulterated Windows.

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



Re: maven 2.0.9+ and windows absolute paths

2008-12-17 Thread Dmitry Beransky
Another datapoint:

I've taken out the ant plugin where the problem was showing up before,
so now the Cargo plugin is failing with the same error.  Here's my
Cargo configuration:

configuration
container
containerIdtomcat5x/containerId
typeremote/type
/container

configuration
typeruntime/type
properties
cargo.tomcat.manager.url
${appserver.home}:8100/manager
/cargo.tomcat.manager.url
cargo.remote.usernamecsa/cargo.remote.username
cargo.remote.passwordcheckit
/cargo.remote.password
/properties
/configuration

deployer
typeremote/type
deployables
deployable
groupIdcom.csatp.website/groupId
artifactIdcsa/artifactId
location
${project.build.directory}/${warName}.war
/location
typewar/type
/deployable
/deployables
/deployer
/configuration
/plugin


Just like the ant plugin before, Cargo configuration uses
${project.build.directory} variable that comes through with an
incorrectly resolved Windows path.


Dmitry
On Wed, Dec 17, 2008 at 10:50 AM, Dmitry Beransky
dmitry.ma...@gmail.com wrote:
 On Tue, Dec 16, 2008 at 3:34 PM, Jörg Schaible joerg.schai...@gmx.de wrote:
 Dmitry Beransky wrote:

 Hi,

 It seems that Maven 2.0.9 has introduced a bug where Windows absolute
 paths aren't being properly resolved.

 [snip]

 Are you running Maven under Cygwin?

 Nope, pure unadulterated Windows.


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



maven 2.0.9+ and windows absolute paths

2008-12-16 Thread Dmitry Beransky
Hi,

It seems that Maven 2.0.9 has introduced a bug where Windows absolute
paths aren't being properly resolved.  A project that builds just fine
with 2.0.8 produces this error under 2.0.9:

[INFO] An Ant BuildException has occured: Failed to copy E:\svn\team\csa\main\re
sources\WEB-INF\log4j-production.xml to E:\svn\team\csa\main\e:\temp\maven\csa\t
arget\csa-5.2.1\WEB-INF\classes\log4j.xml due to java.io.FileNotFoundException E
:\svn\team\csa\main\e:\temp\maven\csa\target\csa-5.2.1\WEB-INF\classes\log4j.xml
 (The filename, directory name, or volume label syntax is incorrect)

Notice that e: is being treated as a relative path.

Here's the plugin where the error happens:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.3/version
executions
execution
idcopy-extra/id
phaseprocess-resources/phase
configuration
tasks
copy
tofile=${buildDirectory}/${artifactId}-${version}/WEB-INF/classes/log4j.xml

file=resources/WEB-INF/log4j-production.xml
  overwrite=true/
copy
tofile=${buildDirectory}/${artifactId}-${version}/META-INF/context.xml
  file=resources/WEB-INF/conf/context.xml
  overwrite=true/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin

${buildDirectory} is defined in the same pom as:

buildDirectory${project.build.directory}/buildDirectory

And the project's output directory is set in a parent pom:

 outputDirectory${buildDir}/classes/outputDirectory

   properties
 workDir${java.io.tmpdir}/workDir
 buildDir${workDir}/maven/${pom.artifactId}/target/buildDir
   /properties


Has anyone seen this or similar problem before, any ideas how to solve it?

I've tried compiling the latest version of Maven 2.1 from the
subversion repo and I'm getting the same error there too.


Thanks
Dmitry

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



Re: maven 2.0.9+ and windows absolute paths

2008-12-16 Thread Jörg Schaible
Dmitry Beransky wrote:

 Hi,
 
 It seems that Maven 2.0.9 has introduced a bug where Windows absolute
 paths aren't being properly resolved.

[snip]

Are you running Maven under Cygwin?

- Jörg


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