That workaround of running a clean mvn build on the cmd line before building in
IntellJ does not work for me anymore. It used sometime back (a month ago?).
No matter what I try… I cant get it to build in IntelliJ.
-roshan
On 3/1/17, 5:20 PM, "Jungtaek Lim" wrote:
The original plan was not
The original plan was not adding anything related storm-core in 1.x version
line and move out 2.0.0 fast. (That's what Bobby proposed for JStorm merger
phases.)
We didn't make it faster (sorry I couldn't contribute for this side at
all), and we broke the plan, and it makes harder and harder to mov
If we leave 1.x in this state it will forever remain un-usable within IntelliJ
.. hard to debug, UT etc. And 1.x will live for a while. Is rolling back some
of the non-critical offending commits that are causing this an option ? i
tried rolling back a bit but was unable to identify the offendi
>If we really need long time to discuss above, I'm even OK to revert DRPC
>port and start 2.0.0 with webservices unported, (DRPC, UI, Logviewer) and
>address them at 2.1 or other minor versions.
>
>Any other opinions?
>
Yes, it may be better to move to 2.0 sooner and migrate the pending components
Thanks Roshan for bring this up.
For me moving toward 2.0.0 makes more sense.
I know master branch has similar issue (DRPC) and it also has
not-yet-ported things but if we are going to struggle with 1.x branch issue
again and again, Storm 2.0.0 will never come. Another recent headache issue
is JD
Lately (about a week and half maybe) it has not been possible to get the
1.x-branch to build inside IntelliJ. None of the modules are able to locate the
LocalCluster class (which is a clojure class). Previously, every once in a
while, I used to get this problem in the storm-starter module and w