Re: [hibernate-dev] 3.3 and maven-eclipse-plugin
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 dependency in cache-ehcache, for example, is created as depending on 'hibernate-core' and 'hibernate-testing'. The physical directories that these projects are located in are 'core' and 'testing' respectively. When I remove the errant project deps and open the dialog to re-add them, I'm given 'core' and 'testing' as possibilities and those work fine. No I sure don't know why they're different, hence this email :) I don't know why maven would assume a project is named after its directory and not its artifactId. I can tell you this was not a problem in the earlier days when 3.3 was trunk. I wonder what changed? Have you built recently? I'm using Maven 2.0.8-SNAPSHOT...will try with 2.0.9. -Chris ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] 3.3 and maven-eclipse-plugin
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? The project dependency in cache-ehcache, for example, is created as depending on 'hibernate-core' and 'hibernate-testing'. The physical directories that these projects are located in are 'core' and 'testing' respectively. When I remove the errant project deps and open the dialog to re-add them, I'm given 'core' and 'testing' as possibilities and those work fine. No I sure don't know why they're different, hence this email :) I don't know why maven would assume a project is named after its directory and not its artifactId. I can tell you this was not a problem in the earlier days when 3.3 was trunk. I wonder what changed? The maven-eclipse-plugin has always assumed that the eclipse project name is equal to the artifactId (unless you configure it otherwise) - this isn't really an assumption, since this is the project name that it writes to the .project file. 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. If you delete the projects from the Eclipse workspace and re-import what the plugin generates, it should correctly name them hibernate-core and hibernate-testing. Have you built recently? Just now. I'm using Maven 2.0.8-SNAPSHOT...will try with 2.0.9. Why would you be using such an old snapshot? Or a snapshot at all? Not that I think it's the problem in this case. Max. signature.asc Description: OpenPGP digital signature ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] 3.3 and maven-eclipse-plugin
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 you dont have to wait for maven to complete it build to see the changes, same goes for refactoring etc). But if you really want it I do believe m2eclipse has an option for not making proper project dependencies but just do jar in repository dependency. -max 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 dependency in cache-ehcache, for example, is created as depending on 'hibernate-core' and 'hibernate-testing'. The physical directories that these projects are located in are 'core' and 'testing' respectively. When I remove the errant project deps and open the dialog to re-add them, I'm given 'core' and 'testing' as possibilities and those work fine. No I sure don't know why they're different, hence this email :) I don't know why maven would assume a project is named after its directory and not its artifactId. I can tell you this was not a problem in the earlier days when 3.3 was trunk. I wonder what changed? Have you built recently? I'm using Maven 2.0.8-SNAPSHOT...will try with 2.0.9. -Chris ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev -- -max ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] 3.3 and maven-eclipse-plugin
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. Hmm. Here's what I did: svn co /Branch_3_3 cd Branch_3_3 mvn install mvn eclipse:eclipse Then import into Eclipse from Branch_3_3 as workspace location. Will try it again from scratch, maybe I missed something. Thanks Max (and Max). -CB ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate Core 3.3.0.SP1 release
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 custom listeners of those events. See http://in.relation.to/Bloggers/330SP1 for additional details and download links. - Steve Ebersole Project Lead http://hibernate.org [EMAIL PROTECTED] Principal Software Engineer JBoss, a division of Red Hat [EMAIL PROTECTED] [EMAIL PROTECTED] ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
