David Matějček

> ``` > $ mvn -X clean package -Pfastest > ... > [ERROR] Failed to execute goal io.github.git-commit-id:git-commit-id-maven-plugin:5.0.0:revision (get-the-git-infos) on project glassfish-common: .git directory is not found! Please specify a...

> ...and fails. I either fudge it, get a git commit id or give up. I only know how to do the later. ``` git clone [email protected]:eclipse-ee4j/glassfish.git cd glassfish mvn...

> It just hangs on start. Actually it usually doesn't hang, but the initialization failed for some reason, so it cannot log anything. The first log is logged by the...

I can't see what we could improve with this now until we receive the `asadmin start-domain --verbose` output at least. @oxdrove , I have doubts about your results too, because...

> The same for 7.0.1 I will get here soon as I am preparing a video and a blog too ;)

Sorry, but GlassFish 4 is not a release of Eclipse GlassFish, but of it's predecessor Oracle GlassFish, which was maintained by Oracle. Can you reproduce it with GlassFish 7.0.5 and...

Shouldn't it be already possible just with ``` mvn clean install -pl :security-ee -amd -Pfastest -T4C ``` It is quite standard without additional custom magic which we want to avoid...

It is rather a convention to have the major version number in the root directory name in a zip file. Eclipse uses `eclipse` folder without version, Maven uses `maven-3.9.6`, JDK...

> I suggest dropping the version number and just have `glassfish` directory. > > I saw plenty of production installations that keep the default directory name, e.g. `glassfish5` even after...

That is more steps than "unpack and run" and later create a symlink (after verification that new production version is alright). I think that this is also why JDK and...