Here's some crucial information shared by Matt Burgess in one of the mailing lists:
With the release of Pentaho 6.0, I wanted to let you know that there are some important changes coming, and some may break your plugins, "glue code", etc. This often happens at major release boundaries, so hopefully this won't come as a huge surprise.
Pentaho has upgraded their use of VFS libraries from version 1.x (a custom version forked from the Apache project) to basically Apache VFS 2.1-SNAPSHOT. We are working with the project maintainers to release a proper 2.1 so we don't have snapshot artifacts in our release. In fact we have locked down a particular commit in the 2.1 branch and have built our own release version for Apache VFS 2.1.
The relevant commits are here:
https://github.com/pentaho/pentaho-kettle/pull/1595
https://github.com/pentaho/pentaho-kettle/pull/1681
How does this impact you? If you use org.apache.commons.vfs.* or KettleVFS and consume the org.apache.commons.vfs.FileObject or other VFS1 classes, then your code will no longer compile against 6.0 artifacts. If you use VFS 1 by itself and include it as a plugin dependency, this may work ok, unless you try to "trade objects" between your plugin and other Kettle classes.
To upgrade, you should be able to simply change the package name from org.apache.commons.vfs.* to org.apache.commons.vfs2.*. If your code still won't compile, please consult the above pull requests to see where other changes were needed.
In general, a good rule of thumb at major release boundaries is to:
As usual you can direct questions for the community in the forums or in this Google Group.
More...
With the release of Pentaho 6.0, I wanted to let you know that there are some important changes coming, and some may break your plugins, "glue code", etc. This often happens at major release boundaries, so hopefully this won't come as a huge surprise.
Pentaho has upgraded their use of VFS libraries from version 1.x (a custom version forked from the Apache project) to basically Apache VFS 2.1-SNAPSHOT. We are working with the project maintainers to release a proper 2.1 so we don't have snapshot artifacts in our release. In fact we have locked down a particular commit in the 2.1 branch and have built our own release version for Apache VFS 2.1.
The relevant commits are here:
https://github.com/pentaho/pentaho-kettle/pull/1595
https://github.com/pentaho/pentaho-kettle/pull/1681
How does this impact you? If you use org.apache.commons.vfs.* or KettleVFS and consume the org.apache.commons.vfs.FileObject or other VFS1 classes, then your code will no longer compile against 6.0 artifacts. If you use VFS 1 by itself and include it as a plugin dependency, this may work ok, unless you try to "trade objects" between your plugin and other Kettle classes.
To upgrade, you should be able to simply change the package name from org.apache.commons.vfs.* to org.apache.commons.vfs2.*. If your code still won't compile, please consult the above pull requests to see where other changes were needed.
In general, a good rule of thumb at major release boundaries is to:
- before the Pentaho release, compile your code against the latest libraries (6.0-SNAPSHOT at this point is good enough, but I think the "real" ones are 6.0.0.0-353)
- after the release, test your plugins (original and/or recompiled) by dropping them into the data-integration/plugins folder, make sure they still operate successfully.
- if you need to re-release for 6.0, please update your entries in the Marketplace.
As usual you can direct questions for the community in the forums or in this Google Group.
More...