IL PROTECTED]>
Sent: Thursday, December 13, 2001 9:23 PM
Subject: Re: [JBoss-dev] Support for upackaged EARs, JARs, WARs added to 2.4
>
> >
> > > 2) Should manifest lib(s) be hot deployable. I have
> > to restart jboss to
> > have it recgonize the new classes in the j
>
> > 2) Should manifest lib(s) be hot deployable. I have
> to restart jboss to
> have it recgonize the new classes in the jar?
> >
> Meaning what? That you update the libs and then touch
> the deployment
> descriptor
> to redeploy? If your expecting the libs to be watched
> for updates to trigg
>
> 1) If your ear directory lives in the deploy dir, then don't specify your
unpackaged ear dir in jboss.jcml. It causes Auto Deployer to deploy, then
un-deploy, then deploy again. Thus causing context root namespace conflicts
in tomcat for your war(s).
>
I'll fix this.
> 2) Should manifest lib(
I am testing out the new "unpackaged ear" feature in 2.4.4-beta.
Two things I have come across:
1) If your ear directory lives in the deploy dir, then don't specify your unpackaged
ear dir in jboss.jcml. It causes Auto Deployer to deploy, then un-deploy, then deploy
again. Thus causing context
On Tue, 11 Dec 2001, Scott M Stark wrote:
>
> I'll update the source tonight.
Kisses. The feature in $topic will allow us here at work to completely change
our build system, to generate this unpacked form, then use rsync to send to
the live servers. We are all waiting anxiously.
I'll update the source tonight.
- Original Message -
From: "Adam Heath" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: "JBoss Dev" <[EMAIL PROTECTED]>
Sent: Tuesday, December 11, 2001 6:27 PM
Subject: Re: [JBoss-dev
On Tue, 11 Dec 2001, Dain Sundstrom wrote:
> > 2.4.3 < 2.4.4 < 2.4.4beta
>
> Adam, I know you didn't write the debian package rules, but this is the most
> retarded fucking thing I have ever seen.
Well, it does cause problems, I'll agree there.
I'll explain how dpkg does version comparison belo
001 5:47 PM
Subject: Re: [JBoss-dev] Support for upackaged EARs, JARs, WARs added to 2.4
> On Sun, 9 Dec 2001, Scott M Stark wrote:
>
> > [snip]
>
> > I'll put out a new 2.4.4 beta tomorrow with this capability included to
> > allow for
> > additional te
> 2.4.3 < 2.4.4 < 2.4.4beta
Adam, I know you didn't write the debian package rules, but this is the most
retarded fucking thing I have ever seen.
-dain
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/j
On Sun, 9 Dec 2001, Scott M Stark wrote:
> [snip]
> I'll put out a new 2.4.4 beta tomorrow with this capability included to
> allow for
> additional testing.
It's past tomorrow, yet no release(no rush, this isn't the point of my mail).
I'm really anticipating using the new feature of deploying
Most excellent,
2.4.4 is going to be in production a LONG time :)
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Sunday, December 09, 2001 9:58 PM
|To: JBoss Dev
|Subject: [JBoss-dev] Support for upackaged EARs
I have added support for deployment of unpackaged J2EE modules,
EARs, EJB-JARs and WARs to the 2.4 branch for inclusion in the
2.4.4 release. This goes from the current extreme of copying everything
to NO copies of anything. The J2EE module must be completely unpackaged.
An EAR must have the modul
12 matches
Mail list logo
