Bump jhlite dependency to 1.3.0

[murdos]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2716e1b) 100.00% compared to head (0430fa6) 100.00%.

Additional details and impacted files

@@             Coverage Diff             @@
##                main     #8760   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity      2819      2819           
===========================================
  Files            719       719           
  Lines          12410     12410           
  Branches         250       250           
===========================================
  Hits           12410     12410           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pascalgrimaud]

The main problem is:

• when generating jhlite custom, it will use the previous release instead of the last one
• in the CI, we can't use the last release as it doesn't exist yet

I don't know how we could solve it. Any idea?

[murdos]

@pascalgrimaud : I thought a bit about it, and I think we might solve that by:

• using maven resources filtering to replace jhlite version in src/main/resources/generator/dependencies/pom.xml by current jhlite version, using ${project.version} => that way custom-jhlite will always use the version of jhlite it has been generated with
• in CI, for custom-jhlite tests, extract the jhlite version required by custom-jhlite, and install in the maven local repository the jhlite-jar with the extracted version. mvn install:install-file -Dfile=jhlite.jar -DgroupId=tech.jhipster.lite -DartifactId=jhlite -Dversion=<extracted-version>

WDYT?

[pascalgrimaud]

Yes sound good
For th CI, we could use snapshot version too