Module to make custom JHLite instance

[DamnClin]

Create a module to make custom JHLite instances to allow custom modules.

TODO:

• Deploy releases on maven central (cc @pascalgrimaud);
• Make the module.

In fact the module is pretty simple, it needs:

• The JHLite dependency;
• An updated main class with @SpringBootApplication(scanBasePackageClasses = { JHLiteApp.class, JHipsterCustomApp.class })
• Some documentation.

[pascalgrimaud]

Cc @avdev4j : we should discuss about this

[hdurix]

Good idea 👍

It would be easy to customize the common JHipster Lite!

[pascalgrimaud]

@jdubois : can you help here as you're the admin in the sonatype orga? I wonder if we can already publish this artifact or should we do a new request?

[jdubois]

@pascalgrimaud I don't understand, you want a specific project for JHipster Lite on Sonar cloud?

[pascalgrimaud]

@jdubois : no I want to publish to maven central, managed by sonatype (not sonarcloud)

[jdubois]

Oh sorry! Sonar/Sonatype this is confusing... As long as it's in the same groupId (tech.jhipster) I think you can directly push, and it will create a new project in that groupId. I can then check in the UI and give you statistics.

[pascalgrimaud]

Thanks, I'll try to publish it, so :-)

[pascalgrimaud]

Good news, it seems to work:

• https://oss.sonatype.org/content/repositories/snapshots/tech/jhipster/

I'm preparing the other PRs to update the current pom.xml

[pascalgrimaud]

I'm adding the bounty on the 2nd part: the module to generate this project.
This part can be done only after the release

[pascalgrimaud]

I manage to init the repository, but I think it needs to be validated.

@jdubois : can you log and have a look at https://oss.sonatype.org/#stagingRepositories plz ?

[pascalgrimaud]

And if I go to https://oss.sonatype.org/service/local/staging/deploy/maven2/tech/jhipster/lite I have this error:

<nexus-error>
<errors>
<error>
<id>*</id>
<msg>Staging of Repository within profile ID='58b316c0f54bc' is not yet started!</msg>
</error>
</errors>
</nexus-error>

[pascalgrimaud]

Maybe try to release it:

[pascalgrimaud]

I found the documentation about the workflow here : https://help.sonatype.com/repomanager2/staging-releases/managing-staging-repositories

[DamnClin]

The published jar is a spring boot style jar: that mean we can't really use it as a dependency since we won't have access to the JHLite classes.

We can decide to:

• Publish a "classic" jar;
• Publish a spring-boot AND "classic" jar using maven-jar-plugin;

Publishing the spring-boot jar don't seems to make a lot of sense since we already have a published docker image and the possibility to download it from github releases.

@pascalgrimaud what do you think? Any other impact I missed?

[avdev4j]

hi @DamnClin
Does that mean we can use this to generate empty modules to create our own? A kind of module starter, or something else?

Sorry if my question seems to be weird but I wanted to be sure ;-)

[DamnClin]

Not really. The goal is to be able to deploy an application and add custom JHLite modules without adding them to the open source project.

It is designed to allow custom modules in organizations. Ex: you are entando and want to deploy an instance without the module you don't support and with some specific modules.

[DamnClin]

Claimed https://opencollective.com/generator-jhipster/expenses/96567

[pascalgrimaud]

@DamnClin : approved