Hi Tatu, 

*Idea for Jackson 3.0:* consider switching from Maven to Gradle (I would be 
happy to help).

*Rationale:* Gradle provides clean separation of the API and implementation 
for java libraries.

*Links:*

   - https://docs.gradle.org/3.4/release-notes.html#the-java-library-plugin
   - 
   
https://docs.gradle.org/4.1/userguide/java_library_plugin.html#sec:java_library_separation
   
Regards, 
Dejan

On Monday, August 21, 2017 at 2:29:50 AM UTC+2, Tatu Saloranta wrote:
>
> Quick update on design process for Jackson 3.0, regarding public API 
> incompatible ("major") changes [1]. So far I had collected ideas 
> under: 
>
>
> https://github.com/FasterXML/jackson-future-ideas 
>
> but for more concrete plans, I created a new repo (as per earlier 
> explanation on the mailing list) at: 
>
> https://github.com/FasterXML/jackson3-dev 
>
> So far I have created couple of initial ideas, and I will discuss many 
> of them over the list soon. 
> My goal here is that all API-changing modifications [1] would have an 
> entry (or be part of one) there. 
> While I will still be the Benevolent Dictator, I will try to consider 
> community's feedback as much as possible, and would especially 
> appreciate comments that add information about aspects I may not have 
> thought, including downstream effects on existing libraries, 
> frameworks and use cases. 
> Similarly if and when my impression on things like "no one uses this 
> feature" is wrong, please let me know. I usually hear about 
> compatibility breakages after the fact -- would be great to get signal 
> beforehand to either avoid those, or at least mitigate effects, offer 
> alternative up-front. 
>
> Also note that issue tracker here should NOT be used for filing issues 
> against Jackson itself -- for that existing trackers are to be used. I 
> will create entries here wherever needed to solve issues, but will try 
> to keep set of issues relatively lean. 
> Ideally these entries should form the backbone of 3.0 release notes, 
> although it is possible that I might use other issue trackers for 
> concrete work (i.e. details are TBD). 
>
> -+ Tatu +- 
>
> [1] about same as "changes that could not go in a minor version" -- 
> API that is exposed directly to using applications via mechanism other 
> than inheritance + override (and some of inheritance changes too). 
> Includes things like removal of piece of functionality; change to 
> interface(s); changes to default settings. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"jackson-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to