Comments on: Maven, Hibernate, JPA http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/ Middleware tech talk Fri, 21 Nov 2008 23:29:06 +0000 http://wordpress.org/?v=MU hourly 1 By: Fred http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1624 Fred Fri, 01 Feb 2008 22:37:02 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1624 I suffered also when I tried it first until I found that a nice guy in codehaus is maintaining a POM. So now I have only: >dependencies< >dependency< >groupId<junit>/groupId< >artifactId<junit>/artifactId< >version<3.8.1>/version< >scope<test>/scope< >/dependency< >dependency< >groupId<org.codehaus.mojo.hibernate3>/groupId< >artifactId<maven-hibernate3-jdk15>/artifactId< >version<2.0-alpha-1>/version< >/dependency< >dependency< >groupId<org.apache.derby>/groupId< >artifactId<derby>/artifactId< >version<10.2.2.0>/version< >/dependency< >/dependencies< I used JavaDB and so build a JUnit test that can run without container. The code full runnable code is <a href="https://www.jfrog.org/svn-jfrog/greenhouse/jpa/trunk/" rel="nofollow">here</a>, and the blog entry <a href="http://freddy33.blogspot.com/2007/07/jpa-namedqueries-and-jdbc-40.html" rel="nofollow">here</a>. I suffered also when I tried it first until I found that a nice guy in codehaus is maintaining a POM.
So now I have only:
>dependencies<
>dependency<
>groupId<junit>/groupId<
>artifactId<junit>/artifactId<
>version<3.8.1>/version<
>scope<test>/scope<
>/dependency<
>dependency<
>groupId<org.codehaus.mojo.hibernate3>/groupId<
>artifactId<maven-hibernate3-jdk15>/artifactId<
>version<2.0-alpha-1>/version<
>/dependency<
>dependency<
>groupId<org.apache.derby>/groupId<
>artifactId<derby>/artifactId<
>version<10.2.2.0>/version<
>/dependency<
>/dependencies<
I used JavaDB and so build a JUnit test that can run without container.
The code full runnable code is here, and the blog entry here.

]]> By: Cédric Vidal http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1537 Cédric Vidal Tue, 15 Jan 2008 09:30:06 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1537 Hi Bill, You might want to give a look at the Maven dependency mechanism documentation: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html It mentions transitive dependencies, which are very important to get right in order for maven to work properly. You also might want to give a look at Mavenizer, a little tool I have created which helps in mavenizing third party libraries. It handles transitive dependencies: http://mavenizer.sourceforge.net/ Kind regards, Cédric Hi Bill,

You might want to give a look at the Maven dependency mechanism documentation:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

It mentions transitive dependencies, which are very important to get right in order for maven to work properly.

You also might want to give a look at Mavenizer, a little tool I have created which helps in mavenizing third party libraries. It handles transitive dependencies:
http://mavenizer.sourceforge.net/

Kind regards,

Cédric

]]> By: alrubinger http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1464 alrubinger Tue, 08 Jan 2008 17:33:16 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1464 There's an example of extracting the versions into properties in the JBoss EJB3 Parent Build: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/build/pom.xml ...this way, all versions are together at the top, and will be consistent among all children of the parent (subproject POMs will not designate a version number). S, ALR There’s an example of extracting the versions into properties in the JBoss EJB3 Parent Build:

http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/build/pom.xml

…this way, all versions are together at the top, and will be consistent among all children of the parent (subproject POMs will not designate a version number).

S,
ALR

]]> By: Anonymous http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1460 Anonymous Tue, 08 Jan 2008 13:16:54 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1460 WTF just imagine those are xml tags :) <code> properties hibernate-em.version (3.3.1.GA,] hibernate-em.version properties </code> and your dependency looks like <code> dependency groupId hibernate-entitymanager groupId artifactId hibernate-entitymanager artifactId version ${hibernate-em.version} version dependency </code> Hopefully this time it works. WTF
just imagine those are xml tags :)


properties
hibernate-em.version
(3.3.1.GA,]
hibernate-em.version
properties

and your dependency looks like

dependency
groupId
hibernate-entitymanager
groupId
artifactId
hibernate-entitymanager
artifactId
version
${hibernate-em.version}
version
dependency

Hopefully this time it works.

]]> By: Anonymous http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1458 Anonymous Tue, 08 Jan 2008 13:06:45 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1458 (Pls remove previous comment) <code> [3.3.1.GA,) </code> <code> hibernate-entitymanager hibernate-entitymanager ${hibernate-em.version} </code> (A Preview mode would be very helpful sometimes ;) ) The version range simply defines minimum 3.3.1.GA or better. (Pls remove previous comment)

[3.3.1.GA,)

hibernate-entitymanager
hibernate-entitymanager
${hibernate-em.version}

(A Preview mode would be very helpful sometimes ;) )

The version range simply defines minimum 3.3.1.GA or better.

]]> By: Anonymous http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1457 Anonymous Tue, 08 Jan 2008 13:00:38 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1457 damn of course I meant (forgot the code tag) <code> [3.3.1.GA,) </code> and in your dependencies like <code> hibernate-entitymanager hibernate-entitymanager ${hibernate-em.version} </code> damn of course I meant (forgot the code tag)

[3.3.1.GA,)

and in your dependencies like

hibernate-entitymanager
hibernate-entitymanager
${hibernate-em.version}

]]> By: billburke http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1447 billburke Mon, 07 Jan 2008 22:43:19 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1447 Thanks for the Maven lesson. I'll have to figure out WTF that means now... :) Thanks for the Maven lesson. I’ll have to figure out WTF that means now… :)

]]> By: Anonymous http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1440 Anonymous Mon, 07 Jan 2008 19:38:32 +0000 http://bill.burkecentral.com/2008/01/07/maven-hibernate-jpa/#comment-1440 Well if the hibernate-entitymanager would be configured like the one on mvnrepository.com you would also get persistence-api and could leave out a lot of dependencies and only add them if you really need a specific version (annotations or in general hibernate). Furthermore I prefer either a parent pom with version extracted or at least in the same pom. Like [3.3.1.GA,) Well if the hibernate-entitymanager would be configured like the one on mvnrepository.com you would also get persistence-api and could leave out a lot of dependencies and only add them if you really need a specific version (annotations or in general hibernate). Furthermore I prefer either a parent pom with version extracted or at least in the same pom. Like
[3.3.1.GA,)

]]>