You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@predictionio.apache.org by "Donald Szeto (JIRA)" <ji...@apache.org> on 2018/09/17 21:28:00 UTC

[jira] [Commented] (PIO-82) Improve debugging experience in IntelliJ/Eclipse when developing templates

    [ https://issues.apache.org/jira/browse/PIO-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618169#comment-16618169 ] 

Donald Szeto commented on PIO-82:
---------------------------------

Documentation has been updated with instructions that will work with the latest version of IntelliJ. Keeping this open to address the other aspect of {{pio build}}.

> Improve debugging experience in IntelliJ/Eclipse when developing templates 
> ---------------------------------------------------------------------------
>
>                 Key: PIO-82
>                 URL: https://issues.apache.org/jira/browse/PIO-82
>             Project: PredictionIO
>          Issue Type: Improvement
>            Reporter: Sara Asher
>            Priority: Major
>
> From Pat: Make debugging templates with IntelliJ or Eclipse much easier. This may be helped by #1 above but perhaps also by doing refactoring of the CLI layers. This is the single worst roadblock to getting templates developed. I figured it out (with Donald) and documented it once upon a time but things you do, like changing the build.sbt or other things, can wipe out the config that was working, causing you to start over. I suspect the somewhat odd support for ES1 and ES5 may have complicated this. This IMO would help more than writing templates in Java! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)