Your regex attempt looks as though you'll find careful reading of
perldoc perlre and
perldoc perlretut and/or the regex tuts
here useful. "Mastering Regular Expressions" would be a good followup; "Regular Expressions Pocket Reference" would often be helpful.
That said, one fairly direct route would be a lookahead -- which tells the regex engine you want to accept matches until the match would be what's in the lookahead... in this case, app/:
$line =~ m|.+(?=app/)(.*)\s--javaproc|
In other words, match 1 or more of anything (dot-plus) until there's a match on app/ and then capture up until the space before the --javaproc. Note that there's no need to escape the slashes in the patch when using alternate regex delimiters.
Update: eliminating the ".java" (per OP's spec) is left so there's some learning exercise left here.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.