|
I'm in a bit of a weird situation. In May last year I made a fork of the S3 plugin on my private server, added a bunch of features I needed and then bumped the version to 0.2 without changing the artifactId (I don't know maven very well). Now that 0.3 is out jenkins is offering to upgrade me to the new release ![]()
As a short term fix I changed the artifactid and turned off the original plugin, but ideally I'd like to re-apply my changes to the new release (some features I added are also in 0.3, but not all of them) and submit a pull request.
However I'm currently hung up on actually loading my settings in 0.3. I'm experimenting with the migration on a testing server, and when I turn on the new plugin Jenkins can't load the data from the old plugin - it's looking for the old com.hyperic.hudson.plugin.S3BucketPublisher and com.hyperic.hudson.plugin.Entry classes. It looks like this changed in a commit from September last year.
Am I missing something, or was this a problem for anyone migrating between the 0.1 and 0.2 releases? Do I just have to suck it up and hand edit the class references in my config to load the new plugin?
|
