Move to Maven

[tbeernot]

Hi all,

For me using Gradle as the build tool for JFXtras has been a headache causing experience, up to the point where I gave up maintaining it. The initial idea of Gradle is appealing, the practical result -requiring Groovy coding in the build scripts- turns out to be complex. I have had many discussions with collegues and developers about that even though Maven's XML format may not be that easily readable, the rigid structure is what keeps the build process clean. I believe Gradle requires the same rigid structure of lifecycles and plugins (something Andres is working on I believe) in order to not because a second ANT trap. Personally, I've learned from the experience in JFXtras and decided to not use Gradle in any of my projects, because it does not provide additional value: syntax readability is devalued with semantic complexibility.

In short: it is my intention to drop Gradle in JFXtras and switch to Maven. I have already a branch is place with does the build using Maven (god how simple that was to setup), I'm working on the last step of deploying to Central.

Please voice any objections.

Regards, Tom

[Gerrit Grunwald]

Go for it 👍🏻

Gerrit Grunwald

Westfalenstr. 93

48165 Münster

Germany

tel: +49 (0)2501 24321

mob: +49 (0)171 1745350

web: http://www.harmonic-code.org

--
You received this message because you are subscribed to the Google Groups "JFXtras Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/e977159b-c137-5653-a58c-6648ed3f5a92%40gmail.com.

[Mark Heckler]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/db6800b1-0dcd-4aaf-bc4a-fafa15e122fe%40Spark.

[Narayan G. Maharjan]

+1

[Michael Hoffer]

Hi Tom,

first of all, thanks for keeping the project alive!

I don't have strong opinions on that. I haven't used Maven for JavaFX projects yet so it will be a good opportunity for me to see how that works :) I have no objections.

Regards,

Michael

--

	Dr. Michael Hoffer Website:  www.mihosoft.eu Email:      in...@michaelhoffer.de

[tbeernot]

Hi Michael,

Agenda and more recently ResponsivePane is still enjoying some attention, so doing a bit of maintenance whilst there is not much better to do is no problem. ;-)

Regards, Tom

--
You received this message because you are subscribed to the Google Groups "JFXtras Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jfxtras-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/c513d723-66df-4eeb-981d-38a952a6e056%40googlegroups.com.

[Pedro Duque Vieira]

Hi Tom and guys,

No objections from me either. 

Given you are the one that is currently maintaining and working more with the main jfxtras repo, makes sense for you to use the tool you´re most comfortable with.

Personally I prefer Gradle, though might be because I use it all the time and it's the build tool I'm most acquainted with. 

Looking forward to the day where we don't even have to bother about these tools, only actually with programming. Everything will just be done automatically or in a really easy, quick, simple way :)

Cheers,

To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/99c70854-f419-6801-c1e2-4af2f5a08b4e%40gmail.com.

--

Pedro Duque Vieira - https://www.pixelduke.com

[Dean Iverson]

Sounds great to me.  I definitely understand why people may prefer Maven and I agree with Pedro that, as the primary maintainer, you get to choose the build tools you're like the most!

To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/CAAEud6bVD65C8WsgY9nwSUoOhaAPuzPjDzbYVaiHG4g%3DgsQBQA%40mail.gmail.com.

[tbeernot]

Totally not wanting to start a Gradle vs Maven discussion (luckily this is the right audience not to do that) I'd still want to elaborate just a tiny bit on what bugs me. For example the Asciidoclet part that Andres contributed so kindly.

https://github.com/JFXtras/jfxtras/blob/9.0/gradle/javadoc.gradle

Looking at that code it is well organized and readable. At first glance. But even after buying (and reading) a Gradle book and having spent numerous attempts trying to do it myself, there is no way I could have reproduced that. A javadoc block, and then another javadoc block. Wait... What?

https://github.com/JFXtras/jfxtras/blob/mavenfy/pom.xml#L78

Taking a look at the Maven implementation, then yes this is syntactically verbose with the XML and all, and at initial glance it gives a more complex impression. But if you strip out the XMLness into Groovy style, it becomes straight to the point. Even given that it is a more complex setup with a plugin in a plugin:

plugin {
    id org.apache.maven.plugins:maven-javadoc-plugin:3.2.0
    executions {
        execution {
            goal: jar
        }
    }
    configuration {
        doclet org.asciidoctor.Asciidoclet
        docletArtifact org.asciidoctor:asciidoclet:1.5.4
        additionalOptions {
            additionalOption --base-dir ${project.basedir}
            additionalOption --attribute "name=${project.name}"
            additionalOption --attribute "version=${project.version}"
            additionalOption --attribute "title-link=http://jfxtras.com[${project.name} ${project.version}]"
        }
    }
}

I think someone may start to say that 'yes, but someone wrote a plugin for Maven and in Gradle this was setup in the project'. But that would be making my point. :-D

Maybe the mental Gradle build structure image I have in my head is simply not right, so things do not hook up correctly there, apparently there are people alive who 'get it'. I do not. But hey, I am getting older :-)

Thanks all for supporting the change!

Tom

To view this discussion on the web visit https://groups.google.com/d/msgid/jfxtras-dev/CAMaih7HS5cQEX%3DQbHzBLOWTSFx-ANsPBv3EW1qkWXxkNCehz9g%40mail.gmail.com.

[Andreas Billmann]

Hi,

I struggled with gradle and I had my problems with maven.

So either choice is fine with me :-)

Regards,

Andi

Am Sonntag, 17. Mai 2020 10:15:15 UTC+2 schrieb tbee: