Hi!
I'm experimenting with tomee-maven-plugin 1.7.0-SNAPSHOT, and run into a
problem.
If i put a src/main/resources/META-INF/persistence.xml in my simple web
project, and use
true
tomee doubles my persistence unit.
SEVERE - FAIL ... myapp-web: @PersistenceUnit unitName has multiple
matches: unit
Hi
yes, this is "expected" since persistence.xml is in src/main/resources
and target/classes, personally I put it in src/main/webapp/WEB-INF
If I find time I'll enhance it but ATM on another thing
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http:/
Thanks,
WEB-INF/persistence.xml works.
Right after getting this work, i've run into another problem
I get an error from liquibase.
Error Reading Migration File: Found 2 files that match changelog.xml
Just for the enhancement in the future: Any file in resources can cause a
similar problem.
201
Yes, that's the fix to do. Hopefully tonight on trunk (then don't know
if it will be mergeable with 1.7 or too late)
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-07-17
We can probably merge for a 1.7.1 I think.
Not really a big deal and we should get more feedback from users that
requires a maintenance release.
JLouis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 10:12 AM, Romain Manni-Bucau
wrote:
yep that's the open point, I can't fix it now ($dayjob) but not a
blocking for a release since that's something new and still a bit
experimental (but I'm already addicted ;)).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rman
lol
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 10:20 AM, Romain Manni-Bucau
wrote:
> yep that's the open point, I can't fix it now ($dayjob) but not a
> blocking for a release since that's something new and still a bit
> experiment
Thank you guys, even me agree it is not a blocker bug.
Romain: I don't want to be the man who force you work at midnight :)
I've hacked liquibase. Overridden a method not to fail when
classLoader.getResources(path) returns more element.
Now it works.
But i've run into an other problem :P
ecl
Did you also moved the orm?
As per the spec, it should be relative to the persistence archive, so I
guess, Eclipselink is looking for it at WEB-INF/, isn't it?
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 11:04 AM, Tamás Kimmel wrote:
Yes, tried moving it, and leaving in resources too.
Eclipselink does not log an exact path where is it looking for
eclipselink-orm.xml. Even on FINEST level.
But found a workaround. It finds the file from a jar in WEB-INF/lib, just
have to load in persistence xml via .
So now i have a persistence.
Thanks for sharing
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Jul 17, 2014 at 12:41 PM, Tamás Kimmel wrote:
> Yes, tried moving it, and leaving in resources too.
> Eclipselink does not log an exact path where is it looking for
> eclipselink-orm.xm
hmm, looked a bit and fixing it for mvn plugin would introduce side
effects in other usages (where you want it). Actually it means the war
shouldn't take into account these resources. This is not what does
default config but it can be done with some more config.
I'll let it this way for next relea
I think the current behavior should be left alone. If you have an
Apache Maven multi-module project where you are putting different
persistence.xml units for different modules, then you should exclude
them from the final artifact for those intermediary modules. Both
m-jar-p and m-war-p support excl
13 matches
Mail list logo
