Publish Serial and IO libraries to Maven Central by avinxshKD · Pull Request #1421

Publish Serial and IO libraries to Maven Central by avinxshKD · Pull Request #1421 · processing/processing4

Ported Serial and IO libraries from Ant to Gradle with Maven publishing, Serial now uses upstream jssc from Maven Central instead of the bundled fork. This completes the library migration work started in #1407 and #1411.

closes #1403

@Stefterv hey good evening, I’ve opened the PR as discussed.

Please let me know if any changes are needed Thanks

		dependencies {
		compileOnly(project(":core"))
		// TODO: https://github.com/java-native/jssc
		implementation(files("library/jssc.jar"))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#1106 please see here why this was this way

@Stefterv hey... saw that TODO was left there in #1106. At the time there wasn't a good public version. Looks like io.github.java-native:jssc:2.10.2 is being maintained now and works fine. Only API diff I found was getPortProperties() being removed, handled that by deprecating getProperties().

If there's something from the old fork that still needs to be there pls let me knw

Oh great, can you separate that out into a 2nd PR? I will need to look a bit deeper into that and don't want to block this one.

@Stefterv Done, PR now only has the IO library migration.

will open a separate PR for the jssc migration later as you asked. Pls let me know

Ah, please keep the work you did on publishing the serial library, just keep the jssc jar like it was 😅

@Stefterv oh alright, give me some time

college chaos ongoing 🥀

@Stefterv @catilac hey let me know if any adjustments needed.
Also pls let me know if there are any new issues for me, exams done :)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just tested on the raspi, seems fine!

Hey @Stefterv Just wanted to say I’ve genuinely enjoyed working on these migrations with you. Digging into the build setup and packaging details was a great learning experience for mee indeed :)

and really appreciate the thoughtful reviews and the context you shared in b/w, it helped a lot.

Also, is there a preferred place to keep an eye on upcoming or priority work for the project?

Thanks again🌸@Stefterv @catilac @SableRaf

Thanks @avinxshKD!

There is a public Processing Roadmap. I am not entirely sure how up to date it is right now. There are also priority labels on issues, thought they might also need to be revisited based on the current state of the project. You can always ask for clarification on a given issue.

The best way to see what is being worked on at the moment is probably to join discord.processing.org and chat with the maintainers on the dev channel, or attend one of the live calls with @catilac on Tuesdays!

@avinxshKD discord is best! let me know if you need help getting on discord

Thanks @SableRaf for the pointers. I’ll go through the roadmap and keep an eye on the priority labels.
And join Discord to stay in the loop, I haven’t used it much, but will try it out :)

Yes sure, happy to connect and discuss things with the maintainers.

That means a lot @catilac I’ll join Discord, haven’t used it much, but will try to figure it out fs
Open to discussing any of this further whenever it makes sense.

Once again thankyou all of you 🌸

@Stefterv can confirm the build works fine on a Pi 5. Y'all need any other testing before merging?