Checkstyle Error: Unable to get class information for ParseException.
I've just set up a new eclipse installation with CobaltPlatformSearch, following instructions here:
https://thehub.thomsonreuters.com/docs/DOC-831462
http://nsawiki.int.westgroup.com/wiki/index.php5/Java_developer_startup_instructions_(WestlawNext) I get hundreds of warnings in CobaltPlatformSearch: Unable to get class information for ParseException. This class does exist however, as a derived resource: /CobaltPlatformSearch/derived/com/trgr/cobalt/search/presearch/parser/javacc/ParseException.java Looks like something in the build sequence is not correctly picking up the generated resources? Makes it almost impossible to notice genuined checkstyle warnings as they get hidden amongst the noise of these warnings
https://thehub.thomsonreuters.com/docs/DOC-831462
http://nsawiki.int.westgroup.com/wiki/index.php5/Java_developer_startup_instructions_(WestlawNext) I get hundreds of warnings in CobaltPlatformSearch: Unable to get class information for ParseException. This class does exist however, as a derived resource: /CobaltPlatformSearch/derived/com/trgr/cobalt/search/presearch/parser/javacc/ParseException.java Looks like something in the build sequence is not correctly picking up the generated resources? Makes it almost impossible to notice genuined checkstyle warnings as they get hidden amongst the noise of these warnings
Tagged:
1
Answers
-
Here is one suggestion to look at. There is an answer there about configuring the classpath, rather than the source tree.
http://sourceforge.net/p/checkstyle/bugs/703/0 -
That seems to be the bug, but can't figure out fix/workaround from the link. As we're running in eclipse, would assume it uses the eclipse build path. Can't see anything in checkstyle settings in eclipse that let us choose a build path separate from the project build path?0
-
Read below the bug, in the section that says "Won't Fix"0
-
Are you sure you have the JavaCC plugin installed? I've not had this issue and build CobaltPlatformSearch all the time.0
-
The answer I got back via email was to manually delete the checkstyle warnings. Not ideal, as it means have to assume only false positives in massive list when I initialy delete everything. But does seem that with each new build, only shows new checkstyle warnings. Haven't been game to try a clean build and see if it brings back all those other warnings.0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛