![]() ![]() For example, Repositor圜reatedEvent is now in .repository Java model The monolithic package has been broken down and the events it formerly contained have been moved into subpackages. Stash 3.x .StashEventīitbucket 4.x .ApplicationEvent ![]() Java User modelīitbucket 4.x .ApplicationUser Java Authentication ContextĬom.īitbucket 4.x .AuthenticationContext Java Event model For example, NoSuchRepositoryException is now in the package. The exceptions it previously contained have been moved into the module they belong to. The monolithic package has been removed. Changing this value could lead to data loss, and will cause you to lose review and download history on the Atlassian Marketplace.įor example, you would replace the variables below with the values for groupId and artifactId in your pom.xml.Ĭom. This is often defined in terms of the maven groupId and artefactId of your plugin. This value is used by Atlassian Marketplace and other parts of Bitbucket Server as a unique identifier for your plugin. ![]() The value of your app key, as defined within the atlassian-plugin.xml file, must not change. How to update your app The app key of your plugin must not change There is more detail on these changes below.Īny methods or modules that were deprecated for removal in 4.0 have been removed. For API Soy templates, these are now also under the bitbucket namespace - is now .Īnother front-end change is that most keys – including Form Fragments, Web Panel & Section locations, and Web Resource apps – have been moved to Bitbucket namespaces. ![]() For example, stash/api/util/navbuilder is now bitbucket/util/navbuilder. Non-API modules will be under bitbucket/internal. AMD Modules, previously found under stash/api/*, are now bitbucket/*. Our Javascript and Soy API modules have moved to the Bitbucket namespace. These new API modules contain all of the code that is published for plugin developers to use. In 4.0, the exported APIs from all of our plugins have been extracted into separate modules (like with the stash-build-integration example, the build API is now in :bitbucket-build-api). This was a frequent source of plugin issues because plugin developers attempted to use our internal classes. However, only a small portion of the code in that jar was exported. You can consult the latest Stash 3.x documentation for details on what replacement method to use if the new method is not obvious.įinally, several of our bundled plugins were exporting API (our :stash-build-integration plugin, for example), which meant plugin developers added dependencies on that jar. Most of these had existing replacement methods in place, but some were removed without replacement. In addition to the repackage, we've also removed all APIs from the codebase. The Bitbucket Server team updated over 100 apps internally and the process was quite straightforward using refactoring support in modern IDEs. The largest change was we renamed our package namespace from to, but this should also be a simple change when you update your plugins. While Stash 3.x supports running on Java 8 Bitbucket Server supports compiling to Java 8. One of the exciting changes with this release is the new JDK minimum requirement of 1.8, that allows you to use a wide new array of language features in your app code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |