> "Joe" == Joe Phillips <[EMAIL PROTECTED]> writes:
Joe> On Mon, 2003-01-20 at 14:44, Adam Heath wrote:
>> On Mon, 20 Jan 2003, Greg Wilkins wrote:
>> > + The setting of JAVA_HOME should be done by an auto search
>> and/or > a debconf dialog.
>>
>> Use /etc/defaults/jbo
> "Joe" == Joe Phillips <[EMAIL PROTECTED]> writes:
Joe> On Mon, 2003-01-20 at 14:44, Adam Heath wrote:
>> On Mon, 20 Jan 2003, Greg Wilkins wrote:
>> > + The setting of JAVA_HOME should be done by an auto search
>> and/or > a debconf dialog.
>>
>> Use /etc/defaults/jbo
> > /var/lib/jboss/
> what's this for? I guess I'll find out when I poke through your
> packages (later this week).
/var/lib/jboss/deploy/, which is where deployments occur. It was g+ws jboss,
and update-jboss(a helper script) had --deploy and --undeploy cmds for users
to run as non-root.
> I think we should work to package each individually (eg. javamail) if
> possible and they fall into the above case. The jboss-contrib package
> would shrink over time. The problem with this approach is that future
> versions of jboss-contrib won't be backward compatible with earlier
> versions
> > /var/lib/jboss/
> what's this for? I guess I'll find out when I poke through your
> packages (later this week).
/var/lib/jboss/deploy/, which is where deployments occur. It was g+ws jboss,
and update-jboss(a helper script) had --deploy and --undeploy cmds for users
to run as non-root.
> I think we should work to package each individually (eg. javamail) if
> possible and they fall into the above case. The jboss-contrib package
> would shrink over time. The problem with this approach is that future
> versions of jboss-contrib won't be backward compatible with earlier
> versions
Adam Heath wrote:
jboss debs on jboss-web-container, a virtual package
jboss-jetty(does not exist) and jboss-catalina provide jboss-web-container.
That's how my 2.4 packages worked. I even made a test jboss-jetty, and even
had *both* deployed at once(I used alternatives to select the default web
Joe Phillips wrote:
I know I know, that was *only* in the name of expediency in getting *a*
package. Future packages *will* be built from source, at least my 3.2+
packages will - I'm still debating on a 3.0.5 package.
3.0.5 is well broken - go for either 3.0 head or wait a week for 3.0.6
3.2 is s
On Mon, 2003-01-20 at 14:44, Adam Heath wrote:
> On Mon, 20 Jan 2003, Greg Wilkins wrote:
>
> > + The setting of JAVA_HOME should be done by an auto search and/or
> > a debconf dialog.
>
> Use /etc/defaults/jboss, and if not set, have it look at standard locations
> that java debs(from blac
Adam Heath wrote:
jboss debs on jboss-web-container, a virtual package
jboss-jetty(does not exist) and jboss-catalina provide jboss-web-container.
That's how my 2.4 packages worked. I even made a test jboss-jetty, and even
had *both* deployed at once(I used alternatives to select the default w
Joe Phillips wrote:
I know I know, that was *only* in the name of expediency in getting *a*
package. Future packages *will* be built from source, at least my 3.2+
packages will - I'm still debating on a 3.0.5 package.
3.0.5 is well broken - go for either 3.0 head or wait a week for 3.0.6
3.
On Mon, 2003-01-20 at 14:48, Adam Heath wrote:
> On 20 Jan 2003, Joe Phillips wrote:
> > Are you saying that the non-tomcat binary releases are
> > configured for jetty? If so, I was not aware of that. I
> > figured they were jboss without any web containers. I'll need to look
> > into this.
On 20 Jan 2003, Joe Phillips wrote:
> I don't know what you mean by the default deployment. jboss-tomcat is
> it's own, optional package. Note that jboss-server-all and
> jboss-server-default depend on jboss-tomcat. The deployment that my
> packages install is straight out of the binary release
On Mon, 20 Jan 2003, Greg Wilkins wrote:
> + The setting of JAVA_HOME should be done by an auto search and/or
> a debconf dialog.
Use /etc/defaults/jboss, and if not set, have it look at standard locations
that java debs(from blackdown, maybe /usr/local) contain.
> + The default webconta
On Mon, 2003-01-20 at 14:44, Adam Heath wrote:
> On Mon, 20 Jan 2003, Greg Wilkins wrote:
>
> > + The setting of JAVA_HOME should be done by an auto search and/or
> > a debconf dialog.
>
> Use /etc/defaults/jboss, and if not set, have it look at standard locations
> that java debs(from blac
On Mon, 2003-01-20 at 14:48, Adam Heath wrote:
> On 20 Jan 2003, Joe Phillips wrote:
> > Are you saying that the non-tomcat binary releases are
> > configured for jetty? If so, I was not aware of that. I
> > figured they were jboss without any web containers. I'll need to look
> > into this.
On 20 Jan 2003, Joe Phillips wrote:
> I don't know what you mean by the default deployment. jboss-tomcat is
> it's own, optional package. Note that jboss-server-all and
> jboss-server-default depend on jboss-tomcat. The deployment that my
> packages install is straight out of the binary release
On Mon, 20 Jan 2003, Greg Wilkins wrote:
> + The setting of JAVA_HOME should be done by an auto search and/or
> a debconf dialog.
Use /etc/defaults/jboss, and if not set, have it look at standard locations
that java debs(from blackdown, maybe /usr/local) contain.
> + The default webconta
Joe Phillips wrote:> On Mon, 2003-01-20 at 05:00, Greg Wilkins wrote:
Your jboss debs for 3.0.2-2 deployed without problems on my
debian sid system. Good work!
+ Does it really need to depend on your jdk1.4 package?
Jboss can run on 1.3 and most debian users will have already
installed j
On Mon, 2003-01-20 at 05:00, Greg Wilkins wrote:
>
> Your jboss debs for 3.0.2-2 deployed without problems on my
> debian sid system. Good work!
Great! thanks.
> + Does it really need to depend on your jdk1.4 package?
> Jboss can run on 1.3 and most debian users will have already
> i
Joe Phillips wrote:> On Mon, 2003-01-20 at 05:00, Greg Wilkins wrote:
Your jboss debs for 3.0.2-2 deployed without problems on my
debian sid system. Good work!
+ Does it really need to depend on your jdk1.4 package?
Jboss can run on 1.3 and most debian users will have already
instal
On Mon, 2003-01-20 at 05:00, Greg Wilkins wrote:
>
> Your jboss debs for 3.0.2-2 deployed without problems on my
> debian sid system. Good work!
Great! thanks.
> + Does it really need to depend on your jdk1.4 package?
> Jboss can run on 1.3 and most debian users will have already
> i
Your jboss debs for 3.0.2-2 deployed without problems on my
debian sid system. Good work!
But a couple of comments:
+ Does it really need to depend on your jdk1.4 package?
Jboss can run on 1.3 and most debian users will have already
installed jdk - having an extra 40MB download is a bit of
Your jboss debs for 3.0.2-2 deployed without problems on my
debian sid system. Good work!
But a couple of comments:
+ Does it really need to depend on your jdk1.4 package?
Jboss can run on 1.3 and most debian users will have already
installed jdk - having an extra 40MB download is a bit
On Fri, 2003-01-17 at 22:28, Andrew Savory wrote:
> On Tue, 14 Jan 2003, Joe Phillips wrote:
>
> > I spent yesterday rebuilding and testing my debs. The versions
> > currently on my company site[1] have been tested to properly start/stop
> > the server without exceptions.
>
> Just been trying t
On Fri, 2003-01-17 at 22:28, Andrew Savory wrote:
> On Tue, 14 Jan 2003, Joe Phillips wrote:
>
> > I spent yesterday rebuilding and testing my debs. The versions
> > currently on my company site[1] have been tested to properly start/stop
> > the server without exceptions.
>
> Just been trying t
26 matches
Mail list logo
