How to "pathconvert" under Maven?

Question

I am having a similar problem as Ant produces jsfl with backslashes instead of slashes except that I'm running under Maven.

I'd like to generate cross-platform paths relative to Maven's built-in property ${basedir}. The problem is that under Windows, ${basedir} resolves to a path containing Windows-style slashes. Is there an easy way for me to get ${basedir} into a form that always uses Unix-style slashes even under Windows?

I want to pass a path that depends on ${basedir} into "java.library.path" but ${basedir} contains the wrong slash type under Windows. — Gili, Jun 17 '10 at 18:59
I'm actually having a problem in that I need to pass in ${basedir}/passwordfile to maven-embedded-glassfish-plugin commands which the solutions below do not help with. — Archimedes Trajano, Dec 23 '13 at 09:27
@ArchimedesTrajano I suggest posting a separate question and linking to the answers that didn't work for you (explain what actually happened). — Gili, Dec 23 '13 at 15:42

Gili · Accepted Answer · 2016-10-07T03:18:36.057

11

Answering my own question:

Use ${file.separator} instead of slash and watch out for bug MEXEC-81 which was fixed in 2010 by git commit 6e8be6881fe50714a00509f8f106e21d50d606a6 (svn: 12372) which was where quotes and backslashes were misinterpreted.

edited Oct 07 '16 at 03:18

answered Jul 13 '10 at 02:58

Gili

86,244
97
390
689

score 2 · Answer 2 · edited May 23 '17 at 12:08

In the case of adding a dir to the library path, you are better off creating a new artifact with its own pom, installing it in your local repo and adding it as a dependency in the project.

Maven and Native Libraries: JDIC and java.library.path UPDATED goes into more detail about getting a native dependency into the library path.

Using native dependencies inside Maven Is another approach.

How to "pathconvert" under Maven?

2 Answers2