---Navigation---Main PageCommunity portalCurrent eventsRecent changesRandom pageHelp
---Toolbox---Page informationPermanent linkPrintable versionSpecial pagesRelated changesWhat links here
This application is an example of what Eclipse Lyo can be used for, in the form of an OSLC-CM compatible adapter for the Bugzilla bugtracker application. It wraps Bugzilla (interacting with it through Bugzilla's native XMLRPC API) with an OSLC-CM provider server accessible through REST calls.
team provider for git (recommended) or .
for Maven support in the Eclipse IDE
This example assumes EGit is being used.
Open the Git Repositories view in Eclipse and click the Clone Git Repository icon
as the URI (browse it also ). User/Password are not required.
On the Branch Selection page, select the master branch
On the Local Destination page, specify a location or accept the default and click Finish
The repository should now show up in your Git Repositories view.
In the Git Repositories view, right click org.eclipse.lyo.server and select Import Projects
Select the Import Existing Projects wizard and click Next
Import the following projects:
org.eclipse.lyo.samples.bugzilla
org.eclipse.lyo.server.oauth.consumerstore
org.eclipse.lyo.server.oauth.core
org.eclipse.lyo.server.oauth.webapp
[Optional] Add the projects to a new working set.
The sample requires Bugzilla 4.0. By default, it uses the
test server, but you can specify your own.
Edit org.eclipse.lyo.samples.bugzilla/src/main/resources/bugz.properties.
Change the bugzilla_uri property to the URL of your Bugzilla server.
Change the admin property to your user ID. This ID has authority to manage OAuth consumers.
Edit org.eclipse.lyo.samples.bugzilla/src/test/resources/test.properties.
Enter your ID and password for the JUnit tests.
In the Eclipse Package Explorer view, select all the projects you've imported, right click, and select Maven-&Update Project Configuration. Click OK.
Run Maven Install on each project in this order,
org.eclipse.lyo.server.oauth.core
org.eclipse.lyo.server.oauth.consumerstore
org.eclipse.lyo.server.oauth.webapp
org.eclipse.lyo.server.samples.bugzilla
To run Maven Install,
Expand the project
Right click pom.xml and select Run As-&Maven install.
IBM JVM/JRE Users: There is an issue with m2eclipse and the the IBM JRE. If you have see the error java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder when running a Maven install, you need to copy a newer slf4j api jar into your JRE directory to work around the issue until it is fixed:
and extract the zip.
copy slf4j-api-1.6.2.jar from the slf4j distribution to the JAVA_HOME\jre\lib\ext directory
if you are interested in the details
You may need to check
for instructions on how to install the missing j2bugzilla dependency in case the Maven install fails for this project.
Select Run-&Run Configurations and double click Maven Build
Give the configuration a name
Specify a base directory of ${workspace_loc:/org.eclipse.lyo.samples.bugzilla} and a goal of jetty:run-exploded and Click Run
You should now be able to point a local web browser at . See the
for more about the Bugzilla adapter and OSLC.SIMPrivacy_开发规范（3）
登陆Bugzilla
Bugzilla登陆地址：
密码：123456
Bugzilla简介
Bugzilla是一个问题跟踪的专门工具
基于web方式、使用方便简单
有利于问题的跟踪，问题的统计分析
系统灵活，强大的可配置能力
自动发送email通知相关人员
Bug处理流程
软测提交Bug之后，状态为“新建”。
软件收到bug，确认是自己的bug，请选择接受Bug,状态会变成已分配。
如果不是自己的bug，请将bug状态设置为“重分配”并提交给相应责任人。
如是重复bug,则填好重复的bug号码后，更改状态为“解决Bug”。
如此bug是无效的，开发人员则更改bug状态为“无效”
如此bug的耦合度较高，修改会造成未知的问题，开发人员可以更改bug状态为“决定不改”“稍后再改”。
如此问题开发人员无法复现则可以更改状态为“无法重现”。
如修复了此bug,则更改状态为已修复。
Bug处理要求
Bug修复后需要及时更新bug状态至Fix，并在评论中写清楚在哪一版验证，而不是诸如“已解决”等，如下图。
Bug不修复，与测试沟通确认后，需要及时作相应的处理，在评论说明不改的原因，而不是诸如“不改”“无聊的bug”等， 如下图。
注意事项：Bug状态的变更
软测提交bug后，bugzilla上显示为“new”，如下图
开发接收bug，bugzilla上显示为“assigned”，如下图
修改完毕后，更改状态为“repaired”，并写明验证版本，如下图
参考知识库
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：838857次
积分：8969
积分：8969
排名：第1741名
原创：135篇
转载：77篇
译文：13篇
评论：114条
(1)(9)(1)(3)(2)(13)(11)(9)(6)(8)(8)(6)(5)(14)(28)(89)(6)(1)(2)(2)(1)git - Using GitHub with another Bug-tracker? - Stack Overflow
Join the Stack Overflow Community
Stack Overflow is a community of 6.9 million programmers, just like you, helping each other.
J it only takes a minute:
I am involved in this project, , and we are currently using GitHub for our development. We all love Git and GitHub and want to keep using it. However, now the project is getting stable and involved, and it's time we started using a more capable bug tracking system than GitHub's simple issue tracker. We also want to start doing GetText based translations.
We are looking at Launchpad which has both a nice bug tracker and translation manager, but we want to keep using GitHub for development. I'm worried that these will not integrate well, and it will make development harder.
Has anyone used GitHub with another bug tracking system and had any success? Any recommendations?
closed as primarily opinion-based by , , , ,
Many good questions generate some degree of opinion based on expert experience, but answers to this question
will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the , please .
We use Lighthouse with GitHub and the integration in both directions is very handy.
Projects use external (to github) bug tracking systems all the time.
Mostly, you just need to document the way to get to the bug tracker well and inform any current community of the change.
3,36621937
Use Bugzilla. It may not have direct integration, but it's the best bug-tracking software out there IMHO. And you honestly don't need direct integration for something like bug-tracking.
6,784115591
Not the answer you're looking for?
Browse other questions tagged
rev .25625
Stack Overflow works best with JavaScript enabledbugzilla.lyx.org Git
5 years ago
2 months ago
4 years ago
4 months ago
17 months ago
2 months ago
2 years ago
5 hours ago
5 years ago