Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BAEL-137 Intro do JHipster #1427

Merged
merged 13 commits into from
Mar 21, 2017
Merged

BAEL-137 Intro do JHipster #1427

merged 13 commits into from
Mar 21, 2017

Conversation

felipe-gdr
Copy link
Contributor

First PR submission.

Let me know if the changes I made to the pom.xml generated by JHipster are enough to comply with Baeldung standards. pom.xml changes are in the last commit.

Moves inner implementations of Answer and ArgumentMatcher to the top of
the test classes.
Also changes the lambda expression to a regular "pre java 8" expression
in one of the tests.

Resolves: BAEL-632
Commit just after creating a JHipster project, before making any modifications.

Resolves: BAEL-137
From baeldung to jhipster-monolithic and JHipster Monolithic Application

Relates to: BAEL-137
- moved the <properties> element to the bottom of the file
- excluded integration tests in the default surefire configuration
- added a new profile, called integration, and added the integration tests there
- added Java 8 in the <source> and <target> tags, under maven-compiler

solves: BAEL-137
@pedja4 pedja4 merged commit 78f8710 into eugenp:master Mar 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants