I have a plugin which is custom built for Jira 6.x and I want to make the same plugin to work for Jira 7.x. What are the ways to do this?
Say the only resource I have is the .jar plugin file which has all the information about classes, dependencies, related to old version of jira.
If I make changes to the pom.xml file and upload the addon to jira, will it work with Jira 7.x?
Error From Log:
/rest/issueNav/1/issueTable [c.atlassian.ozymandias.SafePluginPointAccess] A LinkageError indicates that plugin code was compiled with outdated versions.Unable to run plugin code because of 'java.lang.AbstractMethodError - null'.
Thank You.
There are API changes which requires source code changes, some details here:
https://developer.atlassian.com/jiradev/latest-updates/preparing-for-jira-7-0/jira-7-0-api-changes
Related
Since version 2.2.0 Tycho has introduced a new feature to allow using maven artifacts in PDE target platforms, and here's the how-to. Following its instructions I have included an artifact of Saxon-HE into my target platform. I can see the wrapped OSGi bundle of Saxon after ticking the Show Location Content option in the Target Definition Editor. Also I ran mvn clean verify command to make sure that the artifact is downloaded into my computer. However,
as I began to try to import the package into my Eclipse plugin code, I found no suggestions from this package.
When I tried to include the package as a feature in the Product Editor, I couldn't find any option.
In addition, when attempting to include it as required plugin / imported packages in the Plugin Editor, there was no option, too.
What's more, the product produced by mvn clean verify did not contain such plugin as Saxon-HE after checking my whole RCP project.
All the efforts in vain above made me wonder how I can use a maven artifact in my plugin development. I desperately need the functionalities Saxon-HE provides with to enhance my plugin. Anyone experienced sharing your expertise?
-- 2021.08.13 update --
Manually I included this plugin in the plugin list of my RCP project via source file editing. Its jar file appeared in the plugin folder of the product. But anyway I was not able to validate the availability of the library in the dependency tab of the plugin manifest editor as shown in Vogella's tutorial. Restarting the IDE did not help, either. This might mean that I have to manually code the source code without the content assistance.
I am trying to implement SOAP services in my app, the best plugin I found is CXF, but I couln't install it, it looks like that I should put some additional repository.
I raised an issue in the source page, but if someone has faced this before, can share the solution plz?
If you are trying to use version 3.1.2 of the plugin, you want org.grails.plugins:cxf:3.1.2, not org.grails.plugins:grails-cxf:3.1.2.
The problem is that the plugin's documentation talks about to use the version 3.1.2, but the latest version in the repository is the 3.0.9
That feature was very useful for us, but after upgrade sonar 5.1 to 5.6 we have missed it.
Reading this topic : Sonarqube dependency feature missing i want to ask if you know a similar alternative to check dependency libraries for a proyect.
We was using this feature for check 3PPs dependency shared between projects and check what other projects was using the same 3pp.
Do you know a similar tool?
I'm new(ish) to Java/Netbeans/ControlsFX. I know about Javadoc and would like NetBeans to show me javadoc for ControlsFX. I see the online version of the docs for ControlsFX but that defeats (at least part of) the purpose of using an IDE? I know how to add the doc zip file in NetBeans but I don't see the doc file for ControlsFX.
Am I missing something?
Found this lately. ControlFx java doc. You can manipulate the version number at the end of the url to get to page of any other version of the doc if it is in existence. Download the jar version on that page to use it locally controlsfx-version-javadoc.jar. Then you can add the jar in your netbeans Javafx project.
I am trying to write my pom.xml for a multimodal flex application. I have been using this resource as an example:
http://www.sonatype.com/books/mvnref-book/reference/flex-dev-sect-creating-with-archetype.html
I am using M2E v1.01 but I am faced with a number of 'Plugin execution not covered by lifecycle configuration" errors. As far as I can see - there are no m2E connectors available to resolve this and I have tried all the Maven advice I can find - to include:
Clean
Update dependencies
Update project configuration
The problem only occurs if the project is declared as swc or swf package. My next move to ask Eclipse to 'permanently mark goal as ignored' - which seems a little brash.
Any advice would be appreciated.
Thanks in advance.
With STS 2.8.0, we have upgraded m2eclipse to be version 1.0. However, this can cause a bit of trouble with existing projects. I wrote a blog on this a couple of months ago.
http://blog.springsource.org/2011/10/18/upgrading-maven-integration-for-springsource-tool-suite-2-8-0/
Essentially, the new architecture for m2eclipse requires that each maven plugin you use must be mapped to one Eclipse plugin to handle the plugin's execution inside of Eclipse. This obviously causes problems since not every maven plugin author has the knowledge or time to create also create and maintain an Eclipse plugin.
By marking the plugin as ignored, you are saying that the plugin should never be executed inside of Eclipse (implying that whenever you need it to be executed, you will do so from the command line). Once marked as ignored, you can then change it to execute, which means that it should always be executed whenever the associated lifecycle is performed in Eclipse. This may cause performance problems, and so only do it if you know the risks.
If all this is too much for you, then STS provides a downgrade option to revert to an older version of m2eclipse. Go to the Dashboard extensions page. Unfortunately, you will have to manually revert all changes to your .project and .classpath files (we provide an auto-upgrade mechanism, but not a downgrade mechanism...presumably everything is in version control).
Any questions or problems should be sent to the STS forums:
http://forum.springsource.org/forumdisplay.php?32-SpringSource-Tool-Suite
You can check this alpha connector "Flex Maven Integration for Flash Builder" on the eclipse marketplace: http://marketplace.eclipse.org/node/648556.