<div dir="ltr">I agree that relative paths are a good idea. +1</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Aug 10, 2014 at 11:00 PM, Ondrej Zizka <span dir="ltr">&lt;<a href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I suggest we use relative paths.<br>
For the reports, using full paths may get overly verbose and make the<br>
reports unreadable.<br>
Relative paths are usually not, that much.<br>
Compare e.g.:<br>
<br>
      INFO: Unzipping<br>
/home/ondra/work/Migration/Windup/tests/core/target/../../../test-files/Windup1x-javaee-example.war<br>
to<br>
/home/ondra/work/Migration/Windup/tests/core/target/windupreport/archives/Windup1x-javaee-example.war<br>
<br>
vs.<br>
<br>
     INFO: Unzipping ../../../test-files/Windup1x-javaee-example.war to<br>
windupreport/archives/Windup1x-javaee-example.war<br>
<br>
The base path may be stated just once somewhere else.<br>
<br>
 From my experience, using relative paths may get tricky, needing to<br>
carry the base path(s) along with the relative, but still, is worth the<br>
work.<br>
<br>
my2c,<br>
Ondra<br>
<br>
_______________________________________________<br>
windup-dev mailing list<br>
<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>&quot;Simpler is better.&quot;
</div>