Bug#1011131: josm: FTBFS with JavaCC 6

2022-05-20 Thread Emmanuel Bourg 

Le 17/05/2022 à 17:37, Sebastiaan Couwenberg a écrit :

In the upstream issue it's noted that javacc 6.1.3 was never released:

"
  This tagged release may or may not be released, but is tagged here so
  that we maintain a history prior to merging in Francis' substantial
  changes.
"

https://github.com/javacc/javacc/releases/tag/release_6_1_3


Good catch, and the tag has now been removed.



Would you consider downgrading to 6.1.2?


No I'll instead upgrade to the latest 7.x release, that's the version 
expected by javaparser.


Emmanuel Bourg

Bug#1011131: josm: FTBFS with JavaCC 6

2022-05-17 Thread Sebastiaan Couwenberg 

In the upstream issue it's noted that javacc 6.1.3 was never released:

"
 This tagged release may or may not be released, but is tagged here so
 that we maintain a history prior to merging in Francis' substantial
 changes.
"

https://github.com/javacc/javacc/releases/tag/release_6_1_3

6.1.2 is the most recent 6.x on Maven Central:

 https://search.maven.org/artifact/net.java.dev.javacc/javacc

And that works as expected:


https://github.com/simonpoole/OpeningHoursParser/issues/72#issuecomment-1129016265

Would you consider downgrading to 6.1.2?

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1011131: josm: FTBFS with JavaCC 6

2022-05-17 Thread Sebastiaan Couwenberg 

Control: tags -1 pending

On 5/17/22 13:27, Emmanuel Bourg wrote:

This can be fixed by building with the javacc5 package instead of javacc


Thanks for this workaround, I'll use that for the time being.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1011131: josm: FTBFS with JavaCC 6

2022-05-17 Thread Emmanuel Bourg 
Source: josm
Version: 0.0.svn18427+dfsg-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

josm fails to build with JavaCC 6:

[javac] 
/<>/src/ch/poole/openinghoursparser/OpeningHoursParserTokenManager.java:1182:
 error: incompatible types: possible lossy conversion from int to char
[javac]  throw new TokenMgrError(EOFSeen, curLexState, error_line, 
error_column, error_after, curChar, TokenMgrError.LEXICAL_ERROR);
[javac] 
  ^


This can be fixed by building with the javacc5 package instead of javacc