Details
-
Type: Bug
-
Status: Ready for testing
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.11.2.7, 2.11.3.0, 2.11.3_js
-
Fix Version/s: 2.11.3_js
-
Component/s: gradle, jalview-j2s
-
Labels:None
-
Epic Link:
Description
During the jalviewjs build process in gradle, the jalviewjsTranspile task uses an external eclipse (usually installed in ~/buildtools/eclipse) to run the transpilation.
Sometimes, for unknown reasons, this installation can get itself into a state that runs, but does not run the transpilations, even though it has the j2s plugin present (and running). In this case the jalviewjsTranspile task doesn't fail although it has not transpiled any jalview classes.
The jalviewjsTranspile task can analyse the eclipse output to decide whether a suitably successful transpilation has happened.
In future, it may be that the jalviewjsTranspile task runs eclipse but eclipse decides nothing is new to compile and therefore nothing is compiled or transpiled so try and take account of that.
Sometimes, for unknown reasons, this installation can get itself into a state that runs, but does not run the transpilations, even though it has the j2s plugin present (and running). In this case the jalviewjsTranspile task doesn't fail although it has not transpiled any jalview classes.
The jalviewjsTranspile task can analyse the eclipse output to decide whether a suitably successful transpilation has happened.
In future, it may be that the jalviewjsTranspile task runs eclipse but eclipse decides nothing is new to compile and therefore nothing is compiled or transpiled so try and take account of that.
Attachments
Issue Links
- blocks
-
JAL-4059 update swingJS for JalviewJS 2.11.2,2.11.3, and 2.11.4
- In Progress