You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(48) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(17) |
Mar
(30) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(3) |
Aug
(10) |
Sep
(8) |
Oct
(28) |
Nov
(24) |
Dec
(6) |
| 2003 |
Jan
(2) |
Feb
(6) |
Mar
(3) |
Apr
(7) |
May
(11) |
Jun
(14) |
Jul
(39) |
Aug
(9) |
Sep
(4) |
Oct
(21) |
Nov
(6) |
Dec
(26) |
| 2004 |
Jan
(3) |
Feb
(18) |
Mar
(9) |
Apr
(19) |
May
(8) |
Jun
(14) |
Jul
(11) |
Aug
(22) |
Sep
(11) |
Oct
(6) |
Nov
|
Dec
(3) |
| 2005 |
Jan
(8) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(3) |
Oct
(19) |
Nov
(12) |
Dec
|
| 2006 |
Jan
(3) |
Feb
(5) |
Mar
(4) |
Apr
(5) |
May
|
Jun
|
Jul
(2) |
Aug
(6) |
Sep
(36) |
Oct
(10) |
Nov
(40) |
Dec
(17) |
| 2007 |
Jan
(5) |
Feb
(2) |
Mar
(10) |
Apr
(7) |
May
(26) |
Jun
(31) |
Jul
(14) |
Aug
(12) |
Sep
(14) |
Oct
(8) |
Nov
(1) |
Dec
(9) |
| 2008 |
Jan
(2) |
Feb
(13) |
Mar
(3) |
Apr
(8) |
May
(1) |
Jun
(3) |
Jul
(6) |
Aug
(16) |
Sep
(2) |
Oct
|
Nov
(8) |
Dec
(3) |
| 2009 |
Jan
(2) |
Feb
(2) |
Mar
(4) |
Apr
(8) |
May
(5) |
Jun
(7) |
Jul
(1) |
Aug
(6) |
Sep
(5) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
| 2010 |
Jan
(11) |
Feb
(7) |
Mar
(2) |
Apr
(4) |
May
|
Jun
(2) |
Jul
(2) |
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2011 |
Jan
(7) |
Feb
(4) |
Mar
(26) |
Apr
(3) |
May
|
Jun
|
Jul
(10) |
Aug
(11) |
Sep
(11) |
Oct
(3) |
Nov
(3) |
Dec
|
| 2012 |
Jan
(5) |
Feb
(4) |
Mar
(4) |
Apr
(2) |
May
(7) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
| 2013 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
(5) |
Oct
(1) |
Nov
(5) |
Dec
(11) |
| 2014 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2015 |
Jan
(2) |
Feb
(6) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(7) |
Mar
(3) |
Apr
(2) |
May
|
Jun
(5) |
Jul
(5) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
(1) |
Sep
|
Oct
|
Nov
(6) |
Dec
|
| 2019 |
Jan
(1) |
Feb
(5) |
Mar
(3) |
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(2) |
| 2021 |
Jan
(2) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Adam W. <win...@gm...> - 2011-03-15 01:24:12
|
I have a plugin I would like to release. Who can I send it to for review and incorporation into the main branch? Thanks, Adam |
|
From: Adam W. <win...@gm...> - 2011-03-15 01:22:54
|
I know you can get the schemaName and other object info by doing this: IDatabaseObjectInfo doi = getDatabaseObjectInfo(); final String schemaName = doi.getSchemaName(); Is there a way to get the current logged in user and currently selected DB name? Thanks, Adam |
|
From: Adam W. <win...@gm...> - 2011-03-13 04:24:15
|
Rob, I had the DatabaseObjectType wrong. I got it working now. Thanks, Adam On Sat, Mar 12, 2011 at 4:54 PM, Robert Manning <rob...@gm...>wrote: > Adam, > > One guess would be that the type used to add the details tab doesn't match > the one being returned by the object in the tree. You could set a > breakpoint in ObjectTreePanel.getTabbedPane(DatabaseObjectType) to see what > DatabaseObjectType is being used to get the tabbed pane that is displayed > on the right when you click an object in the tree. It must be the same as > the one you used to register the details tab with the ObjectTree for your > details tab to be displayed and populated. > > > Rob > > On Fri, Mar 11, 2011 at 1:58 PM, Adam Winn <win...@gm...> wrote: > >> I was looking at the Netezza External Table plugin and trying to mimic it >> for another DB type. I can display the external tables just fine by >> using objTree.addExpander(), but I can't get any details to appear when I >> click on the external tables or expand the arrow beside them. I'm also >> using objTree.addDetailTab(). In my details java file, it enters the >> method ExternalTableDetailsTab() but it never goes inside >> createStatement(). >> Does anyone know why this is? I read in the docs that when you extend >> the >> base tab class, it will run the SQL you have in the createStatement() >> method, but that is not happening for me. It isn't even entering that >> method for me. I'm assuming this worked fine in the Netezza External >> Table >> plugin and I'm essentially doing what it's doing but it never >> enters createStatement() and I don't get any details of the external >> table. >> >> The docs say: >> A source tab can then be implemented by extending the classes >> BaseSourceTab< >> https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourceTab.java >> > >> and BaseSourcePanel< >> https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourcePanel.java >> >. >> In particular, BaseSourceTab has an abstract method called createStatement >> which is implemented to return a PreparedStatement by using >> BaseObjectTab.getSession() and BaseObjectTab.getDatabaseObjectInfo(). The >> method getDatabaseObjectInfo returns the node that is selected from which >> can be found the name, schema and catalog of the object to write an SQL >> statement that queries the data dictionary for the source for that object. >> The BaseSourcePanel load method is then called with the ResultSet obtained >> by executing the PreparedStatement. >> >> Does anyone know why it's not entering the createStatement() method and >> therefore not showing me the details of the external table? >> >> Thanks, >> Adam >> >> ------------------------------------------------------------------------------ >> Colocation vs. Managed Hosting >> A question and answer guide to determining the best fit >> for your organization - today and in the future. >> http://p.sf.net/sfu/internap-sfd2d >> _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > > |
|
From: Robert M. <rob...@gm...> - 2011-03-12 23:54:37
|
Adam, One guess would be that the type used to add the details tab doesn't match the one being returned by the object in the tree. You could set a breakpoint in ObjectTreePanel.getTabbedPane(DatabaseObjectType) to see what DatabaseObjectType is being used to get the tabbed pane that is displayed on the right when you click an object in the tree. It must be the same as the one you used to register the details tab with the ObjectTree for your details tab to be displayed and populated. Rob On Fri, Mar 11, 2011 at 1:58 PM, Adam Winn <win...@gm...> wrote: > I was looking at the Netezza External Table plugin and trying to mimic it > for another DB type. I can display the external tables just fine by > using objTree.addExpander(), but I can't get any details to appear when I > click on the external tables or expand the arrow beside them. I'm also > using objTree.addDetailTab(). In my details java file, it enters the > method ExternalTableDetailsTab() but it never goes inside > createStatement(). > Does anyone know why this is? I read in the docs that when you extend the > base tab class, it will run the SQL you have in the createStatement() > method, but that is not happening for me. It isn't even entering that > method for me. I'm assuming this worked fine in the Netezza External Table > plugin and I'm essentially doing what it's doing but it never > enters createStatement() and I don't get any details of the external table. > > The docs say: > A source tab can then be implemented by extending the classes > BaseSourceTab< > https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourceTab.java > > > and BaseSourcePanel< > https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourcePanel.java > >. > In particular, BaseSourceTab has an abstract method called createStatement > which is implemented to return a PreparedStatement by using > BaseObjectTab.getSession() and BaseObjectTab.getDatabaseObjectInfo(). The > method getDatabaseObjectInfo returns the node that is selected from which > can be found the name, schema and catalog of the object to write an SQL > statement that queries the data dictionary for the source for that object. > The BaseSourcePanel load method is then called with the ResultSet obtained > by executing the PreparedStatement. > > Does anyone know why it's not entering the createStatement() method and > therefore not showing me the details of the external table? > > Thanks, > Adam > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Adam W. <win...@gm...> - 2011-03-12 00:41:56
|
That worked. thanks. On Fri, Mar 11, 2011 at 3:26 PM, Robert Manning <rob...@gm...>wrote: > Try : > > mvn -e clean install > > Rob > > On Fri, Mar 11, 2011 at 1:52 PM, Adam Winn <win...@gm...> wrote: > >> At the root of the sql12 dir, I ran 'mvn -e clean compile' and the >> SQuirreL >> Plugin Archetype fails to compile: >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Building SQuirreL Plugin Archetype 3.3.0-SNAPSHOT >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] >> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ >> squirrelsql-plugin-archetype --- >> [INFO] >> [INFO] --- maven-dependency-plugin:2.1:unpack-dependencies >> (copy-example-project-java) @ squirrelsql-plugin-archetype --- >> [INFO] Unpacking >> /Users/awinn/Documents/sql12/plugins/example/target/classes >> to >> >> >> /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java >> with includes **\/*.java and excludes:**\/*Test.java >> org.codehaus.plexus.archiver.ArchiverException: The source must not be a >> directory. >> at >> >> org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) >> at >> >> org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) >> at >> >> org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) >> at >> >> org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) >> at >> >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] SQuirreL Root POM ................................. SUCCESS >> [0.092s] >> [INFO] Framework Library ................................. SUCCESS >> [4.168s] >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS >> [3.255s] >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS >> [0.001s] >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS >> [0.008s] >> [INFO] Example Plugin .................................... SUCCESS >> [0.326s] >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE >> [0.432s] >> [INFO] Codecompletion Plugin ............................. SKIPPED >> [INFO] Dataimport Plugin ................................. SKIPPED >> [INFO] Db2 Plugin ........................................ SKIPPED >> [INFO] Dbcopy Plugin ..................................... SKIPPED >> [INFO] Dbdiff Plugin ..................................... SKIPPED >> [INFO] Derby Plugin ...................................... SKIPPED >> [INFO] Editextras Plugin ................................. SKIPPED >> [INFO] Exportconfig Plugin ............................... SKIPPED >> [INFO] Favs Plugin ....................................... SKIPPED >> [INFO] Firebird Plugin ................................... SKIPPED >> [INFO] Firebirdmanager Plugin ............................ SKIPPED >> [INFO] Graph Plugin ...................................... SKIPPED >> [INFO] Greenplum Plugin .................................. SKIPPED >> [INFO] H2 Plugin ......................................... SKIPPED >> [INFO] Hibernate Plugin .................................. SKIPPED >> [INFO] I18n Plugin ....................................... SKIPPED >> [INFO] Informix Plugin ................................... SKIPPED >> [INFO] Look and Feel Plugin .............................. SKIPPED >> [INFO] Macosx Plugin ..................................... SKIPPED >> [INFO] Mssql Plugin ...................................... SKIPPED >> [INFO] Mysql Plugin ...................................... SKIPPED >> [INFO] Netezza Plugin .................................... SKIPPED >> [INFO] Oracle Plugin ..................................... SKIPPED >> [INFO] Postgres Plugin ................................... SKIPPED >> [INFO] Refactoring Plugin ................................ SKIPPED >> [INFO] Sessionscript Plugin .............................. SKIPPED >> [INFO] Smarttools Plugin ................................. SKIPPED >> [INFO] Sqlbookmark Plugin ................................ SKIPPED >> [INFO] Sqlparam Plugin ................................... SKIPPED >> [INFO] Sqlreplace Plugin ................................. SKIPPED >> [INFO] Sqlscript Plugin .................................. SKIPPED >> [INFO] Sqlval Plugin ..................................... SKIPPED >> [INFO] Sybase Plugin ..................................... SKIPPED >> [INFO] Syntax Plugin ..................................... SKIPPED >> [INFO] Userscript Plugin ................................. SKIPPED >> [INFO] Plugin Modules POM file ........................... SKIPPED >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 8.882s >> [INFO] Finished at: Fri Mar 11 11:50:11 MST 2011 >> [INFO] Final Memory: 20M/105M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies >> (copy-example-project-java) on project squirrelsql-plugin-archetype: Error >> unpacking file: >> /Users/awinn/Documents/sql12/plugins/example/target/classes >> to: >> >> /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java >> [ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must >> not >> be a directory. >> [ERROR] -> [Help 1] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal >> org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies >> (copy-example-project-java) on project squirrelsql-plugin-archetype: Error >> unpacking file: >> /Users/awinn/Documents/sql12/plugins/example/target/classes >> to: >> >> /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java >> org.codehaus.plexus.archiver.ArchiverException: The source must not be a >> directory. >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> at >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) >> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> at >> >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> Caused by: org.apache.maven.plugin.MojoExecutionException: Error unpacking >> file: /Users/awinn/Documents/sql12/plugins/example/target/classes to: >> >> /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java >> org.codehaus.plexus.archiver.ArchiverException: The source must not be a >> directory. >> at >> >> org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:269) >> at >> >> org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) >> at >> >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) >> at >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> ... 19 more >> Caused by: org.codehaus.plexus.archiver.ArchiverException: The source must >> not be a directory. >> at >> >> org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) >> at >> >> org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) >> at >> >> org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) >> ... 22 more >> >> ------------------------------------------------------------------------------ >> Colocation vs. Managed Hosting >> A question and answer guide to determining the best fit >> for your organization - today and in the future. >> http://p.sf.net/sfu/internap-sfd2d >> _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > > |
|
From: Robert M. <rob...@gm...> - 2011-03-11 22:26:24
|
Try : mvn -e clean install Rob On Fri, Mar 11, 2011 at 1:52 PM, Adam Winn <win...@gm...> wrote: > At the root of the sql12 dir, I ran 'mvn -e clean compile' and the SQuirreL > Plugin Archetype fails to compile: > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building SQuirreL Plugin Archetype 3.3.0-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ > squirrelsql-plugin-archetype --- > [INFO] > [INFO] --- maven-dependency-plugin:2.1:unpack-dependencies > (copy-example-project-java) @ squirrelsql-plugin-archetype --- > [INFO] Unpacking > /Users/awinn/Documents/sql12/plugins/example/target/classes > to > > > /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java > with includes **\/*.java and excludes:**\/*Test.java > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > > org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) > at > > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) > at > > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > at > > org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] SQuirreL Root POM ................................. SUCCESS [0.092s] > [INFO] Framework Library ................................. SUCCESS [4.168s] > [INFO] SQuirreL Main Application Jar ..................... SUCCESS [3.255s] > [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS [0.001s] > [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS [0.008s] > [INFO] Example Plugin .................................... SUCCESS [0.326s] > [INFO] SQuirreL Plugin Archetype ......................... FAILURE [0.432s] > [INFO] Codecompletion Plugin ............................. SKIPPED > [INFO] Dataimport Plugin ................................. SKIPPED > [INFO] Db2 Plugin ........................................ SKIPPED > [INFO] Dbcopy Plugin ..................................... SKIPPED > [INFO] Dbdiff Plugin ..................................... SKIPPED > [INFO] Derby Plugin ...................................... SKIPPED > [INFO] Editextras Plugin ................................. SKIPPED > [INFO] Exportconfig Plugin ............................... SKIPPED > [INFO] Favs Plugin ....................................... SKIPPED > [INFO] Firebird Plugin ................................... SKIPPED > [INFO] Firebirdmanager Plugin ............................ SKIPPED > [INFO] Graph Plugin ...................................... SKIPPED > [INFO] Greenplum Plugin .................................. SKIPPED > [INFO] H2 Plugin ......................................... SKIPPED > [INFO] Hibernate Plugin .................................. SKIPPED > [INFO] I18n Plugin ....................................... SKIPPED > [INFO] Informix Plugin ................................... SKIPPED > [INFO] Look and Feel Plugin .............................. SKIPPED > [INFO] Macosx Plugin ..................................... SKIPPED > [INFO] Mssql Plugin ...................................... SKIPPED > [INFO] Mysql Plugin ...................................... SKIPPED > [INFO] Netezza Plugin .................................... SKIPPED > [INFO] Oracle Plugin ..................................... SKIPPED > [INFO] Postgres Plugin ................................... SKIPPED > [INFO] Refactoring Plugin ................................ SKIPPED > [INFO] Sessionscript Plugin .............................. SKIPPED > [INFO] Smarttools Plugin ................................. SKIPPED > [INFO] Sqlbookmark Plugin ................................ SKIPPED > [INFO] Sqlparam Plugin ................................... SKIPPED > [INFO] Sqlreplace Plugin ................................. SKIPPED > [INFO] Sqlscript Plugin .................................. SKIPPED > [INFO] Sqlval Plugin ..................................... SKIPPED > [INFO] Sybase Plugin ..................................... SKIPPED > [INFO] Syntax Plugin ..................................... SKIPPED > [INFO] Userscript Plugin ................................. SKIPPED > [INFO] Plugin Modules POM file ........................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 8.882s > [INFO] Finished at: Fri Mar 11 11:50:11 MST 2011 > [INFO] Final Memory: 20M/105M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies > (copy-example-project-java) on project squirrelsql-plugin-archetype: Error > unpacking file: /Users/awinn/Documents/sql12/plugins/example/target/classes > to: > > /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java > [ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must not > be a directory. > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal > org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies > (copy-example-project-java) on project squirrelsql-plugin-archetype: Error > unpacking file: /Users/awinn/Documents/sql12/plugins/example/target/classes > to: > > /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error unpacking > file: /Users/awinn/Documents/sql12/plugins/example/target/classes to: > > /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java > org.codehaus.plexus.archiver.ArchiverException: The source must not be a > directory. > at > > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:269) > at > > org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) > at > > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) > at > > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.codehaus.plexus.archiver.ArchiverException: The source must > not be a directory. > at > > org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) > at > > org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) > at > > org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) > ... 22 more > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Adam W. <win...@gm...> - 2011-03-11 18:58:22
|
I was looking at the Netezza External Table plugin and trying to mimic it for another DB type. I can display the external tables just fine by using objTree.addExpander(), but I can't get any details to appear when I click on the external tables or expand the arrow beside them. I'm also using objTree.addDetailTab(). In my details java file, it enters the method ExternalTableDetailsTab() but it never goes inside createStatement(). Does anyone know why this is? I read in the docs that when you extend the base tab class, it will run the SQL you have in the createStatement() method, but that is not happening for me. It isn't even entering that method for me. I'm assuming this worked fine in the Netezza External Table plugin and I'm essentially doing what it's doing but it never enters createStatement() and I don't get any details of the external table. The docs say: A source tab can then be implemented by extending the classes BaseSourceTab<https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourceTab.java> and BaseSourcePanel<https://sourceforge.net/apps/trac/squirrel-sql/browser/trunk/sql12/app/src/main/java/net/sourceforge/squirrel_sql/client/session/mainpanel/objecttree/tabs/BaseSourcePanel.java>. In particular, BaseSourceTab has an abstract method called createStatement which is implemented to return a PreparedStatement by using BaseObjectTab.getSession() and BaseObjectTab.getDatabaseObjectInfo(). The method getDatabaseObjectInfo returns the node that is selected from which can be found the name, schema and catalog of the object to write an SQL statement that queries the data dictionary for the source for that object. The BaseSourcePanel load method is then called with the ResultSet obtained by executing the PreparedStatement. Does anyone know why it's not entering the createStatement() method and therefore not showing me the details of the external table? Thanks, Adam |
|
From: Adam W. <win...@gm...> - 2011-03-11 18:52:45
|
At the root of the sql12 dir, I ran 'mvn -e clean compile' and the SQuirreL Plugin Archetype fails to compile: [INFO] ------------------------------------------------------------------------ [INFO] Building SQuirreL Plugin Archetype 3.3.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ squirrelsql-plugin-archetype --- [INFO] [INFO] --- maven-dependency-plugin:2.1:unpack-dependencies (copy-example-project-java) @ squirrelsql-plugin-archetype --- [INFO] Unpacking /Users/awinn/Documents/sql12/plugins/example/target/classes to /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java with includes **\/*.java and excludes:**\/*Test.java org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory. at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) at org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] SQuirreL Root POM ................................. SUCCESS [0.092s] [INFO] Framework Library ................................. SUCCESS [4.168s] [INFO] SQuirreL Main Application Jar ..................... SUCCESS [3.255s] [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS [0.001s] [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS [0.008s] [INFO] Example Plugin .................................... SUCCESS [0.326s] [INFO] SQuirreL Plugin Archetype ......................... FAILURE [0.432s] [INFO] Codecompletion Plugin ............................. SKIPPED [INFO] Dataimport Plugin ................................. SKIPPED [INFO] Db2 Plugin ........................................ SKIPPED [INFO] Dbcopy Plugin ..................................... SKIPPED [INFO] Dbdiff Plugin ..................................... SKIPPED [INFO] Derby Plugin ...................................... SKIPPED [INFO] Editextras Plugin ................................. SKIPPED [INFO] Exportconfig Plugin ............................... SKIPPED [INFO] Favs Plugin ....................................... SKIPPED [INFO] Firebird Plugin ................................... SKIPPED [INFO] Firebirdmanager Plugin ............................ SKIPPED [INFO] Graph Plugin ...................................... SKIPPED [INFO] Greenplum Plugin .................................. SKIPPED [INFO] H2 Plugin ......................................... SKIPPED [INFO] Hibernate Plugin .................................. SKIPPED [INFO] I18n Plugin ....................................... SKIPPED [INFO] Informix Plugin ................................... SKIPPED [INFO] Look and Feel Plugin .............................. SKIPPED [INFO] Macosx Plugin ..................................... SKIPPED [INFO] Mssql Plugin ...................................... SKIPPED [INFO] Mysql Plugin ...................................... SKIPPED [INFO] Netezza Plugin .................................... SKIPPED [INFO] Oracle Plugin ..................................... SKIPPED [INFO] Postgres Plugin ................................... SKIPPED [INFO] Refactoring Plugin ................................ SKIPPED [INFO] Sessionscript Plugin .............................. SKIPPED [INFO] Smarttools Plugin ................................. SKIPPED [INFO] Sqlbookmark Plugin ................................ SKIPPED [INFO] Sqlparam Plugin ................................... SKIPPED [INFO] Sqlreplace Plugin ................................. SKIPPED [INFO] Sqlscript Plugin .................................. SKIPPED [INFO] Sqlval Plugin ..................................... SKIPPED [INFO] Sybase Plugin ..................................... SKIPPED [INFO] Syntax Plugin ..................................... SKIPPED [INFO] Userscript Plugin ................................. SKIPPED [INFO] Plugin Modules POM file ........................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 8.882s [INFO] Finished at: Fri Mar 11 11:50:11 MST 2011 [INFO] Final Memory: 20M/105M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (copy-example-project-java) on project squirrelsql-plugin-archetype: Error unpacking file: /Users/awinn/Documents/sql12/plugins/example/target/classes to: /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java [ERROR] org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory. [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (copy-example-project-java) on project squirrelsql-plugin-archetype: Error unpacking file: /Users/awinn/Documents/sql12/plugins/example/target/classes to: /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error unpacking file: /Users/awinn/Documents/sql12/plugins/example/target/classes to: /Users/awinn/Documents/sql12/plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src/main/java org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory. at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:269) at org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.codehaus.plexus.archiver.ArchiverException: The source must not be a directory. at org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:174) at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:107) at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:260) ... 22 more |
|
From: Robert M. <rob...@gm...> - 2011-03-08 04:11:13
|
All, In case anyone is trying to launch from a local build on Mac OS X, I have the following observations after doing this myself: 1. I did not intend to, but I recently broke maven 2.2.1 builds, so for now go get maven 3.0.x (in general this is a good idea anyway) 2. You should uncomment the "installers" profile in ~/.m2/settings.xml 3. There are failing tests in the fw/ project that I need to fix (use 'mvn clean install -DskipTests' for now) 4. You should launch using the squirrel-sql.sh file the macosx installer target dir. For example: cd sql12/installer/squirrelsql-macosx-installer/target/squirrel-install-from-maven ./squirrel-sql.sh 5. You can also launch SQuirreL with a single loaded plugin by going into that plugin folder and running the following command: mvn clean install -P launch However, the plugin launch profile doesn't yield a SQuirreL that is integrated into Mac OS X in terms of preferences in the top menu bar and such. The macosx installer does, so running squirrel-sql.sh from the squirrel-install-from-maven is the nicest way to bring it up on Mac OS X. Rob |
|
From: Adam W. <win...@gm...> - 2011-03-07 22:24:21
|
Thanks. Please let me know what you find out. On Mon, Mar 7, 2011 at 12:25 PM, Robert Manning <rob...@gm...>wrote: > Hmmm.... I'll have to take a closer look. It could be a problem with the > code I just added this weekend, though it built fine on the build server and > in my local environment. > > Rob > > On Mon, Mar 7, 2011 at 1:54 PM, Adam Winn <win...@gm...> wrote: > >> It compiles everything fine up until the generic installer and then it >> dies the same way as before. >> >> On Mon, Mar 7, 2011 at 11:35 AM, Robert Manning < >> rob...@gm...> wrote: >> >>> >>> Try going up a level (so that you are in the installer/ directory, and >>> 'mvn clean install' from there) >>> >>> Rob >>> >>> On Mon, Mar 7, 2011 at 1:10 PM, Adam Winn <win...@gm...> wrote: >>> >>>> I cd'd into the sql12/installer/squirrelsql-other-installer/ dir and ran >>>> 'mvn clean install' and got this: >>>> >>>> ..... >>>> [[INFO] Copying autocomplete-r239.jar to >>>> /Users/awinn/Desktop/sql12/installer/squirrelsql-other-installer/target/lib/autocomplete.jar >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] FATAL ERROR >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] null >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Trace >>>> java.lang.NullPointerException >>>> at >>>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.getResolvedPomArtifact(CopyDependenciesMojo.java:229) >>>> at >>>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.copyPoms(CopyDependenciesMojo.java:212) >>>> at >>>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.execute(CopyDependenciesMojo.java:122) >>>> at >>>> net.sf.squirrel_sql.CopySquirrelDependenciesMojo.execute(CopySquirrelDependenciesMojo.java:143) >>>> at >>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >>>> at >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >>>> at >>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>> at java.lang.reflect.Method.invoke(Method.java:597) >>>> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>>> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >>>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> >>>> >>>> Any ideas? >>>> >>>> On Mon, Mar 7, 2011 at 10:36 AM, Robert Manning < >>>> rob...@gm...> wrote: >>>> >>>>> Right, you cannot simply run the compiled SQuirreL from there. There >>>>> is an installer directory : sql12/installer/squirrelsql-other-installer/, >>>>> where you can go to build and extract the installer again using >>>>> >>>>> mvn clean install >>>>> >>>>> Then, cd into the target folder and you will see folders that contain >>>>> timestamps and a suffix of "base", "standard and "optional". They each will >>>>> contain a launch script that when inoked will launch the SQuirreL that you >>>>> have built locally - the only difference is the set of plugins that are >>>>> installed (for example, optional contains all of the plugins). >>>>> >>>>> If you always want the installer to be created and extracted, in the >>>>> ~/.m2/settings.xml uncomment the line near the bottom that looks like this: >>>>> >>>>> <!-- <activeProfile>installer</activeProfile>--> >>>>> If you just want to launch SQuirreL with a single plugin loaded, cd >>>>> into the plugins/<plugin> that you are interested in, and execute the >>>>> following command: >>>>> >>>>> mvn clean install -P launch >>>>> >>>>> Rob >>>>> >>>>> On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: >>>>> >>>>>> I did this: >>>>>> >>>>>> 1) svn co >>>>>> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 >>>>>> >>>>>> 2) cd sql12/ >>>>>> >>>>>> 3) mvn clean install >>>>>> >>>>>> 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar >>>>>> >>>>>> and I got this: >>>>>> >>>>>> Exception in thread "main" java.lang.NoClassDefFoundError: >>>>>> net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory >>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>> net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory >>>>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>>>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>>>>> >>>>>> Any ideas? Thanks! >>>>>> >>>>>> On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning < >>>>>> rob...@gm...> wrote: >>>>>> >>>>>>> To get your development environment setup see the following: >>>>>>> >>>>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >>>>>>> SQuirreL is built with Maven, and follows the conventions that Maven >>>>>>> specifies, making it easy for new developers who are familiar with Maven to >>>>>>> get started. If you are new to Maven, you should read the following guide: >>>>>>> >>>>>>> http://maven.apache.org/run-maven/index.html#Quick_Start >>>>>>> >>>>>>> Essentially, at the top-most point in the sql12/ tree there is a >>>>>>> pom.xml file that allows you to build the entire tree with the following >>>>>>> command: >>>>>>> >>>>>>> mvn clean install >>>>>>> >>>>>>> Rob >>>>>>> >>>>>>> >>>>>>> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...>wrote: >>>>>>> >>>>>>>> Does anyone know where current instructions are to compile >>>>>>>> squirrelsql? >>>>>>>> >>>>>>>> Are the following links the correct way to compile the app? Thanks. >>>>>>>> >>>>>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>>>>>>> >>>>>>>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> What You Don't Know About Data Connectivity CAN Hurt You >>>>>>>> This paper provides an overview of data connectivity, details >>>>>>>> its effect on application quality, and explores various alternative >>>>>>>> solutions. http://p.sf.net/sfu/progress-d2d >>>>>>>> _______________________________________________ >>>>>>>> Squirrel-sql-develop mailing list >>>>>>>> Squ...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > |
|
From: Robert M. <rob...@gm...> - 2011-03-07 19:26:02
|
Hmmm.... I'll have to take a closer look. It could be a problem with the code I just added this weekend, though it built fine on the build server and in my local environment. Rob On Mon, Mar 7, 2011 at 1:54 PM, Adam Winn <win...@gm...> wrote: > It compiles everything fine up until the generic installer and then it dies > the same way as before. > > On Mon, Mar 7, 2011 at 11:35 AM, Robert Manning < > rob...@gm...> wrote: > >> >> Try going up a level (so that you are in the installer/ directory, and >> 'mvn clean install' from there) >> >> Rob >> >> On Mon, Mar 7, 2011 at 1:10 PM, Adam Winn <win...@gm...> wrote: >> >>> I cd'd into the sql12/installer/squirrelsql-other-installer/ dir and ran >>> 'mvn clean install' and got this: >>> >>> ..... >>> [[INFO] Copying autocomplete-r239.jar to >>> /Users/awinn/Desktop/sql12/installer/squirrelsql-other-installer/target/lib/autocomplete.jar >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] FATAL ERROR >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] null >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Trace >>> java.lang.NullPointerException >>> at >>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.getResolvedPomArtifact(CopyDependenciesMojo.java:229) >>> at >>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.copyPoms(CopyDependenciesMojo.java:212) >>> at >>> org.apache.maven.plugin.dependency.CopyDependenciesMojo.execute(CopyDependenciesMojo.java:122) >>> at >>> net.sf.squirrel_sql.CopySquirrelDependenciesMojo.execute(CopySquirrelDependenciesMojo.java:143) >>> at >>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >>> at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >>> at >>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:597) >>> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> >>> Any ideas? >>> >>> On Mon, Mar 7, 2011 at 10:36 AM, Robert Manning < >>> rob...@gm...> wrote: >>> >>>> Right, you cannot simply run the compiled SQuirreL from there. There is >>>> an installer directory : sql12/installer/squirrelsql-other-installer/, where >>>> you can go to build and extract the installer again using >>>> >>>> mvn clean install >>>> >>>> Then, cd into the target folder and you will see folders that contain >>>> timestamps and a suffix of "base", "standard and "optional". They each will >>>> contain a launch script that when inoked will launch the SQuirreL that you >>>> have built locally - the only difference is the set of plugins that are >>>> installed (for example, optional contains all of the plugins). >>>> >>>> If you always want the installer to be created and extracted, in the >>>> ~/.m2/settings.xml uncomment the line near the bottom that looks like this: >>>> >>>> <!-- <activeProfile>installer</activeProfile>--> >>>> If you just want to launch SQuirreL with a single plugin loaded, cd into >>>> the plugins/<plugin> that you are interested in, and execute the following >>>> command: >>>> >>>> mvn clean install -P launch >>>> >>>> Rob >>>> >>>> On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: >>>> >>>>> I did this: >>>>> >>>>> 1) svn co >>>>> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 >>>>> >>>>> 2) cd sql12/ >>>>> >>>>> 3) mvn clean install >>>>> >>>>> 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar >>>>> >>>>> and I got this: >>>>> >>>>> Exception in thread "main" java.lang.NoClassDefFoundError: >>>>> net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory >>>>> Caused by: java.lang.ClassNotFoundException: >>>>> net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory >>>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>>>> at java.security.AccessController.doPrivileged(Native Method) >>>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>>>> >>>>> Any ideas? Thanks! >>>>> >>>>> On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning < >>>>> rob...@gm...> wrote: >>>>> >>>>>> To get your development environment setup see the following: >>>>>> >>>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >>>>>> SQuirreL is built with Maven, and follows the conventions that Maven >>>>>> specifies, making it easy for new developers who are familiar with Maven to >>>>>> get started. If you are new to Maven, you should read the following guide: >>>>>> >>>>>> http://maven.apache.org/run-maven/index.html#Quick_Start >>>>>> >>>>>> Essentially, at the top-most point in the sql12/ tree there is a >>>>>> pom.xml file that allows you to build the entire tree with the following >>>>>> command: >>>>>> >>>>>> mvn clean install >>>>>> >>>>>> Rob >>>>>> >>>>>> >>>>>> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: >>>>>> >>>>>>> Does anyone know where current instructions are to compile >>>>>>> squirrelsql? >>>>>>> >>>>>>> Are the following links the correct way to compile the app? Thanks. >>>>>>> >>>>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>>>>>> >>>>>>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> What You Don't Know About Data Connectivity CAN Hurt You >>>>>>> This paper provides an overview of data connectivity, details >>>>>>> its effect on application quality, and explores various alternative >>>>>>> solutions. http://p.sf.net/sfu/progress-d2d >>>>>>> _______________________________________________ >>>>>>> Squirrel-sql-develop mailing list >>>>>>> Squ...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > |
|
From: Adam W. <win...@gm...> - 2011-03-07 18:54:32
|
It compiles everything fine up until the generic installer and then it dies the same way as before. On Mon, Mar 7, 2011 at 11:35 AM, Robert Manning <rob...@gm...>wrote: > > Try going up a level (so that you are in the installer/ directory, and 'mvn > clean install' from there) > > Rob > > On Mon, Mar 7, 2011 at 1:10 PM, Adam Winn <win...@gm...> wrote: > >> I cd'd into the sql12/installer/squirrelsql-other-installer/ dir and ran >> 'mvn clean install' and got this: >> >> ..... >> [[INFO] Copying autocomplete-r239.jar to >> /Users/awinn/Desktop/sql12/installer/squirrelsql-other-installer/target/lib/autocomplete.jar >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] FATAL ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] null >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Trace >> java.lang.NullPointerException >> at >> org.apache.maven.plugin.dependency.CopyDependenciesMojo.getResolvedPomArtifact(CopyDependenciesMojo.java:229) >> at >> org.apache.maven.plugin.dependency.CopyDependenciesMojo.copyPoms(CopyDependenciesMojo.java:212) >> at >> org.apache.maven.plugin.dependency.CopyDependenciesMojo.execute(CopyDependenciesMojo.java:122) >> at >> net.sf.squirrel_sql.CopySquirrelDependenciesMojo.execute(CopySquirrelDependenciesMojo.java:143) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375) >> [INFO] >> ------------------------------------------------------------------------ >> >> >> Any ideas? >> >> On Mon, Mar 7, 2011 at 10:36 AM, Robert Manning < >> rob...@gm...> wrote: >> >>> Right, you cannot simply run the compiled SQuirreL from there. There is >>> an installer directory : sql12/installer/squirrelsql-other-installer/, where >>> you can go to build and extract the installer again using >>> >>> mvn clean install >>> >>> Then, cd into the target folder and you will see folders that contain >>> timestamps and a suffix of "base", "standard and "optional". They each will >>> contain a launch script that when inoked will launch the SQuirreL that you >>> have built locally - the only difference is the set of plugins that are >>> installed (for example, optional contains all of the plugins). >>> >>> If you always want the installer to be created and extracted, in the >>> ~/.m2/settings.xml uncomment the line near the bottom that looks like this: >>> >>> <!-- <activeProfile>installer</activeProfile>--> >>> If you just want to launch SQuirreL with a single plugin loaded, cd into >>> the plugins/<plugin> that you are interested in, and execute the following >>> command: >>> >>> mvn clean install -P launch >>> >>> Rob >>> >>> On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: >>> >>>> I did this: >>>> >>>> 1) svn co >>>> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 >>>> >>>> 2) cd sql12/ >>>> >>>> 3) mvn clean install >>>> >>>> 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar >>>> >>>> and I got this: >>>> >>>> Exception in thread "main" java.lang.NoClassDefFoundError: >>>> net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory >>>> Caused by: java.lang.ClassNotFoundException: >>>> net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory >>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>>> at java.security.AccessController.doPrivileged(Native Method) >>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>>> >>>> Any ideas? Thanks! >>>> >>>> On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning < >>>> rob...@gm...> wrote: >>>> >>>>> To get your development environment setup see the following: >>>>> >>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >>>>> SQuirreL is built with Maven, and follows the conventions that Maven >>>>> specifies, making it easy for new developers who are familiar with Maven to >>>>> get started. If you are new to Maven, you should read the following guide: >>>>> >>>>> http://maven.apache.org/run-maven/index.html#Quick_Start >>>>> >>>>> Essentially, at the top-most point in the sql12/ tree there is a >>>>> pom.xml file that allows you to build the entire tree with the following >>>>> command: >>>>> >>>>> mvn clean install >>>>> >>>>> Rob >>>>> >>>>> >>>>> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: >>>>> >>>>>> Does anyone know where current instructions are to compile >>>>>> squirrelsql? >>>>>> >>>>>> Are the following links the correct way to compile the app? Thanks. >>>>>> >>>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>>>>> >>>>>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> What You Don't Know About Data Connectivity CAN Hurt You >>>>>> This paper provides an overview of data connectivity, details >>>>>> its effect on application quality, and explores various alternative >>>>>> solutions. http://p.sf.net/sfu/progress-d2d >>>>>> _______________________________________________ >>>>>> Squirrel-sql-develop mailing list >>>>>> Squ...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>>>>> >>>>> >>>>> >>>> >>> >> > |
|
From: Robert M. <rob...@gm...> - 2011-03-07 18:36:07
|
Try going up a level (so that you are in the installer/ directory, and 'mvn clean install' from there) Rob On Mon, Mar 7, 2011 at 1:10 PM, Adam Winn <win...@gm...> wrote: > I cd'd into the sql12/installer/squirrelsql-other-installer/ dir and ran > 'mvn clean install' and got this: > > ..... > [[INFO] Copying autocomplete-r239.jar to > /Users/awinn/Desktop/sql12/installer/squirrelsql-other-installer/target/lib/autocomplete.jar > [INFO] > ------------------------------------------------------------------------ > [ERROR] FATAL ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] null > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugin.dependency.CopyDependenciesMojo.getResolvedPomArtifact(CopyDependenciesMojo.java:229) > at > org.apache.maven.plugin.dependency.CopyDependenciesMojo.copyPoms(CopyDependenciesMojo.java:212) > at > org.apache.maven.plugin.dependency.CopyDependenciesMojo.execute(CopyDependenciesMojo.java:122) > at > net.sf.squirrel_sql.CopySquirrelDependenciesMojo.execute(CopySquirrelDependenciesMojo.java:143) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > ------------------------------------------------------------------------ > > > Any ideas? > > On Mon, Mar 7, 2011 at 10:36 AM, Robert Manning < > rob...@gm...> wrote: > >> Right, you cannot simply run the compiled SQuirreL from there. There is >> an installer directory : sql12/installer/squirrelsql-other-installer/, where >> you can go to build and extract the installer again using >> >> mvn clean install >> >> Then, cd into the target folder and you will see folders that contain >> timestamps and a suffix of "base", "standard and "optional". They each will >> contain a launch script that when inoked will launch the SQuirreL that you >> have built locally - the only difference is the set of plugins that are >> installed (for example, optional contains all of the plugins). >> >> If you always want the installer to be created and extracted, in the >> ~/.m2/settings.xml uncomment the line near the bottom that looks like this: >> >> <!-- <activeProfile>installer</activeProfile>--> >> If you just want to launch SQuirreL with a single plugin loaded, cd into >> the plugins/<plugin> that you are interested in, and execute the following >> command: >> >> mvn clean install -P launch >> >> Rob >> >> On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: >> >>> I did this: >>> >>> 1) svn co >>> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 >>> >>> 2) cd sql12/ >>> >>> 3) mvn clean install >>> >>> 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar >>> >>> and I got this: >>> >>> Exception in thread "main" java.lang.NoClassDefFoundError: >>> net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory >>> Caused by: java.lang.ClassNotFoundException: >>> net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory >>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >>> >>> Any ideas? Thanks! >>> >>> On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning < >>> rob...@gm...> wrote: >>> >>>> To get your development environment setup see the following: >>>> >>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >>>> SQuirreL is built with Maven, and follows the conventions that Maven >>>> specifies, making it easy for new developers who are familiar with Maven to >>>> get started. If you are new to Maven, you should read the following guide: >>>> >>>> http://maven.apache.org/run-maven/index.html#Quick_Start >>>> >>>> Essentially, at the top-most point in the sql12/ tree there is a pom.xml >>>> file that allows you to build the entire tree with the following command: >>>> >>>> mvn clean install >>>> >>>> Rob >>>> >>>> >>>> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: >>>> >>>>> Does anyone know where current instructions are to compile squirrelsql? >>>>> >>>>> Are the following links the correct way to compile the app? Thanks. >>>>> >>>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>>>> >>>>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> What You Don't Know About Data Connectivity CAN Hurt You >>>>> This paper provides an overview of data connectivity, details >>>>> its effect on application quality, and explores various alternative >>>>> solutions. http://p.sf.net/sfu/progress-d2d >>>>> _______________________________________________ >>>>> Squirrel-sql-develop mailing list >>>>> Squ...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>>>> >>>> >>>> >>> >> > |
|
From: Adam W. <win...@gm...> - 2011-03-07 18:10:36
|
I cd'd into the sql12/installer/squirrelsql-other-installer/ dir and ran 'mvn clean install' and got this: ..... [[INFO] Copying autocomplete-r239.jar to /Users/awinn/Desktop/sql12/installer/squirrelsql-other-installer/target/lib/autocomplete.jar [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] null [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.dependency.CopyDependenciesMojo.getResolvedPomArtifact(CopyDependenciesMojo.java:229) at org.apache.maven.plugin.dependency.CopyDependenciesMojo.copyPoms(CopyDependenciesMojo.java:212) at org.apache.maven.plugin.dependency.CopyDependenciesMojo.execute(CopyDependenciesMojo.java:122) at net.sf.squirrel_sql.CopySquirrelDependenciesMojo.execute(CopySquirrelDependenciesMojo.java:143) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] ------------------------------------------------------------------------ Any ideas? On Mon, Mar 7, 2011 at 10:36 AM, Robert Manning <rob...@gm...>wrote: > Right, you cannot simply run the compiled SQuirreL from there. There is an > installer directory : sql12/installer/squirrelsql-other-installer/, where > you can go to build and extract the installer again using > > mvn clean install > > Then, cd into the target folder and you will see folders that contain > timestamps and a suffix of "base", "standard and "optional". They each will > contain a launch script that when inoked will launch the SQuirreL that you > have built locally - the only difference is the set of plugins that are > installed (for example, optional contains all of the plugins). > > If you always want the installer to be created and extracted, in the > ~/.m2/settings.xml uncomment the line near the bottom that looks like this: > > <!-- <activeProfile>installer</activeProfile>--> > If you just want to launch SQuirreL with a single plugin loaded, cd into > the plugins/<plugin> that you are interested in, and execute the following > command: > > mvn clean install -P launch > > Rob > > On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: > >> I did this: >> >> 1) svn co >> https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 >> >> 2) cd sql12/ >> >> 3) mvn clean install >> >> 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar >> >> and I got this: >> >> Exception in thread "main" java.lang.NoClassDefFoundError: >> net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory >> Caused by: java.lang.ClassNotFoundException: >> net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory >> at java.net.URLClassLoader$1.run(URLClassLoader.java:202) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:190) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> >> Any ideas? Thanks! >> >> On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning < >> rob...@gm...> wrote: >> >>> To get your development environment setup see the following: >>> >>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >>> SQuirreL is built with Maven, and follows the conventions that Maven >>> specifies, making it easy for new developers who are familiar with Maven to >>> get started. If you are new to Maven, you should read the following guide: >>> >>> http://maven.apache.org/run-maven/index.html#Quick_Start >>> >>> Essentially, at the top-most point in the sql12/ tree there is a pom.xml >>> file that allows you to build the entire tree with the following command: >>> >>> mvn clean install >>> >>> Rob >>> >>> >>> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: >>> >>>> Does anyone know where current instructions are to compile squirrelsql? >>>> >>>> Are the following links the correct way to compile the app? Thanks. >>>> >>>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>>> >>>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>>> >>>> ------------------------------------------------------------------------------ >>>> What You Don't Know About Data Connectivity CAN Hurt You >>>> This paper provides an overview of data connectivity, details >>>> its effect on application quality, and explores various alternative >>>> solutions. http://p.sf.net/sfu/progress-d2d >>>> _______________________________________________ >>>> Squirrel-sql-develop mailing list >>>> Squ...@li... >>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>>> >>> >>> >> > |
|
From: Robert M. <rob...@gm...> - 2011-03-07 17:36:20
|
Right, you cannot simply run the compiled SQuirreL from there. There is an installer directory : sql12/installer/squirrelsql-other-installer/, where you can go to build and extract the installer again using mvn clean install Then, cd into the target folder and you will see folders that contain timestamps and a suffix of "base", "standard and "optional". They each will contain a launch script that when inoked will launch the SQuirreL that you have built locally - the only difference is the set of plugins that are installed (for example, optional contains all of the plugins). If you always want the installer to be created and extracted, in the ~/.m2/settings.xml uncomment the line near the bottom that looks like this: <!-- <activeProfile>installer</activeProfile>--> If you just want to launch SQuirreL with a single plugin loaded, cd into the plugins/<plugin> that you are interested in, and execute the following command: mvn clean install -P launch Rob On Mon, Mar 7, 2011 at 10:36 AM, Adam Winn <win...@gm...> wrote: > I did this: > > 1) svn co > https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 > > 2) cd sql12/ > > 3) mvn clean install > > 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar > > and I got this: > > Exception in thread "main" java.lang.NoClassDefFoundError: > net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory > Caused by: java.lang.ClassNotFoundException: > net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:307) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:248) > > Any ideas? Thanks! > > On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning <rob...@gm... > > wrote: > >> To get your development environment setup see the following: >> >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide >> SQuirreL is built with Maven, and follows the conventions that Maven >> specifies, making it easy for new developers who are familiar with Maven to >> get started. If you are new to Maven, you should read the following guide: >> >> http://maven.apache.org/run-maven/index.html#Quick_Start >> >> Essentially, at the top-most point in the sql12/ tree there is a pom.xml >> file that allows you to build the entire tree with the following command: >> >> mvn clean install >> >> Rob >> >> >> On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: >> >>> Does anyone know where current instructions are to compile squirrelsql? >>> >>> Are the following links the correct way to compile the app? Thanks. >>> >>> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >>> >>> http://squirrel-sql.sourceforge.net/buildandrelease.html >>> >>> ------------------------------------------------------------------------------ >>> What You Don't Know About Data Connectivity CAN Hurt You >>> This paper provides an overview of data connectivity, details >>> its effect on application quality, and explores various alternative >>> solutions. http://p.sf.net/sfu/progress-d2d >>> _______________________________________________ >>> Squirrel-sql-develop mailing list >>> Squ...@li... >>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>> >> >> > |
|
From: Adam W. <win...@gm...> - 2011-03-07 15:36:08
|
I did this: 1) svn co https://squirrel-sql.svn.sourceforge.net/svnroot/squirrel-sql/trunk/sql12sql12 2) cd sql12/ 3) mvn clean install 4) java -jar ./app/target/squirrel-sql-3.3.0-SNAPSHOT.jar and I got this: Exception in thread "main" java.lang.NoClassDefFoundError: net/sourceforge/squirrel_sql/fw/util/log/ILoggerFactory Caused by: java.lang.ClassNotFoundException: net.sourceforge.squirrel_sql.fw.util.log.ILoggerFactory at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Any ideas? Thanks! On Mon, Mar 7, 2011 at 8:16 AM, Robert Manning <rob...@gm...>wrote: > To get your development environment setup see the following: > > http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide > SQuirreL is built with Maven, and follows the conventions that Maven > specifies, making it easy for new developers who are familiar with Maven to > get started. If you are new to Maven, you should read the following guide: > > http://maven.apache.org/run-maven/index.html#Quick_Start > > Essentially, at the top-most point in the sql12/ tree there is a pom.xml > file that allows you to build the entire tree with the following command: > > mvn clean install > > Rob > > > On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: > >> Does anyone know where current instructions are to compile squirrelsql? >> >> Are the following links the correct way to compile the app? Thanks. >> >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases >> >> http://squirrel-sql.sourceforge.net/buildandrelease.html >> >> ------------------------------------------------------------------------------ >> What You Don't Know About Data Connectivity CAN Hurt You >> This paper provides an overview of data connectivity, details >> its effect on application quality, and explores various alternative >> solutions. http://p.sf.net/sfu/progress-d2d >> _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > > |
|
From: Robert M. <rob...@gm...> - 2011-03-07 15:16:53
|
To get your development environment setup see the following: http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide SQuirreL is built with Maven, and follows the conventions that Maven specifies, making it easy for new developers who are familiar with Maven to get started. If you are new to Maven, you should read the following guide: http://maven.apache.org/run-maven/index.html#Quick_Start Essentially, at the top-most point in the sql12/ tree there is a pom.xml file that allows you to build the entire tree with the following command: mvn clean install Rob On Mon, Mar 7, 2011 at 8:28 AM, Adam Winn <win...@gm...> wrote: > Does anyone know where current instructions are to compile squirrelsql? > > Are the following links the correct way to compile the app? Thanks. > > http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases > > http://squirrel-sql.sourceforge.net/buildandrelease.html > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Adam W. <win...@gm...> - 2011-03-07 13:28:17
|
Does anyone know where current instructions are to compile squirrelsql? Are the following links the correct way to compile the app? Thanks. http://sourceforge.net/apps/trac/squirrel-sql/wiki/SQuirreLReleases http://squirrel-sql.sourceforge.net/buildandrelease.html |
|
From: Robert M. <rob...@gm...> - 2011-02-26 20:28:43
|
For #2 - nevermind, you are absolutely correct; I mistook setPreparedStatementValue for setting a bind var in the where clause. As of yet there is no IoC container being used in the main application. For the update application, since it must run outside of SQuirreL, and because it was brand new I took liberty to use Spring there. For now, an instance variable initialized in the declaration is fine. Should we decide to move to IoC in the future, any statics we can avoid will help. Rob On Sat, Feb 26, 2011 at 2:05 PM, Stefan Willinger <ste...@ao...>wrote: > Hi Rob, > > > 1. Can we change the name of NopWhereClausePart to EmptyWhereClausePart ? > That seems a bit more readable to me. > > Of course. The first programming language I learned was Step 5 (the > programming language for Simatic S5 an Programable Logic Controller within > automation systems. Within the most build in functions you needed the NOP > operator for the NoOperation - Seems that the old times are very present in > my head :-) > I will update the code and JavaDoc. > > 2. Would it be possible to use an additional ParameterWhereClausePart to > make the call to CellComponentFactory.setPreparedStatementValue unnecessary? > > Hm, with the call of CellComponentFactory.setPreparedStatementValue we set > the data of the changed data field. In the strict sense, this is not an part > of the where clause. If we add an additional ParameterWhereClausePart for > the changed data - that would be like cheating. > If we want do this, we could: > > - use an placeholder that is on the right (first) position which is > responsible only for setting the parameter and not for creating the set=? > part. > - or enhance the functionality, that constructing the update statement > is part of if (and maybe - insert/delete/select) > - or another suggestion? > > 3. Would it be too much trouble to give WhereClausePartUtil an interface. > > Of course not. I think I didn't see an Dependency Injection Container > within Squirrel - So would it be appropriate to create an instance variable > initialized with an default, that could be overwritten by the setter at each > class where is is used? > > > I will prepare the first and the third part of your suggestions. > > But what should we do with the second one? > > Stefan > > > Am 2011-02-26 15:52, schrieb Robert Manning: > > I am reviewing it now. So far I like what I am seeing. At the moment I > have a few questions: > > 1. Can we change the name of NopWhereClausePart to Empty WhereClausePart > ? That seems a bit more readable to me. > > 2. In DataSetUpdateableTableModelImpl.updateTableComponent, in your new > code, there is now this: > > // into the first (and only) variable position in the prepared > stmt > CellComponentFactory.setPreparedStatementValue( > colDefs[col], pstmt, newValue, 1); > WhereClausePartUtil.setParameters(pstmt, whereClauseParts, 2); > > Would it be possible to use an additional ParameterWhereClausePart to > make the call to CellComponentFactory.setPreparedStatementValue unnecessary > ? > > 3. Would it be too much trouble to give WhereClausePartUtil an interface > (say IWhereClausePartUtil) and have it be injectable instead of static ? (so > - a WhereClausePartUtil instance variable with a public setter that > accepts IWhereClausePartUtil in each class where it is used; This helps with > testability) > > Rob > > |
|
From: Stefan W. <ste...@ao...> - 2011-02-26 19:06:02
|
Hi Rob,
1. Can we change the name of NopWhereClausePart to EmptyWhereClausePart
? That seems a bit more readable to me.
Of course. The first programming language I learned was Step 5 (the
programming language for Simatic S5 an Programable Logic Controller
within automation systems. Within the most build in functions you
needed the NOP operator for the NoOperation - Seems that the old
times are very present in my head :-)
I will update the code and JavaDoc.
2. Would it be possible to use an additional ParameterWhereClausePart to
make the call to CellComponentFactory.setPreparedStatementValue unnecessary?
Hm, with the call of CellComponentFactory.setPreparedStatementValue
we set the data of the changed data field. In the strict sense, this
is not an part of the where clause. If we add an additional
ParameterWhereClausePart for the changed data - that would be like
cheating.
If we want do this, we could:
* use an placeholder that is on the right (first) position which
is responsible only for setting the parameter and not for
creating the set=? part.
* or enhance the functionality, that constructing the update
statement is part of if (and maybe - insert/delete/select)
* or another suggestion?
3. Would it be too much trouble to give WhereClausePartUtil an interface.
Of course not. I think I didn't see an Dependency Injection
Container within Squirrel - So would it be appropriate to create an
instance variable initialized with an default, that could be
overwritten by the setter at each class where is is used?
I will prepare the first and the third part of your suggestions.
But what should we do with the second one?
Stefan
Am 2011-02-26 15:52, schrieb Robert Manning:
> I am reviewing it now. So far I like what I am seeing. At the
> moment I have a few questions:
>
> 1. Can we change the name of NopWhereClausePart to Empty
> WhereClausePart ? That seems a bit more readable to me.
>
> 2. In DataSetUpdateableTableModelImpl.updateTableComponent, in your
> new code, there is now this:
>
> // into the first (and only) variable position in the
> prepared stmt
> CellComponentFactory.setPreparedStatementValue(
> colDefs[col], pstmt, newValue, 1);
> WhereClausePartUtil.setParameters(pstmt, whereClauseParts, 2);
>
> Would it be possible to use an additional ParameterWhereClausePart to
> make the call to CellComponentFactory.setPreparedStatementValue
> unnecessary ?
>
> 3. Would it be too much trouble to give WhereClausePartUtil an
> interface (say IWhereClausePartUtil) and have it be injectable instead
> of static ? (so - a WhereClausePartUtil instance variable with a
> public setter that accepts IWhereClausePartUtil in each class where it
> is used; This helps with testability)
>
> Rob
|
|
From: Robert M. <rob...@gm...> - 2011-02-26 14:52:42
|
I am reviewing it now. So far I like what I am seeing. At the moment I
have a few questions:
1. Can we change the name of NopWhereClausePart to EmptyWhereClausePart ?
That seems a bit more readable to me.
2. In DataSetUpdateableTableModelImpl.updateTableComponent, in your new
code, there is now this:
// into the first (and only) variable position in the prepared
stmt
CellComponentFactory.setPreparedStatementValue(
colDefs[col], pstmt, newValue, 1);
WhereClausePartUtil.setParameters(pstmt, whereClauseParts, 2);
Would it be possible to use an additional ParameterWhereClausePart to make
the call to CellComponentFactory.setPreparedStatementValue unnecessary ?
3. Would it be too much trouble to give WhereClausePartUtil an interface
(say IWhereClausePartUtil) and have it be injectable instead of static ? (so
- a WhereClausePartUtil instance variable with a public setter that
accepts IWhereClausePartUtil in each class where it is used; This helps with
testability)
Rob
On Sat, Feb 19, 2011 at 2:45 PM, Stefan Willinger <ste...@ao...>wrote:
> Hi Rob,
>
> after some time (unfortunate several months) I have finished the
> implementation for the patch.
>
> *First: Like TDD - let me explain, how to test the changes:*
> According to your suggestion,I have prepared 2 SQL-Scripts, which prepare
> an DB-Table (called basicTypes) for an MySQL and Oracle Database.
>
> -
> /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/mysql.sql
> -
> /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/oracle.sql
>
> The content of this table contains some characters, which must be escaped
> in an MySQL Database (according to
> http://dev.mysql.com/doc/refman/5.1/en/string-syntax.html). There existing
> 3 Test-Classes which tests the behavior of the JDBC-Driver for the escaping
> of the special characters:
>
> -
> /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/MySQLAdhocTests.java
> -
> /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/MySQLnoBackslashEscapesAdhocTests.java
> -
> /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/OracleAdhocTests.java
>
> By extending their super class (AbstractAdhocTests) it should be very
> simple to use the test for another db-driver.
>
> These provided ad-hoc tests uses CellComponentFactory.getWhereClauseValue()
> to create the where clause and count the affected rows (each row is unique)
> when we use each column (the same as Squirrel did, when updating
> table-data). So, this should be a representing test-case.
>
> For the new code, e.g. *IsNullWhereClausePart* exists new test cases e.g.
> *IsNullWhereClausePartTest.
>
> Second: The Idea behind the implementation
> *Normally the jdbc-driver is responsible to escape the special characters
> of an database, when sql-parameters are used. Until now, Squirrel build the
> where-clause for updating data or counting the affected rows without
> parameters. In the future, Squirrel uses an PreparedStatement for this. So
> the responsibility is moved to the jdbc-driver.
>
> *Third: The implementation*
> The most new code exists in the module "fw". There is a new package called
> *net.sourceforge.squirrel_sql.fw.datasetviewer.cellcomponent.whereClause*.
> The interface *IWhereClausePart* replaces the simple String return type
> of *IDataTypeComponent.getWhereClauseValue()*.
> There are some implementations for this new interface:
>
> - *IsNullWhereClausePart*
> - *NoParameterWhereClausePart*
> - *NopWhereClausePart*
> - *ParameterWhereClausePart*
>
> The new *WhereClausePartUtil *is responsible for creating the String for
> the where-clause and setting the parameter into the PreparedStatement.
> Each implementation of the *IWhereClausePart *knows the *
> IDataTypeComponent* which created the instance because it uses the
> existing functionality for setting the parameter value.
>
>
> Now, please review the changes. And if you think this is an suitable
> solution, I would be happy if Squirrel contains this piece of code.
> If there are some things to change - let me know - I will do it.
>
>
> Stefan
>
>
>
>
>
>
> Am 2010-11-06 19:54, schrieb Stefan Willinger:
>
> Hi Rob,
>
> your comment sounds reasonable.
>
> I will finish the implementation and create a script a you recommended.
>
> At first, I will change the DataTypes by a conservative way, so that the
> actual behaviour will not be changed. In a future step it seems, that
> some DataTypes which doesn't support the where clause at the moment,
> could change their behaviour.
>
> But first I will ensure the actual functionality with PreparedStatements.
>
> OK - so far...
>
> Stefan
>
>
>
> Am 2010-11-04 01:40, schrieb Robert Manning:
>
> Setfan,
>
> Thinking about this more, I agree that this change would be beneficial
> in the ways you have described. However, it is a bit like major
> surgery and presents a bit of risk to include in the 3.2 release which
> we are currently preparing. If Gerd agrees, I would like to see this
> as a patch soon after we release 3.2. One other thing; it would be
> nice to demonstrate how effective this implementation is on various
> databases. I am thinking perhaps 1) simple SQL script to create a
> table and populate it with data that needs to be quoted and 2) a test
> driver that connects and verifies that the PreparedStatement approach
> works as expected. If such a test existed I have a number of
> databases setup to verify it against. I know that this sounds like
> more of a test for JDBC drivers, but as SQuirreL depends on the
> driver, it is affected by the bugs they have. Does that sound
> reasonable ?
>
> Rob
>
>
>
|
|
From: Stefan W. <ste...@ao...> - 2011-02-19 19:46:05
|
Hi Rob,
after some time (unfortunate several months) I have finished the
implementation for the patch.
/*First: Like TDD - let me explain, how to test the changes:*/
According to your suggestion,I have prepared 2 SQL-Scripts, which
prepare an DB-Table (called basicTypes) for an MySQL and Oracle Database.
* /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/mysql.sql
* /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/oracle.sql
The content of this table contains some characters, which must be
escaped in an MySQL Database (according to
http://dev.mysql.com/doc/refman/5.1/en/string-syntax.html). There
existing 3 Test-Classes which tests the behavior of the JDBC-Driver for
the escaping of the special characters:
* /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/MySQLAdhocTests.java
* /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/MySQLnoBackslashEscapesAdhocTests.java
* /squirrel-sql/src/test/java/net/sourceforge/squirrel_sql/fw/datasetviewer/cellcomponent/whereClause/OracleAdhocTests.java
By extending their super class (AbstractAdhocTests) it should be very
simple to use the test for another db-driver.
These provided ad-hoc tests uses
CellComponentFactory.getWhereClauseValue() to create the where clause
and count the affected rows (each row is unique) when we use each column
(the same as Squirrel did, when updating table-data). So, this should be
a representing test-case.
For the new code, e.g. /IsNullWhereClausePart/ exists new test cases
e.g. /IsNullWhereClausePartTest.
*Second: The Idea behind the implementation
*/Normally the jdbc-driver is responsible to escape the special
characters of an database, when sql-parameters are used. Until now,
Squirrel build the where-clause for updating data or counting the
affected rows without parameters. In the future, Squirrel uses an
PreparedStatement for this. So the responsibility is moved to the
jdbc-driver.
/*Third: The implementation*/
The most new code exists in the module "fw". There is a new package
called
/net.sourceforge.squirrel_sql.fw.datasetviewer.cellcomponent.whereClause/.
The interface /IWhereClausePart/ replaces the simple String return type
of /IDataTypeComponent.getWhereClauseValue()/.
There are some implementations for this new interface:
* /IsNullWhereClausePart/
* /NoParameterWhereClausePart/
* /NopWhereClausePart/
* /ParameterWhereClausePart/
The new /WhereClausePartUtil /is responsible for creating the String for
the where-clause and setting the parameter into the PreparedStatement.
Each implementation of the /IWhereClausePart /knows the
/IDataTypeComponent/ which created the instance because it uses the
existing functionality for setting the parameter value.
Now, please review the changes. And if you think this is an suitable
solution, I would be happy if Squirrel contains this piece of code.
If there are some things to change - let me know - I will do it.
Stefan
Am 2010-11-06 19:54, schrieb Stefan Willinger:
> Hi Rob,
>
> your comment sounds reasonable.
>
> I will finish the implementation and create a script a you recommended.
>
> At first, I will change the DataTypes by a conservative way, so that the
> actual behaviour will not be changed. In a future step it seems, that
> some DataTypes which doesn't support the where clause at the moment,
> could change their behaviour.
>
> But first I will ensure the actual functionality with PreparedStatements.
>
> OK - so far...
>
> Stefan
>
>
>
> Am 2010-11-04 01:40, schrieb Robert Manning:
>> Setfan,
>>
>> Thinking about this more, I agree that this change would be beneficial
>> in the ways you have described. However, it is a bit like major
>> surgery and presents a bit of risk to include in the 3.2 release which
>> we are currently preparing. If Gerd agrees, I would like to see this
>> as a patch soon after we release 3.2. One other thing; it would be
>> nice to demonstrate how effective this implementation is on various
>> databases. I am thinking perhaps 1) simple SQL script to create a
>> table and populate it with data that needs to be quoted and 2) a test
>> driver that connects and verifies that the PreparedStatement approach
>> works as expected. If such a test existed I have a number of
>> databases setup to verify it against. I know that this sounds like
>> more of a test for JDBC drivers, but as SQuirreL depends on the
>> driver, it is affected by the bugs they have. Does that sound
>> reasonable ?
>>
>> Rob
>>
|
|
From: Robert M. <rob...@gm...> - 2011-01-31 19:49:42
|
At the moment no. But considering that there are at least 5 different flavors of DB2 (LUW, OS/400, zOS) and not to mention versions, I am considering it. I have access to LUW, someone else contributed OS/400 and recently we had an offer to provide the similar schema information and testing for zOS. I just have not had the time to implement it. I will let everyone know when there is a candidate version of the DB2 plugin that supports zOS available for testing. Rob On Mon, Jan 31, 2011 at 6:49 AM, Domen Dolar <dom...@zp...> wrote: > Hello, > > > > We have problem browsing SEQUENCES in your tool. The problem is because the > information of sequences is stored in other table than that you specify in > the tool. Other browsing (tables, views, .) is working OK. > > > > Error: SEQUENCE: com.ibm.db2.jcc.a.nn: DB2 SQL Error: SQLCODE=-204, > SQLSTATE=42704, SQLERRMC=SYSCAT.SEQUENCES, DRIVER=3.52.95 > > > > The target database is DB2 (version 9.1) which is running on zOS. The table > where information of sequences is stored is located in SYSIBM.SYSSEQUENCES. > > > > Is it possible to change these settings somewhere? > > > > Best regards Domen Dolar > > > > > > > ---------------------------------------------------------------------------- > > Msc. Domen Dolar > > Head of Application Development > > The institute of pension and invalidity insurance of Slovenia > > Kolodvorska 15, 1518 Ljubljana, Slovenija > > E: Dom...@zp... > > Tel: +386 1 474 5105 > > > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Domen D. <dom...@zp...> - 2011-01-31 12:26:08
|
Hello, We have problem browsing SEQUENCES in your tool. The problem is because the information of sequences is stored in other table than that you specify in the tool. Other browsing (tables, views, .) is working OK. Error: SEQUENCE: com.ibm.db2.jcc.a.nn: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=SYSCAT.SEQUENCES, DRIVER=3.52.95 The target database is DB2 (version 9.1) which is running on zOS. The table where information of sequences is stored is located in SYSIBM.SYSSEQUENCES. Is it possible to change these settings somewhere? Best regards Domen Dolar ---------------------------------------------------------------------------- Msc. Domen Dolar Head of Application Development The institute of pension and invalidity insurance of Slovenia Kolodvorska 15, 1518 Ljubljana, Slovenija E: Dom...@zp... Tel: +386 1 474 5105 |
|
From: Robert M. <rob...@gm...> - 2011-01-11 22:21:28
|
OpenLogic is one such company that I know of. http://olex.openlogic.com/packages/squirrel/2.6.7 Rob On Mon, Jan 10, 2011 at 8:48 PM, TuckMeng Lam <tuc...@gm...> wrote: > Hi, > > This is a question that's not commonly asked, but is there any company that > supports Squirrel? Got a case where my users may want to consider > purchasing > support.Support to them means a person who can answer questions via > email/phone on usage of the software. > > Regards, > TuckMeng > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
