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: Gerd W. <ger...@t-...> - 2012-01-03 11:42:49
|
Hi Meo, On 03.01.2012 09:55, meo (XeniaLab) wrote: > Hi, > > I upgraded the italian translation of the tutorial (my email address was > not longer valid)... > > Maybe You can publish it (eg. > http://www.squirrelsql.org/index.php?page=screenshots ) ? is done, see http://www.squirrelsql.org/index.php?page=screenshots Thanks a lot for your efforts Gerd |
|
From: meo (XeniaLab) <me...@xe...> - 2012-01-03 09:14:16
|
Hi, I upgraded the italian translation of the tutorial (my email address was not longer valid)... Maybe You can publish it (eg. http://www.squirrelsql.org/index.php?page=screenshots ) ? Thanks meo bogliolo |
|
From: Conrad B. <con...@gm...> - 2011-11-16 09:07:55
|
Hi Matt, I filed an issue in the tracker. Let's see what will happen. Hope they sort it out as I have to do some migrations. https://sourceforge.net/tracker/?func=detail&aid=3438689&group_id=28383&atid=393417 Conrad -------- Original-Nachricht -------- > Datum: Mon, 14 Nov 2011 09:37:13 -0800 > Von: Matt Dahlman <mda...@ja...> > An: Conrad Beckert <con...@gm...> > CC: squ...@li... > Betreff: Re: [Squirrel-sql-develop] Field Mapping Error Microsoft SQL Server 2005 > I think the best long-term solution is to log an enhancement request that > would let a user define his own hibernate mappings on the fly. > > It came up in this thread recently: > http://sourceforge.net/mailarchive/message.php?msg_id=28178046 > > I did not log the enhancement request. Rob added the dialect I cared about > and solved that particular case. But the general problem can still come > up. (As it did for you!) It would be convenient to have user-defined mappings > to augment (optionally override???) the default hibernate mappings. > > In the short term you need to figure out precisely which Hibernate dialect > you are using for your SQL Server connection, and then modify it to > include a mapping for NVARCHAR. > > Regards, > Matt > > > On 14 Nov 2011, at 3:28, Conrad Beckert wrote: > > > could anyone please help me with this: I have a Microsoft SQL Server > 2005 database which I want to migrate. For that I want to recreate the tables > using SQirreL's Create Table Script. > > > > Unfortunately I get an: > > org.hibernate Mapping Exception No dialect mapping for JDBC type -9 > > > > Using an ODBC/JDBC bridge for connecting to the database doesn't help > either: > > > > JDBC-ODBC bridge doesn't provide all off the necessary metadata. ... > Server State S1002 > > > > > > I did some research and discovered that the error occurs if there is a > NVARCHAR field in the table to export. Unfortunately it is the case for > almost all of the tables. > > > > Any ideas to work around this? I know, that it is a rather known error > as there is an message on the list yet. But what to do? > > > > Thank you in advance for your help > > Conrad > > > > > ------------------------------------------------------------------------------ > > RSA(R) Conference 2012 > > Save $700 by Nov 18 > > Register now > > http://p.sf.net/sfu/rsa-sfdev2dev1 > > _______________________________________________ > > Squirrel-sql-develop mailing list > > Squ...@li... > > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Matt D. <mda...@ja...> - 2011-11-14 18:02:23
|
I think the best long-term solution is to log an enhancement request that would let a user define his own hibernate mappings on the fly. It came up in this thread recently: http://sourceforge.net/mailarchive/message.php?msg_id=28178046 I did not log the enhancement request. Rob added the dialect I cared about and solved that particular case. But the general problem can still come up. (As it did for you!) It would be convenient to have user-defined mappings to augment (optionally override???) the default hibernate mappings. In the short term you need to figure out precisely which Hibernate dialect you are using for your SQL Server connection, and then modify it to include a mapping for NVARCHAR. Regards, Matt On 14 Nov 2011, at 3:28, Conrad Beckert wrote: > could anyone please help me with this: I have a Microsoft SQL Server 2005 database which I want to migrate. For that I want to recreate the tables using SQirreL's Create Table Script. > > Unfortunately I get an: > org.hibernate Mapping Exception No dialect mapping for JDBC type -9 > > Using an ODBC/JDBC bridge for connecting to the database doesn't help either: > > JDBC-ODBC bridge doesn't provide all off the necessary metadata. ... Server State S1002 > > > I did some research and discovered that the error occurs if there is a NVARCHAR field in the table to export. Unfortunately it is the case for almost all of the tables. > > Any ideas to work around this? I know, that it is a rather known error as there is an message on the list yet. But what to do? > > Thank you in advance for your help > Conrad > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop |
|
From: Conrad B. <con...@gm...> - 2011-11-14 11:28:43
|
could anyone please help me with this: I have a Microsoft SQL Server 2005 database which I want to migrate. For that I want to recreate the tables using SQirreL's Create Table Script. Unfortunately I get an: org.hibernate Mapping Exception No dialect mapping for JDBC type -9 Using an ODBC/JDBC bridge for connecting to the database doesn't help either: JDBC-ODBC bridge doesn't provide all off the necessary metadata. ... Server State S1002 I did some research and discovered that the error occurs if there is a NVARCHAR field in the table to export. Unfortunately it is the case for almost all of the tables. Any ideas to work around this? I know, that it is a rather known error as there is an message on the list yet. But what to do? Thank you in advance for your help Conrad |
|
From: Erwan D. <erw...@ho...> - 2011-10-07 07:37:38
|
Thousands men enjoy it every day!. http://esculta.scoutsdelcarmen.com/com.page.php?mihSID=03jn4 |
|
From: Erwan D. <erw...@ho...> - 2011-10-06 20:55:55
|
Hello! My proposal will help you to improve your health... http://mikeyjetadore.free.fr/com.page.php?eCID=25ar6 |
|
From: Robert M. <rob...@gm...> - 2011-10-02 19:26:03
|
I am pleased to announce that our updated plugin archetype allows you to develop a plugin for SQuirreL without requiring you to download the source for SQuirreL. If you are interested, please read the following wiki page: https://sourceforge.net/apps/trac/squirrel-sql/wiki/PluginArchetype <https://sourceforge.net/apps/trac/squirrel-sql/wiki/PluginArchetype>If you have questions or you find that anything is unclear in this document, please reply to the list. Rob On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt <an...@ho... > wrote: > Hi, > > I have just downloaded latest from trunk wanting to create a plugin. > But following the guide found here: > http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does > not really get me anywhere except for different kind of build errors. > > The best result I'm getting is when disabling junittest but ends up with: > > [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ > standalone-pom --- > [INFO] [INFO] Generating project in Batch mode > [INFO] [INFO] Archetype repository missing. Using the one from > [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] > found in cata > log local > [INFO] [ERROR] A Maven 2 project already exists in the directory > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f > irsttest > [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A > Maven 2 project already exists in the directory > C:\projects\sql12\plugins\squirr > elsql-plugin-archetype\target\it\projects\firsttest\firsttest > [INFO] at > org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) > [INFO] at > org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) > [INFO] at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) > [INFO] at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [INFO] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [INFO] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [INFO] at java.lang.reflect.Method.invoke(Method.java:597) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 1.500s > [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 > [INFO] [INFO] Final Memory: 5M/15M > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:2.0:generate > (default-cli) on project standalone-pom: A Maven 2 > project already exists in the directory > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest > -> [Help 1] > [INFO] [ERROR] > [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven > with the -e switch. > [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug > logging. > [INFO] [ERROR] > [INFO] [ERROR] For more information about the errors and possible > solutions, please read the following articles: > [INFO] [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [INFO] ..FAILED (2.7 s) > [INFO] The build exited with code 1. See > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log > for details. > [INFO] ------------------------------------------------- > [INFO] Build Summary: > [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 > [INFO] ------------------------------------------------- > [ERROR] The following builds failed: > [ERROR] * firsttest > [INFO] ------------------------------------------------- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] SQuirreL Root POM ................................. SUCCESS [4.593s] > [INFO] Framework Library ................................. SUCCESS > [22.839s] > [INFO] SQuirreL Main Application Jar ..................... SUCCESS > [42.836s] > [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS [0.046s] > [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS [0.125s] > [INFO] Example Plugin .................................... SUCCESS [0.719s] > [INFO] SQuirreL Plugin Archetype ......................... FAILURE [8.905s] > [INFO] Codecompletion Plugin ............................. SKIPPED > [INFO] Dataimport Plugin ................................. SKIPPED > What do I miss? > > And that is with adding extra memory to both heapspace and permgen > space that is not mentioned. > > Regards > > Anders > > > ------------------------------------------------------------------------------ > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market businesses > from deploying virtual desktops? How do next-generation virtual desktops > provide companies an easier-to-deploy, easier-to-manage and more affordable > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Robert M. <rob...@gm...> - 2011-09-25 17:38:24
|
If you have already checked out the SQuirreL source from subversion before now, you may find the following error on your next subversion update attempt : svn: Failed to add directory 'plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src': an unversioned directory of the same name already exists This is due to a change that I made to the plugin archetype to fix an issue with new project creation. I converted a directory tree that was previously auto-generated to one that is now version-controlled and subversion's update mechanism does not like that. To remedy this, it should be safe to execute the following command from the root directory of your checked out sources : rm -rf plugins/squirrelsql-plugin-archetype/src/main/resources/archetype-resources/src After executing that command, try the update again. If anyone still has issues with this after performing the above step, send email to the list and I will help. Rob |
|
From: John H. <jh...@im...> - 2011-09-23 19:27:23
|
On Fri, 23 Sep 2011, Robert Manning wrote: > It would be best to use the latest maven version (3.x). For most of the > projects, maven 2 works ok, but it is not something any of us use to my > knowledge, so you will be blazing your own trail. > > Rob Rob: Would it be possible to review the instructions for setting up Eclipse and the rest of the dev environment for Squirrel? The instructions are getting a bit stale and I had a lot of difficulty trying to get everything installed and working when I tried in early July. -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jh...@im... FALaholic #11174 pgpk -a jh...@im... key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- [People] are socialists because they are blinded by envy and ignorance. -- economist Ludwig von Mises (1881-1973) ----------------------------------------------------------------------- 288 days since the first successful private orbital launch (SpaceX) |
|
From: Robert M. <rob...@gm...> - 2011-09-23 15:39:32
|
It would be best to use the latest maven version (3.x). For most of the projects, maven 2 works ok, but it is not something any of us use to my knowledge, so you will be blazing your own trail. Rob On Fri, Sep 23, 2011 at 3:23 AM, Anders Holmbech Brandt <an...@ho... > wrote: > Hi, > > Sorry for the late answer. I tried on my work machine where we need a > litte special plugin and it worked fine. But when and tried it at home > on my mac it gave me an maven error. > What is the required maven version? > > Regards > > Anders > > > > On Fri, Sep 16, 2011 at 15:42, Robert Manning > <rob...@gm...> wrote: > > Forgot to mention, if you run the "mvn archetype:generate..." command, > you > > should do so outside of the source tree that you have checked out. The > > source code is not needed - the archetype has what it needs to generate a > > new project. > > > > Rob > > > > On Fri, Sep 16, 2011 at 8:38 AM, Robert Manning < > rob...@gm...> > > wrote: > >> > >> Anders, > >> > >> This week I released a version of the maven archetype that I created for > >> generating plugin projects from scratch. When I tested it with the > >> following invocation: > >> > >> mvn archetype:generate -DarchetypeGroupId=net.sf.squirrel-sql.plugins > >> -DarchetypeArtifactId=squirrelsql-plugin-archetype > >> -DarchetypeVersion=3.3.0-rc1 > >> > >> I noted that the directory structure that was created was not correct. > I > >> have decided how to fix this but haven't had time to make the changes > yet. > >> For now, you could run the command above and when it prompts you for > >> "package", just use "p". When it finishes, go into src/main/java and > >> src/test/java and move the "net" directory out from under the "p" > directory, > >> so that you have src/main/java/net/.. and src/test/java/net/.. instead > of > >> src/main/java/p/net.. and src/test/java/p/net/.. > >> > >> If that is too confusing and I admit that it is, since you have the > source > >> checked out, you could simply make changes to the ExamplePlugin in > >> sql12/plugins/example. To launch SQuirreL with the example plugin > >> installed, you should be able to execute the command: > >> > >> mvn clean install -P launch > >> > >> I will follow up when I have fixed the archetype, but it probably won't > be > >> until sometime next week. > >> > >> Rob > >> > >> > >> On Fri, Sep 16, 2011 at 6:22 AM, Anders Holmbech Brandt > >> <an...@ho...> wrote: > >>> > >>> Anything new on this matter? > >>> > >>> Regards > >>> > >>> Anders > >>> > >>> > >>> > >>> On Mon, Sep 12, 2011 at 19:01, Robert Manning > >>> <rob...@gm...> wrote: > >>> > Yup, the use of the archetype (a critical step for new plugin > >>> > developers!) > >>> > was omitted from the documentation :( > >>> > > >>> > I will fix that soon and get back to you. > >>> > > >>> > Rob > >>> > > >>> > On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt > >>> > <an...@ho...> wrote: > >>> >> > >>> >> Hi, > >>> >> > >>> >> I have just downloaded latest from trunk wanting to create a plugin. > >>> >> But following the guide found here: > >>> >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuidedoes > >>> >> not really get me anywhere except for different kind of build > errors. > >>> >> > >>> >> The best result I'm getting is when disabling junittest but ends up > >>> >> with: > >>> >> > >>> >> [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) > @ > >>> >> standalone-pom --- > >>> >> [INFO] [INFO] Generating project in Batch mode > >>> >> [INFO] [INFO] Archetype repository missing. Using the one from > >>> >> > >>> >> > [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] > >>> >> found in cata > >>> >> log local > >>> >> [INFO] [ERROR] A Maven 2 project already exists in the directory > >>> >> > >>> >> > >>> >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f > >>> >> irsttest > >>> >> [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: > A > >>> >> Maven 2 project already exists in the directory > >>> >> C:\projects\sql12\plugins\squirr > >>> >> elsql-plugin-archetype\target\it\projects\firsttest\firsttest > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > >>> >> [INFO] at > >>> >> > >>> >> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > >>> >> [INFO] at > >>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > >>> >> [INFO] at > >>> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > >>> >> [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > >>> >> [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > >>> >> [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > >>> >> [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > >>> >> [INFO] at > >>> >> > >>> >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > >>> >> [INFO] at > >>> >> > >>> >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > >>> >> [INFO] at java.lang.reflect.Method.invoke(Method.java:597) > >>> >> [INFO] at > >>> >> > >>> >> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > >>> >> [INFO] at > >>> >> > >>> >> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > >>> >> [INFO] at > >>> >> > >>> >> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > >>> >> [INFO] at > >>> >> > >>> >> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > >>> >> [INFO] [INFO] > >>> >> > >>> >> > ------------------------------------------------------------------------ > >>> >> [INFO] [INFO] BUILD FAILURE > >>> >> [INFO] [INFO] > >>> >> > >>> >> > ------------------------------------------------------------------------ > >>> >> [INFO] [INFO] Total time: 1.500s > >>> >> [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 > >>> >> [INFO] [INFO] Final Memory: 5M/15M > >>> >> [INFO] [INFO] > >>> >> > >>> >> > ------------------------------------------------------------------------ > >>> >> [INFO] [ERROR] Failed to execute goal > >>> >> org.apache.maven.plugins:maven-archetype-plugin:2.0:generate > >>> >> (default-cli) on project standalone-pom: A Maven 2 > >>> >> project already exists in the directory > >>> >> > >>> >> > >>> >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest > >>> >> -> [Help 1] > >>> >> [INFO] [ERROR] > >>> >> [INFO] [ERROR] To see the full stack trace of the errors, re-run > Maven > >>> >> with the -e switch. > >>> >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug > >>> >> logging. > >>> >> [INFO] [ERROR] > >>> >> [INFO] [ERROR] For more information about the errors and possible > >>> >> solutions, please read the following articles: > >>> >> [INFO] [ERROR] [Help 1] > >>> >> > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > >>> >> [INFO] ..FAILED (2.7 s) > >>> >> [INFO] The build exited with code 1. See > >>> >> > >>> >> > >>> >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log > >>> >> for details. > >>> >> [INFO] ------------------------------------------------- > >>> >> [INFO] Build Summary: > >>> >> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 > >>> >> [INFO] ------------------------------------------------- > >>> >> [ERROR] The following builds failed: > >>> >> [ERROR] * firsttest > >>> >> [INFO] ------------------------------------------------- > >>> >> [INFO] > >>> >> > >>> >> > ------------------------------------------------------------------------ > >>> >> [INFO] Reactor Summary: > >>> >> [INFO] > >>> >> [INFO] SQuirreL Root POM ................................. SUCCESS > >>> >> [4.593s] > >>> >> [INFO] Framework Library ................................. SUCCESS > >>> >> [22.839s] > >>> >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS > >>> >> [42.836s] > >>> >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS > >>> >> [0.046s] > >>> >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS > >>> >> [0.125s] > >>> >> [INFO] Example Plugin .................................... SUCCESS > >>> >> [0.719s] > >>> >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE > >>> >> [8.905s] > >>> >> [INFO] Codecompletion Plugin ............................. SKIPPED > >>> >> [INFO] Dataimport Plugin ................................. SKIPPED > >>> >> What do I miss? > >>> >> > >>> >> And that is with adding extra memory to both heapspace and permgen > >>> >> space that is not mentioned. > >>> >> > >>> >> Regards > >>> >> > >>> >> Anders > >>> >> > >>> >> > >>> >> > >>> >> > ------------------------------------------------------------------------------ > >>> >> Doing More with Less: The Next Generation Virtual Desktop > >>> >> What are the key obstacles that have prevented many mid-market > >>> >> businesses > >>> >> from deploying virtual desktops? How do next-generation virtual > >>> >> desktops > >>> >> provide companies an easier-to-deploy, easier-to-manage and more > >>> >> affordable > >>> >> virtual desktop model. > http://www.accelacomm.com/jaw/sfnl/114/51426474/ > >>> >> _______________________________________________ > >>> >> Squirrel-sql-develop mailing list > >>> >> Squ...@li... > >>> >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > >>> > > >>> > > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > >>> http://p.sf.net/sfu/rim-devcon-copy2 > >>> _______________________________________________ > >>> Squirrel-sql-develop mailing list > >>> Squ...@li... > >>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > >> > > > > > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Anders H. B. <an...@ho...> - 2011-09-23 07:24:00
|
Hi, Sorry for the late answer. I tried on my work machine where we need a litte special plugin and it worked fine. But when and tried it at home on my mac it gave me an maven error. What is the required maven version? Regards Anders On Fri, Sep 16, 2011 at 15:42, Robert Manning <rob...@gm...> wrote: > Forgot to mention, if you run the "mvn archetype:generate..." command, you > should do so outside of the source tree that you have checked out. The > source code is not needed - the archetype has what it needs to generate a > new project. > > Rob > > On Fri, Sep 16, 2011 at 8:38 AM, Robert Manning <rob...@gm...> > wrote: >> >> Anders, >> >> This week I released a version of the maven archetype that I created for >> generating plugin projects from scratch. When I tested it with the >> following invocation: >> >> mvn archetype:generate -DarchetypeGroupId=net.sf.squirrel-sql.plugins >> -DarchetypeArtifactId=squirrelsql-plugin-archetype >> -DarchetypeVersion=3.3.0-rc1 >> >> I noted that the directory structure that was created was not correct. I >> have decided how to fix this but haven't had time to make the changes yet. >> For now, you could run the command above and when it prompts you for >> "package", just use "p". When it finishes, go into src/main/java and >> src/test/java and move the "net" directory out from under the "p" directory, >> so that you have src/main/java/net/.. and src/test/java/net/.. instead of >> src/main/java/p/net.. and src/test/java/p/net/.. >> >> If that is too confusing and I admit that it is, since you have the source >> checked out, you could simply make changes to the ExamplePlugin in >> sql12/plugins/example. To launch SQuirreL with the example plugin >> installed, you should be able to execute the command: >> >> mvn clean install -P launch >> >> I will follow up when I have fixed the archetype, but it probably won't be >> until sometime next week. >> >> Rob >> >> >> On Fri, Sep 16, 2011 at 6:22 AM, Anders Holmbech Brandt >> <an...@ho...> wrote: >>> >>> Anything new on this matter? >>> >>> Regards >>> >>> Anders >>> >>> >>> >>> On Mon, Sep 12, 2011 at 19:01, Robert Manning >>> <rob...@gm...> wrote: >>> > Yup, the use of the archetype (a critical step for new plugin >>> > developers!) >>> > was omitted from the documentation :( >>> > >>> > I will fix that soon and get back to you. >>> > >>> > Rob >>> > >>> > On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt >>> > <an...@ho...> wrote: >>> >> >>> >> Hi, >>> >> >>> >> I have just downloaded latest from trunk wanting to create a plugin. >>> >> But following the guide found here: >>> >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does >>> >> not really get me anywhere except for different kind of build errors. >>> >> >>> >> The best result I'm getting is when disabling junittest but ends up >>> >> with: >>> >> >>> >> [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ >>> >> standalone-pom --- >>> >> [INFO] [INFO] Generating project in Batch mode >>> >> [INFO] [INFO] Archetype repository missing. Using the one from >>> >> >>> >> [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] >>> >> found in cata >>> >> log local >>> >> [INFO] [ERROR] A Maven 2 project already exists in the directory >>> >> >>> >> >>> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f >>> >> irsttest >>> >> [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A >>> >> Maven 2 project already exists in the directory >>> >> C:\projects\sql12\plugins\squirr >>> >> elsql-plugin-archetype\target\it\projects\firsttest\firsttest >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >>> >> [INFO] at >>> >> >>> >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >>> >> [INFO] at >>> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >>> >> [INFO] at >>> >> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >>> >> [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >>> >> [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >>> >> [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >>> >> [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> >> [INFO] at >>> >> >>> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> >> [INFO] at >>> >> >>> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> >> [INFO] at java.lang.reflect.Method.invoke(Method.java:597) >>> >> [INFO] at >>> >> >>> >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >>> >> [INFO] at >>> >> >>> >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >>> >> [INFO] at >>> >> >>> >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >>> >> [INFO] at >>> >> >>> >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >>> >> [INFO] [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] [INFO] BUILD FAILURE >>> >> [INFO] [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] [INFO] Total time: 1.500s >>> >> [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 >>> >> [INFO] [INFO] Final Memory: 5M/15M >>> >> [INFO] [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] [ERROR] Failed to execute goal >>> >> org.apache.maven.plugins:maven-archetype-plugin:2.0:generate >>> >> (default-cli) on project standalone-pom: A Maven 2 >>> >> project already exists in the directory >>> >> >>> >> >>> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest >>> >> -> [Help 1] >>> >> [INFO] [ERROR] >>> >> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven >>> >> with the -e switch. >>> >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug >>> >> logging. >>> >> [INFO] [ERROR] >>> >> [INFO] [ERROR] For more information about the errors and possible >>> >> solutions, please read the following articles: >>> >> [INFO] [ERROR] [Help 1] >>> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>> >> [INFO] ..FAILED (2.7 s) >>> >> [INFO] The build exited with code 1. See >>> >> >>> >> >>> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log >>> >> for details. >>> >> [INFO] ------------------------------------------------- >>> >> [INFO] Build Summary: >>> >> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 >>> >> [INFO] ------------------------------------------------- >>> >> [ERROR] The following builds failed: >>> >> [ERROR] * firsttest >>> >> [INFO] ------------------------------------------------- >>> >> [INFO] >>> >> >>> >> ------------------------------------------------------------------------ >>> >> [INFO] Reactor Summary: >>> >> [INFO] >>> >> [INFO] SQuirreL Root POM ................................. SUCCESS >>> >> [4.593s] >>> >> [INFO] Framework Library ................................. SUCCESS >>> >> [22.839s] >>> >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS >>> >> [42.836s] >>> >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS >>> >> [0.046s] >>> >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS >>> >> [0.125s] >>> >> [INFO] Example Plugin .................................... SUCCESS >>> >> [0.719s] >>> >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE >>> >> [8.905s] >>> >> [INFO] Codecompletion Plugin ............................. SKIPPED >>> >> [INFO] Dataimport Plugin ................................. SKIPPED >>> >> What do I miss? >>> >> >>> >> And that is with adding extra memory to both heapspace and permgen >>> >> space that is not mentioned. >>> >> >>> >> Regards >>> >> >>> >> Anders >>> >> >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> Doing More with Less: The Next Generation Virtual Desktop >>> >> What are the key obstacles that have prevented many mid-market >>> >> businesses >>> >> from deploying virtual desktops? How do next-generation virtual >>> >> desktops >>> >> provide companies an easier-to-deploy, easier-to-manage and more >>> >> affordable >>> >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >>> >> _______________________________________________ >>> >> Squirrel-sql-develop mailing list >>> >> Squ...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >>> > >>> > >>> >>> >>> ------------------------------------------------------------------------------ >>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >>> http://p.sf.net/sfu/rim-devcon-copy2 >>> _______________________________________________ >>> Squirrel-sql-develop mailing list >>> Squ...@li... >>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > > |
|
From: Robert M. <rob...@gm...> - 2011-09-16 13:42:56
|
Forgot to mention, if you run the "mvn archetype:generate..." command, you should do so outside of the source tree that you have checked out. The source code is not needed - the archetype has what it needs to generate a new project. Rob On Fri, Sep 16, 2011 at 8:38 AM, Robert Manning <rob...@gm...>wrote: > Anders, > > This week I released a version of the maven archetype that I created for > generating plugin projects from scratch. When I tested it with the > following invocation: > > mvn archetype:generate -DarchetypeGroupId=net.sf.squirrel-sql.plugins > -DarchetypeArtifactId=squirrelsql-plugin-archetype > -DarchetypeVersion=3.3.0-rc1 > > I noted that the directory structure that was created was not correct. I > have decided how to fix this but haven't had time to make the changes yet. > For now, you could run the command above and when it prompts you for > "package", just use "p". When it finishes, go into src/main/java and > src/test/java and move the "net" directory out from under the "p" directory, > so that you have src/main/java/net/.. and src/test/java/net/.. instead of > src/main/java/p/net.. and src/test/java/p/net/.. > > If that is too confusing and I admit that it is, since you have the source > checked out, you could simply make changes to the ExamplePlugin in > sql12/plugins/example. To launch SQuirreL with the example plugin > installed, you should be able to execute the command: > > mvn clean install -P launch > > I will follow up when I have fixed the archetype, but it probably won't be > until sometime next week. > > Rob > > > > On Fri, Sep 16, 2011 at 6:22 AM, Anders Holmbech Brandt < > an...@ho...> wrote: > >> Anything new on this matter? >> >> Regards >> >> Anders >> >> >> >> On Mon, Sep 12, 2011 at 19:01, Robert Manning >> <rob...@gm...> wrote: >> > Yup, the use of the archetype (a critical step for new plugin >> developers!) >> > was omitted from the documentation :( >> > >> > I will fix that soon and get back to you. >> > >> > Rob >> > >> > On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt >> > <an...@ho...> wrote: >> >> >> >> Hi, >> >> >> >> I have just downloaded latest from trunk wanting to create a plugin. >> >> But following the guide found here: >> >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does >> >> not really get me anywhere except for different kind of build errors. >> >> >> >> The best result I'm getting is when disabling junittest but ends up >> with: >> >> >> >> [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ >> >> standalone-pom --- >> >> [INFO] [INFO] Generating project in Batch mode >> >> [INFO] [INFO] Archetype repository missing. Using the one from >> >> >> [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] >> >> found in cata >> >> log local >> >> [INFO] [ERROR] A Maven 2 project already exists in the directory >> >> >> >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f >> >> irsttest >> >> [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A >> >> Maven 2 project already exists in the directory >> >> C:\projects\sql12\plugins\squirr >> >> elsql-plugin-archetype\target\it\projects\firsttest\firsttest >> >> [INFO] at >> >> >> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) >> >> [INFO] at >> >> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) >> >> [INFO] at >> >> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) >> >> [INFO] at >> >> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) >> >> [INFO] at >> >> >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) >> >> [INFO] at >> >> >> org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) >> >> [INFO] at >> >> >> org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) >> >> [INFO] at >> >> >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> >> [INFO] at >> >> >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> >> [INFO] at >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >> >> [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> >> [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> >> [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> >> [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> >> [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> [INFO] at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> [INFO] at >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> [INFO] at java.lang.reflect.Method.invoke(Method.java:597) >> >> [INFO] at >> >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> >> [INFO] at >> >> >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> >> [INFO] at >> >> >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> >> [INFO] at >> >> >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> >> [INFO] [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] [INFO] BUILD FAILURE >> >> [INFO] [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] [INFO] Total time: 1.500s >> >> [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 >> >> [INFO] [INFO] Final Memory: 5M/15M >> >> [INFO] [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] [ERROR] Failed to execute goal >> >> org.apache.maven.plugins:maven-archetype-plugin:2.0:generate >> >> (default-cli) on project standalone-pom: A Maven 2 >> >> project already exists in the directory >> >> >> >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest >> >> -> [Help 1] >> >> [INFO] [ERROR] >> >> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven >> >> with the -e switch. >> >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug >> >> logging. >> >> [INFO] [ERROR] >> >> [INFO] [ERROR] For more information about the errors and possible >> >> solutions, please read the following articles: >> >> [INFO] [ERROR] [Help 1] >> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> >> [INFO] ..FAILED (2.7 s) >> >> [INFO] The build exited with code 1. See >> >> >> >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log >> >> for details. >> >> [INFO] ------------------------------------------------- >> >> [INFO] Build Summary: >> >> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 >> >> [INFO] ------------------------------------------------- >> >> [ERROR] The following builds failed: >> >> [ERROR] * firsttest >> >> [INFO] ------------------------------------------------- >> >> [INFO] >> >> >> ------------------------------------------------------------------------ >> >> [INFO] Reactor Summary: >> >> [INFO] >> >> [INFO] SQuirreL Root POM ................................. SUCCESS >> >> [4.593s] >> >> [INFO] Framework Library ................................. SUCCESS >> >> [22.839s] >> >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS >> >> [42.836s] >> >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS >> >> [0.046s] >> >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS >> >> [0.125s] >> >> [INFO] Example Plugin .................................... SUCCESS >> >> [0.719s] >> >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE >> >> [8.905s] >> >> [INFO] Codecompletion Plugin ............................. SKIPPED >> >> [INFO] Dataimport Plugin ................................. SKIPPED >> >> What do I miss? >> >> >> >> And that is with adding extra memory to both heapspace and permgen >> >> space that is not mentioned. >> >> >> >> Regards >> >> >> >> Anders >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Doing More with Less: The Next Generation Virtual Desktop >> >> What are the key obstacles that have prevented many mid-market >> businesses >> >> from deploying virtual desktops? How do next-generation virtual >> desktops >> >> provide companies an easier-to-deploy, easier-to-manage and more >> >> affordable >> >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >> >> _______________________________________________ >> >> Squirrel-sql-develop mailing list >> >> Squ...@li... >> >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > >> > >> >> >> ------------------------------------------------------------------------------ >> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >> http://p.sf.net/sfu/rim-devcon-copy2 >> _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > > |
|
From: Robert M. <rob...@gm...> - 2011-09-16 12:38:29
|
Anders, This week I released a version of the maven archetype that I created for generating plugin projects from scratch. When I tested it with the following invocation: mvn archetype:generate -DarchetypeGroupId=net.sf.squirrel-sql.plugins -DarchetypeArtifactId=squirrelsql-plugin-archetype -DarchetypeVersion=3.3.0-rc1 I noted that the directory structure that was created was not correct. I have decided how to fix this but haven't had time to make the changes yet. For now, you could run the command above and when it prompts you for "package", just use "p". When it finishes, go into src/main/java and src/test/java and move the "net" directory out from under the "p" directory, so that you have src/main/java/net/.. and src/test/java/net/.. instead of src/main/java/p/net.. and src/test/java/p/net/.. If that is too confusing and I admit that it is, since you have the source checked out, you could simply make changes to the ExamplePlugin in sql12/plugins/example. To launch SQuirreL with the example plugin installed, you should be able to execute the command: mvn clean install -P launch I will follow up when I have fixed the archetype, but it probably won't be until sometime next week. Rob On Fri, Sep 16, 2011 at 6:22 AM, Anders Holmbech Brandt <an...@ho... > wrote: > Anything new on this matter? > > Regards > > Anders > > > > On Mon, Sep 12, 2011 at 19:01, Robert Manning > <rob...@gm...> wrote: > > Yup, the use of the archetype (a critical step for new plugin > developers!) > > was omitted from the documentation :( > > > > I will fix that soon and get back to you. > > > > Rob > > > > On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt > > <an...@ho...> wrote: > >> > >> Hi, > >> > >> I have just downloaded latest from trunk wanting to create a plugin. > >> But following the guide found here: > >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does > >> not really get me anywhere except for different kind of build errors. > >> > >> The best result I'm getting is when disabling junittest but ends up > with: > >> > >> [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ > >> standalone-pom --- > >> [INFO] [INFO] Generating project in Batch mode > >> [INFO] [INFO] Archetype repository missing. Using the one from > >> > [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] > >> found in cata > >> log local > >> [INFO] [ERROR] A Maven 2 project already exists in the directory > >> > >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f > >> irsttest > >> [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A > >> Maven 2 project already exists in the directory > >> C:\projects\sql12\plugins\squirr > >> elsql-plugin-archetype\target\it\projects\firsttest\firsttest > >> [INFO] at > >> > org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) > >> [INFO] at > >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) > >> [INFO] at > >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) > >> [INFO] at > >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) > >> [INFO] at > >> > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) > >> [INFO] at > >> > org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) > >> [INFO] at > >> > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) > >> [INFO] at > >> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > >> [INFO] at > >> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > >> [INFO] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > >> [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > >> [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > >> [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > >> [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > >> [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> [INFO] at > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > >> [INFO] at > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > >> [INFO] at java.lang.reflect.Method.invoke(Method.java:597) > >> [INFO] at > >> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > >> [INFO] at > >> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > >> [INFO] at > >> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > >> [INFO] at > >> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > >> [INFO] [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] [INFO] BUILD FAILURE > >> [INFO] [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] [INFO] Total time: 1.500s > >> [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 > >> [INFO] [INFO] Final Memory: 5M/15M > >> [INFO] [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] [ERROR] Failed to execute goal > >> org.apache.maven.plugins:maven-archetype-plugin:2.0:generate > >> (default-cli) on project standalone-pom: A Maven 2 > >> project already exists in the directory > >> > >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest > >> -> [Help 1] > >> [INFO] [ERROR] > >> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven > >> with the -e switch. > >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug > >> logging. > >> [INFO] [ERROR] > >> [INFO] [ERROR] For more information about the errors and possible > >> solutions, please read the following articles: > >> [INFO] [ERROR] [Help 1] > >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > >> [INFO] ..FAILED (2.7 s) > >> [INFO] The build exited with code 1. See > >> > >> > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log > >> for details. > >> [INFO] ------------------------------------------------- > >> [INFO] Build Summary: > >> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 > >> [INFO] ------------------------------------------------- > >> [ERROR] The following builds failed: > >> [ERROR] * firsttest > >> [INFO] ------------------------------------------------- > >> [INFO] > >> ------------------------------------------------------------------------ > >> [INFO] Reactor Summary: > >> [INFO] > >> [INFO] SQuirreL Root POM ................................. SUCCESS > >> [4.593s] > >> [INFO] Framework Library ................................. SUCCESS > >> [22.839s] > >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS > >> [42.836s] > >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS > >> [0.046s] > >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS > >> [0.125s] > >> [INFO] Example Plugin .................................... SUCCESS > >> [0.719s] > >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE > >> [8.905s] > >> [INFO] Codecompletion Plugin ............................. SKIPPED > >> [INFO] Dataimport Plugin ................................. SKIPPED > >> What do I miss? > >> > >> And that is with adding extra memory to both heapspace and permgen > >> space that is not mentioned. > >> > >> Regards > >> > >> Anders > >> > >> > >> > ------------------------------------------------------------------------------ > >> Doing More with Less: The Next Generation Virtual Desktop > >> What are the key obstacles that have prevented many mid-market > businesses > >> from deploying virtual desktops? How do next-generation virtual > desktops > >> provide companies an easier-to-deploy, easier-to-manage and more > >> affordable > >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > >> _______________________________________________ > >> Squirrel-sql-develop mailing list > >> Squ...@li... > >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > > > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > http://p.sf.net/sfu/rim-devcon-copy2 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Anders H. B. <an...@ho...> - 2011-09-16 10:23:09
|
Anything new on this matter? Regards Anders On Mon, Sep 12, 2011 at 19:01, Robert Manning <rob...@gm...> wrote: > Yup, the use of the archetype (a critical step for new plugin developers!) > was omitted from the documentation :( > > I will fix that soon and get back to you. > > Rob > > On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt > <an...@ho...> wrote: >> >> Hi, >> >> I have just downloaded latest from trunk wanting to create a plugin. >> But following the guide found here: >> http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does >> not really get me anywhere except for different kind of build errors. >> >> The best result I'm getting is when disabling junittest but ends up with: >> >> [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ >> standalone-pom --- >> [INFO] [INFO] Generating project in Batch mode >> [INFO] [INFO] Archetype repository missing. Using the one from >> [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] >> found in cata >> log local >> [INFO] [ERROR] A Maven 2 project already exists in the directory >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f >> irsttest >> [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A >> Maven 2 project already exists in the directory >> C:\projects\sql12\plugins\squirr >> elsql-plugin-archetype\target\it\projects\firsttest\firsttest >> [INFO] at >> org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) >> [INFO] at >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) >> [INFO] at >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) >> [INFO] at >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) >> [INFO] at >> org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) >> [INFO] at >> org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) >> [INFO] at >> org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) >> [INFO] at >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >> [INFO] at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> [INFO] at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> [INFO] at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> [INFO] at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) >> [INFO] at >> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) >> [INFO] at >> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) >> [INFO] at >> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) >> [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) >> [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) >> [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) >> [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) >> [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) >> [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> [INFO] at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> [INFO] at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> [INFO] at java.lang.reflect.Method.invoke(Method.java:597) >> [INFO] at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> [INFO] at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> [INFO] at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> [INFO] at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> [INFO] [INFO] BUILD FAILURE >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> [INFO] [INFO] Total time: 1.500s >> [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 >> [INFO] [INFO] Final Memory: 5M/15M >> [INFO] [INFO] >> ------------------------------------------------------------------------ >> [INFO] [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-archetype-plugin:2.0:generate >> (default-cli) on project standalone-pom: A Maven 2 >> project already exists in the directory >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest >> -> [Help 1] >> [INFO] [ERROR] >> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven >> with the -e switch. >> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug >> logging. >> [INFO] [ERROR] >> [INFO] [ERROR] For more information about the errors and possible >> solutions, please read the following articles: >> [INFO] [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> [INFO] ..FAILED (2.7 s) >> [INFO] The build exited with code 1. See >> >> C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log >> for details. >> [INFO] ------------------------------------------------- >> [INFO] Build Summary: >> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 >> [INFO] ------------------------------------------------- >> [ERROR] The following builds failed: >> [ERROR] * firsttest >> [INFO] ------------------------------------------------- >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] SQuirreL Root POM ................................. SUCCESS >> [4.593s] >> [INFO] Framework Library ................................. SUCCESS >> [22.839s] >> [INFO] SQuirreL Main Application Jar ..................... SUCCESS >> [42.836s] >> [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS >> [0.046s] >> [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS >> [0.125s] >> [INFO] Example Plugin .................................... SUCCESS >> [0.719s] >> [INFO] SQuirreL Plugin Archetype ......................... FAILURE >> [8.905s] >> [INFO] Codecompletion Plugin ............................. SKIPPED >> [INFO] Dataimport Plugin ................................. SKIPPED >> What do I miss? >> >> And that is with adding extra memory to both heapspace and permgen >> space that is not mentioned. >> >> Regards >> >> Anders >> >> >> ------------------------------------------------------------------------------ >> Doing More with Less: The Next Generation Virtual Desktop >> What are the key obstacles that have prevented many mid-market businesses >> from deploying virtual desktops? How do next-generation virtual desktops >> provide companies an easier-to-deploy, easier-to-manage and more >> affordable >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >> _______________________________________________ >> Squirrel-sql-develop mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > |
|
From: Robert M. <rob...@gm...> - 2011-09-12 17:01:32
|
Yup, the use of the archetype (a critical step for new plugin developers!) was omitted from the documentation :( I will fix that soon and get back to you. Rob On Mon, Sep 12, 2011 at 9:32 AM, Anders Holmbech Brandt <an...@ho... > wrote: > Hi, > > I have just downloaded latest from trunk wanting to create a plugin. > But following the guide found here: > http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does > not really get me anywhere except for different kind of build errors. > > The best result I'm getting is when disabling junittest but ends up with: > > [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ > standalone-pom --- > [INFO] [INFO] Generating project in Batch mode > [INFO] [INFO] Archetype repository missing. Using the one from > [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] > found in cata > log local > [INFO] [ERROR] A Maven 2 project already exists in the directory > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f > irsttest > [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A > Maven 2 project already exists in the directory > C:\projects\sql12\plugins\squirr > elsql-plugin-archetype\target\it\projects\firsttest\firsttest > [INFO] at > org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) > [INFO] at > org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) > [INFO] at > org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) > [INFO] at > org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) > [INFO] at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > [INFO] at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > [INFO] at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [INFO] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [INFO] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [INFO] at java.lang.reflect.Method.invoke(Method.java:597) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > [INFO] at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] BUILD FAILURE > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [INFO] Total time: 1.500s > [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 > [INFO] [INFO] Final Memory: 5M/15M > [INFO] [INFO] > ------------------------------------------------------------------------ > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:2.0:generate > (default-cli) on project standalone-pom: A Maven 2 > project already exists in the directory > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest > -> [Help 1] > [INFO] [ERROR] > [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven > with the -e switch. > [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug > logging. > [INFO] [ERROR] > [INFO] [ERROR] For more information about the errors and possible > solutions, please read the following articles: > [INFO] [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [INFO] ..FAILED (2.7 s) > [INFO] The build exited with code 1. See > > C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log > for details. > [INFO] ------------------------------------------------- > [INFO] Build Summary: > [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 > [INFO] ------------------------------------------------- > [ERROR] The following builds failed: > [ERROR] * firsttest > [INFO] ------------------------------------------------- > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] SQuirreL Root POM ................................. SUCCESS [4.593s] > [INFO] Framework Library ................................. SUCCESS > [22.839s] > [INFO] SQuirreL Main Application Jar ..................... SUCCESS > [42.836s] > [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS [0.046s] > [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS [0.125s] > [INFO] Example Plugin .................................... SUCCESS [0.719s] > [INFO] SQuirreL Plugin Archetype ......................... FAILURE [8.905s] > [INFO] Codecompletion Plugin ............................. SKIPPED > [INFO] Dataimport Plugin ................................. SKIPPED > What do I miss? > > And that is with adding extra memory to both heapspace and permgen > space that is not mentioned. > > Regards > > Anders > > > ------------------------------------------------------------------------------ > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market businesses > from deploying virtual desktops? How do next-generation virtual desktops > provide companies an easier-to-deploy, easier-to-manage and more affordable > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Anders H. B. <an...@ho...> - 2011-09-12 13:33:07
|
Hi, I have just downloaded latest from trunk wanting to create a plugin. But following the guide found here: http://sourceforge.net/apps/trac/squirrel-sql/wiki/DeveloperGuide does not really get me anywhere except for different kind of build errors. The best result I'm getting is when disabling junittest but ends up with: [INFO] [INFO] --- maven-archetype-plugin:2.0:generate (default-cli) @ standalone-pom --- [INFO] [INFO] Generating project in Batch mode [INFO] [INFO] Archetype repository missing. Using the one from [net.sf.squirrel-sql.plugins:squirrelsql-plugin-archetype:3.3.0-SNAPSHOT] found in cata log local [INFO] [ERROR] A Maven 2 project already exists in the directory C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\f irsttest [INFO] org.apache.maven.archetype.exception.ProjectDirectoryExists: A Maven 2 project already exists in the directory C:\projects\sql12\plugins\squirr elsql-plugin-archetype\target\it\projects\firsttest\firsttest [INFO] at org.apache.maven.archetype.generator.DefaultFilesetArchetypeGenerator.generateArchetype(DefaultFilesetArchetypeGenerator.java:198) [INFO] at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.processFileSetArchetype(DefaultArchetypeGenerator.java:136) [INFO] at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:106) [INFO] at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:149) [INFO] at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:209) [INFO] at org.apache.maven.archetype.DefaultArchetypeManager.generateProjectFromArchetype(DefaultArchetypeManager.java:71) [INFO] at org.apache.maven.archetype.mojos.CreateProjectFromArchetypeMojo.execute(CreateProjectFromArchetypeMojo.java:190) [INFO] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) [INFO] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) [INFO] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) [INFO] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) [INFO] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) [INFO] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) [INFO] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) [INFO] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) [INFO] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) [INFO] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [INFO] at java.lang.reflect.Method.invoke(Method.java:597) [INFO] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) [INFO] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) [INFO] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) [INFO] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] BUILD FAILURE [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [INFO] Total time: 1.500s [INFO] [INFO] Finished at: Mon Sep 12 14:36:30 CEST 2011 [INFO] [INFO] Final Memory: 5M/15M [INFO] [INFO] ------------------------------------------------------------------------ [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.0:generate (default-cli) on project standalone-pom: A Maven 2 project already exists in the directory C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\firsttest -> [Help 1] [INFO] [ERROR] [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [INFO] [ERROR] [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles: [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [INFO] ..FAILED (2.7 s) [INFO] The build exited with code 1. See C:\projects\sql12\plugins\squirrelsql-plugin-archetype\target\it\projects\firsttest\build.log for details. [INFO] ------------------------------------------------- [INFO] Build Summary: [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------- [ERROR] The following builds failed: [ERROR] * firsttest [INFO] ------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] SQuirreL Root POM ................................. SUCCESS [4.593s] [INFO] Framework Library ................................. SUCCESS [22.839s] [INFO] SQuirreL Main Application Jar ..................... SUCCESS [42.836s] [INFO] SQuirreL-SQL Plugins Parent POM ................... SUCCESS [0.046s] [INFO] SQuirreL-SQL Plugin Assembly Descriptor ........... SUCCESS [0.125s] [INFO] Example Plugin .................................... SUCCESS [0.719s] [INFO] SQuirreL Plugin Archetype ......................... FAILURE [8.905s] [INFO] Codecompletion Plugin ............................. SKIPPED [INFO] Dataimport Plugin ................................. SKIPPED What do I miss? And that is with adding extra memory to both heapspace and permgen space that is not mentioned. Regards Anders |
|
From: Stefan W. <wil...@ao...> - 2011-09-11 20:14:29
|
Hi, i have added a new default driver. It will be available with the next snapshot. Please note, that current users have to import the new driver configuration (Menu Drivers => Install Default Driver Definitions). Otherwise the won't see it. For the changes, please have a look at default_drivers.xml <Bean Class="net.sourceforge.squirrel_sql.fw.sql.SQLDriver"> <name>LucidDB</name> <driverClassName>org.luciddb.jdbc.LucidDbClientDriver</driverClassName> <url>jdbc:luciddb:http://<server>[:<8034>]</url> <usesClassPath>true</usesClassPath> <jarFileNames Indexed="true"/> <identifier Class="net.sourceforge.squirrel_sql.fw.id.UidIdentifier"> <string>-52</string> </identifier> <websiteUrl>http://www.luciddb.org</websiteUrl> </Bean> Thanks Stefan Am 2011-09-03 20:33, schrieb Brandon Jackson: > Greetings, > > There is an opensource column based database who I would like to get > registered on the default list of drivers called LucidDB. Here is a link to > the wiki page where a graphic of manually setting up the driver in Squirrel > appears. > > http://pub.eigenbase.org/wiki/LucidDbSquirrel > For easy copy/paste reference > > Name: > LucidDB > > Example URL: > jdbc:luciddb:http://localhost > > Website URL: > http://www.luciddb.org > > Class Name: > org.luciddb.jdbc.LucidDbClientDriver > > Thanks ahead of time for either doing this for me or otherwise directing me > so I can modify a file and commit to the source tree. > > Brandon > ------------------------------------------------------------------------------ > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Brandon J. <usb...@gm...> - 2011-09-03 18:33:40
|
Greetings, There is an opensource column based database who I would like to get registered on the default list of drivers called LucidDB. Here is a link to the wiki page where a graphic of manually setting up the driver in Squirrel appears. http://pub.eigenbase.org/wiki/LucidDbSquirrel For easy copy/paste reference Name: LucidDB Example URL: jdbc:luciddb:http://localhost Website URL: http://www.luciddb.org Class Name: org.luciddb.jdbc.LucidDbClientDriver Thanks ahead of time for either doing this for me or otherwise directing me so I can modify a file and commit to the source tree. Brandon |
|
From: Robert M. <rob...@gm...> - 2011-08-30 13:03:53
|
Beautiful. I will look at your path and verify. I just ran into this during integration testing last night, so this is very timely ! Rob On Tue, Aug 30, 2011 at 7:54 AM, Jesus Marin <jes...@gm...>wrote: > Using trigger objects in Derby plugin results in continous errors stating > that cannot convert from BOOLEAN into INTEGER and trigger is not visualized > as expected > I attach TriggerSourceTab.java file with the solution. > The only change has been made in lines 47 and 51. > Now this plugin works as expected. > -- > > *Jesús Marín* > > > ------------------------------------------------------------------------------ > Special Offer -- Download ArcSight Logger for FREE! > Finally, a world-class log management solution at an even better > price-free! And you'll get a free "Love Thy Logs" t-shirt when you > download Logger. Secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsisghtdev2dev > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > |
|
From: Jesus M. <jes...@gm...> - 2011-08-30 11:54:09
|
Using trigger objects in Derby plugin results in continous errors stating that cannot convert from BOOLEAN into INTEGER and trigger is not visualized as expected I attach TriggerSourceTab.java file with the solution. The only change has been made in lines 47 and 51. Now this plugin works as expected. -- *Jesús Marín* |
|
From: Vladimir K. <vla...@ko...> - 2011-08-08 07:34:15
|
Hi, > Does anyone use Squirrel with Teradata? > There doesn't seem to be a Teradata plugin. Is anyone working on one? I use Squirrel with Teradata quite often, and yes, it would be great to have Teradata plugin available. I have also noticed Squirrel does not display Teradata macros (used more often than stored procedures in td, imo) in object tree view. Other td specific functionality I miss in Squirel concerns displaying object references and space summary or by amp. On Sat, Aug 6, 2011 at 10:35 PM, Dennis DiMaria <zin...@ya...> wrote: > I'm wondering if Subhabrata's code would work with Teradata stored procedures since only standard jdbc calls were used. > > Does anyone use Squirrel with Teradata? There doesn't seem to be a Teradata plugin. Is anyone working on one? > > -Dennis > > > > ________________________________ > From: Robert Manning <rob...@gm...> > To: Subhabrata Biswas <sub...@gm...> > Cc: squ...@li... > Sent: Friday, August 5, 2011 2:52 PM > Subject: Re: [Squirrel-sql-develop] Procedure execution plugin > > You are correct - the current Oracle plugin doesn't have the functionality > that you've described. Please submit a patch for your plugin here: > > http://sourceforge.net/tracker/?group_id=28383&atid=393416 > > You can attach the files that you want to contribute there in an archive > file. We can then take a look at how to integrate it into the existing > Oracle plugin or add it to the distro as a separate plugin. > > Rob > > On Fri, Aug 5, 2011 at 12:03 PM, Subhabrata Biswas < > sub...@gm...> wrote: > >> Hi Rob, >> >> I guess the Oracle plugin let's you execute procedures that don't have >> OUT parameters? Or did I get that wrong? I could not find a way to do >> that and hence wrote this plugin. This plugin shows the parameters in >> a table - let's you enter the values for input arguments and when you >> execute the SP, it shows the values of the OUT variables in the same >> table. >> >> Regards, >> >> -- Subhabrata >> >> >> On Fri, Aug 5, 2011 at 4:44 PM, Robert Manning >> <rob...@gm...> wrote: >> > Hello, >> > >> > The Oracle plugin that ships with SQuirreL today allows you to execute >> > stored procedures from the SQL editor. Can you give it a try and tell us >> > how your plugin is different or does a better job of it ? >> > >> > For bug reports you can file them here: >> > >> > http://sourceforge.net/tracker/?group_id=28383&atid=393414 >> > >> > Rob >> > >> > On Fri, Aug 5, 2011 at 6:43 AM, Subhabrata Biswas >> > <sub...@gm...> wrote: >> >> >> >> Hi, >> >> >> >> I needed a plugin for executing stored procedures in our Oracle >> >> database. I have developed the same and wish to contribute it back to >> >> the community. >> >> >> >> I had access to an Oracle database only - I have not tested this on >> >> any other database. However, I stuck to standard JDBC calls only in >> >> order to maximize its chances of working with other databases too. >> >> >> >> Is this plugin interesting to the community? If yes, how do I contribute >> >> it? >> >> >> >> In the process I have found a bug in core Squirrel SQL too (problems >> >> when a custom IMainPanelTab is closed - entry is removed from _tabPnl >> >> and not from _tabs in MainPanel::removeMainpanelTab()). Where do I >> >> report this bug? >> >> >> >> Best regards, >> >> >> >> -- Subhabrata Biswas >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >> >> The must-attend event for mobile developers. Connect with experts. >> >> Get tools for creating Super Apps. See the latest technologies. >> >> Sessions, hands-on labs, demos & much more. Register early & save! >> >> http://p.sf.net/sfu/rim-blackberry-1 >> >> _______________________________________________ >> >> Squirrel-sql-develop mailing list >> >> Squ...@li... >> >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop >> > >> > >> > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: John H. <jh...@im...> - 2011-08-07 20:24:28
|
On Mon, 8 Aug 2011, Subhabrata Biswas wrote: > John: the CallableStatement::execute() method returns a boolean and no > other code. Are you referring to some other API? Please let me know > and I'll look into it. Sadly, I'm not familiar with JDBC, but the documentation for CallableStatement::execute() says: This escape syntax has one form that includes a result parameter and one that does not. If used, the result parameter must be registered as an OUT parameter. ...so it may be that with Oracle (where SPs do not return anything) it's only returning a boolean. Have you tried using your plugin to call an Oracle function that returns (say) a string of characters? > This plugin does not show any resultset returned by an SP that some > databases allow. _That_ I wouldn't expect support for. If you're going to call an SP that returns result set(s), do it in the regular query window. -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jh...@im... FALaholic #11174 pgpk -a jh...@im... key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- Ignorance is no excuse for a law. ----------------------------------------------------------------------- 8 days until the 66th anniversary of the end of World War II |
|
From: Subhabrata B. <sub...@gm...> - 2011-08-07 20:12:04
|
Thank you John, Dennis and Rob for taking the time to respond to my mails. I believe the code is generic and should work with many databases - it will be great if you can test and verify - I can't do that since I don't have access to any database other than Oracle at the moment. I'll be, of course, willing to fix any issues that you may find. I'll post a screenshot tomorrow. It'll take me a day to package things properly and submit the code. Rob: I believe it should be a separate plugin since it can work with many databases. John: the CallableStatement::execute() method returns a boolean and no other code. Are you referring to some other API? Please let me know and I'll look into it. This plugin does not show any resultset returned by an SP that some databases allow. Regards, -- Subhabrata On Sat, Aug 6, 2011 at 2:44 AM, John Hardin <jh...@im...> wrote: > On Fri, 5 Aug 2011, Robert Manning wrote: > >>> This plugin shows the parameters in a table - let's you enter the >>> values for input arguments and when you execute the SP, it shows the >>> values of the OUT variables in the same table. > >> You are correct - the current Oracle plugin doesn't have the functionality >> that you've described. > > That sounds to me like a very attractive way to run SPs/functions with > _any_ backend. I would hope that it's generalizable. > > Does it also display the return code of the SP/function? That's useful to > know, too... > > -- > John Hardin KA7OHZ http://www.impsec.org/~jhardin/ > jh...@im... FALaholic #11174 pgpk -a jh...@im... > key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 > ----------------------------------------------------------------------- > Gun Control: The theory that a woman found dead in an alley, raped > and strangled with her panty hose, is somehow morally superior to > a woman explaining to police how her attacker got that fatal bullet > wound. -- L. Neil Smith > ----------------------------------------------------------------------- > Today: the 276th anniversary of John Peter Zenger's acquittal > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Squirrel-sql-develop mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > |
|
From: Dennis D. <zin...@ya...> - 2011-08-06 19:35:11
|
I'm wondering if Subhabrata's code would work with Teradata stored procedures since only standard jdbc calls were used. Does anyone use Squirrel with Teradata? There doesn't seem to be a Teradata plugin. Is anyone working on one? -Dennis ________________________________ From: Robert Manning <rob...@gm...> To: Subhabrata Biswas <sub...@gm...> Cc: squ...@li... Sent: Friday, August 5, 2011 2:52 PM Subject: Re: [Squirrel-sql-develop] Procedure execution plugin You are correct - the current Oracle plugin doesn't have the functionality that you've described. Please submit a patch for your plugin here: http://sourceforge.net/tracker/?group_id=28383&atid=393416 You can attach the files that you want to contribute there in an archive file. We can then take a look at how to integrate it into the existing Oracle plugin or add it to the distro as a separate plugin. Rob On Fri, Aug 5, 2011 at 12:03 PM, Subhabrata Biswas < sub...@gm...> wrote: > Hi Rob, > > I guess the Oracle plugin let's you execute procedures that don't have > OUT parameters? Or did I get that wrong? I could not find a way to do > that and hence wrote this plugin. This plugin shows the parameters in > a table - let's you enter the values for input arguments and when you > execute the SP, it shows the values of the OUT variables in the same > table. > > Regards, > > -- Subhabrata > > > On Fri, Aug 5, 2011 at 4:44 PM, Robert Manning > <rob...@gm...> wrote: > > Hello, > > > > The Oracle plugin that ships with SQuirreL today allows you to execute > > stored procedures from the SQL editor. Can you give it a try and tell us > > how your plugin is different or does a better job of it ? > > > > For bug reports you can file them here: > > > > http://sourceforge.net/tracker/?group_id=28383&atid=393414 > > > > Rob > > > > On Fri, Aug 5, 2011 at 6:43 AM, Subhabrata Biswas > > <sub...@gm...> wrote: > >> > >> Hi, > >> > >> I needed a plugin for executing stored procedures in our Oracle > >> database. I have developed the same and wish to contribute it back to > >> the community. > >> > >> I had access to an Oracle database only - I have not tested this on > >> any other database. However, I stuck to standard JDBC calls only in > >> order to maximize its chances of working with other databases too. > >> > >> Is this plugin interesting to the community? If yes, how do I contribute > >> it? > >> > >> In the process I have found a bug in core Squirrel SQL too (problems > >> when a custom IMainPanelTab is closed - entry is removed from _tabPnl > >> and not from _tabs in MainPanel::removeMainpanelTab()). Where do I > >> report this bug? > >> > >> Best regards, > >> > >> -- Subhabrata Biswas > >> > >> > >> > ------------------------------------------------------------------------------ > >> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > >> The must-attend event for mobile developers. Connect with experts. > >> Get tools for creating Super Apps. See the latest technologies. > >> Sessions, hands-on labs, demos & much more. Register early & save! > >> http://p.sf.net/sfu/rim-blackberry-1 > >> _______________________________________________ > >> Squirrel-sql-develop mailing list > >> Squ...@li... > >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop > > > > > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Squirrel-sql-develop mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-develop |
