Thanks for the feedback, Dan. I have clarified the bug summary as you
suggested and noted that this is a master JIRA to which subtasks can be
linked.
Regards,
-Rick
Daniel John Debrunner wrote:
Rick Hillegas (JIRA) wrote:
Control ability to create plugins (procedures/functions)
I'm
Jean T. Anderson wrote:
I'm looking at web site updates for DERBY-2173 and notice that the
eclipse plug-in distribution started incorporating the svn revision in
10.2. Here are the available zips:
derby_core_plugin_10.2.2.485682.zip
derby_core_plugin_10.2.1.452058.zip
I would like to continue the discussion about system shutdown and
privileges. For further context, please see DERBY-2109.
I am a bit puzzled about the interaction between engine shutdown and
network server shutdown. I would appreciate the community's advice about:
1) What is supposed to be
Bryan Pendleton wrote:
The results of these experiments puzzle me. I think it is odd that
you need credentials to bring down the engine, but you don't need
credentials to bring down the network server--which then brings down
the engine as a side effect. Is this behavior expected and correct
Oystein Grovlen - Sun Norway wrote:
Rick Hillegas wrote:
2) What behavior would we like to see in 10.3 when we control engine
shutdown with Java Security?
I think we need to prevent unauthorized users from bringing down the
network server. I wonder if there is much difference between
/SecurityExpectations
Thanks in advance for your feedback,
-Rick
Daniel John Debrunner wrote:
Oystein Grovlen - Sun Norway wrote:
Rick Hillegas wrote:
It seems to me a sysadmin needs our system privileges because she
wants
to prevent malicious shutdown (shutdownEngine privilege) and resource
Suresh Thalamati wrote:
Rick Hillegas wrote:
Oystein Grovlen - Sun Norway wrote:
Rick Hillegas wrote:
2) What behavior would we like to see in 10.3 when we control
engine shutdown with Java Security?
I think we need to prevent unauthorized users from bringing down
the network server. I
.
Thanks,
-Rick
Thanks,
David
Rick Hillegas wrote:
I have taken a stab at describing various security expectations which
customers might have and also how we could balance these expectations
against the desire to run the network server secure by default. The
following wiki page addresses
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I have taken a stab at describing various security expectations which
customers might have and also how we could balance these expectations
against the desire to run the network server secure by default. The
following wiki page addresses
Geir Høydalsvik, a member of the Norwegian Derby team, will be visiting
SF on February 14. I was hoping to use this as an excuse for a Bay Area
Derby lunch. Please let me know if you can attend. Once we know who's
coming, we can vote on a venue. Looking forward to seeing you all!
Regards,
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I have taken a stab at describing various security expectations
which customers might have and also how we could balance these
expectations against the desire to run the network server secure
I know this is kind of spur of the moment, but some of us Derby folks in
the Bay Area are going to get together next Thursday (January 18). This
is in addition to the lunch we're planning for mid-February. If you're
in the Bay Area (sorry, Jean!) and feeling footloose, come join us at
noon in
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I know this is kind of spur of the moment, but some of us Derby folks
in the Bay Area are going to get together next Thursday (January 18).
This is in addition to the lunch we're planning for mid-February. If
you're in the Bay Area (sorry
I have taken the liberty of starting a 10.3 release page to track the
features, bug fixes, and documentation we plan to roll into our next big
release:
http://wiki.apache.org/db-derby/DerbyTenThreeRelease
I have hung this page off the Developer's page. Feel free to move the
page (and let us
if the databasename is an url or a path. Would !, #,
*, +, |, ; be better?
Thanks,
-Rick
David Van Couvering wrote:
Why not use . rather than @? Seems more natural to me...
David
Rick Hillegas (JIRA) wrote:
[
https://issues.apache.org/jira/browse/DERBY-2109?page
Andrew McIntyre wrote:
On 1/19/07, Rick Hillegas [EMAIL PROTECTED] wrote:
Hi David,
This is a possibility. It seems to me that . is a bad choice for
customers whose usernames take the form firstName.lastName. And @ is
bad for customers whose usernames are email addresses. And -, _,
can all
I've just started having problems attaching comments and files to JIRAs.
I'm getting an ugly little stack trace when I try to add a comment or
file. Is this just me or are other people seeing this problem?
Thanks,
-Rick
Hi Mike,
I agree that the Bug Fix Candidates heading is misleading because the
query sweeps up all open 10.3 issues, including bugs, features, and
documentation. I agree that Bug Fix Candidates should have a more
focussed query associated with it. Sounds like you're happy to wire a
narrower
Hi Siamak,
Some work has already gone into creating management tools for Derby.
Please take a look at DERBY-1387. That issue describes a JMX-based
scheme for managing Derby servers and databases. It would be great if
you could piggyback your work on top of those JMX extensions. I think
you
It looks like the automated build needs to use a Java 5 or Java 6 compiler.
Regards,
-Rick
---BeginMessage---
ant
ant.properties.jdk16:
j14lib=/usr/local/java/jdk1.4/jre/lib
j13lib=/usr/local/java/jdk1.3/jre/lib
jdk16=/usr/local/java/jdk1.6.0
proceed=false
sane=false
I have committed the patch attached to DERBY-3117. After you sync with
the mainline, you will need to use the Java 5 (or later) compiler to
build Derby. This implements the community's consensus to move to an
advanced compiler, as recorded in the following vote:
ken gen wrote:
I'm trying to work out how easy it would be to leverage the
Derby DRDA
server endpoint, but instead of passing requests/queries to the
SQL engine,
forward them to my application code directly. I'd like to use
something like
JXPath, JoSQL or Quaere
I have set deprecation=off in my ant.properties. I also run ant with
the -quiet switch. Those little tweaks reduce the build chatter to a
manageable screenful and help me see the signal through the noise.
Regards,
-Rick
Myrna van Lunteren wrote:
On 10/17/07, Knut Anders Hatlen [EMAIL
Recently, the DB PMC discussed whether we should make Derby a top level
Apache project. The consensus seemed to be that a) Derby is mature
enough to be a top level project, b) no-one felt passionately one way or
another, c) therefore this decision should be left to the Derby
community. It
Laura Stewart wrote:
On 10/17/07, Rick Hillegas [EMAIL PROTECTED] wrote:
Recently, the DB PMC discussed whether we should make Derby a top level
Apache project. The consensus seemed to be that a) Derby is mature
enough to be a top level project, b) no-one felt passionately one way or
another
Hi Ramin,
The problem may be that your test is not reading derby.system.home from
inside a privileged block. If your test extends BaseTestCase, then you
can call getSystemProperty() to read derby.system.home and that method
will set up the privileged block needed to read the property.
Hope
Right now, the osgi support is an optional part of the Derby build. I
think this is because people used to have to click through a license
agreement in order to download the osgi jarball which Derby needed to
compile this support. However, it appears to me that this jarball is now
available
Right now, we need 2 jar files in order to build the small device
support into Derby. Let me give them the following names:
1) foundation.jar
These are the pared-back versions of the core jdk classes in packages
like java.lang, java.util, etc.
2) jsr169.jar
These are the pared-back
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Right now, we need 2 jar files in order to build the small device
support into Derby. Let me give them the following names:
1) foundation.jar
These are the pared-back versions of the core jdk classes in packages
like java.lang, java.util
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Getting these jarballs is time-consuming and requires clicking
through licenses. For these reasons, the small device support is an
optional part of the Derby build. It would be good if we could
eliminate this time-consuming,
This would
Oystein Grovlen - Sun Norway wrote:
Jørgen Løland wrote:
In the current proof of concept replication code, we boot the slave
database by calling
Database db =
(Database)Monitor.findService(Property.DATABASE_MODULE, dbname);
This requires org.apache.derby.iapi.db.Database to be imported.
Dag H. Wanvik wrote:
I think the reason is that the VTI demo result set template presumes
JDK1.5, since the JDBC has more methods in JDK 1.6 which are
unimplemented in the VTI template.
Dag
I just checked in submission 587905. Hopefully this fixes the build in
Java 6 environments. Please
I am seeing security exceptions when I run the junit tests via the ant
harness. Since I don't normally run the junit tests that way, I'm
guessing this is an environment problem. Does the following kind of
error look familiar to anyone? Thanks-Rick
[junit] Running
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I am seeing security exceptions when I run the junit tests via the
ant harness. Since I don't normally run the junit tests that way, I'm
guessing this is an environment problem. Does the following kind of
error look familiar to anyone? Thanks
I've checked in my patch for DERBY-1670. At this point, you no longer
need to copy the osgi jarball into your Derby subversion clients. Derby
now uses the osgi jarball from the Apache Felix project and osgi support
is now automatically included with Derby builds.
Regards,
-Rick
Daniel John Debrunner wrote:
B) Are there other ideas about how we could get Derby unencumbered
jarballs so that we always build the small device support?
Two possible options:
1) Look for an open-source J2ME option, Motorola has done MIDP but I
haven't seen any Foundation open source
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
B) Are there other ideas about how we could get Derby unencumbered
jarballs so that we always build the small device support?
Two possible options:
1) Look for an open-source J2ME option, Motorola has done
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
B) Are there other ideas about how we could get Derby unencumbered
jarballs so that we always build the small device support?
Two possible options:
1) Look for an open-source J2ME option
Hi Henrik and Svein Erik,
Thanks for doing this. Could you create a JIRA and attach your changes
to it? That will give us a tidy place to continue this discussion and
also make the changes easier to track and commit.
Thanks,
-Rick
Henrik Holum wrote:
We (Svein Erik Løvland and Henrik Holum)
Kathey Marsden wrote:
At some point I need to bump the version from 10.3.1.5 to 10.3.2.0 for
the maintenance release release candidate. Should this happen right
before the release candidate is made or should it have occurred right
after the last release was finalized?
Kathey
Hi Kathey,
I am able to run Derby 10.2 on the phoneME implementation of the CDC
platform. That is, using Derby 10.2 on that platform, I am able to
successfully create a database and query the system tables. So far so good.
However, when I run the same experiment with Derby 10.3, the database
fails to
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I am able to run Derby 10.2 on the phoneME implementation of the CDC
platform. That is, using Derby 10.2 on that platform, I am able to
successfully create a database and query the system tables. So far so
good.
However, when I run the same
Kathey Marsden wrote:
Well, I found my problem, The issue was that my release version did
not match the fix version in the fixedBugsList.xml. I am not sure the
best way to address this. There are three options I can think of.
1) Change the release note generator to ignore the version in
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I am able to run Derby 10.2 on the phoneME implementation of the
CDC platform. That is, using Derby 10.2 on that platform, I am able
to successfully create a database and query the system
As of release 10.3, when you boot the network server from the command
line, the server installs a Java SecurityManager with a default policy.
This change (DERBY-2196) limits the ability of hackers, connecting from
arbitrary machines, to use Derby to corrupt the environment in which it
is
. Derby and Network Server
are used with sample code and readily available for use as a business
system data store. The statement I received is:
I am all for it. Anything that will mean not breaking customers out
of the box is a good thing.
Rick Hillegas wrote:
As of release 10.3, when you boot
Samuel Morgan wrote:
Hi,
Thanks for a wonderful database management system.
How do I create custom types in Derby? what would be the formal
approach in creating a geometry type for example?
Im interested as I would love to see Derby with spatial features like
postgis, and Im a postgis
Hi Dag,
Here's my $.02: I think that there is plenty of precedent for checking
in partial features. There is even precedent for removing unfinished
features before cutting the release branch. I suspect that your upgrade
code will be checked in long before Bernt builds the 10.4
I need 5 minutes of help from someone who uses the IBM JDKs on windows
or windows/cygwin.
I need your help to test-drive the latest patch which I attached to
DERBY-3117. The goal of the patch is to supply reasonable values for our
build properties so that a new developer can run the Derby
Myrna van Lunteren wrote:
On 11/9/07, Rick Hillegas [EMAIL PROTECTED] wrote:
I need 5 minutes of help from someone who uses the IBM JDKs on windows
or windows/cygwin.
I need your help to test-drive the latest patch which I attached to
DERBY-3117. The goal of the patch is to supply
Kathey Marsden wrote:
The test SecurityPolicyReloadingTest loads its own initial policy file
so does not need to install the default test policy file. The test
currently loads the default test policy file and then installs its own
policy file using SecurityManagerSetup. I would like to change
://issues.apache.org/jira/browse/DERBY-3176
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.3.1.4
Reporter: Rick Hillegas
Assignee: Rick Hillegas
Attachments: derby-3176-01-phoneME-aa.diff,
derby-3176-01-phoneME-ab.diff
: https://issues.apache.org/jira/browse/DERBY-3176
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.3.1.4
Reporter: Rick Hillegas
Assignee: Rick Hillegas
Attachments: derby-3176-01-phoneME-aa.diff,
derby-3176-01-phoneME
://db.apache.org/derby/docs/dev/ref/rrefsistabs38369.html
It may be advisable to tackle some smaller issue first, so you know
your way around a bit before you try to attack this issue. Your call :)
Thanks,
Dag
Sam
Dag H. Wanvik wrote:
Rick Hillegas [EMAIL PROTECTED] writes:
Samuel
Laura Stewart wrote:
On 11/14/07, Lance J. Andersen [EMAIL PROTECTED] wrote:
Perhaps this is an indication that we need to revisit the layout of the
manuals to make them easier to use and put this as a high priority for
things to address going forward. If the documentation is difficult to
I have checked in some build logic which automatically sets the compiler
classpath properties. This is part of the work on DERBY-3117 and the
goal, ultimately, is to have a Derby build script which works out of
the box without any customizing of ant.properties.
In order to take advantage of
Vemund Ostgaard wrote:
Rick Hillegas wrote:
I have checked in some build logic which automatically sets the
compiler classpath properties. This is part of the work on DERBY-3117
and the goal, ultimately, is to have a Derby build script which
works out of the box without any customizing
Vemund Ostgaard wrote:
I tried it out in my sandbox Rick, and it worked fine except for one
thing that probably isn't related to your changes.
The first time I do ant all after having done ant clean or ant
clobber, the build fails when compiling
junitcomponents:
[javac] Compiling 1
Thanks to everyone for the useful discussion of this issue. It does not
seem to me that there is a consensus for backing out this feature. I am
inclined to leave it in.
Regards,
-Rick
Rick Hillegas wrote:
As of release 10.3, when you boot the network server from the command
line, the server
Knut Anders Hatlen wrote:
Rick Hillegas [EMAIL PROTECTED] writes:
I have checked in some build logic which automatically sets the
compiler classpath properties. This is part of the work on DERBY-3117
and the goal, ultimately, is to have a Derby build script which works
out of the box
Daniel John Debrunner wrote:
Rick Hillegas wrote:
The place to add support for additional platforms/vms would be
trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java The
class has a pretty extensive header comment explaining what the class
does--but please let me know if the header
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Daniel John Debrunner wrote:
Rick Hillegas wrote:
The place to add support for additional platforms/vms would be
trunk/java/build/org/apache/derbyPreBuild/PropertySetter.java The
class has a pretty extensive header comment explaining what
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
At line 207 (just after this code)
if ( j14lib != null ) { setClasspathFromLib( J14LIB, j14lib ); }
if ( j15lib != null ) { setClasspathFromLib( J15LIB, j15lib ); }
The wrong property names were being passed to
Hi Kathey,
I think that we do indeed want to make this change. However, currently
we don't require that you set java15compile.classpath. It is set
automatically only if you include autosetProps=on in your
ant.properties. This is the trajectory I thought we were on:
1) Continue to collect
Jason D'cruz wrote:
I'm writing a java application using Derby embedded and network drivers.
Initially i access the database using a default username and password.
How can i change the username and password to access the database?
Or can i create a new user with the same privileges and delete
Hi Manjula,
During the implementation of DERBY-2196, we discussed how we should
parameterize the codebases which receive permissions. There were two
main proposals:
1) Express the codebases as ${derby.jar}, ${derbynet.jar}, etc.
or
2) Express the codebases as ${derby.install.url}derby.jar,
requirement is to create a new user or to change the password for an
existing user.Is that possible?
Regards,
Jason
Rick Hillegas-2 wrote:
Jason D'cruz wrote:
I'm writing a java application using Derby embedded and network drivers.
Initially i access the database using a default username
Kathey Marsden wrote:
I just checked in the release notes and changes files for the
10.3.2.0. One thing I noticed is that none of the issues have release
notes. Please let me know right away if any issues are missing,
release notes are needed or you see any other problems with the
release
Hi Kathey,
I just downloaded the release note for DERBY-2967 and sanity-checked it
using the standalone ReleaseNoteReader (see
http://wiki.apache.org/db-derby/ReleaseNoteProcess). The sanity-checks
passed in my environment. Could you run the following experiment on your
machine:
1)
John Embretsen wrote:
Kathey Marsden wrote:
I just checked in the release notes and changes files for the
10.3.2.0. One thing I noticed is that none of the issues have
release notes. Please let me know right away if any issues are
missing, release notes are needed or you see any other
Hi Cíntia,
Derby does not have any builtin support for distributed joins--that is
for running a query which mentions tables in two different databases.
However, you may be able to accomplish what you need to do by using
table functions, a feature that is implemented in the development trunk
Daniel John Debrunner wrote:
Kathey Marsden wrote:
Please test and vote on the 10.3.2.0 release candidate available at:
I'm still thinking about the change made to 10.3 for DERBY-3083.
In 10.2 bringing up the server in all cases did not install a security
manager.
In 10.3.1.4:
- server
Dag H. Wanvik wrote:
Isn't this a bug? Or?... I could not find a JIRA for it.
(unqualified schema in a view definition fails in view used by another user)
http://www.jroller.com/gmazza/entry/apache_derby_sql_state_42y07
Dag
In the trunk, the table reference is correctly resolved if, while
Frank Griffin wrote:
Hi All,
I'm evaluating the extending of Derby for use as a JDBC access path to a
non-SQL data engine. Conceptually, what I need to do is a CREATE TABLE
which reflects the metadata of the result set which will be returned by
the non-SQL engine, and then intercept SELECT
Rameshkumar Ramasamy wrote:
Hello,
I am interested in contributing to Apache Derby project and Bug
fixing activities.
Could you please add me to derby-developers group?
My user name is :rr204483
Thank you in advance!
Regards,
Ramesh
Done.
Regards,
-Rick
Kathey Marsden wrote:
Done.
55 of Derby's reserved keywords are not reserved keywords in the ANSI
2003 standard. These include keywords like key and collation, which
are non-reserved keywords in ANSI 2003. Keeping these as reserved
keywords creates migration problems when people try to port their
applications from other
+ 1 based on my tests using Java 5 on Mac OS X, and on the accumulating
good results on the wiki.
Regards,
-Rick
Kathey Marsden wrote:
Please test and vote on the 10.3.2.1 release candidate, available at:
http://people.apache.org/~kmarsden/derby10.3.2.1.599110/
You can report platform
I am seeing the following diff in the outerjoin.sql test when I run
against a clean subversion client newly populated from the mainline:
MasterFileName = master/outerjoin.out
1737 del
Empty right rows returned = 1
1737a1737
Empty right rows returned = 0
Test Failed.
*** End: outerjoin
I am trying to figure out how Derby BUILTIN and LDAP authentication can
be used without storing a master password in plaintext. I would
appreciate the community's advice.
1) With BUILTIN authentication, there is no encrypted storage for
server-wide credentials. E.g., the credentials needed to
Kathey Marsden wrote:
Could a jira admin please merge 10.3.1.5 and 10.3.2.0 into 10.3.2.1
and mark 10.3.2.1 released.
Thanks
Kathey
Done.
Kathey Marsden wrote:
In http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
The maven instructions currently have you attempt to deploy directly
to people.apache.org. Then as a separate step sign the jars and ftp
the *.asc files to the server. There are alternate instructions in
case the
Brjc wrote:
Hi Iam trying to create a table function which returns a JDBC ResultSet. For
this Iam follwing the documentation provided here
http://db.apache.org/derby/docs/dev/devguide/cdevspecialtfbasic.html
When Iam trying to register my function by ising the below mentioned
construct I get
Hi Kathey,
Thanks for all the hard work getting 10.3.2 out the door!
Regards,
-Rick
Unless someone objects, tomorrow I would like to change the Derby build
so that, by default, the build will try to automatically set the
compiler properties if they are not already set in ant.properties. I
checked in this behavior a month ago, but right now you have to opt into
this behavior
Dag H. Wanvik wrote:
Working on SQL roles, I have encountered a problem related to
invalidation of prepared statements.
My understanding at this point: Presently, at execute time, permission
is only checked the first time a prepared statement is executed for a
connection, as part of creating
Myrna van Lunteren wrote:
On 12/17/07, Rick Hillegas [EMAIL PROTECTED] wrote:
Unless someone objects, tomorrow I would like to change the Derby build
so that, by default, the build will try to automatically set the
compiler properties if they are not already set in ant.properties. I
checked
Jazarine Jamal wrote:
Good Day..
I am Jazarine Jamal, a student of Computer Science and is
participating in Sun's Code for freedom contest.
I've registered for a JIRA account at http://issues.apache.org/jira
I request you to grant developer access to my account so that I can
work on bugs in
John Embretsen wrote:
Rick Hillegas wrote:
After making this change, the Derby build will behave this way:
1) If ant.properties is empty, then the build will try to set the
compiler properties based on your platform and vm vendor.
2) If this breaks the build for you, then you can get
Dag H. Wanvik wrote:
Thanks for your answer, Rick,
Rick Hillegas [EMAIL PROTECTED] writes:
1) You can't set yourself to a role which is not granted to you. Is
that right?
It must be granted to the current user or to PUBLIC, yes, cf. section
18.3 GR 4.
2) What does it mean
the build smart enough to handle your environment.
Thanks,
-Rick
Rick Hillegas wrote:
Unless someone objects, tomorrow I would like to change the Derby
build so that, by default, the build will try to automatically set the
compiler properties if they are not already set in ant.properties. I
Vemund Ostgaard wrote:
I'm trying to get all the tests in suites.All to run successfully with
the phoneME advanced platform.
A problem I have discovered is that when JUnit creates a suite of
tests from the test* methods in a class, I get them executed in a
different order on this platform
Frank Griffin wrote:
I've been looking into Table Functions as a way to access external data,
and I'm running into some design questions.
Briefly, I need to provide Java code which provides access to arbitrary
tables in a foreign database.
The problem I'm seeing from the docs is that it looks
Hi Myrna,
Just to confirm what Kristian has said, this is how it is supposed to work:
1) The out-of-the-box experience, which should work for most users is
this: Do nothing. That is, don't even create an ant.properties. The
Derby build should successfully figure out where your JDKs live and
The system privileges work (DERBY-2109) will introduce a compatibility
issue for 10.4. I would like to commit Martin's work on this issue, but
before I do that, I would like to make sure that the community is
comfortable with the compatibility behavior. I am taking this question
to the
Hi John,
Thanks for testing this. A couple comments follow...
John Embretsen wrote:
In relation to DERBY-2109 (System privileges) I decided to apply the
principle
of learning by doing, and started to experiment with a customized
version of
the template policy file for the network server.
Daniel John Debrunner wrote:
Rick Hillegas wrote:
[snip]
DERBY-2109 reduces our exposure to denial-of-service (and possible
theft and corruption) attacks
What are the possible theft and corruption attacks?
Hi Dan,
These may come into play when we allow anyone to create a database
Hi Dyre,
These two issues were marked as blockers by the people who logged them.
Is that anything more than a statement of how much pain these issues
cause those people? If I were to categorize issues according to the
severity of their impact, it would look something like this (in
declining
the misgivings about (b): the
longer we delay this change, the more customers will be affected.
Are there other concerns which we should collect before polling the user
community for their opinion?
Thanks,
-Rick
Rick Hillegas wrote:
The system privileges work (DERBY-2109) will introduce
below...
Rick Hillegas wrote:
The property setter yields the output I have attached at the bottom.
If I had very custom jar files (spread around in multipe dirs, not
in j1Xlib), and maybe a VM vender the property setter doesn't
recognize, I would specify java14compile.classpath
801 - 900 of 11787 matches
Mail list logo
