1. Atlassian
  2. Project: Atlassian
  3. amps

Source

amps /

Filename Size Date modified Message
amps-product-archetypes
amps-product-plugins
maven-3-tests
maven-amps-dispatcher-plugin
maven-amps-plugin
plugin-module-codegen-api
plugin-module-codegen-engine
plugin-module-codegen-maven-client
sdk-installer
standalone
test-codegen-jar-classes
108 B
Split maven.version into separate build and bundleds versions. The former is needed to enforce a version only for building AMPS itself, while the latter is needed for picking up and packaging a version of Maven to patch and bundle with the SDK, and for use within the plugin. Also added a shade artifact to the .gitignore, which due to the way Maven works, needs to go in the same directory as the POM, rather than in the target directory
10.2 KB
- AMPS-142: apply apache license
2.4 KB
Update Bamboo and PROE links in README
18 B
Fix bug AMPSDEV-49: The AMPS maven plugin does not respect the <includes> part of the global resources configuration
17.8 KB
Merge remote-tracking branch 'origin/6.2-stable'

Welcome to the Atlassian Plugin SDK Source!

Using the Plugin SDK

Please consult our Getting Started documentation to learn how to build Atlassian Plugins. We also have a quick-start tutorial for those who want to get stuck straight in to it.

Reporting a Problem

If you're having problems with the Plugin SDK, please go to Atlassian Answers, our Q&A community site, and ask for help. To report a bug, use the AMPS JIRA Project. If you're not sure if you've hit a bug, or just a usage problem, try Answers first!

Contributing

This project is licensed under the Apache 2.0 Software License. External contributors are welcome, but you must agree to the terms of the Atlassian Contributor License Agreement and then sign and submit a copy of the agreement to Atlassian.

Rules of Engagement

If you want to submit bug fixes or improvements to the Plugin SDK, please assist us by adhering to these simple guidelines:

  1. Do not commit directly to the primary branch. Please either fork this repo or use a 'feature branch' and then create a Pull Request for your changes to be accepted. The Developer Relations team will review and merge your work.
  2. Create a JIRA Issue for any changes and prefix your commit messages with the relevant issue key.
  3. You are responsible for testing and verifying your own changes. Yes, the Plugin SDK is a complex beast that must run on a variety of platforms against a variety of Atlassian products and must remain very backwards compatible and this means making changes can be difficult - please be diligent in this and help make life better for everyone who has to work on this project! :)

Atlassian developers, please see The Platform Rules of Engagement (go/proe).