DEPRECATED: use https://github.com/jhipster/jhipster-bom instead

This is a merge of two "competing" (complementary) PRs: https://github.com/jhipster/jhipster/pull/46 https://github.com/jhipster/jhipster/pull/47

I will close those in favour of this one.

@DanielFran I hope this is satisfactory to you, if not please let me know! @jdubois If you prefer I can squash all my commits into one.

@jdubois To make my thinking more concrete, here's a proposal to put the jhipster serverside library and jhipster-dependencies in a single repository, with all plugin configuration managed in the same place.

This would resolve the co-dependency issue I mentioned here.

I've verified that maven-release-plugin, when running mvn release:prepare from the top directory, correctly replaces all the right version properties, so I would expect mvn release:perform to work well and release all three artifacts simultaneously.

Also, Travis works because it just hands off to the maven reactor, which builds the modules in the appropriate order -- and so Travis would fail if Maven fails.

But I noticed that the server-side library doesn't have any unit tests? This means that surefire and jacoco don't actually do anything at the moment... This is already the case on current master, though, so unrelated to this PR.

For what it's worth, I think it'd be all right to consider something like this change independently of the moment at which you would like to move generator-jhipster to use the new BOM.

Finally, if we would like to add some "steroids" like @Tcharl suggested, we would now have quite a natural place to do that.

Filtering over metamodel should create an outer join when query is entity?referenceEntityId.specified=boolean

The specification which is build based on an attribute, needs to check if this attribute is a referencing entity or is normal attribute

This is new PR for the new server side lib jhipster-framework which is gone be part o the new version 5.0.0. PR #37 is based on top of server side lib jhipster version 1.3.0. I do not know what is intent regarding acceptance of a patch for JHipster V4.

Fixes jhipster/generator-jhipster#6735

As promised earlier, I have been writing unit tests for the server lib. Unfortunately I am now starting a new project and can probably not spend (a lot of) time on this for the next couple of days / weeks.

So I thought I'd submit what I have, even though it's not entirely complete:

• The coverage for the classes that I have tests for is 100%, but I am still missing QueryService -- which I wasn't really sure how to test to be honest.
• Also not covered are the JSR310 converters, but I was wondering why we don't simply use the ones provided by Spring?

The first commit adds a utility class to assert the contents written to logback. If you like this idea, we could use it in the apps generated by the main generator too.

I adapted the project using the 'pom framework' here https://github.com/Tcharl/jhipster-parent

Feel free to create the jhipster-parent on the jhipster organization side and use it for the jhipster corp project.

Features:

• A jhipster 'corporate pom' to fill developpers, ci info, license...

• Automated ACL V2 header generation for corporate projects (using the maven-licence plugin

• Use of the maven-release-plugin to release projects to the maven central (tagging automatically the scm, deploying to sonatype staging, see readme.md for infos)

• Maven reporting standard site generation (goal: site site:stage will generate the maven site on /tmp/deploy)

• A bom to manage project dependencies (tested for the jhipster project: we should maybe add more)

• Plugin management for plugins versions and behavior

• Vendor neutral pom hierarchy (only the child jhipster-corp pom contains jhipster specific information)

• Apache compliance checking before jhipster project release.

See https://github.com/jhipster/generator-jhipster/issues/11681

Associated generator-jhipster PR: https://github.com/jhipster/generator-jhipster/pull/11682

Requirement for : https://github.com/jhipster/generator-jhipster/pull/7050

• Add git and maven build properties to /info endpoints (if build .properties files are on the classpath
• Add the active profiles to /info with a custom InfoContributor

I've been dreaming of this for a long long time. This is my proposal of a base entity to all entities. I can provide a PR for the generator afterward.

Enables some nice capabilities to Jhipster repo maintainers:

• Ability to release a snapshot pom using these two commands

./mvnw release:prepare --batch-mode -Prelease -s /.../settings.xml
./mvnw release:perform --batch-mode -Prelease -s /.../settings.xml

This release will increment SNAPSHOT to version to SNAPSHOT+1, tag release version.

• Generates a site listing dependencies or plugins upgrade (mvn site, or on the gh-pages branch after a release), which could be useful for maintaining bom

• Generates License headers automatically (that's the reason of all files modification).

Only the parent pom has been edited, and a new src/site/site.xml file at the root

@jdubois I would like to propose renaming the server-lib artifact, because it clashes with the artifactId of generated apps (with default settings) and Eclipse refuses to import because of it... It would only require a minimal change in generator and registry. The major v5 of the generator, along with a major v2 of the server-lib, would be the time to do it (if it is done at all).

Also, jhipster-parent is not a very descriptive name for the POM at this repo's root, it's not actually used as a parent anywhere. How about jhipster-build instead?

PS -- I think I had this in the original PR which merged jhipster-dependencies into this repository, looks like you changed it back deliberately. So maybe you don't think this is a good idea... Feel free to just close this in that case!

The file git.properties can conflict with the one from generated project (if there is one).

• Change prefix to jhipster-lib.git, properties looks like jhipster-lib.git.* instead of git.*
• Change generated file from git.properties to META-INF/jhipster-lib.git.properties

Related to https://github.com/jhipster/generator-jhipster/issues/12251