Use a regular expression to not consider comma between quote while co…

[YannLeCorse]

This PR addresses the issue described in #9309.
Rather than splitting on comma, we are using a regular expression to ignore the comma that are between a pair of quotes.
By doing that, we properly the exported packages even if the input string contains syntax like org.sample.pkg1;version="1.0.0";uses:="fr.free.ylc,fr.free.ylc.sample",org.sample.pkg2;version="1.0.0"

[matthiasblaesing]

In general this looks sane to me. Specially thanks for the added test. Please check the author information though the "Paperwork" check ensures that author information is valid and the assumption, that a real name consists of at least two parts that are separated by a space.

Have a look at https://github.com/apache/netbeans/pull/9310.patch (or your preferred git client that shows real author information), line "From: ".

I'm aware that there are countries/regions where a single name is common and if that is the case, no problem, if that does not apply to you, please adjust the author information. Thank you.

[matthiasblaesing]

@YannLeCorse before I forget this: changing author information requires a forced push. Contrary to normal pushes to PR branches, forced pushed don't result in information from github sent to reviewers, so if you do that, please also add a comment.

[YannLeCorse]

@matthiasblaesing Author info should be fixed now. Thanks again.

[matthiasblaesing]

Thank you for the update. From the code perspective this looks sane to me. I'm in the region of nitpicking. The commit message should describe why a change was done (and if huge give a summary of the changes). A quick idea:

Netigso: Fix parsing of complex Export-Package manifest entries

Export-Package entries are not just comma separated values, but can contain
parameters, which themselves can contain commas in quoted strings. These cases
need to be handled correctly.

This is a suggestion, feel free to rephrase of course.