On 9 Sep, Jason Dillon wrote:
So, the first question is why does an MDB with NotSupported cause TX
timeouts?
Hiram is the one who did the transaction parts of the MDB, but I would
geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
that is), the flags only determins
Hiram is the one who did the transaction parts of the MDB, but I would
geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
that is), the flags only determins under what TX context the bean is
invoked. This mean there will allways be a transaction going on under
the
Is the manual build working? I just did a clean check out on jboss-all and
tried jboss-all\manual\build docs-html, but it failed (see attached output
error and build.log). Is it related the manual filtering problem you're
talking about? I checked the file
Looks like that URL spec is not happy. you can change the
oasis.docbook.xsl.root property in ../build/local.properties, to something
win32 compatible.
Can someone explain to my what the file:// semantics for a win32 path spec
is?
I am almost done testing some changes to the build system (the
Hi,
Under branch 2.4.1.
jboss-j2ee.jar in src/client and src/lib are not the same, the one in client
does not contain EJB 2.0 classes.
Regards.
Vincent.
___
Jboss-development mailing list
[EMAIL PROTECTED]
I thought about it this weekend some more, and worked on an example xml
configuration too. This is a spin off of the Jetty config, but I think most
uses will not require some of the advanced get/new stuff (which leaves you
mostly with what we have no, only more flexibly).
This is all/mostly
Couldn't you also define classloaders here for the Security Manager?
Jason Dillon wrote:
I thought about it this weekend some more, and worked on an example xml
configuration too. This is a spin off of the Jetty config, but I think most
uses will not require some of the advanced get/new
On 10 Sep, Jason Dillon wrote:
Hiram is the one who did the transaction parts of the MDB, but I would
geuss this is what is going on: An MDB is ALWAYS transacted (the receipt
that is), the flags only determins under what TX context the bean is
invoked. This mean there will allways be a
User: kimptoc
Date: 01/09/10 05:40:33
Modified:src/bin run.sh
Log:
fixed bug with regard to setting the -server flag, it was never being set before
Revision ChangesPath
1.29 +2 -2 jboss/src/bin/run.sh
Index: run.sh
Hi I thought of an Idea that should fix Jason's problem while not chaning
the current MDB invoker too much. What we have to do is get rid of that
ugly timeout. So when MDB TX is NotSupported, lets not elist the TX with
the TM since he sill timeout the transaction. Lets just manually
On 10 Sep, Hiram Chirino wrote:
Hi I thought of an Idea that should fix Jason's problem while not chaning
the current MDB invoker too much. What we have to do is get rid of that
ugly timeout. So when MDB TX is NotSupported, lets not elist the TX with
the TM since he sill timeout the
Jason,
I'm still confused about what you are trying to accomplish here. I would
really appreciate it if you could take a few minutes and write down,
without specifying a notation, the sequence of events you are trying to
control and the variation points along that sequence.
for instance (made
Rickard,
We were hoping you would respond to this email. I'll have to answer for
Sacha, since he's in London. What he's really getting at is, Is there
really any meat behind JINI? JavaGroups(JG) is definately pretty meaty and
provides solid, reliable communications protocols. Read on
Hi,
I'd like to fix the org.jboss.logging deprecation messages - which
means replacing the logging with log4j calls...
So - is anyone doing this already?
I plan to look for code that has the correct logging and doing
like-wise - so any recommendations?
I am assuming that there is no reason
User: starksm
Date: 01/09/10 09:36:32
Modified:src/build Tag: Branch_2_4 build.xml
Log:
Add install and src-install target to build the j2ee jars into jboss dist
Revision ChangesPath
No revision
No revision
1.8.2.1
User: starksm
Date: 01/09/10 09:38:59
Modified:src/client Tag: Branch_2_4 jboss-j2ee.jar
Log:
Synch up the jars from jboss-j2ee
Revision ChangesPath
No revision
No revision
1.3.4.1 +140 -127
User: starksm
Date: 01/09/10 09:38:59
Modified:src/lib Tag: Branch_2_4 jboss-j2ee.jar jboss-jdbc_ext.jar
Log:
Synch up the jars from jboss-j2ee
Revision ChangesPath
No revision
No revision
1.5.4.1 +135 -134
User: starksm
Date: 01/09/10 09:51:53
Modified:src/docs binary.jsp
Log:
Update 2.4.1 info for repackaging
Revision ChangesPath
1.4 +6 -9 newsite/src/docs/binary.jsp
Index: binary.jsp
===
Hi,
I'd like to fix the org.jboss.logging deprecation messages - which
means replacing the logging with log4j calls...
So - is anyone doing this already?
I plan to look for code that has the correct logging and doing
like-wise - so any recommendations?
What do you mean by changing
I synched up the jboss-j2ee.jar from client and lib with the jboss-j2ee
module
and repackaged the 2.4.1 release bundles.
- Original Message -
From: Vincent Harcq [EMAIL PROTECTED]
To: Dev JBoss [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 1:27 AM
Subject: [JBoss-dev] Jboss 2.4.1
I thought I'd write a note explaining what my recent changes to the mbean
deployment in rh do.
1. Recursive deployment. The classpath elements in a *service.xml file may
be used to specify dependencies on jar and zip archives, sar archives
(containing a jboss-service.xml file), or *-service.xml
Hi Geeks
I run into several problems with the new build system:
jboss-all:
- I can't compile Jetty to get the webserver running
jboss-website:
- Whatever I build the manual is builded but not the website
Any ideas ?
Andy
___
Jboss-development
Hi,
I had some problem recently with a PK Class and how JawsEMD build the list
of pk fields.
I have a PK class APK with a public field code.
I also have a PK class BPK that extends APK and also re-define code (ok
strange but why not)
This line (of JawsEMD)
Field[] pkClassFields =
Hi,
--- Scott M Stark [EMAIL PROTECTED] wrote:
I plan to look for code that has the correct logging and doing
like-wise - so any recommendations?
What do you mean by changing code that has the correct logging?
umm, perhaps correct is the wrong phrase.
I mean look for jboss code
Ok. Just moving to log4j to avoid deprecation warning is not worth the
effort as we need to define a logging usage pattern and then move to it.
One big issue we have right now is that debug msgs are anything from
verbose one-time initialization mgs to per method traces of activity. The
server.log
Hi Geeks
Is someone doing the Tomcat integration into RH ??
Andy
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Eventually.
- Original Message -
From: Andreas Schaefer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 12:14 PM
Subject: [JBoss-dev] Tomcat Integration into RH
Hi Geeks
Is someone doing the Tomcat integration into RH ??
Andy
For the jbossmq-service.xml example, does reploying jbossmq-service.xml
cause
jboss-service.xml to be undeployed and redeployed?
Likewise, would just undeploying jbossmq-service.xml undeploy
jboss-service.xml?
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: jboss-dev
User: starksm
Date: 01/09/10 12:41:57
Modified:src/docs binary.jsp
Log:
Indicate 1.3 is needed for 2.4.x
Revision ChangesPath
1.5 +1 -2 newsite/src/docs/binary.jsp
Index: binary.jsp
===
Hi,
So far I have been unsuccessful in turning on the TRACE priority -- thus
the excessive DEBUG stuff I have been using. Do you have an example of how
to turn it on? If I can get it to work I will happily turn most of my
debugs into traces.
Thanks
david jencks
On 2001.09.10 15:12:06 -0400
On 2001.09.10 15:39:58 -0400 Scott M Stark wrote:
For the jbossmq-service.xml example, does reploying jbossmq-service.xml
cause
jboss-service.xml to be undeployed and redeployed?
No, jboss-service.xml is not listed as a dependency of jbossmq-service.xml.
Likewise, would just undeploying
From: David Jencks [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: jboss-dev [EMAIL PROTECTED]
Subject: [JBoss-dev] Mbean package deployment and undeployment
Date: Mon, 10 Sep 2001 14:16:17 -0400
(As part of the jbosscx reorganization, all jca related classes are in the
jbosscx.sar, which
Yes, there is an example in the default log4j.properties file that is
commented
out. Simply uncomment the last line as follows:
# An example of enabling the custom TRACE level priority that is used
# by the JBoss internals to diagnose low level details. This example
# turns on TRACE level msgs
On 2001.09.10 15:39:58 -0400 Scott M Stark wrote:
For the jbossmq-service.xml example, does reploying jbossmq-service.xml
cause
jboss-service.xml to be undeployed and redeployed?
No, jboss-service.xml is not listed as a dependency of
jbossmq-service.xml.
But JBossMQ requires that a JNDI
I'd like to do something about the test suite so we have separate unit
(fast) and stress (slow) test suites and so the test script doesn't try to
execute non test classes as tests.
How about this naming convention:
*UnitTest.java indicates a class containing only quick, unit tests.
Thanks, Hiram
Are the attached files what you mean? (I haven't tested to make sure they
work).
Is some part of the jbossmq-service.jar required for jbossmq to work,
whereas the rest is an example of how to set up usage of it? If so, can we
package the required part into a jboss-service.xml in
The last suggested naming convention was *TestCase.java so:
*TestCase.java indicates a class containing only quick, unit tests.
*StressTestCase.java indicates a class containing (only) lengthy iterative
tests.
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: jboss-dev
Time for my two cents...
I have just finished incorporating my scheme (the use of the depends
elements) with David J's and it seems to work for the simple examples I have
tested it on. I am a bit unsure whether or not to commit the changes (after
more testing) though because the two schemes
Scott,
Do you mean that you have edited the 2.4.1 release on SourceForge ?
If so, I need to trash the 2.4.1/Jetty release I am doing and start aain
on the new release.
Thanks,
Jules
Scott M Stark wrote:
I synched up the jboss-j2ee.jar from client and lib with the jboss-j2ee
module
and
Yes.. almost perfect. Just move the
- !-- The JMS provider loader
--
- mbean code=org.jboss.jms.jndi.JMSProviderLoader
name=:service=JMSProviderLoader,name=JBossMQProvider
attribute name=ProviderNameDefaultJMSProvider/attribute
attribute
Whatever happened to Simple is the word... ;-)
David
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 11, 2001 9:24 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Mbean package deployment and undeployment
Ok, my thinking is coming
This sounds good.
--jason
On Mon, 10 Sep 2001, Scott M Stark wrote:
The last suggested naming convention was *TestCase.java so:
*TestCase.java indicates a class containing only quick, unit tests.
*StressTestCase.java indicates a class containing (only) lengthy iterative
tests.
-
Well,
after struggling to get a working jboss startup using only the recursive
dependencies, I am inclined to agree with you that relying solely on them
is not necessarily appropriate. I don't know a good final answer:
--recursive deployment is nice because it lets you aggregate chunks of
Are we still planning on dropping the older Log Logger stuff in favor of
Log4j? If so, lets replace Logger with a new class that extends from
Category, and provides Logger create() methods to access an instance. It
would have the trace() and isTraceEnabled().
Trace seems to be best suited for
jboss-all:
- I can't compile Jetty to get the webserver running
I am not sure this really works yet. I had to use the 2.4.x/Jetty package
to test the website deployment.
jboss-website:
- Whatever I build the manual is builded but not the website
Could you explain this in more detail; I
OK, thats good, I wanted your nod before committing, which I will do some
time today.
My stuff doesn't break the current startup and I have made a few changes to
the startup configuration so that it all works nicely. However I will need
you to look over the changes and check I haven't stuffed
Yes, those two jars were updated and the packages redone.
- Original Message -
From: Julian Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 2:05 PM
Subject: Re: [JBoss-dev] Jboss 2.4.1
Scott,
Do you mean that you have edited the 2.4.1 release on
We need to agree on and formalize our logging convention and then move to it.
Let us do this. Logging is a critical system.
What is left to decide?
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
javax.xml.parsers.FactoryConfigurationError:
org.apache.crimson.jaxp.SAXParserFactoryImpl
at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:84)
at
org.apache.tools.ant.ProjectHelper.getParserFactory(ProjectHelper.java:780)
at
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 2:41 PM
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
Are we still planning on dropping the older Log Logger stuff in favor of
Log4j? If so, lets
I think just the custom logging class that replaces the existing Log, Logger
and
JBossCategory and the use of TRACE. I'm in agreement with you on this
items so unless there is other input to the contrary the details of the new
Logger or
whatever is all that remains. Due to the proposed change to
Or even better, as Jason Dillon points out, does it provide an abstracted
interface with the above features that JG can plug into? Sacha and I have
developed our own abstraction interface, but maybe JINI provides a better
one. I personally know jack squat about JINI and should really read
I'm still confused about what you are trying to accomplish here. I would
really appreciate it if you could take a few minutes and write down,
without specifying a notation, the sequence of events you are trying to
control and the variation points along that sequence.
Sure. There are three
Let's get both approaches working as it remains to be seen if the complexity
of
the recursive/implicit stuff is worth the trouble.
- Original Message -
From: David Maplesden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 2:31 PM
Subject: RE: [JBoss-dev] Mbean
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 2:43 PM
Subject: Re: [JBoss-dev] Build Problems
jboss-all:
- I can't compile Jetty to get the webserver running
I am not sure this really works yet. I had to use the
Couldn't you also define classloaders here for the Security Manager?
Sure, though I would defer all security bits to Scott.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
I think just the custom logging class that replaces the existing Log, Logger
and
JBossCategory and the use of TRACE. I'm in agreement with you on this
items so unless there is other input to the contrary the details of the new
Logger or
whatever is all that remains.
What about the current
I started to read the JINI spec. Pretty cool stuff. The leasing interface
is also very interesting. Sacha and I are pretty close to having HA JNDI,
HA SLSBs, and HA EBs hooked into javagroups. We'll probably just iterate
and look into JINI later.
Bill
-Original Message-
From:
Hi I thought of an Idea that should fix Jason's problem while not chaning
the current MDB invoker too much. What we have to do is get rid of that
ugly timeout. So when MDB TX is NotSupported, lets not elist the TX with
the TM since he sill timeout the transaction. Lets just manually
I'd like to see substitution variables in jboss.jcml so that you can use
environment variables to get at some of the hardcoded paths that need to be
set up in config
BIll
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Jencks
Sent: Monday,
Because I don't want redundant interfaces to the logging system.
- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 10, 2001 4:14 PM
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
What is wrong with rewriting
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
Date: Mon, 10 Sep 2001 14:41:20 -0700 (PDT)
Are we still planning on dropping the older Log Logger stuff in favor of
Log4j? If so, lets
1) Expose as much configuration to integrators as possible, with out
complicating the system for users who do not need to muck with the
boot config.
Right now with rh, you can specify all the directories you need (and some
you probably don't) as urls on the command line (as I
I'd like to see substitution variables in jboss.jcml so that you can use
environment variables to get at some of the hardcoded paths that need to be
set up in config
Environment variables or properties?
--jason
___
Jboss-development mailing list
User: jules_gosnell
Date: 01/09/10 16:52:05
Modified:jetty/src/build build.xml
Log:
jetty repackaging and build script fixes
Revision ChangesPath
1.13 +12 -9 contrib/jetty/src/build/build.xml
Index: build.xml
What is trying to connect to 127.0.0.2 ? Why is any machine configured to
use 127.0.0.2 as its ip addr?
--jason
On Mon, 10 Sep 2001, Andreas Schaefer wrote:
Hi Geeks
Maybe it is just me but I have a problem to access
JBoss JNDI naming service from Windows to an
Linux box but vice versa
Good question, I have no idea.
Strange is that local lookups from the Linux server are
working fine, too. Only when W2K tries to make the
lookup it fails this way. I will try to make the lookup
from another Linux box.
Andy
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To:
User: user57
Date: 01/09/10 18:07:18
Modified:bin ant
Log:
o updating to ant v1.4
o ANT_OPTS has been moved closer to class name (like the dist version)
o added JAVA_OPTS to replace it, though current usage of ANT_OPTS should
still work
Revision Changes
User: user57
Date: 01/09/10 18:07:19
Modified:lib ant.jar optional.jar
Log:
o updating to ant v1.4
o ANT_OPTS has been moved closer to class name (like the dist version)
o added JAVA_OPTS to replace it, though current usage of ANT_OPTS should
still work
Okay, I understand now... It was very clear
answer. Thanx. ;-)
- kimion -
- Original Message -
From:
David Maplesden
To: '[EMAIL PROTECTED]'
Sent: Monday, September 10, 2001 9:35
PM
Subject: RE: [JBoss-dev] JBoss MS
SQL Server 2000
I
think you are
Yeah, sorry, properties
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hiram
Chirino
Sent: Monday, September 10, 2001 10:15 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] exposing boot sequence richer xml config
I like properties.
JBoss daily test results
SUMMARY
Number of tests run: 223
Successful tests: 99
Errors:87
Failures: 37
[time of test: 11 September 2001 3:27 GMT]
[java.version:
I like properties.
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] exposing boot sequence richer xml config
Date: Mon, 10 Sep 2001 16:52:29 -0700 (PDT)
I'd like to see substitution variables in jboss.jcml so that you can use
Forgive the ignorance, I spoke without a full understanding of how log4j
works..
Regards,
HIram
From: Scott M Stark [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] log4j switchover - anyone working on this?
Date: Mon, 10 Sep 2001 17:33:00 -0700
User: dmaplesden
Date: 01/09/10 19:45:46
Modified:src/main/org/jboss/deployment AutoDeployer.java
Log:
Altered so that the AutoDeployer can be deployed before the individual deployers it
uses.
Revision ChangesPath
1.3 +90 -19
User: dmaplesden
Date: 01/09/10 19:46:57
Modified:src/main/org/jboss/jmx/META-INF jboss-service.xml
Log:
Altered configuration to work with new deployment mechanism
Revision ChangesPath
1.2 +3 -0 jboss/src/main/org/jboss/jmx/META-INF/jboss-service.xml
User: dmaplesden
Date: 01/09/10 19:46:13
Modified:src/main/org/jboss/deployment ServiceDeployer.java
Log:
Added support for depends elements in service.xml files.
Revision ChangesPath
1.6 +245 -45 jboss/src/main/org/jboss/deployment/ServiceDeployer.java
User: dmaplesden
Date: 01/09/10 19:48:21
Modified:src/resources/jca-sar/META-INF jboss-service.xml
Log:
Altered configuration to work with new deployment mechanism
Revision ChangesPath
1.2 +1 -18 jbosscx/src/resources/jca-sar/META-INF/jboss-service.xml
User: dmaplesden
Date: 01/09/10 19:48:05
Modified:src/etc/conf/default mail-service.xml jboss-service.xml
hsql-default-service.xml
Added: src/etc/conf/default jms-service.xml jetty-service.xml
j2eedeployment-service.xml
User: dmaplesden
Date: 01/09/10 19:48:32
Modified:jbossbuild.xml
Log:
Altered configuration to work with new deployment mechanism
Revision ChangesPath
1.19 +45 -5 build/jboss/build.xml
Index: build.xml
The reason for the isXXXEnabled() methods is not the cost of the method
call which is minimal but to avoid constructing the log arguments which
typically involve a bunch of string manipulation which is time consuming.
The category.debug() call itself is very quick.
david jencks
On 2001.09.10
Ok, I just committed the changes I have been working on to the deployment
mechanism.
Basically you can now use the depends tags as proposed in *service.xml
files, that is
server
dependsJBOSS-SYSTEM:service=Naming/depends
... your mbeans
/server
will
I gotten lastest in
awhile. How do I build now? I want to build the cluster module on
Win2k. Do I get jboss-most? jboss-all? or what?
Thanks,
Bill
User: dmaplesden
Date: 01/09/10 20:05:26
Modified:src/etc/conf/default jbossmq-service.xml
Log:
Altered configuration to work with new deployment mechanism
Revision ChangesPath
1.3 +4 -59 jbossmq/src/etc/conf/default/jbossmq-service.xml
Index:
jboss-all, then `build/build.bat` should build the cluster module.
jboss-most will work too, but I suggest jboss-all.
--jason
On Mon, 10 Sep 2001, Bill Burke wrote:
I gotten lastest in awhile. How do I build now? I want to build the
cluster module on Win2k. Do I get jboss-most?
I get the following error on Win2k. I had to revert to an older build.bat
to get it to compile
D:\main\jboss-all\jboss-all\buildbuild.bat
Calling ..\tools\bin\ant.bat
Buildfile: build.xml
BUILD FAILED
D:\main\jboss-all\jboss-all\build\build.xml:276: You must specify value,
locatio
n or
Connector module is
broken!
most-pool:[execmodules]
==
== Executing 'most' in module 'connector'...
==
init-buildlog:
init:[moduleinfo] Project root:
D:\main\jboss-most[moduleinfo] Module root:
I just had the same thing, its complaining about the lines...
property name=executemodules.header![CDATA[
==
== Executing '${target}' in module '${module}'...
==]]/property
property
I am in the process of updating some build files, please do not change
anything at the moment.
I will get the conenctor to build shortly, though I was not aware that it
stopped.
--jason
On Mon, 10 Sep 2001, Bill Burke wrote:
Connector module is broken!
most-pool:
[execmodules]
Never seen this before either... give me a few minutes to finish up what I
am doing now and I will look into all of these problems.
--jason
On Mon, 10 Sep 2001, Bill Burke wrote:
I get the following error on Win2k. I had to revert to an older build.bat
to get it to compile
Windows?
--jason
On Tue, 11 Sep 2001, David Maplesden wrote:
I just had the same thing, its complaining about the lines...
property name=executemodules.header![CDATA[
==
== Executing '${target}' in module
Yes, I fixed it easily enough by changing them to...
property name=executemodules.header value=Executing '${target}' in
module '${module}'.../
property name=executemodules.footer value=...Finished with '${target}'
in module '${module}'./
I hate to add to your problems but I did a build
Julian, did you forget to update the thirdparty/mortbay/jetty libs?
--jason
compile-classes:
[mkdir] Created dir:
/nfs/home/jason/ws/jboss/jboss-all/plugins/jetty/output/classes
[javac] Compiling 8 source files to
/nfs/home/jason/ws/jboss/jboss-all/plugins/jetty/output/classes
Yes, I fixed it easily enough by changing them to...
property name=executemodules.header value=Executing '${target}' in
module '${module}'.../
property name=executemodules.footer value=...Finished with '${target}'
in module '${module}'./
This is very strange, perhaps the stuff I am
I don't know if you have see this yet... I just read the notice on
enhydra.org. I am really surprised by this.
What the *uck is Sun doing? I generally never really read source licenses,
because they are written by lawyers.
I just want to write software...
--jason
-- Forwarded
Bugs item #460582, was opened at 2001-09-10 21:39
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=460582group_id=22866
Category: JBossDoc
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to:
User: user57
Date: 01/09/10 21:45:12
Removed: mortbay/jetty/lib .cvsignore
Log:
o oops, cvs did not ignore this
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: user57
Date: 01/09/10 21:47:35
Log:
o Import of Jetty3Extra 0.0.7
Status:
Vendor Tag: mortbay
Release Tags: jetty3extra_0_0_7
N thirdparty/mortbay/jetty3extra/lib/org.mortbay.ftp.jar
N thirdparty/mortbay/jetty3extra/lib/jmxri.jar
N
User: user57
Date: 01/09/10 21:44:41
Log:
o import of Jetty 3.1 RC9
Status:
Vendor Tag: mortbay
Release Tags: jetty_3_1_RC9
N thirdparty/mortbay/jetty/lib/.cvsignore
N thirdparty/mortbay/jetty/lib/com.sun.net.ssl.jar
N
User: user57
Date: 01/09/10 21:50:08
Removed: mortbay/jetty3extra/lib com.mortbay.ftp.jar
com.mortbay.jetty.jmx.jar
com.mortbay.jetty.sasl.jar com.mortbay.tools.jar
jmxri.jar jmxtools.jar
Log:
o removing
1 - 100 of 128 matches
Mail list logo
