[kepler-dev] Problems with building kepler alpha3 installer

[Ilkay Altintas]

Dan, Shawn,

The problem seems like a mix of both.

I have updated the run target and made the classpath same
with the run-dev one except for the part that uses the project
jars. It seems to work for me to compile and run the actors?

The only part that doesn't work is the actor search part.
It find the right folders but doesn't seem to clone the actors.
So I'm not sure if anything else need to be done in the run target
except for the classpath set up. Maybe we need to include a few
more files in the jars. I'll look into this more.

But as far as I could test, everything else works. I've checked
it in so that maybe Shawn and Chad can look at it. They know
which file to include better than me for the search to work.

Dan: Thanks for building the installer! =)

--Ilkay



> -----Original Message-----
> From: kepler-dev-admin at ecoinformatics.org
> [mailto:kepler-dev-admin at ecoinformatics.org]On Behalf Of Shawn Bowers
> Sent: Saturday, October 16, 2004 4:25 PM
> To: Dan Higgins
> Cc: Bertram Ludaescher; kepler-dev at ecoinformatics.org
> Subject: Re: [kepler-dev] Problems with building kepler alpha3 installer
>
>
> On Sat, 16 Oct 2004, Dan Higgins wrote:
>
> > Bertram,
> >     It looks like we can just comment it out for now. (Kepler is not
> > really using it). I am not sure that the problem is just the 'Python
> > Script' actor. It really appears to be some interaction with the new
> > ActorLibrary tree code created by Chad/Shawn which is trying to build
> > the actor tree dynamically at start up. I have a minimal zip version of
> > an installer working. I will test it some more and probably get the
> > InstallAnywhere installers done sometime tomorrow.
>
> Sorry, I don't understand: are you saying it is a problem with what Chad
> and I did, or a problem with missing jars?  Also, I don't think there are
> problems if you use run-dev, so it sounds like it isn't a problem with
> Python or what Chad and I did, but the run target?
>
> shawn
>
> >
> > Dan
> >
> > Bertram Ludaescher wrote:
> >
> > >hmmm... do we know who is the author of Python Script or who uses it?
> > >
> > >Maybe we can just do without it for the alpha3 release?
> > >
> > >Bertram
> > >
> > >
> > >
> > >>>>>>"DH" == Dan Higgins <higgins at nceas.ucsb.edu> writes:
> > >>>>>>
> > >>>>>>
> > >DH>
> > >DH> Incidently,
> > >DH>     I find that 'ant run' works if I simply comment out
> the entity named
> > >DH> "Python Script" in the file "basicKeplerActorLibrary,xml"
> > >DH>
> > >DH> Dan
> > >DH>
> > >DH>
> > >DH> Dan Higgins wrote:
> > >DH>
> > >
> > >
> > >>>Hi All,
> > >>>FYI, I have not yet been able to get a Kepler Alpha3 installer
> > >>>working due to problems with setting the correct class paths. I think
> > >>>the problem is related to the fact that with the current head of CVS
> > >>>the 'ant run-dev' command will launch kepler OK, but the 'ant run'
> > >>>command will not.
> > >>>
> > >>>Does anyone know why 'ant run' no longer works? It looks
> like the only
> > >>>difference is in the use of jar files versus uncompressed class file!
> > >>>
> > >>>Dan Higgins
> > >>>_______________________________________________
> > >>>kepler-dev mailing list
> > >>>kepler-dev at ecoinformatics.org
> > >>>http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
> > >>>
> > >>>
> > >DH>
> > >DH>
> > >DH> _______________________________________________
> > >DH> kepler-dev mailing list
> > >DH> kepler-dev at ecoinformatics.org
> > >DH> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
> > >
> > >
> >
> > _______________________________________________
> > kepler-dev mailing list
> > kepler-dev at ecoinformatics.org
> > http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
> >
>
> _______________________________________________
> kepler-dev mailing list
> kepler-dev at ecoinformatics.org
> http://www.ecoinformatics.org/mailman/listinfo/kepler-dev
>