garypedretti / liquibase-eclipse-plugin Goto Github PK

The version of liquibase to use should be selectable in the preferences. By 
default the latest available version should be used.

What steps will reproduce the problem?
1. Run an update script.
2. Check the FILENAME in DATABASECHANGELOG

What is the expected output? What do you see instead?
It should just include the file name, not the path. Currently the workspace 
relative path is included.
The reason for this is that scripts run from applications just include the file 
name, so this should match that behaviour.

Add tycho to the maven build.
Ensure plugin builds correctly through maven.
Prerequisite to adding automated UI testing.

Currently the only way to get the plugin to detect Liquibase scripts in the 
workspace is to flag a project as a Liquibase project (Right click 
project->configure->convert to Liquibase Project). The need to do this is not 
obvious to the user.

A button should be placed on the Liquibase Scripts view and on the rollback 
wizard. This button will open up a dialog containing a checkbox list of 
projects with the current Liquibase projects checked. The user will then be 
able to check/uncheck projects to add/remove the Liquibase nature.

The rollback wizard summary page should be refreshed after new projects are 
flagged and the subsequent build complete so that it can locate missing scripts 
in the workspace.

Create an Update Site project to support installation of the plugin via Eclipse 
"Install New Software" and Marketplace.

With the following structure:

-all.xml
-folder
  |-file1.xml

Where all.xml imports file1.xml running the script works, but the rollback 
wizard is unable to locate the imported file.

Attempting to generate a Liquibase script from an existing database fails with 
the following exception using Liquibase 3.0.1. Reported against a mysql 
database.

Jul 30, 2013 9:32:00 AM com.arjuna.ats.arjuna.recovery.TransactionStatusManager
addService
INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatus
Service on port 49314
Jul 30, 2013 9:32:00 AM com.arjuna.ats.internal.arjuna.recovery.TransactionStatu
sManagerItem <init>
INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 49314
Jul 30, 2013 9:32:00 AM com.arjuna.ats.arjuna.recovery.TransactionStatusManager
start
INFO: ARJUNA012170: TransactionStatusManager started on port 49314 and host 127.
0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
java.lang.NullPointerException
        at 
liquibase.diff.core.StandardDiffGenerator.compareObjectType(StandardD
iffGenerator.java:62)
        at 
liquibase.diff.core.StandardDiffGenerator.compare(StandardDiffGenerat
or.java:38)
        at 
liquibase.diff.DiffGeneratorFactory.compare(DiffGeneratorFactory.java
:81)
        at 
com.svcdelivery.liquibase.eclipse.v3.LiquibaseServiceV3.diff(Liquibas
eServiceV3.java:119)
        at 
com.svcdelivery.liquibase.eclipse.internal.ui.GenerateScriptWizard$1.
run(GenerateScriptWizard.java:67)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Jul 30, 2013 9:33:01 AM com.arjuna.ats.arjuna.coordinator.TransactionReaper chec
k
WARN: ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffac113334:c0a3:
51f7ce60:2 in state  RUN
Jul 30, 2013 9:33:02 AM com.arjuna.ats.arjuna.coordinator.BasicAction checkChild
ren
WARN: ARJUNA012095: Abort of action id 0:ffffac113334:c0a3:51f7ce60:2 invoked wh
ile multiple threads active within it.
Jul 30, 2013 9:33:02 AM com.arjuna.ats.arjuna.coordinator.CheckedAction check
WARN: ARJUNA012108: CheckedAction::check - atomic action 0:ffffac113334:c0a3:51f
7ce60:2 aborting with 1 threads active!
Jul 30, 2013 9:33:02 AM com.arjuna.ats.arjuna.coordinator.TransactionReaper doCa
ncellations
WARN: ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction
 Reaper Worker 0,5,main] successfully canceled TX 

With the following structure:

-all.xml
-folder
  |-file1.xml

Where all.xml imports file1.xml running the script works, but the rollback 
wizard is unable to locate the imported file.

Build and test the update site for the 1.2.0 release.
Add zipped update site to downloads page.
Add announcement to web site.

Add context menu for "drop all" command. If an IConnectionProfile is selected 
then the wizard will just allow selection of the schema (default schema 
automatically selected).
For any other selection the wizard will first allow the data source to be 
selected.

This will provide the functionality to generate changelog files from existing 
database schemas. Access to the functionality will be via:

1. The main explorer context menu - select data source, schema and target file.

2. The data source view.

What steps will reproduce the problem?
1. Open the Liquibase Data Sources view.
2. Right click an installed change set and select Rollback.
3. Check finish button.

What is the expected output? What do you see instead?
The rollback wizard should locate the relevant scripts for the change set in 
the workspace. If all scripts are located the finish button should be enabled. 
If they are not located the user should be able to manually select a script.

Currently the scripts are not located and the manual selection is not yet 
implemented.

What steps will reproduce the problem?
1. Expand a data source in the Liquibase Data Source view
2. Check the installed change sets
3. Run a script against the data source
4. Check the view for the newly run change sets

What is the expected output? What do you see instead?

The change sets from the newly run scripts should appear. Currently the view is 
not being refreshed.

the view should get refreshed automatically on completion of an update/rollback 
script. It would also be useful to include a manual refresh button/menu item.

Create a feature project to include:

- Liquibase Eclipse Plugin
- Liquibase OSGi bundle

The context menu for "Generate Liquibase Script" should only show for Data 
Sources. Currently it shows regardless of the selection.

What steps will reproduce the problem?
1. Run a changelog script against a valid eclipse DataSource

What is the expected output? What do you see instead?

In the Liquibase Results list, to be able to see information about the success 
or failure of the run.

Instead, I only see a generic marker with zero indication of what went wrong, 
which makes it impossible to fix the script.

What version of the product are you using? On what operating system?

Liquibase Eclipse v1.2.1.201309060948 on Eclipse Luna (4.4.1.20140925-1820), on 
Ubuntu Linux 14.4 LTS (fully updated)

1. The background colour of the label doesn't match the page background.
2. There are no column headers on the table.
3. The version number should be a separate column.
4. Label should be top-aligned.

Create a general project icon.
Create an icon for adding/managing Liquibase Projects.

Release 1.2.0 has been tested against Juno and Indigo but not Kepler.

Generation of Liquibase scripts in particular needs testing as there have been 
reports of ut not working with Kepler.

The default Liquibase logger sends output to System.err. Add a custom logger to 
redirect the output to the Eclipse log.

Add wizard to support diffing of two data sources.

The different liquibase versions are provided as OSGi services, but they 
currently report their version numbers as v2 and v3. They should report the 
exact version number of the library. 

What steps will reproduce the problem?
1. Create a project containing a liquibase script.
2. Convert it to a Liquibase project.
3. Check the Liquibase Scripts view, the script should be there.
4. Restart Eclipse
5. Check the Liquibase Scripts view again, the script should still be there.

What is the expected output? What do you see instead?

The script is not in the Liquibase Scripts view after restart. Either the 
builder needs to be re-invoked on startup or the builder should persist/reload 
the list of located scripts.