Max Bowsher wrote:
Hi Max.
Chris Bredesen wrote:
and it creates them with
the assumption that the project names are the same as the artifact ID.
This is in fact not the case.
It should be the case, and is for me. What is it for you, and have you
any idea why it's different?
The project
Chris Bredesen wrote:
Max Bowsher wrote:
Chris Bredesen wrote:
and it creates them with
the assumption that the project names are the same as the artifact ID.
This is in fact not the case.
It should be the case, and is for me. What is it for you, and have you
any idea why it's different?
1) Are you using the *final* Ganymede ? the RC1 of Ganymede had a broken
understanding of project names vs. directory names.
2) That m2eclipse actually resolves dependencies to project dependencies
insteead of jar dependencies is a *Good thing* (e.g. change something in
hibernate core and
Max Bowsher wrote:
There does exist a corner case however - once you import a project into
Eclipse, Eclipse no longer cares about the name value in the on-disk
.project file. I suppose you had the relevant directories added to
Eclipse using manually created rather than plugin-generated projects.
Today I released 3.3.0.SP1 to account for a single issue with the
3.3.0.GA released a few days ago. Specifically, http://opensource.atlassian.com/projects/hibernate/browse/HHH-3437
. A public method got inadvertently removed from two event classes
which would cause general issues for any
