You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2004/04/11 09:44:38 UTC
Avalon Phoenix
Gumpster!
Avalon Phoenix needs the following projects.
<!-- Unlisted Dependencies
Spice LoggerStore
http://osdn.dl.sourceforge.net/sourceforge/spice/spice-loggerstore-0.5.tar.gz
Spice ConfigKit
http://osdn.dl.sourceforge.net/sourceforge/spice/spice-configkit-1.1.2.tar.gz
Spice XMLPolicy
http://osdn.dl.sourceforge.net/sourceforge/spice/spice-xmlpolicy-1.0.tar.gz
Spice ClassMan
http://osdn.dl.sourceforge.net/sourceforge/spice/spice-classman-1.0.tar.gz
-->
The thing there is, that all these can be dynamically downloaded and expanded
by calling the following ANT targets;
ant get-configkit
ant get-xmlpolicy
ant get-loggerstore
ant get-classman
Is it possible/recommendable that Gump calls these targets first, or are these
Spice modules available somewhere in the Gump infrastructure?
Cheers
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: installed package vs jar in CVS
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 14 Apr 2004, Leo Simons <ls...@jicarilla.org> wrote:
> You can only distribute the sun packages as part of a larger work
> IIRC.
If it only was that easy. 8-)
Some of them may only be distributed in combined works, others may not
be distributed at all ... I don't even want to think of crypto
libraries downloaded from an US server.
Right now, we don't have anything more problematic than the Sun
packages, I agree. So my worries can get addressed once they become
real.
> Stefan Bodewig wrote:
>> Right now I have a set of shell scripts that has grown over time
>> that helps me deploy new packages,
>
> workflow issue! (as in, I don't have the scripts :D)
You have, the gump-server-side is in my home dir on every machine I
have access to (minus hermes where I never logged in). My master
script simply consists of repeated invocations of scp and ssh to run
the remote side.
It's not exactly rocket science. 8-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: installed package vs jar in CVS
Posted by Leo Simons <ls...@jicarilla.org>.
Stefan Bodewig wrote:
> On Wed, 14 Apr 2004, Leo Simons <ls...@jicarilla.org> wrote:
>
>>Stefan Bodewig wrote:
>
>>>Otherwise I'd probably prefer an "installed" package which is not
>>>easy to do for you without access to the live servers.
>>
>>workflow issue!
>
> More than that. Think of the click-through licenses and all that, it
> may be illegal to distribute installed packages in an automated way.
> I'm not sure, though.
been thinking about that. You can only distribute the sun packages as
part of a larger work IIRC. If we create a really big gump tarball that
we move around, they're part of the larger work. And if we put the
materials for the gump tarball in a private svn module...that's half of
the issue solved.
Need to ask Geir, probably.
Anyways, its not like spice-classman has a click-through license. The
primary reason to have installed packages at all are that license IIUC.
For everything else, we want everyone to be able to "install packages",
which we have, throug the use of <jar/> without <ant/>. But that's not a
clean way to manage things. It doesn't show that the project is not
being built hence the dependency is "tainted".
> Right now I have a set of shell scripts that has grown over time that
> helps me deploy new packages,
workflow issue! (as in, I don't have the scripts :D)
if gump is to grow big(ger), it needs to be easier for people to help
out in "gumpmeistering".
--
cheers,
- Leo Simons
-----------------------------------------------------------------------
Weblog -- http://leosimons.com/
Component Community -- http://componentplanet.org/
Component Glue -- http://jicarilla.org/
-----------------------------------------------------------------------
"We started off trying to set up a small anarchist community, but
people wouldn't obey the rules."
-- Alan Bennett
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: installed package vs jar in CVS
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 14 Apr 2004, Leo Simons <ls...@jicarilla.org> wrote:
> Stefan Bodewig wrote:
>> Otherwise I'd probably prefer an "installed" package which is not
>> easy to do for you without access to the live servers.
>
> workflow issue!
More than that. Think of the click-through licenses and all that, it
may be illegal to distribute installed packages in an automated way.
I'm not sure, though.
Right now I have a set of shell scripts that has grown over time that
helps me deploy new packages, but in the end it has been me who
accepted the license and installed the package.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
installed package vs jar in CVS (was: Re: Avalon Phoenix)
Posted by Leo Simons <ls...@jicarilla.org>.
Stefan Bodewig wrote:
>>Now, what is the right path forward here? LeoSimons suggests that I
>>stick the JARs into the Phoenix CVS, which seems like a reasonable
>>and straight forward approach.
>
> As long as no other projects need Spice, yes. Otherwise I'd probably
> prefer an "installed" package which is not easy to do for you without
> access to the live servers.
workflow issue! Need to make that easy :-D
--
cheers,
- Leo Simons
-----------------------------------------------------------------------
Weblog -- http://leosimons.com/
Component Community -- http://componentplanet.org/
Component Glue -- http://jicarilla.org/
-----------------------------------------------------------------------
"We started off trying to set up a small anarchist community, but
people wouldn't obey the rules."
-- Alan Bennett
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Avalon Phoenix
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 13 Apr 2004, Niclas Hedhman <ni...@hedhman.org> wrote:
> PeterD has also moved his Spice stuff to CodeHaus, and in the
> process changed the package names.
I understand.
> Now, what is the right path forward here? LeoSimons suggests that I
> stick the JARs into the Phoenix CVS, which seems like a reasonable
> and straight forward approach.
As long as no other projects need Spice, yes. Otherwise I'd probably
prefer an "installed" package which is not easy to do for you without
access to the live servers.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Avalon Phoenix
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tuesday 13 April 2004 15:45, Stefan Bodewig wrote:
> On Sun, 11 Apr 2004, Niclas Hedhman <ni...@hedhman.org> wrote:
> > Is it possible/recommendable that Gump calls these targets first,
>
> possible? Yes and you've already done so IIUC. This will make a
> non-networked Gump run impossible (but there are several other reasons
> why that wouldn't work) and it makes Gump download those jars every
> night.
>
> I wouldn't recommend it but rather try to build the spice stuff from
> sources, if possible.
Phoenix itself is a deprecated container, as a result of Peter Donald's
ousting and fork. That Phoenix fork is called Loom and is hosted on CodeHaus.
PeterD has also moved his Spice stuff to CodeHaus, and in the process changed
the package names. I am not sure if the old sources are still available at
sourceforge (Spice's old home), and I am more than a little reluctant to
modify Phoenix sources...
Now, what is the right path forward here?
LeoSimons suggests that I stick the JARs into the Phoenix CVS, which seems
like a reasonable and straight forward approach.
Advice is appreciated.
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Avalon Phoenix
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 11 Apr 2004, Niclas Hedhman <ni...@hedhman.org> wrote:
> Is it possible/recommendable that Gump calls these targets first,
possible? Yes and you've already done so IIUC. This will make a
non-networked Gump run impossible (but there are several other reasons
why that wouldn't work) and it makes Gump download those jars every
night.
I wouldn't recommend it but rather try to build the spice stuff from
sources, if possible.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Avalon Phoenix
Posted by Leo Simons <ls...@jicarilla.org>.
Niclas Hedhman wrote:
> Spice
>
> Is it possible/recommendable that Gump calls these targets first, or are these
> Spice modules available somewhere in the Gump infrastructure?
Spice was built by gump at some point, but bailed out later (think spice
is using damagecontrol now).
I'd actually suggest you put the jars in CVS (they are ASL-licensed so
its not a legal problem), not call the targets (gump would just download
the same files every night after all), and create "installed packages"
of these projects, ie somewhat like
http://cvs.sourceforge.net/viewcvs.py/jicarilla/jicarilla-maven-repository/gump-module.xml
the downside is of course that gump doesn't test that your download
targets work, but I'll argue gump is not here to test the availability
of the sourceforge distribution server :-D
The alternative works too, of course...put the calling of the download
targets into a seperate project descriptor (customary to prefix with
name of the project whose buildfile you're using, ie
"avalon-phoenix-spice-bla-download"), and have a <jar/> entry in the
project definition that references the place you just downloaded the jar to.
I don't know who started the "should not keep jars in CVS" meme, but
after much experimentation I've found it is just very pragmatic in
situations like this.
--
cheers,
- Leo Simons
-----------------------------------------------------------------------
Weblog -- http://leosimons.com/
Component Community -- http://componentplanet.org/
Component Glue -- http://jicarilla.org/
-----------------------------------------------------------------------
"We started off trying to set up a small anarchist community, but
people wouldn't obey the rules."
-- Alan Bennett
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org