date:20040301


 Stefano Mazzocchi wrote:
  For this specific problem, I would go relational.

 +1. Brain-dead and ugly solution like mysql ;)

When I think about the answers I've received [and thanks for them] I wonder
if folks are thinking more about the ugly/brain dead type problem of results
tracking. I agree, that is fine to do relationally. [That is where this
thread originated, so perhaps I unintentionally led the response.]

BTW: First, let me state for the record, I'm no fan of XML for XML's sake 
don't wish to try to push it where it isn't useful. Also, everybody ought
use relational databases (specifically those wonderful ones from Sybase,
which also happens to have some awesome XML/XQL features, and allows joining
XML and relational data.) Ok, my corporate pitch ;-) ;-) ;-) over...

I realize I was more interested in the XML metadata, and it's changes over
time. The results are why folks invest in granting us/maintaining their
project metadata. The metadata is a map (a graph) of the community, and some
interactions [some, needs to be extended for more], and I was hoping some
form of XML repository could somehow give us a time factor on that.

I might be looking for more than is there, I might be looking for too low
level an assist, but I'd like to know if folks who used to depend upon X no
longer do [change in one XML], and when most migrated away [multiple]. I'd
like to know if a product was a 'huge hit' [multiple], and who was migrating
to it [multiple]. I'd like to see which communities/groups (lamely, for this
mail, based off  repository) were using something. I'd like to know details
like this over time.

I could push this graph into a relational schema but I feel that would be
very restrictive, and would pre-determine the benefits. I guess I can take
deltas, or store historical copies of the whole metadata, but I feel I need
some tool that is into analysing XML over time. Maybe I do need XINDICE, or
something like it.

Again, feel free to correct me -- and/or express your gut feelings against,
but my gut tells me I have a storage problem but I don't know the right
tools for the store, or the query mechanisms.

regards,

Adam


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

Re: Gump TLP Site

2004-03-01 Thread Stefan Bodewig

On Mon, 1 Mar 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote:

 Anybody interested in helping out w/ the Gump site?

Sure.

I just installed Forrest 0.5.1 and get an error:

X [0]   images/gump-logo.pngBROKEN: 
/home/bodewig/ASF/gump/gump/build/tmp/context/resources/images/gump-logo.png (No such 
file or directory)

which I assume is responsible for 

BUILD FAILED
/home/bodewig/apache-forrest-0.5.1-bin/forrest.build.xml:631: Java returned: 1

as there is no other error message.

Is this an expected failure?  Ought I use a more recent version of
Forrest?

Stefan

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

Hmm, not listing reports?

I suspect something in my change to pure Python for file listing/contents is
causing these not to show. I'll investigate...


http://lsd.student.utwente.nl/gump/jicarilla-sandbox/jicarilla-collections.html#Annotations

regards,

Adam
--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com


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

Re: Gump Database

2004-03-01 Thread Stefano Mazzocchi

Adam R. B. Jack wrote:

Stefano Mazzocchi wrote:

For this specific problem, I would go relational.
+1. Brain-dead and ugly solution like mysql ;)


When I think about the answers I've received [and thanks for them] I wonder
if folks are thinking more about the ugly/brain dead type problem of results
tracking. I agree, that is fine to do relationally. [That is where this
thread originated, so perhaps I unintentionally led the response.]
BTW: First, let me state for the record, I'm no fan of XML for XML's sake 
don't wish to try to push it where it isn't useful. Also, everybody ought
use relational databases (specifically those wonderful ones from Sybase,
which also happens to have some awesome XML/XQL features, and allows joining
XML and relational data.) Ok, my corporate pitch ;-) ;-) ;-) over...
I realize I was more interested in the XML metadata, and it's changes over
time. The results are why folks invest in granting us/maintaining their
project metadata. The metadata is a map (a graph) of the community, and some
interactions [some, needs to be extended for more], and I was hoping some
form of XML repository could somehow give us a time factor on that.
I might be looking for more than is there, I might be looking for too low
level an assist, but I'd like to know if folks who used to depend upon X no
longer do [change in one XML], and when most migrated away [multiple]. I'd
like to know if a product was a 'huge hit' [multiple], and who was migrating
to it [multiple]. I'd like to see which communities/groups (lamely, for this
mail, based off  repository) were using something. I'd like to know details
like this over time.
I could push this graph into a relational schema but I feel that would be
very restrictive, and would pre-determine the benefits. I guess I can take
deltas, or store historical copies of the whole metadata, but I feel I need
some tool that is into analysing XML over time. Maybe I do need XINDICE, or
something like it.
Again, feel free to correct me -- and/or express your gut feelings against,
but my gut tells me I have a storage problem but I don't know the right
tools for the store, or the query mechanisms.
Adam,

I think you are looking at the problem from the wrong angle: the use of 
the data.

While the question that you should be asking yourself is: what does the 
data look like? how stuctured is it?

From where I stand, the gump metadata is highly structured and can be 
perfectly mapped in to a relational structure with reasonable effort. 
Also, given its structure, can be indexed precisely and thus queried 
very efficiently.

At that point, once you have the data in the database, you can start 
thinking about what to do with it. Dependency graph visualization, 
history of dependencies, FoG estimation, all of these are problems that 
will result in particular queries and particular use of the result set.

Gump data does not exhibit any of the properties that appear in the 
semi-structured of highly connected pseudo-digraph problem space.

For this reason, I see absolutely no reason to avoid using relational 
solutions. Also because they are, by far, much more solid and easy to 
interoperate with than any other DBMS model.

--
Stefano.


smime.p7s
Description: S/MIME Cryptographic Signature

cvs commit: gump/python/gump engine.py

ajack   2004/03/01 10:58:01

  Modified:python/gump/model project.py state.py module.py property.py
workspace.py object.py
   python/gump/document forrest.py
   python/gump/results resulter.py model.py
   python/gump/utils tools.py
   profile  gump.xml
   python/gump engine.py
  Log:
  1) Tinkering w/ adding a Tracker [one day will link to]

  2) Results ...

  2.1) Gathering results from other servers [downloading/parsing results.xml]

  2.2) Generating results.xml for this server

  3) Making 'catDirectoryToFileHolder' do a directory listing also, for debugging.

  
  Revision  ChangesPath
  1.58  +8 -4  gump/python/gump/model/project.py
  
  Index: project.py
  ===
  RCS file: /home/cvs/gump/python/gump/model/project.py,v
  retrieving revision 1.57
  retrieving revision 1.58
  diff -u -r1.57 -r1.58
  --- project.py29 Feb 2004 19:16:19 -  1.57
  +++ project.py1 Mar 2004 18:58:00 -   1.58
  @@ -66,6 +66,7 @@
   
   from gump.model.state import *
   from gump.model.object import ModelObject, NamedModelObject, Jar,\
  +Resultable, \
Mkdir, Delete, JunitReport, Work
   from gump.model.stats import Statable, Statistics
   from gump.model.property import Property
  @@ -178,10 +179,13 @@
   return os.pathsep.join(self.getSimpleClasspathList())
   
   
  -class Project(NamedModelObject, Statable):
  +class Project(NamedModelObject, Statable, Resultable):
   A single project
   def __init__(self,xml,workspace):
NamedModelObject.__init__(self,xml.getName(),xml,workspace)
  + 
  + Statable.__init__(self)
  + Resultable.__init__(self)

# Navigation
   self.module=None # Module has to claim ownership
  
  
  
  1.12  +24 -3 gump/python/gump/model/state.py
  
  Index: state.py
  ===
  RCS file: /home/cvs/gump/python/gump/model/state.py,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- state.py  17 Feb 2004 21:54:20 -  1.11
  +++ state.py  1 Mar 2004 18:58:00 -   1.12
  @@ -148,6 +148,19 @@
   REASON_BUILD_TIMEDOUT : BuildTimedOut,
   REASON_MISSING_OUTPUTS : MissingBuildOutputs }
   
  +namedReasonCode = { NotSet : REASON_UNSET,
  +CompletePackageInstall : REASON_PACKAGE,
  +BadPackageInstallation : REASON_PACKAGE_BAD,
  +CircularDependency : REASON_CIRCULAR,
  +ConfigurationFailed : REASON_CONFIG_FAILED,
  +UpdateFailed : REASON_UPDATE_FAILED,
  +SynchronizeFailed : REASON_SYNC_FAILED,
  +Pre-BuildFailed : REASON_PREBUILD_FAILED,
  +BuildFailed : REASON_BUILD_FAILED,
  +Post-BuildFailed : REASON_POSTBUILD_FAILED,
  +BuildTimedOut : REASON_BUILD_TIMEDOUT,
  +MissingBuildOutputs : REASON_MISSING_OUTPUTS }
  +
   reasonCodeDescriptions = {   REASON_UNSET : Not Set,
   REASON_PACKAGE : Complete Package Install,
   REASON_PACKAGE_BAD : Bad Package Installation,
  @@ -166,6 +179,14 @@
   
   def reasonDescription(reasonCode):
   return reasonCodeDescriptions.get(reasonCode,'Unknown Reason:' + 
str(reasonCode))
  +
  +def reasonForName(name):
  +return namedReasonCode.get(name,STATE_UNSET)
  +
  +def getStatePairFromNames(stateName,reasonName):
  +state=stateForName(stateName)
  +reason=reasonForName(reasonName)
  +return StatePair(state,reason)
 
   class StatePair:
   Contains a State Plus Reason
  
  
  
  1.34  +8 -5  gump/python/gump/model/module.py
  
  Index: module.py
  ===
  RCS file: /home/cvs/gump/python/gump/model/module.py,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- module.py 23 Feb 2004 20:55:08 -  1.33
  +++ module.py 1 Mar 2004 18:58:00 -   1.34
  @@ -67,7 +67,7 @@
   from gump.model.state import *
   from gump.model.stats import Statable, Statistics
   from gump.model.project import *
  -from gump.model.object import NamedModelObject
  +from gump.model.object import NamedModelObject, Resultable
   from gump.utils import getIndent
   from gump.utils.note import transferAnnotations, Annotatable
   
  @@ -192,11 +192,14 @@
   unnamedModule.complete(workspace)
   return unnamedModule
   
  -class Module(NamedModelObject, Statable):
  +class Module(NamedModelObject, Statable, Resultable):
   Set of Modules

cvs commit: gump/blog/SuccessStories velocity-jdom.txt

nickchalko2004/03/01 11:20:54

  Modified:blog/SuccessStories velocity-jdom.txt
  Log:
  Added enty author line

  PR:

  Obtained from:

  Submitted by: 

  Reviewed by:  

  CVS: --

  CVS: PR:

  CVS:   If this change addresses a PR in the problem report tracking

  CVS:   database, then enter the PR number(s) here.

  CVS: Obtained from:

  CVS:   If this change has been taken from another system, such as NCSA,

  CVS:   then name the system in this line, otherwise delete it.

  CVS: Submitted by:

  CVS:   If this code has been contributed to Apache by someone else; i.e.,

  CVS:   they sent us a patch or a new module, then include their name/email

  CVS:   address here. If this is your work then delete this line.

  CVS: Reviewed by:

  CVS:   If we are doing pre-commit code reviews and someone else has

  CVS:   reviewed your changes, include their name(s) here.

  CVS:   If you have not had it reviewed then delete this line.

  
  Revision  ChangesPath
  1.2   +1 -0  gump/blog/SuccessStories/velocity-jdom.txt
  
  Index: velocity-jdom.txt
  ===
  RCS file: /home/cvs/gump/blog/SuccessStories/velocity-jdom.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- velocity-jdom.txt 19 Feb 2004 23:41:01 -  1.1
  +++ velocity-jdom.txt 1 Mar 2004 19:20:54 -   1.2
  @@ -1,4 +1,5 @@
   Velocity adapts Anakia to changes in JDOM
  +meta-blog-entry-author=antoine
   
   On the 18th of February, Stefan Bodewig wrote :
   blockquote
  
  
  

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

cvs commit: gump/blog TLP.txt

nickchalko2004/03/01 11:44:38

  Added:   blog TLP.txt
  Log:
  Starting the Gump TLP announcemnt entry.

  

  PR:

  Obtained from:

  Submitted by: 

  Reviewed by:  

  CVS: --

  CVS: PR:

  CVS:   If this change addresses a PR in the problem report tracking

  CVS:   database, then enter the PR number(s) here.

  CVS: Obtained from:

  CVS:   If this change has been taken from another system, such as NCSA,

  CVS:   then name the system in this line, otherwise delete it.

  CVS: Submitted by:

  CVS:   If this code has been contributed to Apache by someone else; i.e.,

  CVS:   they sent us a patch or a new module, then include their name/email

  CVS:   address here. If this is your work then delete this line.

  CVS: Reviewed by:

  CVS:   If we are doing pre-commit code reviews and someone else has

  CVS:   reviewed your changes, include their name(s) here.

  CVS:   If you have not had it reviewed then delete this line.

  
  Revision  ChangesPath
  1.1  gump/blog/TLP.txt
  
  Index: TLP.txt
  ===
  PREVIEW Gump is now an Apache Top Level Project
  
  Preparing the blog annoucnement of Gump as a TLP
  Please expand and edit
  view at 
  http://gump.chalko.com/gb/blog/?permalink=TLP.txtpreview=true
  
  http://gump.apache.org
  
  The Board voted ...
  Quote the board and link
  
  
  
  

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

cvs commit: gump/blog TLP.txt

nickchalko2004/03/01 11:49:23

  Added:   blog/News TLP.txt
  Removed: blog TLP.txt
  Log:
  Moved the TLP announcement.

  PR:

  Obtained from:

  Submitted by: 

  Reviewed by:  

  CVS: --

  CVS: PR:

  CVS:   If this change addresses a PR in the problem report tracking

  CVS:   database, then enter the PR number(s) here.

  CVS: Obtained from:

  CVS:   If this change has been taken from another system, such as NCSA,

  CVS:   then name the system in this line, otherwise delete it.

  CVS: Submitted by:

  CVS:   If this code has been contributed to Apache by someone else; i.e.,

  CVS:   they sent us a patch or a new module, then include their name/email

  CVS:   address here. If this is your work then delete this line.

  CVS: Reviewed by:

  CVS:   If we are doing pre-commit code reviews and someone else has

  CVS:   reviewed your changes, include their name(s) here.

  CVS:   If you have not had it reviewed then delete this line.

  
  Revision  ChangesPath
  1.1  gump/blog/News/TLP.txt
  
  Index: TLP.txt
  ===
  PREVIEW Gump is now an Apache Top Level Project
  
  Preparing the blog annoucnement of Gump as a TLPbr/
  Please expand and edit br/
  view at 
  http://gump.chalko.com/gb/blog/News?permalink=TLP.txtpreview=true
  hr/
  p
  http://gump.apache.org
  /p
  pThe Board voted ...
  /p
  blockquote
  Quote the board and link
  /blockquote
  
  
  

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

cvs commit: gump/blog/News TLP.txt

nickchalko2004/03/01 11:51:00

  Modified:blog/News TLP.txt
  Log:
  We will release when the gump website is ready.

  PR:

  Obtained from:

  Submitted by: 

  Reviewed by:  

  CVS: --

  CVS: PR:

  CVS:   If this change addresses a PR in the problem report tracking

  CVS:   database, then enter the PR number(s) here.

  CVS: Obtained from:

  CVS:   If this change has been taken from another system, such as NCSA,

  CVS:   then name the system in this line, otherwise delete it.

  CVS: Submitted by:

  CVS:   If this code has been contributed to Apache by someone else; i.e.,

  CVS:   they sent us a patch or a new module, then include their name/email

  CVS:   address here. If this is your work then delete this line.

  CVS: Reviewed by:

  CVS:   If we are doing pre-commit code reviews and someone else has

  CVS:   reviewed your changes, include their name(s) here.

  CVS:   If you have not had it reviewed then delete this line.

  
  Revision  ChangesPath
  1.2   +2 -0  gump/blog/News/TLP.txt
  
  Index: TLP.txt
  ===
  RCS file: /home/cvs/gump/blog/News/TLP.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- TLP.txt   1 Mar 2004 19:49:23 -   1.1
  +++ TLP.txt   1 Mar 2004 19:51:00 -   1.2
  @@ -4,6 +4,8 @@
   Please expand and edit br/
   view at 
   http://gump.chalko.com/gb/blog/News?permalink=TLP.txtpreview=true
  +br/
  +We will release when the gump website is ready.
   hr/
   p
   http://gump.apache.org
  
  
  

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

Re: [GUMP@lsd]: avalon/avalon failed

Antoine responded:

 This much I figured. But the site docs have a large gap between purpose
and
 details.

 I agree, I had to hack my way also to figure out where is the gump
 descriptor for avalon.
  (used find . -name *.xml | xargs grep avalon)


Could you enter this as an enhancement request into JIRA? I (about a month
ago) tried having this information listed in xref, and also on each
project/module, but even though it is in there (see the href attribute)

http://lsd.student.utwente.nl/gump/avalon/index_details.html#Definition

I somehow failed:

http://build.try.sybase.com/eclipse-gump/gump_xref/descriptor_project.html


regards,

Adam


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

cvs commit: gump/blog/Issues TakingControlOfModule.txt

nickchalko2004/03/01 13:04:43

  Added:   blog/Issues TakingControlOfModule.txt
  Log:
  Preparing comments about Avalon and module.xml

  PR:

  Obtained from:

  Submitted by: 

  Reviewed by:  

  CVS: --

  CVS: PR:

  CVS:   If this change addresses a PR in the problem report tracking

  CVS:   database, then enter the PR number(s) here.

  CVS: Obtained from:

  CVS:   If this change has been taken from another system, such as NCSA,

  CVS:   then name the system in this line, otherwise delete it.

  CVS: Submitted by:

  CVS:   If this code has been contributed to Apache by someone else; i.e.,

  CVS:   they sent us a patch or a new module, then include their name/email

  CVS:   address here. If this is your work then delete this line.

  CVS: Reviewed by:

  CVS:   If we are doing pre-commit code reviews and someone else has

  CVS:   reviewed your changes, include their name(s) here.

  CVS:   If you have not had it reviewed then delete this line.

  
  Revision  ChangesPath
  1.1  gump/blog/Issues/TakingControlOfModule.txt
  
  Index: TakingControlOfModule.txt
  ===
  PREVIEW Communtiy Control of Project Metadata
  Please expand and edit br/
  view at 
  
http://gump.chalko.com/gb/blog/Issues?permalink=TakingControlOfModule.txtpreview=true
  br/
  
  pRecently the Avalon build on gump has been failing because of a missconfigured 
module.xml
  Avalon keeps it module.xml in it's cvs at ??
  /p
  pAvalon has not been responsive to making changes to this 
  file but many other project in gump relay on it so we considered taking 
  moving it's module.xml to the gump cvs.
  pIn general gump preferrs module.xml to be kept in it's cvs where all of apache 
can 
  keep it uptodate and running.  However we defer to what ever a project wants as 
  long as the greater community is served.   For gump that means, succesfull builds. 
  /p
  p
  [So what did we do ?]
  /p
  
  
  

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

cvs commit: gump gumpy.py

ajack   2004/03/01 13:35:31

  Modified:.gumpy.py
  Log:
  Send url to log, don't send whole log...
  
  Revision  ChangesPath
  1.4   +12 -8 gump/gumpy.py
  
  Index: gumpy.py
  ===
  RCS file: /home/cvs/gump/gumpy.py,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- gumpy.py  25 Feb 2004 00:00:03 -  1.3
  +++ gumpy.py  1 Mar 2004 21:35:31 -   1.4
  @@ -234,7 +234,8 @@
   mailserver=wsw.getAttribute('mailserver')

   mailport=wsw.getAttribute('mailport') or 25

   mailto=wsw.getAttribute('mailinglist')

  -mailfrom=wsw.getAttribute('email')

  +mailfrom=wsw.getAttribute('email') 

  +logurl=wsw.getAttribute('logurl')

   # Extract the mail server/address

   ws.unlink()

   

  @@ -248,6 +249,8 @@
   log.write('- GUMP mail from  : ' + mailfrom + '\n')

   if mailto:

   log.write('- GUMP mail to: ' + mailto + '\n')

  +if logurl:

  +log.write('- GUMP log is @   : ' + logurl + '\n')

   

   #

   # Add Gump to Python Path...

  @@ -314,16 +317,17 @@
   # Cat log if failed...

   catFile(sys.stdout, logFile, logTitle)

   

  -if mailserver and mailport and mailto and mailfrom:

  +if mailserver and mailport and mailto and mailfrom and logurl:

   # :TODO: Sucky to read file into memory...

   # Need to figure out attachments, if that

   # helps  doesn't just do same...

  -tmpStream=StringIO.StringIO() 

  -catFile(tmpStream, logFile, logTitle)

  -tmpStream.seek(0)

  -logData=tmpStream.read()

  -tmpStream.close()

  -tmpStream=None

  +#tmpStream=StringIO.StringIO() 

  +#catFile(tmpStream, logFile, logTitle)

  +#tmpStream.seek(0)

  +#logData=tmpStream.read()

  +#tmpStream.close()

  +#tmpStream=None

  +logData='There is a problem with the run at : ' + logurl

   sendEmail(mailto,mailfrom,logTitle,logData,mailserver,mailport)

   

   # bye!

  
  
  

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

cvs commit: gump gumpy.py

ajack   2004/03/01 13:49:30

  Modified:.gumpy.py
  Log:
  I hate that Gumpy resolves workspaces relative to ../ 'cos it runs under ./python
  
  Revision  ChangesPath
  1.6   +1 -1  gump/gumpy.py
  
  Index: gumpy.py
  ===
  RCS file: /home/cvs/gump/gumpy.py,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- gumpy.py  1 Mar 2004 21:46:52 -   1.5
  +++ gumpy.py  1 Mar 2004 21:49:30 -   1.6
  @@ -212,7 +212,7 @@
   if os.environ.has_key('GUMP_WORKSPACE'):

   workspaceName = os.environ['GUMP_WORKSPACE'] + '.xml'

   

  -workspacePath = os.path.abspath(os.path.join('python',workspaceName))

  +workspacePath = os.path.abspath(workspaceName)

   

   projectsExpr='*'

   if os.environ.has_key('GUMP_PROJECTS'):

  
  
  

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

cvs commit: gump gumpy.py

ajack   2004/03/01 13:56:23

  Modified:.gumpy.py
  Log:
  The projects expression '*' gets expanded, so pass 'all'.
  
  Revision  ChangesPath
  1.7   +1 -1  gump/gumpy.py
  
  Index: gumpy.py
  ===
  RCS file: /home/cvs/gump/gumpy.py,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- gumpy.py  1 Mar 2004 21:49:30 -   1.6
  +++ gumpy.py  1 Mar 2004 21:56:23 -   1.7
  @@ -214,7 +214,7 @@
   

   workspacePath = os.path.abspath(workspaceName)

   

  -projectsExpr='*'

  +projectsExpr='all'

   if os.environ.has_key('GUMP_PROJECTS'):

   projectsExpr = os.environ['GUMP_PROJECTS']   

   

  
  
  

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

Re: [GUMP@lsd]: avalon/avalon failed


http://build.try.sybase.com/eclipse-gump/gump_xref/descriptor_project.html

 is this build.try.sybase.com URL supposed to be public ? I cannot open
 it in my Web browser.

Oops, no, sorry -- one of my internal ones. I was using my browser history
to get to an xref link, and didn't look closely.

That said, coincidentally, http://gump.try.sybase.com [a public server] is
under construction once again. Once I get gumpy.py working there (and if the
VMWare ESX on this bigger/more resourced box hold up to full Gumpy load,
like the GSX on lesser hardware didn't) I'll add it to the pool.

Once I get this local box up, I'll look at the foreign world of OSX on
moof...

regards

Adam


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

Re: Gump Database

This can wait a while, and certainly until after your demo.

I'll try to move it to the Wiki so folks can read/contribute as their time
allows, and not struggle to decipher (Adam English)/comprehend/respond
whilst surviving a day's inbox overload...

regards

Adam
- Original Message - 
From: Stefano Mazzocchi [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Monday, March 01, 2004 7:47 PM
Subject: Re: Gump Database


 Adam R. B. Jack wrote:

  Stefano wrote:
 
 
 While the question that you should be asking yourself is: what does the
 data look like? how stuctured is it?
 
  From where I stand, the gump metadata is highly structured and can be
 perfectly mapped in to a relational structure with reasonable effort.
 Also, given its structure, can be indexed precisely and thus queried
 very efficiently.
 
 
  So the fact that I can visualize this it into a huge rats nest in my
head
  (especially when wired into objects) doesn't help me make a case for it
  being unstructured? ;-) ;-)
 
  Ok, I hear you -- and stepping back, looking at the main (named)
entities as
  entries in tables, I can see a relational schema with relationships as
names
  with or without RI. What I can't see (though) is what helps me with the
time
  aspect --- i.e. when a dependency is dropped, what do I compare against?

 nonono wait a second. What are you talking about? I was talking about
 putting the historical data into the system, not the gump metadata.

  I guess the data I'm interested in right now is (somehow) relationships
over
  time. One projects relationship to it's repository, to it's peers, to
  communities (of users). How that looks, I'm not sure, but I'll try to
answer
  that in my head before I continue.

 I have an email in my draft folder about how we can do perfect nagging
 with gump... but I need to understand the graph complexity before I can
 go on and I don't have much time ATM since we are delivering the first
 demo of our project next week.

 At that point, once you have the data in the database, you can start
 thinking about what to do with it. Dependency graph visualization,
 history of dependencies, FoG estimation, all of these are problems that
 will result in particular queries and particular use of the result set.
 
 
  I like XML as the human (community) editable interface, and converting
it to
  relational for each run really doesn't appeal to me.

 Of course!! Nonono, I don't want to move from XML descriptors to
 relational data, that would be stupid without an GUI or a webapp to
 guide people, but I wouldn't use it anyway.

  Even if I do, comparing
  as I load, and detecting changes -- also sounds like work. It also
sounds
  similar to the XML to Object work that Gumpy is doing, and I was hoping
  something could help out here w/o me doing it myself in pedestrian
steps.

 I am *NOT* proposing to change the way gump loads metadata but the way
 gump stores history information

  I need to do more thinking, but thanks for the direct feedback, I
appreciate
  that. Another persons clarity helps.
 
  BTW: So say we want MySQL [for results and maybe more], how do we set
that
  up? Do we install, or leverage an existing MySQL install at Apache?

 good question, but too early now, let's focus on what we want to do and
 how, the infrastructural details will come after that.

 -- 
 Stefano.




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

Wanna join Gump : Development

2004-03-01 Thread krishnamoorthy



Hi,
I am interested to join in this development team.I
checked the outstanding TODOS  list and I am
interested to invole in this team.Let me know if I
could do something.Btw I do't know  Python.I am from
J2EE/Java background.
regds
Kicha

__
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools

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

patch for testsuite/build.xml

2004-03-01 Thread Antoine Lévy-Lambert

Hi Sliders,

can you update the build.xml file located in the testsuite subdir, there 
is a leftover of your last change of jdom version,
this is putting the gump build for your software unneedly in the red, 
where it should be green like a prairie in Normandie.

Cheers,

Antoine
Index: testsuite/build.xml
===
RCS file: /home/cvspublic/jakarta-slide/testsuite/build.xml,v
retrieving revision 1.19
diff -u -r1.19 build.xml
--- testsuite/build.xml 18 Feb 2004 09:31:59 -  1.19
+++ testsuite/build.xml 1 Mar 2004 22:54:25 -
@@ -49,7 +49,7 @@
   target name=make description=builds the tprocessor
 copy todir=${lib} file=${slideclientlib}/${client.jar} overwrite=yes /
 copy todir=${lib} file=${slideclientextlib}/commons-httpclient.jar 
overwrite=yes /
-copy todir=${lib} file=${basedir}/../lib/jdom-b9.jar overwrite=yes /
+copy todir=${lib} file=${basedir}/../lib/jdom-20040226-.jar overwrite=yes 
/
 antcall target=compile /
 antcall target=makejar /
   /target

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

Re: [GUMP@lsd]: avalon/avalon failed

2004-03-01 Thread Stefan Bodewig

On Fri, 27 Feb 2004, Antoine Lévy-Lambert [EMAIL PROTECTED]
wrote:

I had to hack my way also to figure out where is the gump descriptor
for avalon. (used find . -name *.xml | xargs grep avalon)

Looking into Gump's profile may have been easier:

module
href=http://cvs.apache.org/viewcvs.cgi/*checkout*/avalon/buildsystem/gump-integration/project/avalon.xml/

;-)

Niclas Hedhman wrote:

Applied (not that I know why this is needed...)

Stefan Bodewig figured out that we needed this mkdir [1] [2], he
thinks that a path containing some classes is not incorporated into
the build classpath, because at the beginning of the build the
directory does not exist.

Let me expand this a little.

Some JVMs drop things from the CLASSPATH that don't exist at startup
time - I think all Sun VMs after 1.3 do. They will not be included in
java.class.path and the application has no control over it.

If the build process creates a directory and compiles classes into
this directory that are later needed in the same build, we need to
ensure that the directory exists prior to starting the JVM to prevent
this.

This doesn't seem to be necessary for all situations, for example:

* forked junit and java tasks don't need a mkdir upfront since
they'll see the CLASSPATH environment variable.

* javac tasks that include the sources of the compiled classes in
the sourcepath don't need it since javac will use the sources instead.

* javac tasks that compile to the work directory won't need it
since Ant adds the target directory to the classpath.

But in general each work element inside a Gump descriptor will need
a corresponding mkdir.

Stefan

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

Re: [Fwd: [GUMP][PATCH] this should make avalon compile in Gump]