NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
Rob

Close issue 

 

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-1516

2016.02.092016.04.10 Open
Craig

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open

Progress

  
Scott
  • Sprint 28
  • On going Support
Cory
  • Sprint 28
  • On going Support
Deepak
  • Sprint 28
Craig
  • Sprint 28
  • Agile Admin

...

Sprint Status

Current Sprint  Sprint 28 (April 14, 2016 – April 27, 2016)

LexEVS 6.4 Agile Development - Sprint Status

LexEVS Compatibility

  • Remote service and client jar migration

LexEVS 6.4 Remote Service and Client Updates

CaCore caCore legacy code was mentioned and it was suggested that we should remove any CaCore caCore code.

Mayo will need to prioritize this work to determine where it will fit into our schedule. 

TODO:  Craig to create a JIRA item to track the removal of the CaCore caCore code.

PTE for CI and DEV environment discussion

  • CI Server
  • DEV Server

CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB.  This is being investigated by Mayo to see if we can get this working locally.

Scott noted that our Mayo Jenkins server is running on a system that has 8 Cores cores with 32 GB of memory.

 

DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.

There is a new 6.4 DEV container that Jacob is working on getting deployed.

 

NCI testing - They NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.

They NCI will also test the runtime API and Tin may will look at performance to compare 6.3 and 6.4.

 

Jason asked when the remote API will be available.  We suggested that it should be delivered by the end of sprint 29.  We will need to verify performance is still acceptable prior to releasing it to NCI.

CTS2 and jQuery Example Follow upKim was running into a cross site scripting issue.  Scott suggested using a JSONP call to resolve this issue.
LexEVS External UsersNothing to note.

...