Fix error due to changed PHPParser API

[vansante]

This patch should fix #205

PHP Fatal error: Cannot use object of type PHPParser_Comment_Doc as
array in
C:\www\cw4\vendor\doctrine\annotations\lib\Doctrine\Common\Annotations\DocParser.php
on line 351

[aeterno00]

Functional/TranslationTest seems to be failing, but this seems entirely unrelated to the Extractor changes causing the Fatal error earlier as the extractors are not part of that test's scope.

All other tests seem to be passing, so I'm not entirely sure why Scrutinizer is claiming they're erroring out.

The fork also fixes issue #204

[auss]

Any idea when this can be merged ?

[vansante]

I don't know, as far as I know it is ready..
@schmittjoh ?

[damienalexandre]

👍, master is broken, use ~1.1.0.

[Venzon]

@schmittjoh
any update about this bug?

[fotomerchant]

👍 For us... This one is affecting a large number of our projects... LOL. We're doing translations by hand the old way until it's fixed :

[vansante]

You can instruct composer to temporarily use the fork, that will save you a bunch of work ;) :

"repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/vansante/JMSTranslationBundle"
        }
]

[Venzon]

any idea why we cannot merge fix into this repo?

[vansante]

Because no collaborators are responding 😟

[nurikabe]

+1

[chbruyand]

@schmittjoh any update ?

[Majstr]

When is this going to be merged?

[Venzon]

thx for merge