The installation now works, however I think I really need help on the
plugins section. Should I just drop the say lafs.jar into the
plugins/lafs.jar directory and everything will automagically happen? I
tried loading the plugin jar files into the plugins directory and from
the UI I look at Plugins and it just shows 'Summary' with a big empty
text box.
Any ideas what I'm doing wrong? Anyway I think the build-system is 95%
ready with the plugins still preventing a golden build.
-P
Patrick Lacson wrote:
>
> All,
>
> I think with buildmagic, the one thing we have to get used to is a
> CLASSPATH-less environment. Also your environment must not have
> ANT_HOME set or the incorrect version of ANT may be used. The
> build-system "magically" creates the CLASSPATH for us providing a very
> tight and clean build room. This prevents any possiblity of
> contaminated libraries from being loaded which could potentially break
> compilation. So with that I give my status update..
>
> The squirrel module is now 90% complete. I've checked in the izPack
> libraries and 'skeleton' templates that are required to build.
>
> Right now an untested install.jar is created by typing:
>
> ./build izpack
>
> This will automatically compile all the sources and create the jars and
> pack them into the install.jar located in the root directory as
>
> ./squirrel-0.1-alpha-install.jar (naming can easily be modified later)
>
> For developers who want to start the application directly from their
> build environment they can by typing
>
> ./build start (this will launch the application in a separate JVM)
>
> Colin,
>
> I noticed that you have 2 version of the installation, basic and
> complete. I take it that basic is without the source code and plugins,
> while complete is everytihng but the kitchen sink? Also can somebody
> explain the concept of plugins? Are we using them as dynamically
> loadable components? Or are they just plugins that extend the
> application? For example if we wanted to add a query-wizard, that would
> be added as a plugin right? Is the plugin a open interface or is it
> something that we wrote in-house? Open-interface I mean something like
> JMX which seems to be the hottest buzz word for "pluggable" components
> in the J2EE space..
>
> Thanks,
>
> -P
>
> Patrick Lacson wrote:
> >
> > Guys,
> >
> > This was a lot quicker than I suspected. The new module squirrel is
> > ready to go. The only important target left is "release".
> >
> > So far the new system can compile the sources and run the app from a
> > target.
> >
> > Just read the README on how to compile and run. The release target will
> > be a bit tricky since Colin has an elaborate scheme with the izPack
> > stuff which I haven't looked at yet.. MOre fun tommorow!
> >
> > Just a reminder, checkins will now have to be carefully monitored since
> > we've created a whole new module. I wish I could say that his is a
> > branch but it is not, it is a whole new module due to the new tree
> > structures.
> >
> > So pleasse let's all be careful before checking in any new code or else
> > we could easily muck up the two modules and get out of sync and create
> > mass confusion!! Colin, any ideas on how we can keep everybody from
> > checking stuff in? Or rather how can be best prevent an out-of-sync
> > situation between the modules. They are in sync as of 11/19/2001 7:00pm
> > Pacific Standard Time
> >
> > -P
> >
> > _______________________________________________
> > Squirrel-sql-develop mailing list
> > Squ...@li...
> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
>
> _______________________________________________
> Squirrel-sql-develop mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop
|
