RFC: JMC-6173: jmc -open requires full path
Carmine Vincenzo Russo
carusso at redhat.com
Tue Jul 23 09:21:53 UTC 2019
Hi Mario,
Thanks for your reply.
I want to apologize but I misunderstood the issue, therefore I can not work
on it because I only have a Fedora machine available.
Sorry for the inconvenience,
Thanks,
Carmine
On Fri, Jul 12, 2019 at 1:56 PM Mario Torre <neugens at redhat.com> wrote:
> On Fri, Jul 12, 2019 at 1:43 PM Carmine Vincenzo Russo
> <carusso at redhat.com> wrote:
> >
> > Hi Erik,
> >
> > I want to point out a couple of things before going forward.
> >
> > In the issue description it says to use $ jmc -open recording.jfr instead
> > of $ jmc -open /Demo/recording.jfr
> > That's why I assumed the subdirectories where needed. While I get from
> your
> > words that we are working in the directory /Demo and from the command
> line
> > it needs the full path even if the file is in the current directory.
> Please
> > correct me if I am wrong.
>
> I jump on that only now, and I admit I don't have the full context,
> but this is what I understood being the problem.
>
> Basically we have those two use cases are:
>
> 1. A full path is always given
> 2. We open a file in the *current working directory*
>
> 1 is the default, it seems we need to implement 2, however I just
> tried on RHEL 8 too and I can't reproduce it. Perhaps this is an issue
> just on OSX?
>
> Cheers,
> Mario
>
>
> --
> Mario Torre
> Associate Manager, Software Engineering
> Red Hat GmbH <https://www.redhat.com>
> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898
>
--
Carmine Vincenzo Russo
More information about the jmc-dev
mailing list