Workaround for eclipse not activating dev profile by default and hence having issue #9175

[pmverma]

Fix #9175.
Since profile id eclipse will be activated by default in eclipse IDE, dependency has been included there.

• Please make sure the below checklist is followed for Pull Requests.

• Travis tests are green

• Tests are added where necessary

• Documentation is added/updated where necessary

• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

[cbornet]

@jhipster/developers Is there something preventing us to set the dependency in <dependencies /> instead of <build /> ? I think gradle already does it this way !

[PierreBesson]

@cbornet +1, this would be a better solution. And can we remove the cc profile as well.

[jdubois]

• Yes let's remove "cc" I don't think anybody uses it
• And for the "build" part: this was probably coded by me, and as far as I know it can be moved without any issue

[pmverma]

@cbornet @PierreBesson @jdubois I think we should better create a new issue & PR for cleaning and refactoring pom.xml file. Let's close this PR.

I am not expert in configuring the pom.xml but I can help in it.
Is it only removing the cc profile and moving the dependency declaration inside <dependencies />?

[atomfrede]

I would say create a separate PR for removing th cc profile and cleaning up the pom.

[mraible]

Closing as requested by @pmverma.

[pmverma]

@mraible Sorry for my english. I meant to merge and close. This PR is still meant for #9175.
Can you please merge it?