yeah, that was what I was thinking too. It didn't and the tests ended in a NoClassDef...

those aren't compile errors remember

I know, but there was a compile error before the test

...but they ran anyway...

is your assembly complicated? one of the reasons i stay away from that as a general solution is because the artifacts come and go. make sure you're frequently cleaning so that you have a repeatable build and not one that's building up artifacts over time

huh. Is'n't that the whole point of a build system - to get repeatable builds? This build error was due to an actual code error - too many parameters....

good. my point on the assembly is that you have to think in maven to get the repeatable builds. assembly cuts the line and starts grabbing artifacts from various build stages. this sometimes leads to build instability.

you're saying that it runs the assembly creation without regards to the build order which is based on the dependency tree?!

no, just that there's variation in assembly. it's more of a power user feature that requires an understanding of where it's placed and what lifecycle stage you're at to get the right artifacts. I use it myself, but only for a distribution zip that doesn't really fit with the typical packaging. it sounded like you were looking for maven suggestions earlier...if you're up and running, disregard

no no, I appreciate the input. I've only used Maven for two days so I'm still learning 🙂

@permalmberg are you coming from an Ant background?

Some 15 years or so back, yes

😛

I've been doing C++/C# almost exclusively the last 15 years.

this is whole other kind of environment...

yeah...i have worked with those languages too. C# seems like it's getting more Maven-like than the old makefiles I used with MFC

MFC....brrr 🙂

C# has NuGet...which is broken on so many levels

wow, just wow.

File.mkdirs()

returns false if the directories already exists....

yeah...my advice with Maven is that if you're reaching for assembly after 2 days, you're trying to graft your own build system onto Maven and you might have some problems down the line

Well, what should I do then? I want separate jars for each part of my modular project. I don't see any other option...

is your assembly project a separate project in and of itself? What I do is build each JAR as a by-the-book Maven projects (very little in the poms except for dependencies) and have a totally separate JAR pull the dependencies into another project. That's what I'm calling a distribution

No, it is not. I've hooked it up to the

package

phase

what's the rough structure? backend projects, fx projects, etc

@User uploaded a file: and commented: a few common modules which are reused. The rest is eitehr backend or fx

BaseModule, Common are reused by the others.

BaseModule is the parent?

CLI, Core, and Modules/* are all separate executables

No, HAP is the parent

there is a POM at the bottom outside the image 🙂