sions can't be passed as arguments, then that needs to be
fixed too.
Either way, might as well file the bug so you can leave some clues to follow
for others experiencing the same obstacle.
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugi
this to work without quotes (since my path does not
contain any spaces)
2. I am expecting to be able to put anything inside the quotes
Do you agree? Should I file a bug report?
Thanks,
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp
t; or "\a" or "a\"
throw error "args contains not properly formatted string"
but "a\a" is ok
So looks like you can get by if you use the quotes, and then hope the
characters touching the quotes aren't a '\'. I didn't test for nested
quote
ng now, you want a general way to create a
String parameter value containing proper file separators
cowwoc wrote:
>
> ... this looks like a bug in the plugin. What do you think?
>
the parameters are resolved before the plugin even sees them though, right?
--
View this message in
bble.com/file/n696563/exec-output.txt
> exec-output.txt
>
> At first glance, this looks like a bug in the plugin. What do you think?
>
> Thanks,
> Gili
>
Here is a cleaned up log without -Dfoo=${file.separator}. You should be
focusing on java.library.path in this log.
h
cowwoc wrote:
>
> ... one of the arguments equal to "${basedir}/target".
>
maybe I'm missing something here, but why won't ${project.build.directory}
work?
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512
eas,
Surprisingly, this doesn't work. Please take a look at the attached log file
from maven-exec-plugin:
http://maven.40175.n5.nabble.com/file/n696563/exec-output.txt
exec-output.txt
At first glance, this looks like a bug in the plugin. What do you think?
Thanks,
Gili
--
View this me
ah, that is really overkill :-)
On Thu, Jul 1, 2010 at 12:08 AM, Andreas Sewe
wrote:
> Hi,
>
>> I need to invoke an external command using the Exec plugin, with one of
>> the
>> arguments equal to "${basedir}/target". The problem is that under Windows
>> this expands to "c:\\temp\\project/target"
Hi,
I need to invoke an external command using the Exec plugin, with one of the
arguments equal to "${basedir}/target". The problem is that under Windows
this expands to "c:\\temp\\project/target" because ${basedir} uses
Windows-style slashes whereas the rest of the argument uses Unix-style
slas
h. What can I do to
> ensure that the argument contains a consistent slash-style?
>
> Thank you,
> Gili
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512272p512272.html
> Sent from the Maven - Users mailing list arc
e it has no way of
knowing that the command-line argument refers to a path. What can I do to
ensure that the argument contains a consistent slash-style?
Thank you,
Gili
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512272p512272.html
Sent
11 matches
Mail list logo
