You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Thomas <ho...@hotpop.com> on 2005/07/26 12:00:46 UTC

Gump3 presentation

Hi !

So.. after alott of research and looking in to what technolegie to use
the final is Java+struts. I have started make some pages and code one
usecase (read more on wiki page).

Since I don't have so much experience of gump and know what the user
might be interested in pleas come with sugestions on what you whant to
se and what the application should do.

I also have one question regarding the database.
The causes table lists the cause of a stalled package. The same
information could be found by listing the dependencies tree from one
faild build. If I got it right it's the same information on two places.
The only thing that would make my statement wrong is if:

package#1 depends on package#2
and package#1 can be build although package#2 faild.

Another way my statement dosent work on is if.

the causes table refer to somethig else then only dependencies.

As I said before I don't know if got the causes table right need some
clearance on that.

Also I have made my webserver that I work on public so if you whant to
see the ongoing process you can go to
http://nacka.no-ip.com/Gump3Present/. The server will only be running
while I'm working so to be sure that the server is up you can check with
me on irc.freenode.net#afsgump. (if I'm online the server is running.)

regards

Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Re: Gump3 presentation

Posted by Leo Simons <ma...@leosimons.com>.
On 26-07-2005 12:00, "Thomas" <ho...@hotpop.com> wrote:
> Hi !

Hi thomas!

(this is a quick reply, I have limited connectivity atm)

> I also have one question regarding the database.
> The causes table lists the cause of a stalled package. The same
> information could be found by listing the dependencies tree from one
> faild build. If I got it right it's the same information on two places.
> The only thing that would make my statement wrong is if:
> 
> package#1 depends on package#2
> and package#1 can be build although package#2 faild.
> 
> Another way my statement dosent work on is if.
> 
> the causes table refer to somethig else then only dependencies.
> 
> As I said before I don't know if got the causes table right need some
> clearance on that.

A cause can also be failure to update from source control (eg CVS), a
problem with the xml definitions, an internal error within gump, or
something similar. There can be multiple causes (eg multiple failed
dependencies). Think of this as a sort of "lightweight exception stack
trace".

*but*, for now, it might indeed be a good idea to just look for one
dependency that caused a problem and use that. It can be generalized later.

Cheers!

Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org