HALBuilder 2.0.1 release?

[Frederik Bülthoff]

Hello Mark,

first of all I want to thank you for your great work on HALBuilder. I was wondering whether you were planning on releasing a new official build any time soon?

Frederik

[Mark Derricutt]

Hi Frederik,

Well timed - I actually started work on HalBuilder 2.0.1 again last night:

- Separating out the API into its own repository

- Removing Guava as a dependency on the API ( this means the base API no longer exposes Optional<T>'s, or Predicates<T>'s

- Moved the use of Optional/Predicates to a new Representations helper class in halbuilder-java

- Added the initial halbuilder-scala extensions ( same as halbuilder-java, but as implicit conversions and using scala's Option[T]

2.0.1 is quite a change from 1.x in that all the classes have been renamed to be RepresentationXXX rather than ResourceXXX, and the artefact splitting.

Whilst it's a fairly big change, I don't think the changes will be that painful for people given the age of the project itself.

I should be pushing the new repositories later today all being well, then it'll be good to get some further feedback.

Mark

--
You received this message because you are subscribed to the Google Groups "HALBuilder Development" group.
To post to this group, send email to halbuil...@googlegroups.com.
To unsubscribe from this group, send email to halbuilder-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/halbuilder-dev/-/qx3DCRr_4iEJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Frederik Bülthoff]

Hi Mark,

Thank you for your quick response. I'll start looking into those newly created repositories right away.

Frederik

[Mark Derricutt]

I'm keen on hearing feedback on the direction I'm going with the changes.

With the split repositories I need to work out what to do with documentation/issues:

1) Have issues raised on each project, as relevant or
2) Also add another "documentation" or "meta" project to be a central issue repository

I think I favor a mixture, a separate doc project, but keep issues in the repos themselves - tracking the release they're in etc.