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?
Related
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
I am trying to evaluate Gradle as next-gen build tool for some of my future projects.
Steps I've done so far:
I have Java 7 installed on my machine.
Installed Gradle 2.0
Installed Spring Tool Suite 3.6.1, went to dashboard and added support for
Gradle and installed also Groovy-Eclipse package.
Now when I start Gradle projects from scratch or I clone some of the projects from github,
I am not able to get context sensitive help, like Ctrl + Space to autocomplete stuff in
build.gradle file.
I was reading a lot of documentation on net about this, and couldn't find proper answer, so if someone can give me some idea is it working?
Previously I was using Maven, and m2-eclipse, so when I type in pom.xml I am able to do Ctrl + Space which prevents me to make typo mistakes.
NOTE: Just please note that I've enabled Gradle DSL support for my Gradle projects.
Thank You
Gradle's build language is much more dynamic, extensible, and powerful than a Maven POM, and hence it's much harder to develop full IDE support for it. Recent versions of the Eclipse Gradle Plugin have limited editing support, and work is underway to take it to the next level. IntelliJ 14 is already further along, but expect to see further improvements there as well.
Is there a plugin or sth. else for Gradle that informs you when there are new library versions available for a certain depedency?
Might be difficult if some libs do not stick to well-known version conventions but for the others I think it should be possible to find out!?
If there is not, any hints how to implement this feature are appreciated.
Thanks
No such plugin ships with Gradle. There might be a third-party plugin, but I'm not aware of one. To implement this, you would iterate over a configuration's resolved dependencies (using the configuration.resolvedConfiguration or configuration.incoming API) and query some website (e.g. http://search.maven.org) or web service for latest versions. For API details, see the Gradle Build Language Reference.
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.
How do I know what version of a Maven plugin to use?
For example, where on the horrible Maven website can I find a list of versions of the compiler plugin?
http://maven.apache.org/plugins/maven-compiler-plugin/
Here is what I do
Go to http://mvnrepository.com
Search for maven-compiler-plugin
You should find the first one is the one you need. http://mvnrepository.com/artifact/org.apache.maven.plugins/maven-compiler-plugin
Find the one with the latest version and use that one
The above works because maven repo also has the latest plugins. Hope this helps.
Presumably, you're looking for the issue tracker, which shows issues, versions, changelogs, etc. On just about any of the "horrible" Maven plugin pages, you'll find a link to the issue tracker on the left side under "Project Information".