|
From: Patrick L. <pa...@bo...> - 2001-11-21 06:54:17
|
I tried and could not get plugins working.. I believe the structure is correct. Could you try running ./build dist run java -jar <version>-install.jar and look at the produced plugins directory.. I believe I have it right. I checked the squirrel-log file and nothing out of the ordinary except for the exceptions of not being able to load the default jdbc drivers from the CLASSPATH.. -P On Wed, 21 Nov 2001, Colin Bell wrote: > Take a look at /squirrel/doc/plugins.html for more info. > > If you think the have the directory structure correct (see below) but you're > not getting any plugins loaded make sure that the system property user.dir > is pointed to the directory that contains the plugins directory. This would > normally be the case if your shell script is in <squirrel-app> and the > plugins in <squirrel-app>/plugins. > > One screwup that can occur in Windows is in you create a shortcut to the > batch file and change the working directory to the something other than the > default. > > If it still doesn't work look for any error msgs in > <user-home>/.squirrel-sql/squirrel-sql.log > > You can get more info from the log by editing > <user-home>/.squirrel-sql/prefs.xml and replacing > <debugMode>false</debugMode> > > with > <debugMode>true</debugMode> > > Squirrel should be shutdown while you edit prefs.xml or it will overwrite > your changes. > > ---------------------- > > The plugin jars should live in the <squirrel-app>/plugins directory. All > other files should be kept within the plugins personal direcotry beneath > plugins. > > E.G. The Look and Feel plugin has an internal name of laf so its jar should > be called laf.jar, it should be placed in /plugins and its own files should > eb placed in /plugins/laf > > C:\sql\plugins>dir /s > Volume in drive C has no label. > Volume Serial Number is 9802-DD37 > > > Directory of C:\sql\plugins > > 21/11/01 11:48 <DIR> . > 21/11/01 11:48 <DIR> .. > 21/11/01 11:47 <DIR> laf > 20/11/01 09:34 28,267 laf.jar > 4 File(s) 28,267 bytes > > Directory of C:\sql\plugins\laf > > 21/11/01 11:47 <DIR> . > 21/11/01 11:47 <DIR> .. > 20/11/01 09:34 26,925 kunststoff_Licence.txt > 21/11/01 11:47 <DIR> lafs > 20/11/01 09:34 364,713 skinlf.jar > 20/11/01 09:34 2,383 skin_look_and_feel_licence.txt > 20/11/01 09:34 34,072 src.jar > 21/11/01 11:47 <DIR> theme_packs > 8 File(s) 428,093 bytes > > Directory of C:\sql\plugins\laf\lafs > > 21/11/01 11:47 <DIR> . > 21/11/01 11:47 <DIR> .. > 20/11/01 09:34 23,595 kunststoff.jar > 20/11/01 09:34 163 readme.txt > 4 File(s) 23,758 bytes > > Directory of C:\sql\plugins\laf\theme_packs > > 21/11/01 11:47 <DIR> . > 21/11/01 11:47 <DIR> .. > 24/07/01 16:52 108,854 aquathemepack.zip > 24/07/01 16:52 22,851 beosthemepack.zip > 24/07/01 16:52 108,049 macosthemepack.zip > 24/07/01 16:52 45,799 modernthemepack.zip > 20/11/01 09:34 123 readme.txt > 20/06/01 05:11 27,898 themepack.zip > 20/11/01 09:34 25,550 whistlerthemepack.zip > 9 File(s) 339,124 bytes > > > Hope this helps. > Col > > -----Original Message----- > From: Patrick Lacson [mailto:pa...@la...] > Sent: Wednesday, 21 November 2001 10:10 > To: squirrel-dev > Subject: Re: [Squirrel-sql-develop] new module 'squirrel' > > > 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 > > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > -- </Patrick> pa...@bo... Ext: 3694 |
