-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 4.0 - Beta 2
-
Component/s: Documentation - All
-
4
I currently went through the process of upgrading the bamboo plugin from plugins 1 to plugins 2 when i hit an interesting problem.
1) Your plugin can not contain any classes in packages that also exist in jira
2) Our plugin put all action classes inside com.atlassian.jira.web.action to make use of the automatic class resolution.
The solution is to move your action classes to a plugin specific directory and explicitly define the full class name in your atlassian-plugin.xml e.g
<webwork1 key="bambooServerConfig" name="Configure Your Bamboo Server"> <actions> <action name="com.atlassian.jira.plugin.ext.bamboo.web.ViewBambooServers" alias="ViewBambooServers"> <view name="success">/templates/plugins/bamboo/viewServers.vm</view> </action> </actions> </webwork1>
It would be great if this could get documented somewhere.