Is it possible to extend generic extension without messing the source codes? #9044
Unanswered
deceits
asked this question in
DBeaver Development
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
System information:
Windows 10, JDK 1.8, Eclipse RCP 2020-03
7,1
Connection specification:
H2 (2019-10)
Describe your question:
I want to extend the functions of Generic extension in DBeaver without messing
the source codes, so I am trying to create a new extension in DBeaver. The steps I took are following:
Copy-and-paste in org.jkiss.dbeaver.ext.h2 to a new project say org.jkiss.dbeaver.ext.demo
Refactored the class and package names from h2 to demo
Update pom.xml
Update plugin.xml
Update MANIFEST.MF
Move the demo project from workspace to DBeaver/plugins directory
Refresh DBeaver/plugins. The new demo plugin project will show up.
Right-click and select Import as Project
Make sure everything compile.
Add new module entry for demo plugin in DBeaver plugin/pom.xml
Finally, register demo plugin to plugin.xml in generic extension package
To test it out I started DBeaver from Eclipse and create a new connection. In the database selection screen, I can see the Demo database that I created. Used it. Then in the JDBC setting screen, enter H2 JDBC setting (it is actually H2). I can connect and browse the H2 database. Everything seems to be fine.
Now I want to change the tree layout. I copied the dataSourceProvider extension (without drivers and driver-properties) in generic plugin.xml to demo extension and made some changes to it. Restart Dbeaver. The tree layout is not taking effects but always uses the layout in generic extension.
Is this the appropriate? What went wrong? Thanks .
Beta Was this translation helpful? Give feedback.
All reactions