Upstream Requirements for MOI Migration

[ccoffrin]

Issues currently blocking further progress,

• FeasibilitySense Support jump-dev/Ipopt.jl#114
• Unsatisfiable requirements between JuMP, MOI, & Ipopt jump-dev/Ipopt.jl#129
• Add Support for MathOptInterface jump-dev/Cbc.jl#53
• Support for MathOptInterface jump-dev/Pajarito.jl#411
• Support for MathOptInterface jump-dev/Pavito.jl#7
• Support for MathOptInterface Juniper.jl#100
• Support for Start Values in MOI jump-dev/SCS.jl#109
• Solver Parameters in MOI jump-dev/SCS.jl#113

[chriscoey]

also jump-dev/Pavito.jl#7

[ccoffrin]

Migration status update.

https://discourse.julialang.org/t/jump-and-julia-0-7-1-0/12964

[ccoffrin]

At some point it will also be important to discuss the following points,

• the use of the with_optimizer pattern and how it make require PowerModels users to explicitly import JuMP
• will it be possible to specify solvers at the optimize! call, or should they always be provided at JuMP model instantiation

[ccoffrin]

These discussion points were addressed in a recent JuMP-Dev phone call. with_optimizer can be exported by PowerModels to make it cleaner for users. Solvers can be provided at the time of the optimize! call.