I'm not. I guess I just used a bad example :) On Thursday, October 31, 2013 5:45:10 AM UTC-4, Stephen Connolly wrote: > > I hope you are not using the org.jenkinsci.plugins package name bare > without any plugin prefix... > > e.g. org.jenkinsci.plugins.somename is ok, but org.jenkins.plugins is not > as you could hit the package must be from same jar style classloader > conflicts if you haven't given yourself a unique namespace > > > On 30 October 2013 22:41, Eric Lordahl <[email protected] <javascript:>>wrote: > >> I've moved around some packages in a plugin and when installing to >> Jenkins, lose all job settings (build steps). Does anyone have any >> examples of how to migrate data from an old version to a new version when >> the java package layout has changed? Config example below: >> >> Old-- >> <org.jenkinsci.plugins.*package*.Class plugin="plugin-1"> >> .. >> </org.jenkinsci.plugins.*package*.Class> >> >> >> New-- >> <org.jenkinsci.plugins.Class plugin="plugin-2"> >> .. >> </org.jenkinsci.plugins.Class> >> >> >> I want the settings in the first example, to migrate to the second >> example. >> >> Thanks, >> Eric >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > >
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
