RE: sql triggers, stored procedures, packages, format preserved

2003-04-04 Thread Anderson, Rob H - VSCM
I did find an issue that is preventing some packages from loading into
Oracle. I have attached a diff -u that fixes it (one line, pretty self
explanatory). Please commit it. 

-Rob A

-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 1:43 PM
To: Ant Developers List
Subject: Re: sql triggers, stored procedures, packages, format preserved



- Original Message -
From: Anderson, Rob H - VSCM [EMAIL PROTECTED]
To: 'Ant Developers List' [EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 13:04
Subject: RE: sql triggers, stored procedures, packages, format preserved


 Steve, My build process will rely heavily on this task to load packages,
 procedures, triggers, view, types, and apply grants in Oracle9i. I agree
 that some tests are needed and I will look into creating some. Thanks,

 -Rob Anderson


It is in there, via an FTP to a unix box where patch works reliably. We need
expanded documentation and testing, now. The task could also do with a
switch to turn on property expansion.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Index: SQLExec.java
===
RCS file: 
/home/cvspublic/ant/src/main/org/apache/tools/ant/taskdefs/SQLExec.java,v
retrieving revision 1.51
diff -u -r1.51 SQLExec.java
--- SQLExec.java14 Mar 2003 09:24:41 -  1.51
+++ SQLExec.java4 Apr 2003 01:38:05 -
@@ -375,6 +375,7 @@
 }
 try {
 statement = conn.createStatement();
+statement.setEscapeProcessing(false);
 
 
 PrintStream out = System.out;


RE: updated sql documentation....

2003-04-04 Thread Anderson, Rob H - VSCM
I hate it when that happens. How about now?

-Rob A

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 11:19 PM
To: [EMAIL PROTECTED]
Subject: Re: updated sql documentation


On Thu, 3 Apr 2003, Rob H. Anderson [EMAIL PROTECTED]
wrote:

 Attached is the updated sql documentation that I promised.

Didn't make it to the list, sorry.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Index: sql.html
===
RCS file: /home/cvspublic/ant/docs/manual/CoreTasks/sql.html,v
retrieving revision 1.18
diff -u -r1.18 sql.html
--- sql.html18 Dec 2002 17:27:00 -  1.18
+++ sql.html4 Apr 2003 01:46:21 -
@@ -132,6 +132,13 @@
   td width=10% valign=topNo (defaul:normal)/td
 /tr
 
+tr
+  td width=12% valign=topkeepformat/td
+  td width=78% valign=topControl whether the format of the sql will be 
preserved.br
+Usefull when loading packages and procedures.
+  td width=10% valign=topNo (defaul=false)/td
+/tr
+
 /table
 
 h3Parameters specified as nested elements/h3


RE: sql triggers, stored procedures, packages, format preserved

2003-03-13 Thread Anderson, Rob H - VSCM
Steve, My build process will rely heavily on this task to load packages,
procedures, triggers, view, types, and apply grants in Oracle9i. I agree
that some tests are needed and I will look into creating some. Thanks,

-Rob Anderson

-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 9:02 AM
To: Ant Developers List
Subject: Re: sql triggers, stored procedures, packages, format preserved



- Original Message -
From: Anderson, Rob H - VSCM [EMAIL PROTECTED]
To: 'Ant Developers List' [EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 08:41
Subject: RE: sql triggers, stored procedures, packages, format preserved


 The diff -u is now the latest attachement to the bug.

got it.

I am willing to commit these changes, but am not going to be in a position
to test them.

What would be really nice long term would be some tests that used, say hsql
as a sql server. But short term, let me know what breaks.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: ssh exec task...

2003-03-12 Thread Anderson, Rob H - VSCM


Attached is the documentation (I hope).

-Rob A

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2003 12:35 AM
To: [EMAIL PROTECTED]
Subject: Re: ssh exec task...


On Tue, 11 Mar 2003, Rob H. Anderson [EMAIL PROTECTED]
wrote:

 Attached is the documentation.

No it isn't (no HTML parts on our list, even attachments).  Could you
either send it to me directly or simply zip it up before attaching it?

 I wonder if there is anyway to wait for the thread to finnish?

So do I.  I played with reading from the outputstream (much like the
StreamPumper stuff in exec) in the hope the IO would block, but have
no good results so far.

I'll try to understand the inner workings of jsch (though my time is a
bit limited ATM) and ask on jsch-users if all else fails.  You are
invited to do some research of your own, of course 8-)

 Does this mean that ant will report Build Successfull before the
 command has actually completed (Yuk)?

Potentially.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 install.zip 


RE: ssh exec task...

2003-03-12 Thread Anderson, Rob H - VSCM
Crap! I have sent the attachements to your email address
([EMAIL PROTECTED]).

-Rob A

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 12, 2003 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: ssh exec task...


On Wed, 12 Mar 2003, Rob H. Anderson [EMAIL PROTECTED]
wrote:

 Attached is the documentation (I hope).

I received nothing.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: enhanced pvcs task for PVCS version 7.5

2003-03-12 Thread Anderson, Rob H - VSCM
Apparently there is some confusion around repository and config file. I
apologize for not being very clear about this. Let me explain. By default,
when you create a Version Manager project database a config file is created
in the archives directory. You can see the config file name and location
through the GUI if you right click the project database and choose
Properties. You can, however, specify a config file to use when you create
the project database (in the advanced tab) or at any time through the
Properties dialog. For example: I have a local repository that I created
using the defualts (Create a new config file in the Advanced tab) for a
config file. The layout is as follows;

Project Database (-pr)
c:\pvcs
Config file
c:\pvcs\archives\cos0nbu1.cfg

I have a shared project database that was created with a custom config file
(Use an existing configuration file in the Advanced tab)

Project Database (-pr)
s:\Projects\NOONAN
Config File
s:\configuration files\NOONAN.cfg

In both cases, using get works fine without the -c option unless I am doing
a get by promotion group. When doing a get by promotion group I will get an
error that says get: Group CM does not exist in promotion hierarchy.,
because the promotion model is defined in the config file. So, if I specify
the config file with the -c option, this error goes away and the get by
promotion group works as expected.

So using the pvcs task is no different. Doing a normal get works fine, but
a get by promotion group fails with the error mentioned above. If there
was a configfile attribute to the pvcs task I could use it to get by
promotion group. Currently I can only use it to do a get the default
revision. Does this make sense?

-Rob A

 
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 3:22 PM
To: Ant Developers List
Subject: RE: enhanced pvcs task for PVCS version 7.5



Anderson
PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default.
/Anderson

repository attribute is used to point to config location, do you mean
some other configuration files; and as you know this a required attribute,
so no defaults.

Anderson
The advantage to using pcli get rather than
get is that pcli is smart about config files, which has been a problem
for
me with the existing PVCS task.I'm a little new to PVCS Version Manager, so
if there are other advantages please let me know. Of course pcli is pretty
slow compared to the old school get.
/Anderson

Following are advantages stated by our support team:-

adv
All project teams that have been using the legacy Commands (i.e. get, put)
will need to convert to 'PCLI'. Using the PCLI commands is just like using
the I-NET client or Windows client. These three interfaces update
serialized database files that the PVCS Version Manager software uses.
These serialized database files contain all the information for the
archives.  So if one member is using PVCS I-NET and modifies an item that
modification will appear for another team member that is using the PCLI
commands.  Using the old sget or sput does not update these serialized
files.

1.) Easier/More User Friendly
2.) More Reliable
3.) Provides your team the choice to use Command Line or I-NET Client.
4.)May run a little slower since it is updating the serialized files.
/adv

Anderson
It would be nice if the existing PVCS task had a configfile parameter.
/Anderson

Can you explain a bit more about this? because I don't seem to have any
problem when using with old get, with respect to the config files.

sourcePlease find the attachment. Don't miss the added (two) properties.
/source


..(See attached file: Pvcs.java)
Chandra Periyaswamy



 

  Anderson, Rob  H

  - VSCM  To:   'Ant Developers
List' [EMAIL PROTECTED]  
  [EMAIL PROTECTED]cc:

  torscm.com  Subject:  RE: enhanced pvcs
task for PVCS version 7.5   
 

  03/11/2003 05:00

  PM

  Please respond to

  Ant Developers

  List

 

 





PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default. The advatantage to using pcli get rather
than
get is that pcli is smart about config files, which has been a problem
for
me with the existing PVCS task. I'm a little new to PVCS Version Manager,
so
if there are other advantages please let me know. Of course pcli is pretty
slow compared to the old school get. It would be nice if the existing
PVCS
task had a configfile parameter. I would like to check out your source
code. Please attach it to an email and send it to the list. Thanks,

-Rob A



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 12:14

RE: sql triggers, stored procedures, packages, format preserved

2003-03-12 Thread Anderson, Rob H - VSCM
Pretty please :)

-Original Message-
From: Anderson, Rob H - VSCM [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2003 1:27 PM
To: '[EMAIL PROTECTED]'
Subject: sql triggers, stored procedures, packages, format preserved


Committers, Can we get this in the next release? Please :) I guess we will
need to update the documentation for the sql task also. 

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10719

Robert Anderson
Software Configuration Management
Vector SCM
503-450-6514
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: ssh exec task...

2003-03-11 Thread Anderson, Rob H - VSCM
Stefan, Attached is the documentation. I wonder if there is anyway to wait
for the thread to finnish? Does this mean that ant will report Build
Successfull before the command has actually completed (Yuk)?

-Rob A

-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 8:59 AM
To: [EMAIL PROTECTED]
Subject: Re: ssh exec task...


On Tue, 11 Mar 2003, Rob H. Anderson [EMAIL PROTECTED]
wrote:

 There is one problem with the sshexec task that someone should look
 into: I was not able to get the output from the remote command to
 show up in the log.

It works if my machine (the one running Ant) is under heavy load, but
doesn't otherwise. 8-(

The problem seems to be (from some cursory code review on jsch) that
jsch spawns a thread to execute the command - and the task may very
well be finished (and Ant exited) before the thread gets run.

 I will work on some documentation to go with it.

Great.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: enhanced pvcs task for PVCS version 7.5

2003-03-11 Thread Anderson, Rob H - VSCM
PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default. The advatantage to using pcli get rather than
get is that pcli is smart about config files, which has been a problem for
me with the existing PVCS task. I'm a little new to PVCS Version Manager, so
if there are other advantages please let me know. Of course pcli is pretty
slow compared to the old school get. It would be nice if the existing PVCS
task had a configfile parameter. I would like to check out your source
code. Please attach it to an email and send it to the list. Thanks,

-Rob A



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 12:14 PM
To: [EMAIL PROTECTED]
Subject: enhanced pvcs task for PVCS version 7.5


Hi,

I'm a greenhorn to this list, so please pardon my mistakes if any.

I modified the pvcs task to work with PVCS VM version 7.5. Instead of a old
get, I use pcli get in this modified version. It has been tested and
used in my project. I have tested on sun OS. I would be glad to submit the
source, if you'd like. Please let me know what you think.

I also think keeping the support for the old get may also seem important
for the community.


:o) Chandra Periyaswamy




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]