maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Baptiste MATHUS <bmat...@batmat.net>
Subject Re: Maven and JPA/EclipseLink Configuration...
Date Wed, 10 Jul 2013 05:04:33 GMT
If those properties are specific to eclipselink, then I think it's ok and
simpler to just leave them in the persistence.xml even if they're actually
not used when EclipseLink isn't the provider. Then package only one ear.

Cheers


2013/7/9 John Patrick <nhoj.patrick@gmail.com>

> I'm working on a project that uses JPA EclipseLink, everything started of
> fine with Jetty for developers development and WebLogic and Oracle proper
> ear deployments.
>
> EclipseLink has two values that need to be set in persistence.xml depending
> upon your Application Server and Database;
> eclipselink.target-server
> eclipselink.target-database
>
> This mean we have two profiles, Jetty and Release.
>
> Now we support WebSphere and DB2, so have gone to 5 profiles and the need
> to rebuild the ear 4 times which each profile.
>
> Profiles
> Jetty
> WLSOracle
> WLSDB2
> WASOracle
> WASDB2
>
> I feel I'm doing something wrong...
>
> Does someone have any suggestions on what to look at so i could potentially
> build it once and get all the 4 ears build in one command? I've thought
> about types or classifiers but unsure if that is just another hack...
>
> Thoughts? As we soon might also need to support MySQL and Glassfish so
> their is another 5 profiles and 5 more builds for a release.
>
> John
>



-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

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