Command line builder error when setting the port (v1.6.12) #5413

Closed
Erel2 opened this Issue Sep 25, 2016 · 5 comments

Projects

None yet

4 participants

@Erel2
Erel2 commented Sep 25, 2016 edited

Command line example: arduino_debug.exe --upload MyProject.ino --port COM54

Output:

Loading configuration...
java.lang.NullPointerException
at processing.app.BaseNoGui.selectSerialPort(BaseNoGui.java:1088)
at processing.app.helpers.CommandlineParser.parseArgumentsPhase1(CommandlineParser.java:143)
at processing.app.Base.(Base.java:273)
at processing.app.Base.guardedMain(Base.java:219)
at processing.app.Base.main(Base.java:132)

Seems like BaseNoGui.initPackages is not called.

@facchinm
Member

@cmaglie probably caused by 7d27c43

@hanabanana

Not to offend anyone, but regression like this really causes big problem for us because we rely on the CLI to compile and upload. Because of Sierra, we need to upgrade to 1.6.12 but this bug breaks our code from the beginning.
Seems like the IDE has switched from CLI to arduino-builder and separate upload command since 1.6.6(?). Does it mean the CLI will be less likely maintained or regression like this will occur more often in the future?

@facchinm
Member
facchinm commented Oct 3, 2016

@hanabanana, you are right, most of our CI tests switched using only arduino-builder.
I'm really sorry for the inconvenience and we'll immediately add this test to the testing infrastructure.
In the meantime, you can stick with IDE 1.6.11 only replacing the builder on Sierra with this package, or replace arduino-core.jar with the attached one
arduino-core.zip

@facchinm facchinm closed this Oct 3, 2016
@hanabanana

@facchinm Thanks for the workaround and quick fix. We will probably wait for the next release though since downloading and replacing the patches cannot be baked into our code. Any estimate of when the next release will come out?

@SB618
SB618 commented Oct 4, 2016

Yes, this needs to be regression tested. We have code that depends on this and has caused a big compatibility issue. Thanks for the workaround, please let us know when this will be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment