maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Chaudhuri" <>
Subject RE: Hibernate 3 Plugin
Date Thu, 13 Aug 2009 21:53:33 GMT
With Karl's suggestion, I changed my plugin definition as follows:


Unfortunately, I am still getting the same error.  

I am wondering if this has to do with the fact I have a multi-module project.  This persistence
pom produces a jar packaging and is dependent on no other modules, but it does have a parent
pom that simply lists the modules and defines dependencies in common among modules like Spring.
 Should my plugin definition be at the parent level?


-----Original Message-----
From: Karl Heinz Marbaise []
Sent: Thu 8/13/2009 4:09 PM
To: Maven Users List
Subject: Re: Hibernate 3 Plugin

you haven't defined an execution for the PlugIN.


>                     <componentProperties>
>                         <create>true</create>
>                         <drop>false</drop>
>                         <export>false</export>
>                         <configurationfile>/target/classes/persistence.xml</configurationfile>
In my opinion this should be changed...
to the given persistence.xml file...
> Here is the persistence.xml founf in src/main/resources as well as target/classes:


Kind regards
Karl Heinz Marbaise
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 W├╝rselen                 

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message