Niclas Hedhman wrote:
David Crossley wrote:
It seems that Gump is still using the old descriptor in our SVN.
How do i get Gump to switch? The profile/gump.xml looks okay,
but the last time that it was built was two days ago using the
old descriptor.
It doesn't look Ok in my checked out
David Crossley wrote:
David Crossley wrote:
Stefano Mazzocchi wrote:
first of all, I think forrest should really transfer control of their
descriptor to the gump project.
Well, i said that we would sometime soon. I also said
not now because we have an imminent release of Forrest.
Our attention is
On Thursday 14 October 2004 13:06, David Crossley wrote:
It seems that Gump is still using the old descriptor in our SVN.
How do i get Gump to switch? The profile/gump.xml looks okay,
but the last time that it was built was two days ago using the
old descriptor.
It doesn't look Ok in my
Adam R. B. Jack wrote:
A tweet from the background ...
Very welcome.
The email reports that nag us on Cocoon and Forrest
are very hard for me to follow. (Please don't stop the nags.)
I do try to decipher them and even follow through
to the website. However, i inevitably give up
On 06 Oct 2004, David Crossley [EMAIL PROTECTED] wrote:
How to ease the confusion, i do not know.
In some way allow Gumpers a more direct way to modify your Gump
descriptors 8-)
Right now cocoon-lenya's (I realize that this is not yours)
descriptor references project avalon which has gone many
A tweet from the background ...
Very welcome.
The email reports that nag us on Cocoon and Forrest
are very hard for me to follow. (Please don't stop the nags.)
I do try to decipher them and even follow through
to the website. However, i inevitably give up and wait.
Bummer. Can you point
Stefan wrote:
In some way allow Gumpers a more direct way to modify your Gump
descriptors 8-)
You are asking for them to be moved to Gump CVS, right? If so, let's make
that request clear.
Right now cocoon-lenya's (I realize that this is not yours)
descriptor references project avalon which
On Wed, 6 Oct 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote:
Stefan wrote:
In some way allow Gumpers a more direct way to modify your Gump
descriptors 8-)
You are asking for them to be moved to Gump CVS, right? If so, let's
make that request clear.
Not necessarily. Stefano proposed to
David Crossley wrote:
Stefano Mazzocchi wrote:
Adam R. B. Jack wrote:
snip/
Cocoon didn't build 'cos (1) we'd not got enough folks caring about gump
successes (2) we didn't build from repository (and cocoon has lots of
dependencies, so it's chances of a build were unlikely. FWIIW: Communities
Stefano wrote:
look at the cocoon project. it says that it has 1 affected and 54
dependees, then the deli project (which is a package that the cocoon
module exposes) has 2 affected and 1 dependee. Either there is
something wrong or i don't understand what is an affected project and
what
Adam R. B. Jack wrote:
Stefano wrote:
look at the cocoon project. it says that it has 1 affected and 54
dependees, then the deli project (which is a package that the cocoon
module exposes) has 2 affected and 1 dependee. Either there is
something wrong or i don't understand what is an affected
Basically of the N dependees that a project could dork up, M (M=N)
dependees could be affected by that project's failure (with N - M being
dorked up by some earlier dependency). Do *not* ask me how we get 2 and
1.
Some optimization perhaps (this determination once cost far too many
cycles).
Adam R. B. Jack wrote:
Stefano
wait, this does not compute: Y affects 2 (self + Z). The fact that Z was
already affected should not change the situation.
So look at 'dependees' and stop looking at 'affected' -- and make the
dynamic webapp sort by either, or by your choice. Sure I understand your
Stefano Mazzocchi wrote:
Adam R. B. Jack wrote:
snip/
Cocoon didn't build 'cos (1) we'd not got enough folks caring about gump
successes (2) we didn't build from repository (and cocoon has lots of
dependencies, so it's chances of a build were unlikely. FWIIW: Communities
(many), along
Stefano Mazzocchi wrote:
This is not a rant, but constructive criticism.
1) as I mentioned already, I think that having gump (or forrest or
whatever) generate static HTML pages creates more problems than it
solves. I think we should move the architecture with something like this
metadata -
Leo Simons wrote:
Stefano Mazzocchi wrote:
This is not a rant, but constructive criticism.
1) as I mentioned already, I think that having gump (or forrest or
whatever) generate static HTML pages creates more problems than it
solves. I think we should move the architecture with something like
On Monday 04 October 2004 01:29, Stefano Mazzocchi wrote:
So, what do you guys think: should gump metadata still reside in xml
files or should it reside in a database and we have a web application on
top that takes care of managing it?
What is known as Magic, an Ant 1.6 extension system with
Stefano Mazzocchi wrote:
So, what do you guys think: should gump metadata still reside in xml
files or should it reside in a database and we have a web application on
top that takes care of managing it?
If we move, which is probably a good idea, I'd suggest moving over
gradually. Create a
This is not a rant, but constructive criticism.
1) as I mentioned already, I think that having gump (or forrest or
whatever) generate static HTML pages creates more problems than it
solves. I think we should move the architecture with something like this
metadata - gump - database -
On Monday 04 October 2004 06:04, Stefano Mazzocchi wrote:
well, I'm sorry but I don't get it. Gump *is* querying the metadata for
each module. If you choose to encode your data in a different way and
need to transform it to the gump markup format, that's your problem.
AFAIU, Gump doesn't tell
This is not a rant, but constructive criticism.
1) as I mentioned already, I think that having gump (or forrest or
whatever) generate static HTML pages creates more problems than it
solves. I think we should move the architecture with something like this
metadata - gump - database - jenny -
21 matches
Mail list logo
