Missing jars (javax.persistence)
by Carlo de Wolf
Hi all,
I saw that ejb3.deployer no longer contains a lot of jar files.
But I need these three:
<fileset dir="${hibernate.entitymanager.lib}">
<include name="ejb3-persistence.jar"/>
<include name="hibernate-entitymanager.jar"/>
</fileset>
<fileset dir="${hibernate.annotations.lib}">
<include name="hibernate-annotations.jar"/>
</fileset>
(Basicly the javax.persistence stuff.)
They are not in the <server>/lib directory, but they are in the client
directory.
Is another project going to deploy these artifacts or can I add them
back to the build.xml of ejb3.deployer?
IMHO they're part of a separate product (javax.persistence) on which
ejb3 is dependant.
Carlo
18 years, 5 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
All I have done so far is copy the aop-mc-int into the
microcontainer/trunk. Further work can wait for you and Kabir to get in
synch.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Adrian
Brock
Sent: Wednesday, August 02, 2006 9:39 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy
Can we hold on changes for a couple of days.
It is nearly 24 hours since I last had an environment that I could
use to do any work. ;-)
Everytime I resynch and build, I find something different is broken.
On Wed, 2006-08-02 at 23:18 -0500, Scott M Stark wrote:
> > It should be in the microcontainer build.
> Ok
>
> > > I can move the container project into a separate root under
> > > https://svn.jboss.org/repos/jbossas/projects/
> >
> > Ok, but I think this should really be a seperate build.
> > When AOP has a standalone build, it will need a binary of this
> project.
> > MC will also use the binary.
>
> Everything under jbossas/projects should be a separate build that
> produces a binary.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
18 years, 5 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
> It should be in the microcontainer build.
Ok
> > I can move the container project into a separate root under
> > https://svn.jboss.org/repos/jbossas/projects/
>
> Ok, but I think this should really be a seperate build.
> When AOP has a standalone build, it will need a binary of this
project.
> MC will also use the binary.
Everything under jbossas/projects should be a separate build that
produces a binary.
18 years, 5 months
RE: [JBoss-dev] Microcontainer/Breakout Strategy
by Scott M Stark
Where should the
https://svn.jboss.org/repos/jbossas/archives/trunk/aop-mc-int/ be then,
aop, mc or standalone?
I can move the container project into a separate root under
https://svn.jboss.org/repos/jbossas/projects/
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Adrian
Brock
Sent: Wednesday, August 02, 2006 8:20 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy
What is the status of the microcontainer port to SVN?
If I understand correctly cvs is now read only.
Scott just created a microcontainer trunk,
which is missing the aop integration?.
Incidently, although the container project was created as a part
of the microcontainer project, it is intended to be used by all
projects and developed independently.
It's original intention was to define the shared primitives
used by both aop and mc (as opposed to the actual integration)
but other things like the ClassInfo are obviously useful to other
projects.
The project dependencies are:
aop -> container
kernel -> container
kernel -> dependency
aop-mc-int -> container
aop-mc-int -> aop
aop-mc-int -> kernel
18 years, 5 months
