Bug 168018 - Support Trac integration through core Bugtracking system
Support Trac integration through core Bugtracking system
Status: NEW
Product: connecteddeveloper
Classification: Unclassified
Component: Issuetracking Framework
6.x
All All
: P1 with 101 votes (vote)
: TBD
Assigned To: Tomas Stupka
issues@connecteddeveloper
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-02 09:36 UTC by vernons
Modified: 2013-12-14 16:06 UTC (History)
17 users (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vernons 2009-07-02 09:36:50 UTC
Add support through the built-in bugtracking system to support Trac integration. Ideally support should extend not only to defects, but also task support 
which is often used with other Trac plug-ins such as the Burndown plug-in.
Comment 1 puce 2009-08-05 10:41:02 UTC
I think this is OS independent -> OS: ALL
Comment 2 sskjames 2009-08-14 09:02:03 UTC
Trac integration would be great.
Comment 3 jfeid 2009-10-10 11:13:11 UTC
Would be excellent feature to support Trac.
Comment 4 weazle 2009-12-10 11:40:18 UTC
Trac is very popular, so an out of the box integration would be very nice!
Comment 5 nanux 2009-12-21 09:34:22 UTC
The http://code.google.com/p/cubeon/ CubeOn project is working on trac integration into netbeans but it would be nice if I could update issue with commit and this isn't possible with cubeon, so the trac support by native issue tracking framework will be great. Maybe the effort of projects can be merged.
Comment 6 guinsel 2010-02-11 15:05:58 UTC
Trac is widely used in free software projects. Integration with NetBeans would be a very good news for the free software community.
Comment 7 schkovich 2010-04-14 11:37:29 UTC
Having native Trac support will be awesome feature.

I am using Cube°n plugin but I would prefer native Trac support. 

I agree with nanux@netbeans.org that join efforts will beneficial.

I am giving my vote and I will list this issue as the most critical in my opinion. http://wiki.netbeans.org/NetCATParticipants
Comment 8 winnall 2010-04-21 13:14:13 UTC
I would welcome better Trac support in NetBeans. I too currently use Cube°n, but it is fiddly and could work better (NB 6.8).
Comment 9 En_t_end 2010-04-22 07:31:21 UTC
We need it
Comment 10 yobe 2010-04-22 09:24:38 UTC
Just adding another request for this feature. Cubeon is a nice try, but doesn't work very well so native support would be awesome.
Comment 11 schkovich 2010-04-22 09:58:09 UTC
One of the key problems is that TracXMLRPCPlugin does have issues: http://code.google.com/p/cubeon/issues/detail?id=120#c6

Further on Python 2.6 is required on the server side and on some Linux distributions, like CentOS, installing Python 2.6 is challenging task.

I guess that those are, along with need for native NetBeans integration, among main reasons why using Trac with NetBeans is not widely spread.
Comment 12 CMoH 2010-04-22 11:09:07 UTC
(In reply to comment #11)
> One of the key problems is that TracXMLRPCPlugin does have issues:
> http://code.google.com/p/cubeon/issues/detail?id=120#c6

While this may be true, Mylyn's Trac connector seems usable in Eclipse through this XMLRPC plugin.

I don't follow your argumentation about not releasing a Trac connector for netbeans because an external party has issues open on their software:

Gcc seems to have 5582 open bugs. Still people are able to use it. Should netbeans devs have waited until the count got to 0 before releasing the C/C++ plugin for GCC? 

On the Java libs there are 2210 bugs open. (http://bugs.sun.com/) Following the same reasoning, should netbeans not be based on Java?

> Further on Python 2.6 is required on the server side and on some Linux
> distributions, like CentOS, installing Python 2.6 is challenging task.

That is also a reasoning I cannot follow. Usually those using/installing Trac are not idiots, some being able to install even Python 2.6 when they need to. Furthermore, from your words it seems the problem is on the Trac administrator's side - on Netbeans's interface I expect just to see "error: the request to the Trac server (miserably) failed"
Comment 13 vlatkop 2010-04-22 11:30:56 UTC
(In reply to comment #11)
 
> Further on Python 2.6 is required on the server side and on some Linux
> distributions, like CentOS, installing Python 2.6 is challenging task.

Totally disagree and totally irrelevant.

> I guess that those are, along with need for native NetBeans integration, among
> main reasons why using Trac with NetBeans is not widely spread.

I spent days of searching any project management open source software that is as minimalistic as it is Trac and I didn't found any. One of the thing that is important to anyone is easy and good integration with Version Control Systems and integration based on the multiple projects/repositories. In other words, Trac instance for Project A, doesn't mix with Trac instance for Project B.

Also very important thing to notice is that programmer using Netbeans doesn't really need to know if the project management software is Java based, or Python based,... as far as there are communication protocols, services, plug-ins, ... to connect and to collaborate different applications/services.
Comment 14 schkovich 2010-04-22 11:33:20 UTC
(In reply to comment #12)
> I don't follow your argumentation about not releasing a Trac connector for
> netbeans 

My argument was not against Trac integration. On contrary, as you can notice I
voted for this issue.

I was arguing about why using Trac with NetBeans is not widely spread. :)
Comment 15 schkovich 2010-04-22 11:38:28 UTC
(In reply to comment #13)
> (In reply to comment #11)
> 
> > Further on Python 2.6 is required on the server side and on some Linux
> > distributions, like CentOS, installing Python 2.6 is challenging task.
> 
> Totally disagree and totally irrelevant.

Absolutely. If you don't have to do it yourself. ;)

> I spent days of searching any project management open source software that is
> as minimalistic as it is Trac and I didn't found any. One of the thing that is
> important to anyone is easy and good integration with Version Control Systems
> and integration based on the multiple projects/repositories. In other words,
> Trac instance for Project A, doesn't mix with Trac instance for Project B.

That's why I voted for this issue. :)
Comment 16 dellamowica 2010-04-29 08:54:29 UTC
That would be a great feature!
Comment 17 fdisk 2010-07-02 07:54:34 UTC
I'd like to see a Trac connector for Netbeans too
Comment 18 taige 2010-07-04 18:25:38 UTC
This is something I would love to see !
We use Trac in my project and this is something needed !
Comment 19 jnankin 2010-07-30 04:17:08 UTC
Would love this feature.  Please, please implement!
Comment 20 be_live 2010-07-31 10:57:41 UTC
With this inclusion out Netbeans can be more complete development environment. Please include this as early as possible.

Thanks.
Comment 21 dusty 2010-09-07 15:08:35 UTC
I agree, a native support for trac integration would be awesome!
Comment 22 spook.68 2010-09-07 16:33:18 UTC
I hope to see this feature in one of the coming updates.

Is there a reaction of the core team on this? Any status update or something like that?
Comment 23 puce 2010-10-28 09:18:50 UTC
What is the status of this issue?

The lack of Trac integration is one of the reasons I'm currently using Eclipse and not NetBeans. This is really needed.
Comment 24 nathanielkofalt 2010-11-19 04:52:56 UTC
It is depressing to see a year-old bug with no developer response. Trac integration would be very impressive and a major motivator to use NetBeans.
Comment 25 Tomas Stupka 2010-11-22 09:08:21 UTC
unfortunately, due to the current resource situation in the bugtracking team a trac plugin isn't planed for the upcoming release.
However, in case that anybody from the community want's to contribute, we are ready to provide any necessary help in means of advice and direction how to start.
Comment 26 jsl123 2010-12-08 20:30:25 UTC
Hi Tomas, thanks for replying. I'd be grateful if you could post any hints about how to get started with this. I've looked through the netbeans code (I'll be honest I've never done any netbeans module development) which all looked reasonable. However I have a couple of questions:

- The current bugtrackers seem to be tightly woven into the bugtracker code although I'm guessing creating a module to handle new ones is possible.
- From the code it looks like you need to implement a class (and supporting classes) based on BugtrackerConnector and declare it as a service, is this the right start?
- Given the above, the current bugtracker module isn't an API module, so the build process complains that dependants aren't friends, is there a way around this?

Finally is it is better to continue the discussion privately or through another means?
Comment 27 Tomas Stupka 2010-12-08 21:07:31 UTC
people are asking how to write bugtracking support in nb on various places, so
will setup a page with all needed and available info and come back to you then...

as to your questions:

> The current bugtrackers seem to be tightly woven into the bugtracker code
> although I'm guessing creating a module to handle new ones is possible.
yes

> From the code it looks like you need to implement a class (and supporting
> classes) based on BugtrackerConnector and declare it as a service, is this the
> right start?
yes. but as you realized by yourself - it is a friend api that very probably won't
change before the 7.0 release and definitely won't go public in it's current state.

> Given the above, the current bugtracker module isn't an API module, so the
> build process complains that dependants aren't friends, is there a way around
> this? 
if nothing else and you are willing to implement against an unstable api you can 
allways setup an implementation dependency on the bugtracking spi.see http://wiki.netbeans.org/DevFaqImplementationDependency 

> Finally is it is better to continue the discussion privately or through another
> means?
will setup a mailing list too
Comment 28 jsl123 2010-12-09 14:18:32 UTC
A mailing list and help page would be great.

>> Given the above, the current bugtracker module isn't an API module, so the
>> build process complains that dependants aren't friends, is there a way around
>> this? 
>if nothing else and you are willing to implement against an unstable api you can 
>allways setup an implementation dependency on the bugtracking spi.see
>http://wiki.netbeans.org/DevFaqImplementationDependency 

I'd looked at this already, but no Implementation version is defined in the "Issue Tracking" module, looking at the jar file reveals a value of 201007282301 in the manifest. But using this generates build warnings about it being non integer and netbeans won't load my module as it says the implementation version is wrong.

Cheers
Comment 29 Tomas Stupka 2010-12-09 14:23:56 UTC
> I'd looked at this already, but no Implementation version is defined in the ...
not in scope of this issue, lets talk it through via email ...
Comment 30 puce 2011-01-29 16:58:09 UTC
What's the status of this issue?

I've just seen the NetBeans Community Poll "What version control would you want to have added to the NetBeans IDE?", which seems to imply that there are some free resources to work on such an integration.
http://netbeans.org/community/polls/


I checked the issue reports:
http://netbeans.org/bugzilla/show_bug.cgi?id=124436
http://netbeans.org/bugzilla/show_bug.cgi?id=67259
http://netbeans.org/bugzilla/show_bug.cgi?id=139296
http://netbeans.org/bugzilla/show_bug.cgi?id=159825
http://netbeans.org/bugzilla/show_bug.cgi?id=129501

None of them has more than 12 votes from the community, while this issue already has 65! It seems Trac integration is more needed than another version control integration. But then maybe the intention of that poll could be misleading.


Any chance this issue will be reconsidered for NB v7.0?
Comment 31 dusty 2011-01-29 20:45:37 UTC
I would certainly be happy of at least an enhancement in the priority of this project...
Comment 32 zzanzare 2011-05-22 12:50:31 UTC
How much would it cost to develop? I'm willing to pay to have this implemented.
Comment 33 schoffel00 2011-08-21 09:25:40 UTC
Trying Netbeans a few days now, but since we are using Trac as the issuetracker with al our existing projects, we also vote for adding this to the native supported issuetrackers in Netbeans!!
Comment 34 jirka_x1 2011-09-02 18:54:35 UTC
(In reply to comment #32)
> How much would it cost to develop? I'm willing to pay to have this implemented.

You might contact the people around http://code.google.com/p/cubeon/. They have a nice plugin that "is not under active development due to lack of resource/funds".
Comment 35 jnankin 2011-11-09 18:20:14 UTC
It's been over a year since I commented last, but I'd really really really like to see this get done.  I've tried numerous times to get the cubeon plugin to work and it never has.

Trac is widely used in the software development community - most likely even more than Jira.
Comment 36 chrisdlangton 2012-06-07 01:28:38 UTC
I've tried to get the cubeon plugin to work also with no joy.

I agree, Trac is widely used in the software development community - not sure it will remain more than Jira for long, but i'm an Application Support Analyst who has used Trac for years and Jira more recently for some Agile projects.

I use Trac for my personal projects.

Is anyone a fan of the Wildfire Games 0 A.D. ??
They are currently Sourceforge Project of the Month!

Their project wouldnt be what it is without Trac i can assure you!
As I plan to contribute as a developer to 0 A.D. i hoped to stick with Netbeans IDE but looks like ill be moving elsewhere if the community at 0 A.D has a better IDE which they use for subversion AND Trac together...

Which will mean ill move my personal projects out of Netbeans IDE also, no use using 2 IDEs...
Comment 37 coombesy 2012-07-30 19:15:06 UTC
please. native trac support. I use for my personal issue tracking also.

Not a java developer but with the xmlrpc for trac available surely this wouldn't be a major task for a java developer.
http://trac-hacks.org/wiki/XmlRpcPlugin
Comment 38 dusty 2012-10-03 13:10:51 UTC
Trac api should be stable, and there is also a 1.0 release now, native support would be absolutely welcome.
Comment 39 mans71 2013-12-14 16:06:58 UTC
This request/wish was posted 2009. Now its 2013, close to being 2014.

We use Netbeans and TRAC heavily. Both are great, and both has its issues. But we stick with both, since we like the simpleness and logical layout of TRAC, and the support of SVN in NetBeans and the wast settings making it customizable - just some examples why we use them.

Together makes a good solutions for us. But integration, in some smart-fancy way with Netbeands and TRAC would be great!

So, is this issue still in same place as in 2009?

What, exactly would it take to involve to integrate the both? And, why is this not happening still after 4-5 years? Complicated? To little demand?


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo