| Summary: | No tasks listed under the All my current tasks query (XPlanner 0.7b) | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | guofeng zhang <guofeng> |
| Component: | Mylyn | Assignee: | Helen Bershadskaya <hbershadskaya> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | dev | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
guofeng zhang
I found that if I use the standalone release of XPlanner, the connector works well. The source might have new features added, for example, I noticed that when I create a new project, it display 'No releases for this project' and 'No iterations for this project', and we could create a release to store the backlog items, then move it to an iteration. Could the connector be updated to be compatible the main trunk of the XPlanner? Guofeng, Thanks a lot for boiling this problem down -- it would have taken me a long time to do that. I can try to make the connector compatible with the latest version of the trunk, but I am sure you can see the problem inherent in this -- the connector is an external piece, the source can continue to have changes that make the connector misbehave, etc. I suppose this can be triggered whenever, as in your case, someone actually tries the latest version of the XPlanner source build and sees problems. Thank you very much for finding this problem and entering the bug with so much detail. -Helen Mik, sorry to try to do this through e-mail -- you're right -- this belongs in this bug: What is the general Mylyn policy for dealing with external pieces built off of actual open source source? Has this come up with other connectors -- i.e. people requesting features working off of the latest open source source builds as opposed to official releases, and if so, how did you deal with it? Helen: Ideally we support both the latest development build and release build. But this can impose a large overhead, so we sometimes defer to interested parties (e.g. Guofeng) to help us diagnose the problems or contribute a solution. Guofeng: if you are interested in diagnosing this Helen could help you with checking out the XPlanner code to see what's going on. Further instructions are here: http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Workspace Thanks a lot. I think that's my fault that does not use the released version. Now the released version from the sourceforge site works well and will be used in our team. I will try to work on it. Thanks, Guofeng. If it really becomes a requirement for you to use the latest source, let me know -- e.g. if there are features that you are really missing in the official release. Then I can try to work with you on including them in the connector implementation. I wish there was a better resolution for this bug -- but it seems like it should be closed. If there is a real requirement to support the latest source based XPlanner build, that should be a separate issue filed by a user. |