Build System

[Uwe Plonus]

Hi all,

after having a new repository we should decide on the build system.

I'm open in this question.

When using maven I can offer a lot of experience and for any other build system I'm glad to learn much.

So what do you propose as build system?

Uwe

[Jiri Peinlich]

I am using both Maven and Gradle, I would not consider myself an expert in either. Personally I prefer Gradle over Maven, but feel free to ignore me. Gradle IMO provides a lot of ways how to express your build in a readable and flexible way. I would not recomend going too crazy about using all the features from start but the flexibility might come handy in the future. Finding a replacement of some maven plugins with Gradle equivalents might be difficult but we are not migrating a legacy maven build so I would not be too worried about that.

[Uwe Plonus]

When we decided on the build system (we have a gradle and a maven example in our repository now) we should start with transforming the project and try to create a first release with the new build system.

About releasing we should think about how to release...

[Jiri Peinlich]

There is loads of tests scenarios in the project testing corectness of the system. See:

jdip_168r1\etc\test_data

I did not spend much time figuring out yet how are the tests run but think it would be wise to figure out how to have the tests running properly before we do the release.

Jiri

--
You received this message because you are subscribed to the Google Groups "jDip Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jdip-develope...@googlegroups.com.
To post to this group, send email to jdip-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jdip-developers/8b5fbb3b-aec7-440d-837f-c87418c792f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Uwe Plonus]

I found the test cases and also the scripts that are used to execute the test cases (manually).

I started creating a wiki (https://gitlab.com/jdip/jdip/wikis/Home) where we can write down our findings on jdip and also the future structure.

Uwe

[Uwe Plonus]

So nobody has a preference on the build system, as it seems.

We should then start with gradle and refactor the project in a way so that we have the standard file tree in the project (/src/main/java etc).

gradle can work with this structure without any further configuration and then it would be easy to switch to maven if we see any problems (like needed plugins etc).

Uwe

[Jiri Peinlich]

I have rebased the original gradle build and pushed another branch dependent on the first one that now creates a jdip.zip that I can unzip and run the jdip.bat (I work on Windows).

If you run ./gradlew assemble from the root, the build should eventually produce a zip in d:\programming\jdip\jdip\jdip_168r1\build\distributions\jdip.zip. When I unzip the contents of that zip into a directory and run the jdip.bat jdip starts on my PC and I can interact with it. Please try it out.

[Jiri Peinlich]

I would not consider this build stable yet, i was just hoping that having something that works is a good start. I have moved the sources/resources into src/main/java src/main/resources. The variants currently build in a very hacky way.

I think I will now look into how to integrate the testing into the build process.

[Uwe Plonus]

Hi Jiri,

can I delete the branch "conversion-gradle" now? Also when I merge the branch "jdip_168r1-gradle" is this also eligible for deletion?

Uwe

[Jiri Peinlich]

* the conversion-gradle can be delted.

* the jdip branch can be merged I think and deleted as well. I have rebased it on top of master and added all the other subprojects into the gradle build. I did not raise the merge request yet because i wanted to double check the build first. 

* the introducint-generics branch should be introducing-generics - i kind of created it in hurry when i was leaving my home to pick it up on my other laptop. Sorry. I will rename it.

--

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

To view this discussion on the web visit https://groups.google.com/d/msgid/jdip-developers/00b97649-ad4a-40de-a7cf-68c9ee7fd1f1%40googlegroups.com.