I've spent about a day on Google trying to find an answer to this, but to no avail.
Our instance of JIRA has a customised workflow for our project and we would like to use the NetBeans JIRA module to transition issues to the next step in our workflow ("Testing") when our developers commit a change.
However, the JIRA module in NetBeans does not offer any transitions in either the Commit dialog or the Edit Issue window.
We've tried a vanilla JIRA instance with the default workflow and that works fine, but we want a more detailed workflow for our project.
I can't even find an author or even source for this module.
Any help would be appreciated.
I eventually got around to downloading the entire NetBeans source and picked through the JIRA plugin code.
The workflow IS hard-wired to the standard default JIRA workflow.
However, after consultation with the author of the plug-in, we have come up with a way to make the plug-in compatible with any workflow.
Hopefully an update to the plug-in will be available from the 7.3 beta version of NetBeans.
Related
I've downloaded SocialEngine source code, added few plugins to the website I'm testing.
Now, I'm trying to customize the plugins' and SocialEngine's code to fit my use cases.
How can I make a change to the source code of any of these plugins through Eclipse and reflect that on my website? I want to be able to debug the source code from Eclipse.
I understand that I need to create a module through SocialEngine SDK and install it via the package manager tool, but, I've already got the module source code for the plugins I mentioned above. So, speaking of a full development IDE like Eclipse, how can I tweak this code and have it deployed to my website and debug through it as well?
Thanks!
For customizations, you should understand, the plugins releases upgrades and bug fixes. So, you should add your work in such ways, that you merge easily with those updates regularly.
For debugging you should understand and follow zend framework application, on which socialengine is built.
Would be better, if you ask specific issues you are having in development.
Then, you would have better answers with insights.
Maybe this is helpful, for now.
After a terrible decision by Atlassian to discontinue the Eclipse Connector for Jira, it seems to me like there is no way to use Mylyn in Eclipse Neon to integrate with Jira. Is it just me? Are there any workarounds?
I tried installing Tasktop Dev Pro but it failed complaining about a jar not found in the Update Site. Besides, it doesn't seem like a proper solution since it brings a lot more than we need
It definitively works with Eclipse Oxygen (still), using the Updatesite from atlassian, which is also mentioned on the Bitbucket OpenSource project. Please note, the help page, which is also hosted there, offers a download link to use the updatesite offline. Since the actual data there is in fact hosted by atlassian, let's just hope they don't drop support for hosting those files.
Update Site URL: http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.7
I got the Version: 3.2.5.v20150427
As far as I can see, the support is still fully functional, including the ability to create new tickets, add comments and manage ticket lifecycle
PS: I needed to configure the proxy settings accordingly (Jira is hosted in-house here, so we need an exception rule for the proxy used for internet connection by default).
I have not fought with Neon yet, but in Mars which is also not officially supported, I was able to get Jira partly working using this install URL:
Atlassian Connector for Eclipse 3.7 and later - http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.7
It allows me to see my task list, select Jiras and it will remember working sets for each Jira I select, but one important feature to me I cannot get to work is on the Team Synchronizing perspective I CANNOT add changed files to a change set tied to the Jira like I can in Luna.
I can see incoming changes by jira tied change sets, but not create out going jira tied change sets.
I have broken my Mars install many times trying to update Mylyn but if I take the 3.20 version it foo-bars my install.
I'm trying to complete The Official Documentation for Hooks in Liferay. About halfway down that page, there is a note.
Note: If the Liferay server prints the following message to your console,
the Marketplace Portlet and Portal Compatibility Hook must not already be
deployed on your server.
"Plugin example-hook requires marketplace-portlet, portal-compat-hook"
I do get this message, so I attempt to follow the instructions:
You can fork and clone Liferay’s liferay-plugins project from GitHub, checkout the
respective branch and/or tag, and deploy each plugin. You can install the Plugins
SDK in Liferay IDE and import each plugin and deploy them. Here is information on
each of the plugins:
Marketplace Portlet (marketplace-portlet) - is available at liferay-
plugins/portlets/marketplace-portlet.
Portal Compatibility Hook (portal-compat-hook) - is available at liferay-
plugins/hooks/portal-compat-hook.
This is as much information as I can find about setting up the marketplace-portlet.
So I clone, and add the whole repo as an existing Eclipse project, not a liferay project. I check the checkbox for look for nested projects, find and add the marketplace portlet and hit finished. Then I assume to fix the build path by changing plugin-master to portal-6.2.x
As you can see, this solves more than half of the missing .jars, but the ones that are still missing claim the build path is the same, so they are missing from the repo, or need to be built. I have no idea which.
So, how do I deploy the marketplace-portlet?
As requested, combining our comments into an answer:
"Have you tried installing fresh again?" ;)
To make it worth a real answer: The typical bundle installation comes fully runnable (the installation instructions are: unzip, start tomcat) and contains everything you need - especially in a development environment.
If you use Liferay IDE or the EE equivalent Developer Studio (both based on eclipse), they even know how to unzip the server themselves (a necessity if you're developing/redeploying ext plugins).
Glad to be able to help.
This problem happened repeatedly. Something about a bad deploy could cause Liferay to remove its own Marketplace portlet*.
Rather than re-install each time, I grabbed the Marketplace Portlet.war from Liferay's Get Marketplace Portlet page and would deploy it using the Liferay Control Panel.
*: I don't have an exact steps to reproduce, sorry.
For the last few years, we've used m2eclipse without issue, however it seems that the "new" version (ie. m2e) has broken backwards compatibility - something that I really hope that I've just misinterpreted.
My problem is this: I'd like to be able to build my existing project with the minimal amount of fuss. I don't have the time to write connectors for the 3 plugins that don't have them - my understanding of 2 of them is quite limited in the first place, and I have no understanding of the Eclipse plugin mechanism - but I'd still like to be able to use Eclipse to build the project.
Can I achieve this without reverting back to the old (working) version m2eclipse?
Am I correct in my understanding that there is no way to upgrade without having a connector for each plugin?
It seems as if my understanding was correct if this blog post is anything to go by:
http://grumpyapache.blogspot.com.au/2011/08/mess-that-is-m2e-connectors.html
M2E can invoke a plugin as part of the automatic build process if, and only if, there is a connector for the plugin, or you specially configure the plugin
... which means that:
You can no longer use your own plugins in the Eclipse automatic builds, unless you create a connector for the plugin, or create a project-specific configuration
The post goes on to list the issues with this approach. These are many of the same issues I have with the approach.
RANT: So there you have it - the m2e approach does suck as much as I feared it did! I was beginning to think it was just me!
I am currently trying to package the best suite for a development team. We are naturally thinking about the following as the foundation
Eclipse
Mylyn
Hudson (Jenkins)
Subversion (Git, Mercurial, ...)
We are not yet sure about the task manager. JIRA is very interesting as it can be bind to Mylyn and Eclipse IDE.
Moreover, we would like to add the services offered by twitter microblogging like sharing expertise, ideas between persons, groups, teams on certain projects in our development environment.
Confluence seems the next step after JIRA (as proposed by the same company).
Other tools like internal twitter (I am thinking about Yammer) and Social Text may fulfill our requirements.
Any more suggestions?
No set is complete without Subversion.
Some arguments in favor of JIRA:
There is currently an open plugin competition 'Codegeist'. One of the entries providing a microblogging capability to JIRA
Check out http://codegeist.atlassian.com/entry/166220
JIRA Hero is also very promising - it allows you to introduce the concept of badges to JIRA (comparable to stackoverflow).
http://codegeist.atlassian.com/entry/166416
Francis
Trac is an open source Task Tracker and wiki, it also integrates with Subversion to give you a web interface for your source code:
http://trac.edgewall.org/
You can get a plugin for it called Agilo, which turns it in to a scrum management tool:
http://www.agile42.com/cms/pages/agilo/
You can see an example of what Trac looks like with the agilo plugin here:
https://dev.agile42.com/wiki
The Trac site itself is what trac looks like without the agilo plugin.
I think Jira is more polished than Trac and has better integration with a greater number of tools. I don't know for instance if Trac integrates with Mylyn, so you may have to do a bit more manual configuration than with Jira, but you do avoid license fees.
I for one have found the wiki as usable as Confluence (I actually prefer Trac), and for tracking tasks it's good. It can be a pain if you have to re-organise sprints, but overall it's fully featured, and still an active project.
Hudson has a Trac plugin.