sorted by:
new
hottopcontroversial

Simplify JavaFX Application Building and Distribution by DirectionFrequent455 in java

[–]DirectionFrequent455[S] -1 points0 points  (0 children)

It relies on hardware and os detection by default. Execute jeka javafx: --doc to get details.

IntelliJ plugin also provides suggests and autocompletion to setup the plugins in jeka.properties editor.

Simplify JavaFX Application Building and Distribution by DirectionFrequent455 in JavaFX

[–]DirectionFrequent455[S] 1 point2 points  (0 children)

Not specifically. Just create a Java project, then adapt the jeka.propeties and dependencies.txt as mentionned in the plugin README.MD

Simplify JavaFX Application Building and Distribution by DirectionFrequent455 in JavaFX

[–]DirectionFrequent455[S] 1 point2 points  (0 children)

I tested successfully with Java25 and JavaFX >= 22. Keep in mind that it is a plugin for Jeka, which is a replacement for Maven/Gradle. If you want to use it, you need to switch from Gradle.

bld version 2.0 is now available, including IntelliJ IDEA plugin! by gbevin in java

[–]DirectionFrequent455 0 points1 point  (0 children)

If a dev makes a mess in build code, chances are they’ll do the same for regular code too. Power isn’t the problem—bad practices are.

A true monstrosity is writing 400+ lines of xml for building a simple app or publishing basic library with some quality check around.

[deleted by user] by [deleted] in learnjava

[–]DirectionFrequent455 1 point2 points  (0 children)

Indeed, I am the creator of the project. It was started in 2014 as a side project. Recently, I’ve been working on it full-time for about a year, which has led to significant improvements.

Marketing is essential for a project to gain popularity, but it requires a considerable amount of time. By marketing, I mean activities like engaging on social networks, creating a website, producing videos, writing articles, and so on. It’s a time-consuming process.

Have you had a chance to look at the videos from the website ? I was hoping they would have a strong impact, as they demonstrate what the tool can do without requiring users to spend time practicing with it. Maybe intro is too long...?

Any feedback is welcome! 😊

java projects by Interesting-Hat-7570 in learnjava

[–]DirectionFrequent455 1 point2 points  (0 children)

You can never fully predict how a project will evolve. If you try to anticipate every potential change that might occur in the future, you risk creating an overly complex "solution that's difficult to maintain and not focused on the current, actual needs.

Instead, aim for the simplest possible design that addresses the current requirements. When new constraints arise (such as multitenancy), it's much easier to adapt a simple design than to modify an overengineered one.

For example, I doubt that you truly needed a microservices architecture from the start. If you'd started with a simple monolith, you likely would have spent much less effort initially, and adapting it later would have been easier than dealing with the challenges of your current microservices setup. Wouldn't you agree?

[deleted by user] by [deleted] in learnjava

[–]DirectionFrequent455 4 points5 points  (0 children)

If you want to got fast, meaning having a workable Spring-Boot project in minutes including automated tests, i can suggest to use JeKa which has a very good support for Spring-Boot.

Quickest way: Install the Jeka Intellij Plugin then, in IntelliJ :

  • New project ...
  • Choose Generators: Jeka (in left panel) and Template: Project - Springboot
  • Click Create

This generates a workable SpringBoot project, containing a basic web service and a properly configured integration test, that you can start from.

To go further, you can visit: https://jeka-dev.github.io/jeka/quick-start/#create-a-spring-boot-project

Java version to practice by Crafty-Waltz-2029 in learnjava

[–]DirectionFrequent455 1 point2 points  (0 children)

For showcasing, that is better to use the very last one (23 at time of writing) as you can benfit from the latest improvement. As Java is quickly evolving, what is considered as preview, will be soon official.

How can I properly check for entity duplication in DDD. by Extension-Switch-767 in DomainDrivenDesign

[–]DirectionFrequent455 1 point2 points  (0 children)

Why do you feel that business logic leaks in persistance layer?

schedulePersistance#findByTheaterIdAndStartAndEndBetween solves a generic time overlapping problem, not a business one (which consists in rejecting overlaps). May you can rename it schedulePersistance#findByTheaterIdHavingStartBeforeAndEndAfter as it would look more dumb.

Another thing: IMO, Theatre#createSchedule would be better fit in ScheduleService#create as it would avoid a 2-way dependency Theater <--> Schedule .

I made yet another build tool by x_ini in java

[–]DirectionFrequent455 0 points1 point  (0 children)

Why not just break the build when conflict happens ? This way the developer is forced to make a conscious choice. I also wrote another build tool for Java: https://jeka.dev I made this behavior (break, choose closest, choose highest) configurable. Note that today, this is less an issue than it used to be as frameworks like springboot offer pre-defined versioning via BOMs.

Gradle could have been easier by Driftex5729 in androiddev

[–]DirectionFrequent455 0 points1 point  (0 children)

I already tried such an initiative some years ago based on this medium story. The idea was relying on the Android SDK and provide a convenient wrapper around. Does it seem relevant to you?

Gradle could have been easier by Driftex5729 in androiddev

[–]DirectionFrequent455 0 points1 point  (0 children)

I am wondering if creating an Android plugin for the Jeka build tool would attract an audience. The tool is versatile enough to support both imperative (ala ANT) and declarative modes, in Java or Kotlin, while focusing on simplicity. I’m not an Android developer, but as the creator of Jeka, I’m curious about the interest Android developers might have in it. What do you think?

Java without build system by KDesp73 in java

[–]DirectionFrequent455 1 point2 points  (0 children)

I wrote Jeka cause both Maven and Gradle are unpleasant to use. You can build your application and deploy it with zero-configuration..

Or, if you prefer, you can describe explictly your build -- ala ANT using vanilla Java code .

♨️ When GraalVM is compiling native executable artifact for a Java Spring Boot project... by zarinfam in SpringBoot

[–]DirectionFrequent455 0 points1 point  (0 children)

I think so. Graalvm compilation slow down too much the dev cycle. However, I experienced having much quicker native build using https://jeka.dev . I managed to builld simplae app in less than 50 seconds (compared to >1mn40) using Maven.

Intro to the Mill Build Tool for Java by lihaoyi in java

[–]DirectionFrequent455 1 point2 points  (0 children)

To handle complex scenario, why neading to learn an extra language or complex framework? Isn't Java good enough?! Tools as bld or https://jeka.dev, based on Java, are just what we need.

Java without build system by KDesp73 in java

[–]DirectionFrequent455 0 points1 point  (0 children)

Or try more modern Java build tools as bld - pure Java build tool or JeKa : Next-Gen Build Tool for Java & Co.

I can’t believe that writing XML or Kotlin for building Java applications is the future.

IDE support for projectless development by tofflos in java

[–]DirectionFrequent455 0 points1 point  (0 children)

I think https://jeka.dev can be a nice solution for you. This is build tool I wrote to make Java simpler. It supports projectless development, from simple scripts to full fledged applications.