On May 5, 2010, at 12:38 AM, Jean-Louis MONTEIRO wrote:
>
>
> David Blevins wrote:
>>
>> could even generate some ant script or something to grab those jars.
>>
>
> David,
>
> I already have a profile in the openejb-tomcat-webapp to package the
> openejb.war using hibernate as the JPA provider.
>
> Do you think we can push that profile (with another eclipselink profile) in
> that pom so that end users can easily generate the openejb webapp with
> another JPA provider?
>
> Obviously, in my pom (and i should be the case if we add profiles), OpenJPA
> is the default provider (default activated profile).
Perfect. We can add those to the assembly section of the build and simply set
them up to not deploy just like we do with the examples via this little config:
<distributionManagement>
<repository>
<id>localhost</id>
<url>file://${basedir}/target/repo/</url>
</repository>
<snapshotRepository>
<id>localhost</id>
<url>file://${basedir}/target/snapshot-repo/</url>
</snapshotRepository>
</distributionManagement>
Now if only we can get someone to fix up this script to test them and help us
get it running in the build.
http://svn.apache.org/repos/asf/openejb/trunk/openejb3/assembly/test/build.xml
I've also been wondering if we shouldn't just put up a binary of Tomcat with
OpenEJB already in it. Adam Bien mentioned via twitter that he gets asked that
question all that time. Would certainly help simplify the above script and
make it easier to test the integration in the build.
-David
