Home » Eclipse Projects » Mylyn » Problem with Jira and Mylyn on 3.3
| Problem with Jira and Mylyn on 3.3 [message #22154] |
Fri, 17 August 2007 17:09  |
|
This is a multi-part message in MIME format.
--------------060804070007030905000500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
I have four Europa installations two on XP an two on RH Linux. On all
four I am having the same problem with getting Mylyn speaking with our
in house Jira (Professional Edition, Version: 3.3.3-#99). I am migrating
from an Eclipse 3.2.x / Mylar environment where this has worked fine for
near a year. I went back today to the 3.2 systems and confirmed that
they do indeed still work.
I can configure and validate the repository. When I try to create a
query I get an error dialog saying:
Error parsing server response: No project with key "UME" found'
For the fun of it I set up a task repository into
http://jira.jboss.com/jira and have the same problem.
I have checked the Eclipse logs, but there are no relevant items.
What really concerns me is that I have searched the e.t.mylyn news group
and the web, and have come up empty handed with similar problems being
reported.
Any ideas on how to track this down would be very welcome.
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------060804070007030905000500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
I have four Europa installations two on XP an two on RH Linux. On all
four I am having the same problem with getting Mylyn speaking with our
in house Jira (Professional Edition, Version: 3.3.3-#99). I am
migrating from an Eclipse 3.2.x / Mylar environment where this has
worked fine for near a year. I went back today to the 3.2 systems and
confirmed that they do indeed still work.<br>
<br>
I can configure and validate the repository. When I try to create a
query I get an error dialog saying:<br>
</font>
<blockquote><font face="Helvetica, Arial, sans-serif"> Error parsing
server response: No project with key "UME" found'<br>
</font></blockquote>
For the fun of it I set up a task repository into
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira">http://jira.jboss.com/jira</a> and have the same problem.<br>
<br>
I have checked the Eclipse logs, but there are no relevant items.<br>
<br>
What really concerns me is that I have searched the e.t.mylyn news
group and the web, and have come up empty handed with similar problems
being reported.<br>
<br>
Any ideas on how to track this down would be very welcome.<br>
<br>
Thanks,<br>
Joel<font face="Helvetica, Arial, sans-serif"><br>
</font>
<pre class="moz-signature" cols="72">--
Joel Rosi-Schwartz
Etish Limited [<a class="moz-txt-link-freetext" href="http://www.etish.org">http://www.etish.org</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [<a class="moz-txt-link-freetext" href="https://useme.dev.java.net">https://useme.dev.java.net</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</pre>
</body>
</html>
--------------060804070007030905000500--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22201 is a reply to message #22154] |
Fri, 17 August 2007 17:20  |
 Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel,
If you were migrating from previous plugin version it is possible that
cached JIRA repository info is out of sync. To refresh it you can use
"Update Attributes" action on your JIRA repository from the Task
Repositories view.
Also, I strongly recommend to use latest dev builds (those usually
come every Friday), especially for JIRA integration we have lots of
fixes since 2.0 release. See project download page for more details
http://www.eclipse.org/mylyn/downloads/
regards,
Eugene
PS: I've just checked jbos jira and it is working fine for me. I am
running most recent dev build.
Joel Rosi-Schwartz wrote:
> Hi,
>
> I have four Europa installations two on XP an two on RH Linux. On all
> four I am having the same problem with getting Mylyn speaking with our
> in house Jira (Professional Edition, Version: 3.3.3-#99). I am
> migrating from an Eclipse 3.2.x / Mylar environment where this has
> worked fine for near a year. I went back today to the 3.2 systems and
> confirmed that they do indeed still work.
>
> I can configure and validate the repository. When I try to create a
> query I get an error dialog saying:
>
> Error parsing server response: No project with key "UME" found'
>
> For the fun of it I set up a task repository into
> http://jira.jboss.com/jira and have the same problem.
>
> I have checked the Eclipse logs, but there are no relevant items.
>
> What really concerns me is that I have searched the e.t.mylyn news
> group and the web, and have come up empty handed with similar problems
> being reported.
>
> Any ideas on how to track this down would be very welcome.
>
> Thanks,
> Joel
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22245 is a reply to message #22201] |
Fri, 17 August 2007 18:21 |
|
This is a multi-part message in MIME format.
--------------090601070601010201050102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene,
Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
for the mill though. For the XP installs I reused the Eclipse workspaces
from 3.2, but the Linux installs used freshly created workspaces. So
from the gist of message, I would not have thought caching to be an
issue in my Linux environs. Well guess what? Your suggestion about
"Update Attributes" fixed the problem on Linux but not on XP. Now I get
a message:
Error parsing server response: The element "rss" must be terminated
by the matching end tag "</rss>"
If you have fix for that great :-), otherwise I think I will simply save
the preferences from the XP installs and create fresh workspaces. That
may be the path of least resistance here.
Oh, and I do understand where you are coming from on the dev builds, but
I am very reticent to do that on production environments. I did that on
3.2 and ended up with a hodge-podge of plugins that did not quite play
together nicely. After those nightmares, I am not quite as cavalier :-(
Thanks again,
Joel
Eugene Kuleshov wrote:
> Joel,
>
> If you were migrating from previous plugin version it is possible
> that cached JIRA repository info is out of sync. To refresh it you can
> use "Update Attributes" action on your JIRA repository from the Task
> Repositories view.
>
> Also, I strongly recommend to use latest dev builds (those usually
> come every Friday), especially for JIRA integration we have lots of
> fixes since 2.0 release. See project download page for more details
> http://www.eclipse.org/mylyn/downloads/
>
> regards,
> Eugene
>
> PS: I've just checked jbos jira and it is working fine for me. I am
> running most recent dev build.
>
>
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> I have four Europa installations two on XP an two on RH Linux. On all
>> four I am having the same problem with getting Mylyn speaking with
>> our in house Jira (Professional Edition, Version: 3.3.3-#99). I am
>> migrating from an Eclipse 3.2.x / Mylar environment where this has
>> worked fine for near a year. I went back today to the 3.2 systems and
>> confirmed that they do indeed still work.
>>
>> I can configure and validate the repository. When I try to create a
>> query I get an error dialog saying:
>>
>> Error parsing server response: No project with key "UME" found'
>>
>> For the fun of it I set up a task repository into
>> http://jira.jboss.com/jira and have the same problem.
>>
>> I have checked the Eclipse logs, but there are no relevant items.
>>
>> What really concerns me is that I have searched the e.t.mylyn news
>> group and the web, and have come up empty handed with similar
>> problems being reported.
>>
>> Any ideas on how to track this down would be very welcome.
>>
>> Thanks,
>> Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------090601070601010201050102
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene,<br>
<br>
Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
for the mill though. For the XP installs I reused the Eclipse
workspaces from 3.2, but the Linux installs used freshly created
workspaces. So from the gist of message, I would not have thought
caching to be an issue in my Linux environs. Well guess what? Your
suggestion about "Update Attributes" fixed the problem on Linux but not
on XP. Now I get a message:<br>
<blockquote>Error parsing server response: The element "rss" must be
terminated by the matching end tag "</rss>"<br>
</blockquote>
If you have fix for that great :-), otherwise I think I will simply
save the preferences from the XP installs and create fresh workspaces.
That may be the path of least resistance here.<br>
<br>
Oh, and I do understand where you are coming from on the dev builds,
but I am very reticent to do that on production environments. I did
that on 3.2 and ended up with a hodge-podge of plugins that did not
quite play together nicely. After those nightmares, I am not quite as
cavalier :-(<br>
<br>
Thanks again,<br>
Joel<br>
<br>
Eugene Kuleshov wrote:
<blockquote cite="mid:fa4lcd$iol$1@build.eclipse.org" type="cite">Joel,
<br>
<br>
If you were migrating from previous plugin version it is possible that
cached JIRA repository info is out of sync. To refresh it you can use
"Update Attributes" action on your JIRA repository from the Task
Repositories view.
<br>
<br>
Also, I strongly recommend to use latest dev builds (those usually
come every Friday), especially for JIRA integration we have lots of
fixes since 2.0 release. See project download page for more details
<a class="moz-txt-link-freetext" href="http://www.eclipse.org/mylyn/downloads/">http://www.eclipse.org/mylyn/downloads/</a>
<br>
<br>
regards,
<br>
Eugene
<br>
<br>
PS: I've just checked jbos jira and it is working fine for me. I am
running most recent dev build.
<br>
<br>
<br>
Joel Rosi-Schwartz wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
I have four Europa installations two on XP an two on RH Linux. On all
four I am having the same problem with getting Mylyn speaking with our
in house Jira (Professional Edition, Version: 3.3.3-#99). I am
migrating from an Eclipse 3.2.x / Mylar environment where this has
worked fine for near a year. I went back today to the 3.2 systems and
confirmed that they do indeed still work.
<br>
<br>
I can configure and validate the repository. When I try to create a
query I get an error dialog saying:
<br>
<br>
Error parsing server response: No project with key "UME" found'
<br>
<br>
For the fun of it I set up a task repository into
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira">http://jira.jboss.com/jira</a> and have the same problem.
<br>
<br>
I have checked the Eclipse logs, but there are no relevant items.
<br>
<br>
What really concerns me is that I have searched the e.t.mylyn news
group and the web, and have come up empty handed with similar problems
being reported.
<br>
<br>
Any ideas on how to track this down would be very welcome.
<br>
<br>
Thanks,
<br>
Joel
<br>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Joel Rosi-Schwartz
Etish Limited [<a class="moz-txt-link-freetext" href="http://www.etish.org">http://www.etish.org</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [<a class="moz-txt-link-freetext" href="https://useme.dev.java.net">https://useme.dev.java.net</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</pre>
</body>
</html>
--------------090601070601010201050102--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22378 is a reply to message #22245] |
Fri, 17 August 2007 19:11 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
> Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
> for the mill though. For the XP installs I reused the Eclipse
> workspaces from 3.2, but the Linux installs used freshly created
> workspaces. So from the gist of message, I would not have thought
> caching to be an issue in my Linux environs. Well guess what? Your
> suggestion about "Update Attributes" fixed the problem on Linux but
> not on XP. Now I get a message:
>
> Error parsing server response: The element "rss" must be
> terminated by the matching end tag "</rss>"
>
> If you have fix for that great :-), otherwise I think I will simply
> save the preferences from the XP installs and create fresh workspaces.
> That may be the path of least resistance here.
I never saw anything like that before. You can try to delete
<workspace> \.metadata\.plugins\org.eclipse.mylyn.jira.core\serverCache\ repositoryConfigurations
(while Eclipse is not running) and then refresh attributes again.
From the description it also could be either because your JIRA server
returned incomplete XML or that XML has some stuff we don't expect.
Anyways, please open a bug report for that and provide details on how
can we reproduce it. :-)
In a mean time you could also check that you can query the following
public JIRA repositories:
http://jira.codehaus.org
http://issues.apache.org/jira/
http://opensource.atlassian.com/projects/spring
> Oh, and I do understand where you are coming from on the dev builds,
> but I am very reticent to do that on production environments. I did
> that on 3.2 and ended up with a hodge-podge of plugins that did not
> quite play together nicely. After those nightmares, I am not quite as
> cavalier :-(
Fair enough. However we pay a lot of attention to the backward
compatibility and you should be safe to use recent dev builds with
Eclipse 3.3. You will see detail on the download page about required
Eclipse versions and Update Manager would complain if you have an
incompatible one, so you should be safe and in worst case you can always
use Update Manager to roll back to the previous version.
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22423 is a reply to message #22378] |
Fri, 17 August 2007 20:09 |
|
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>> Thanks kindly for the speedy (and accurate;-) reply. A bit more
>> fodder for the mill though. For the XP installs I reused the Eclipse
>> workspaces from 3.2, but the Linux installs used freshly created
>> workspaces. So from the gist of message, I would not have thought
>> caching to be an issue in my Linux environs. Well guess what? Your
>> suggestion about "Update Attributes" fixed the problem on Linux but
>> not on XP. Now I get a message:
>>
>> Error parsing server response: The element "rss" must be
>> terminated by the matching end tag "</rss>"
>>
>> If you have fix for that great :-), otherwise I think I will simply
>> save the preferences from the XP installs and create fresh
>> workspaces. That may be the path of least resistance here.
> I never saw anything like that before. You can try to delete
> <workspace> \.metadata\.plugins\org.eclipse.mylyn.jira.core\serverCache\ repositoryConfigurations
> (while Eclipse is not running) and then refresh attributes again.
Did this and still had the same results.
> From the description it also could be either because your JIRA server
> returned incomplete XML or that XML has some stuff we don't expect.
> Anyways, please open a bug report for that and provide details on how
> can we reproduce it. :-)
That may well be, but the question then is why does it work on 3.2 and
now on Linux but not XP. I really do not have a clue on how to tell
describe how to reproduce it. Of course unless you fancy coming over to
visit; we are in Chichester, West Sussex, United Kingdom and it quite a
lovely place to visit. Be happy to buy you a pint or two. But
seriously, if you have any idea on how I give you more data to explore
or reproduce I would be happy to help.
>
> In a mean time you could also check that you can query the following
> public JIRA repositories:
>
> http://jira.codehaus.org
> http://issues.apache.org/jira/
> http://opensource.atlassian.com/projects/spring
I tried codehaus and had the same result, except that the project was
"MNG" in this case. I did not see much sense in trying the other. Let me
know if you really would like me too.
>> Oh, and I do understand where you are coming from on the dev builds,
>> but I am very reticent to do that on production environments. I did
>> that on 3.2 and ended up with a hodge-podge of plugins that did not
>> quite play together nicely. After those nightmares, I am not quite as
>> cavalier :-(
> Fair enough. However we pay a lot of attention to the backward
> compatibility and you should be safe to use recent dev builds with
> Eclipse 3.3. You will see detail on the download page about required
> Eclipse versions and Update Manager would complain if you have an
> incompatible one, so you should be safe and in worst case you can
> always use Update Manager to roll back to the previous version.
I will give this a try, simply to see if the problem goes away or not.
Actually being very jade after all of the time I spent fixing our
environment up in 3.2.x I take snapshots (tar balls) of all Eclipse
configuration changes at the moment so I can roll back. Not that I do
not trust the Update Manager :-)
I will let you know how that goes.
Cheers,
Joel
> regards,
> Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22511 is a reply to message #22423] |
Fri, 17 August 2007 20:48 |
|
Joel Rosi-Schwartz wrote:
> Eugene Kuleshov wrote:
>
>> Fair enough. However we pay a lot of attention to the backward
>> compatibility and you should be safe to use recent dev builds with
>> Eclipse 3.3. You will see detail on the download page about required
>> Eclipse versions and Update Manager would complain if you have an
>> incompatible one, so you should be safe and in worst case you can
>> always use Update Manager to roll back to the previous version.
> I will give this a try, simply to see if the problem goes away or not.
> Actually being very jade after all of the time I spent fixing our
> environment up in 3.2.x I take snapshots (tar balls) of all Eclipse
> configuration changes at the moment so I can roll back. Not that I do
> not trust the Update Manager :-)
>
> I will let you know how that goes.
I updated to latest dev build of both mylyn and extras. Still the same
result for both my jira and codehaus :-(
One idea I had if you are interested, is I could cut a CD of my install
and and workspace. It would take a week or so for it get to you by snail
mail. Seeing as Codehaus is reproducible that should give you something
to explore. Would you like me to do that?
Joel
|
|
| |
| Re: Problem with Jira and Mylyn on 3.3 [message #22641 is a reply to message #22554] |
Sat, 18 August 2007 10:21 |
|
This is a multi-part message in MIME format.
--------------000903000604010501040300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>> I updated to latest dev build of both mylyn and extras. Still the
>> same result for both my jira and codehaus :-(
>>
>> One idea I had if you are interested, is I could cut a CD of my
>> install and and workspace. It would take a week or so for it get to
>> you by snail mail. Seeing as Codehaus is reproducible that should
>> give you something to explore. Would you like me to do that?
> The thing is that I don't see such problem with the Codehaus and I am
> using it all the time. So, it doesn't seem like it is going to help.
Possibly I was not clear. If I send you my Eclipse installation and
workspace then you should be able to start *my* Eclipse configuration
against *my* workspace. If you cannot then reproduce my problem locally,
then it would point to an environmental issue, e.g. the version of Java
I am using, etc. If you can, then you may have a shot at diagnosing it.
> BTW, can you open repository task for Codehaus or your jira
> repository (from the popup menu on jira repository in the task
> repositories view)? How about Search (Ctrl-H)?
Yes I can do both of these. One oddity I found is that when I opened an
issue that was located by the search, that on the top of the task editor
was a notice that there were incoming changes and that the task should
be synchronised to see them. I synchronised this one task from the task
editor and it succeeded without problem.
> Anyways, the best would be to open a bug report and attach the full
> stack trace for that error. See some pointers at
> http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues
> Please also attach to the report info about your Eclipse install from
> Help / About Eclipse SDK / Configuration Details
There is no stack trace. The only indication of the problem is the error
dialog.
I have enabled debug as suggested in the FAQ, but the output is less
than illuminating. BTW, does the first line mean I do not have Mylyn
attachment support, I have not tried that yet?
[WARN] JavaUtils - Unable to find required classes
(javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
Without a stack trace or a way to describe how to reproduce is it
desirable to open a bug? My experience is that these reports linger for
a few releases and then are summarily closed :-(
Thanks,
Joel
> regards,
> Eugene
--------------000903000604010501040300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene Kuleshov wrote:
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<blockquote type="cite">I updated to latest dev build of both mylyn
and extras. Still the same result for both my jira and codehaus :-(
<br>
<br>
One idea I had if you are interested, is I could cut a CD of my install
and and workspace. It would take a week or so for it get to you by
snail mail. Seeing as Codehaus is reproducible that should give you
something to explore. Would you like me to do that?
<br>
</blockquote>
The thing is that I don't see such problem with the Codehaus and I am
using it all the time. So, it doesn't seem like it is going to help.
<br>
</blockquote>
Possibly I was not clear. If I send you my Eclipse installation and
workspace then you should be able to start *my* Eclipse configuration
against *my* workspace. If you cannot then reproduce my problem
locally, then it would point to an environmental issue, e.g. the
version of Java I am using, etc. If you can, then you may have a shot
at diagnosing it.<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite"> BTW,
can you open repository task for Codehaus or your jira repository (from
the popup menu on jira repository in the task repositories view)? How
about Search (Ctrl-H)?
<br>
</blockquote>
Yes I can do both of these. One oddity I found is that when I opened an
issue that was located by the search, that on the top of the task
editor was a notice that there were incoming changes and that the task
should be synchronised to see them. I synchronised this one task from
the task editor and it succeeded without problem.<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">Anyways,
the best would be to open a bug report and attach the full stack trace
for that error. See some pointers at
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues">http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues</a>
<br>
Please also attach to the report info about your Eclipse install from
Help / About Eclipse SDK / Configuration Details
<br>
</blockquote>
There is no stack trace. The only indication of the problem is the
error dialog. <br>
<br>
I have enabled debug as suggested in the FAQ, but the output is less
than illuminating. BTW, does the first line mean I do not have Mylyn
attachment support, I have not tried that yet?<br>
<blockquote>[WARN] JavaUtils - Unable to find required classes
(javax.activation.DataHandler and javax.mail.internet.MimeMultipart).
Attachment support is disabled.<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".<br>
</blockquote>
Without a stack trace or a way to describe how to reproduce is it
desirable to open a bug? My experience is that these reports linger for
a few releases and then are summarily closed :-(<br>
<br>
Thanks,<br>
Joel<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">regards,
<br>
Eugene
<br>
</blockquote>
</body>
</html>
--------------000903000604010501040300--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22684 is a reply to message #22641] |
Sat, 18 August 2007 11:01 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
>> The thing is that I don't see such problem with the Codehaus and I
>> am using it all the time. So, it doesn't seem like it is going to help.
> Possibly I was not clear. If I send you my Eclipse installation and
> workspace then you should be able to start *my* Eclipse configuration
> against *my* workspace. If you cannot then reproduce my problem
> locally, then it would point to an environmental issue, e.g. the
> version of Java I am using, etc. If you can, then you may have a shot
> at diagnosing it.
I got that, but still doubt it would allow to reproduce. You have more
chances debugging it yourself. :-)
The setup isn't really that difficult. See
http://wiki.eclipse.org/Mylyn_Contributor_Reference#Workspac e
>> BTW, can you open repository task for Codehaus or your jira
>> repository (from the popup menu on jira repository in the task
>> repositories view)? How about Search (Ctrl-H)?
> Yes I can do both of these. One oddity I found is that when I opened
> an issue that was located by the search, that on the top of the task
> editor was a notice that there were incoming changes and that the task
> should be synchronised to see them. I synchronised this one task from
> the task editor and it succeeded without problem.
The odd part is that both search and task retrieval are using
practically the same code as query.
Can you please export query definition you are using for the Codehaus
and send it to me? I assume you are getting the same error up there?
>> Anyways, the best would be to open a bug report and attach the full
>> stack trace for that error. See some pointers at
>> http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues
>> Please also attach to the report info about your Eclipse install
>> from Help / About Eclipse SDK / Configuration Details
> There is no stack trace. The only indication of the problem is the
> error dialog.
>
> I have enabled debug as suggested in the FAQ, but the output is less
> than illuminating. BTW, does the first line mean I do not have Mylyn
> attachment support, I have not tried that yet?
>
> [WARN] JavaUtils - Unable to find required classes
> (javax.activation.DataHandler and
> javax.mail.internet.MimeMultipart). Attachment support is disabled.
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
>
You can ignore message about DataHandler, but it is weird that other
error go to the system console.
The errors and stacktraces should be in the Error Log view or directly
in the Eclipse .log at <workspace>/metadata
>
> Without a stack trace or a way to describe how to reproduce is it
> desirable to open a bug? My experience is that these reports linger
> for a few releases and then are summarily closed :-(
We usually don't close bugs that are reproduceable by someone and it
is good to have report, so the issue will be accounted for.
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22727 is a reply to message #22684] |
Sat, 18 August 2007 14:07 |
|
This is a multi-part message in MIME format.
--------------090300090005000507060407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>
> Can you please export query definition you are using for the Codehaus
> and send it to me? I assume you are getting the same error up there?
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results.
Sorry to muddy the waters further, but this in the debug console:
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
[Fatal Error] :82711:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
>
> The errors and stacktraces should be in the Error Log view or
> directly in the Eclipse .log at <workspace>/metadata
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------090300090005000507060407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene Kuleshov wrote:
<blockquote cite="mid:fa6jj8$loh$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<br>
Can you please export query definition you are using for the Codehaus
and send it to me? I assume you are getting the same error up there?<br>
</blockquote>
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results.
Sorry to muddy the waters further, but this in the debug console:<br>
<blockquote>[Fatal Error] :82707:3: The element type "rss" must be
terminated by the matching end-tag "</rss>".<br>
[Fatal Error] :82711:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".</blockquote>
<blockquote cite="mid:fa6jj8$loh$1@build.eclipse.org" type="cite"><br>
The errors and stacktraces should be in the Error Log view or directly
in the Eclipse .log at <workspace>/metadata
<br>
</blockquote>
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.<br>
<br>
Thanks,<br>
Joel<br>
<pre class="moz-signature" cols="72">--
Joel Rosi-Schwartz
Etish Limited [<a class="moz-txt-link-freetext" href="http://www.etish.org">http://www.etish.org</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [<a class="moz-txt-link-freetext" href="https://useme.dev.java.net">https://useme.dev.java.net</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</pre>
</body>
</html>
--------------090300090005000507060407--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22771 is a reply to message #22727] |
Sat, 18 August 2007 15:08 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
>> Can you please export query definition you are using for the
>> Codehaus and send it to me? I assume you are getting the same error
>> up there?
> I am sending it under to your email address. Note that I no longer get
> the original error message from Codehause and I *do* now get results.
So, it works for the Codehaus then?
> Sorry to muddy the waters further, but this in the debug console:
>
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
> [Fatal Error] :82711:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
>
When exactly those happens? Are those happens only on your own JIRA
repository and on which operation exactly?
>> The errors and stacktraces should be in the Error Log view or
>> directly in the Eclipse .log at <workspace>/metadata
> Yes I know that, and there is no stack trace. I reiterate, the *only*
> indication of the problem is the error dialog and the lack of results.
I don't see anything like that for the Codehaus query you've sent to
me (and btw, it wasn't using MNG project you've mentioned, it was using
some query saved on JIRa server).
Anyways, we should be having this conversation on the bug report, so
can you please create one and provide details about issues you have
(step by step if necessary). Also attach info about your Eclipse
environment there (Help / About Eclipse SDK / Configuration Details...).
If you can't get the stack trace, please attach screenshot for the error
dialog you getting, but specify when exactly it happens.
Any chance I can access that JIRA instance or get exported
configuration for your JIRA server, that I could import locally?
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22815 is a reply to message #22771] |
Sat, 18 August 2007 16:14 |
|
This is a multi-part message in MIME format.
--------------010608040002080708080609
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>>> Can you please export query definition you are using for the
>>> Codehaus and send it to me? I assume you are getting the same error
>>> up there?
>> I am sending it under to your email address. Note that I no longer
>> get the original error message from Codehause and I *do* now get
>> results.
> So, it works for the Codehaus then?
Now, but not the first two times I tried.
>> Sorry to muddy the waters further, but this in the debug console:
>>
>> [Fatal Error] :82707:3: The element type "rss" must be terminated
>> by the matching end-tag "</rss>".
>> [Fatal Error] :82711:3: The element type "rss" must be terminated
>> by the matching end-tag "</rss>".
>>
> When exactly those happens? Are those happens only on your own JIRA
> repository and on which operation exactly?
The above messages are from a synchronization on Codehaus. The first
message shows up about a minute after the I start the synchronization,
the second shows up right before the synchronization either completes
(Codehaus now) or fails (my Jira).
>>> The errors and stacktraces should be in the Error Log view or
>>> directly in the Eclipse .log at <workspace>/metadata
>> Yes I know that, and there is no stack trace. I reiterate, the *only*
>> indication of the problem is the error dialog and the lack of results.
> I don't see anything like that for the Codehaus query you've sent to
> me (and btw, it wasn't using MNG project you've mentioned, it was
> using some query saved on JIRa server).
Yes on that test I chose
1.3.0 fixed issues
http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511
>
> Anyways, we should be having this conversation on the bug report, so
> can you please create one and provide details about issues you have
> (step by step if necessary). Also attach info about your Eclipse
> environment there (Help / About Eclipse SDK / Configuration
> Details...). If you can't get the stack trace, please attach
> screenshot for the error dialog you getting, but specify when exactly
> it happens.
Okay, will do.
>
> Any chance I can access that JIRA instance or get exported
> configuration for your JIRA server, that I could import locally?
I can export the entire Jira instance for you. Do you want that attached
to the bug report or to you personally? But I doubt this is going to
help much seeing how I can create a clean workspace using the same
Eclipse install and everything works fine. Well almost, I still have to
Update Attributes before it the query succeeds, which I find strange.
Also it works fine against 3.2 on XP and against 3.2 and 3.3. on Linux.
This would seem to indicate that issue is with my old (3.2) workspace
not my Jira.
Joel
--------------010608040002080708080609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Eugene Kuleshov wrote:
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<blockquote type="cite">
<blockquote type="cite"> Can you please export query definition
you are using for the Codehaus and send it to me? I assume you are
getting the same error up there?
<br>
</blockquote>
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results. </blockquote>
So, it works for the Codehaus then?
<br>
</blockquote>
Now, but not the first two times I tried.<br>
<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">
<blockquote type="cite">Sorry to muddy the waters further, but this
in the debug console:
<br>
<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated
<br>
by the matching end-tag "</rss>".
<br>
[Fatal Error] :82711:3: The element type "rss" must be terminated
<br>
by the matching end-tag "</rss>".
<br>
<br>
</blockquote>
When exactly those happens? Are those happens only on your own JIRA
repository and on which operation exactly?
<br>
</blockquote>
The above messages are from a synchronization on Codehaus. The first
message shows up about a minute after the I start the synchronization,
the second shows up right before the synchronization either completes
(Codehaus now) or fails (my Jira).<br>
<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">
<blockquote type="cite">
<blockquote type="cite"> The errors and stacktraces should be in
the Error Log view or directly in the Eclipse .log at
<workspace>/metadata
<br>
</blockquote>
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.
<br>
</blockquote>
I don't see anything like that for the Codehaus query you've sent to
me (and btw, it wasn't using MNG project you've mentioned, it was using
some query saved on JIRa server).
<br>
</blockquote>
Yes on that test I chose <br>
<blockquote>1.3.0 fixed issues<br>
<a class="moz-txt-link-freetext" href=" http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511"> http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511</a><br>
</blockquote>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite"><br>
Anyways, we should be having this conversation on the bug report, so
can you please create one and provide details about issues you have
(step by step if necessary). Also attach info about your Eclipse
environment there (Help / About Eclipse SDK / Configuration
Details...). If you can't get the stack trace, please attach screenshot
for the error dialog you getting, but specify when exactly it happens.
<br>
</blockquote>
Okay, will do.<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite"><br>
Any chance I can access that JIRA instance or get exported
configuration for your JIRA server, that I could import locally?
<br>
</blockquote>
I can export the entire Jira instance for you. Do you want that
attached to the bug report or to you personally? But I doubt this is
going to help much seeing how I can create a clean workspace using the
same Eclipse install and everything works fine. Well almost, I still
have to Update Attributes before it the query succeeds, which I find
strange. Also it works fine against 3.2 on XP and against 3.2 and 3.3.
on Linux.<br>
<br>
This would seem to indicate that issue is with my old (3.2) workspace
not my Jira.<br>
<br>
Joel<br>
</body>
</html>
--------------010608040002080708080609--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #22993 is a reply to message #22154] |
Sun, 19 August 2007 22:08 |
Eclipse User |
|
|
|
Originally posted by: stefan.engel.avono.de
Hi,
as far as i can see, the problem with "No project with key "UME" found"
lies in the parsing of the rss data - at least in the Europa version of
Mylyn.
I reproduced this with Jira 3.10 and Mylyn (Europa) using a project
with name "Xyz" and a key of "XYZ". When building a query I got the
mentioned error. When I renamed the project into XYZ too (same value
as the project key which is used for numbering the issues), then
everything worked fine. A little further investigation showed that
Mylyn parses the rss data for an issue looking for the project key
(as the project name is not delivered whithin the rss data).
A side note: Jira always converts the project key to be uppercase.
In Mylyn the project name is extracted using the key and stripping off
the issue number, thus XYZ-123 leads to XYZ, but no project with name
XYZ could be found as the project is Xyz. This is still more confusing,
if project name and project key are not obviously related to each
other, e.g. project name "Hubba" with key "XYZZY" will result in
"No project with key "XYZZY" found" when using a saved filter from
the Jira repository.
As I have seen, there has been some work in the Jira part of Mylyn
and especially in the handling of the project key, maybe this is
fixed now (couldn't test yet).
Looking further into the Jira part of Mylyn, I saw that there are
at least two ways in which Mylyn and Jira talk to each other:
first using the web interface for login and filter queries looking
directly to the rss data of an issue and second using the RPC/SOAP
interface of Jira. Wouldn't it be better to completely skip the
handling of the web-interface access and just use the SOAP interface?
Using the SOAP interface there are some nice features available
which are easier to deal with than using the web interface (worklogs,
setting correct estimates, getting the project name from issue data of
a filter query, ...).
Regards,
Stefan
Joel Rosi-Schwartz wrote:
> Hi,
>
> I have four Europa installations two on XP an two on RH Linux. On all
> four I am having the same problem with getting Mylyn speaking with our
> in house Jira (Professional Edition, Version: 3.3.3-#99). I am migrating
> from an Eclipse 3.2.x / Mylar environment where this has worked fine for
> near a year. I went back today to the 3.2 systems and confirmed that
> they do indeed still work.
>
> I can configure and validate the repository. When I try to create a
> query I get an error dialog saying:
>
> Error parsing server response: No project with key "UME" found'
>
> For the fun of it I set up a task repository into
> http://jira.jboss.com/jira and have the same problem.
>
> I have checked the Eclipse logs, but there are no relevant items.
>
> What really concerns me is that I have searched the e.t.mylyn news group
> and the web, and have come up empty handed with similar problems being
> reported.
>
> Any ideas on how to track this down would be very welcome.
>
> Thanks,
> Joel
>
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577258 is a reply to message #22154] |
Fri, 17 August 2007 17:20 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel,
If you were migrating from previous plugin version it is possible that
cached JIRA repository info is out of sync. To refresh it you can use
"Update Attributes" action on your JIRA repository from the Task
Repositories view.
Also, I strongly recommend to use latest dev builds (those usually
come every Friday), especially for JIRA integration we have lots of
fixes since 2.0 release. See project download page for more details
http://www.eclipse.org/mylyn/downloads/
regards,
Eugene
PS: I've just checked jbos jira and it is working fine for me. I am
running most recent dev build.
Joel Rosi-Schwartz wrote:
> Hi,
>
> I have four Europa installations two on XP an two on RH Linux. On all
> four I am having the same problem with getting Mylyn speaking with our
> in house Jira (Professional Edition, Version: 3.3.3-#99). I am
> migrating from an Eclipse 3.2.x / Mylar environment where this has
> worked fine for near a year. I went back today to the 3.2 systems and
> confirmed that they do indeed still work.
>
> I can configure and validate the repository. When I try to create a
> query I get an error dialog saying:
>
> Error parsing server response: No project with key "UME" found'
>
> For the fun of it I set up a task repository into
> http://jira.jboss.com/jira and have the same problem.
>
> I have checked the Eclipse logs, but there are no relevant items.
>
> What really concerns me is that I have searched the e.t.mylyn news
> group and the web, and have come up empty handed with similar problems
> being reported.
>
> Any ideas on how to track this down would be very welcome.
>
> Thanks,
> Joel
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577281 is a reply to message #22201] |
Fri, 17 August 2007 18:21 |
|
This is a multi-part message in MIME format.
--------------090601070601010201050102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene,
Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
for the mill though. For the XP installs I reused the Eclipse workspaces
from 3.2, but the Linux installs used freshly created workspaces. So
from the gist of message, I would not have thought caching to be an
issue in my Linux environs. Well guess what? Your suggestion about
"Update Attributes" fixed the problem on Linux but not on XP. Now I get
a message:
Error parsing server response: The element "rss" must be terminated
by the matching end tag "</rss>"
If you have fix for that great :-), otherwise I think I will simply save
the preferences from the XP installs and create fresh workspaces. That
may be the path of least resistance here.
Oh, and I do understand where you are coming from on the dev builds, but
I am very reticent to do that on production environments. I did that on
3.2 and ended up with a hodge-podge of plugins that did not quite play
together nicely. After those nightmares, I am not quite as cavalier :-(
Thanks again,
Joel
Eugene Kuleshov wrote:
> Joel,
>
> If you were migrating from previous plugin version it is possible
> that cached JIRA repository info is out of sync. To refresh it you can
> use "Update Attributes" action on your JIRA repository from the Task
> Repositories view.
>
> Also, I strongly recommend to use latest dev builds (those usually
> come every Friday), especially for JIRA integration we have lots of
> fixes since 2.0 release. See project download page for more details
> http://www.eclipse.org/mylyn/downloads/
>
> regards,
> Eugene
>
> PS: I've just checked jbos jira and it is working fine for me. I am
> running most recent dev build.
>
>
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> I have four Europa installations two on XP an two on RH Linux. On all
>> four I am having the same problem with getting Mylyn speaking with
>> our in house Jira (Professional Edition, Version: 3.3.3-#99). I am
>> migrating from an Eclipse 3.2.x / Mylar environment where this has
>> worked fine for near a year. I went back today to the 3.2 systems and
>> confirmed that they do indeed still work.
>>
>> I can configure and validate the repository. When I try to create a
>> query I get an error dialog saying:
>>
>> Error parsing server response: No project with key "UME" found'
>>
>> For the fun of it I set up a task repository into
>> http://jira.jboss.com/jira and have the same problem.
>>
>> I have checked the Eclipse logs, but there are no relevant items.
>>
>> What really concerns me is that I have searched the e.t.mylyn news
>> group and the web, and have come up empty handed with similar
>> problems being reported.
>>
>> Any ideas on how to track this down would be very welcome.
>>
>> Thanks,
>> Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------090601070601010201050102
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene,<br>
<br>
Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
for the mill though. For the XP installs I reused the Eclipse
workspaces from 3.2, but the Linux installs used freshly created
workspaces. So from the gist of message, I would not have thought
caching to be an issue in my Linux environs. Well guess what? Your
suggestion about "Update Attributes" fixed the problem on Linux but not
on XP. Now I get a message:<br>
<blockquote>Error parsing server response: The element "rss" must be
terminated by the matching end tag "</rss>"<br>
</blockquote>
If you have fix for that great :-), otherwise I think I will simply
save the preferences from the XP installs and create fresh workspaces.
That may be the path of least resistance here.<br>
<br>
Oh, and I do understand where you are coming from on the dev builds,
but I am very reticent to do that on production environments. I did
that on 3.2 and ended up with a hodge-podge of plugins that did not
quite play together nicely. After those nightmares, I am not quite as
cavalier :-(<br>
<br>
Thanks again,<br>
Joel<br>
<br>
Eugene Kuleshov wrote:
<blockquote cite="mid:fa4lcd$iol$1@build.eclipse.org" type="cite">Joel,
<br>
<br>
If you were migrating from previous plugin version it is possible that
cached JIRA repository info is out of sync. To refresh it you can use
"Update Attributes" action on your JIRA repository from the Task
Repositories view.
<br>
<br>
Also, I strongly recommend to use latest dev builds (those usually
come every Friday), especially for JIRA integration we have lots of
fixes since 2.0 release. See project download page for more details
<a class="moz-txt-link-freetext" href="http://www.eclipse.org/mylyn/downloads/">http://www.eclipse.org/mylyn/downloads/</a>
<br>
<br>
regards,
<br>
Eugene
<br>
<br>
PS: I've just checked jbos jira and it is working fine for me. I am
running most recent dev build.
<br>
<br>
<br>
Joel Rosi-Schwartz wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
I have four Europa installations two on XP an two on RH Linux. On all
four I am having the same problem with getting Mylyn speaking with our
in house Jira (Professional Edition, Version: 3.3.3-#99). I am
migrating from an Eclipse 3.2.x / Mylar environment where this has
worked fine for near a year. I went back today to the 3.2 systems and
confirmed that they do indeed still work.
<br>
<br>
I can configure and validate the repository. When I try to create a
query I get an error dialog saying:
<br>
<br>
Error parsing server response: No project with key "UME" found'
<br>
<br>
For the fun of it I set up a task repository into
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira">http://jira.jboss.com/jira</a> and have the same problem.
<br>
<br>
I have checked the Eclipse logs, but there are no relevant items.
<br>
<br>
What really concerns me is that I have searched the e.t.mylyn news
group and the web, and have come up empty handed with similar problems
being reported.
<br>
<br>
Any ideas on how to track this down would be very welcome.
<br>
<br>
Thanks,
<br>
Joel
<br>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Joel Rosi-Schwartz
Etish Limited [<a class="moz-txt-link-freetext" href="http://www.etish.org">http://www.etish.org</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [<a class="moz-txt-link-freetext" href="https://useme.dev.java.net">https://useme.dev.java.net</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</pre>
</body>
</html>
--------------090601070601010201050102--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577299 is a reply to message #22245] |
Fri, 17 August 2007 19:11 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
> Thanks kindly for the speedy (and accurate;-) reply. A bit more fodder
> for the mill though. For the XP installs I reused the Eclipse
> workspaces from 3.2, but the Linux installs used freshly created
> workspaces. So from the gist of message, I would not have thought
> caching to be an issue in my Linux environs. Well guess what? Your
> suggestion about "Update Attributes" fixed the problem on Linux but
> not on XP. Now I get a message:
>
> Error parsing server response: The element "rss" must be
> terminated by the matching end tag "</rss>"
>
> If you have fix for that great :-), otherwise I think I will simply
> save the preferences from the XP installs and create fresh workspaces.
> That may be the path of least resistance here.
I never saw anything like that before. You can try to delete
<workspace> \.metadata\.plugins\org.eclipse.mylyn.jira.core\serverCache\ repositoryConfigurations
(while Eclipse is not running) and then refresh attributes again.
From the description it also could be either because your JIRA server
returned incomplete XML or that XML has some stuff we don't expect.
Anyways, please open a bug report for that and provide details on how
can we reproduce it. :-)
In a mean time you could also check that you can query the following
public JIRA repositories:
http://jira.codehaus.org
http://issues.apache.org/jira/
http://opensource.atlassian.com/projects/spring
> Oh, and I do understand where you are coming from on the dev builds,
> but I am very reticent to do that on production environments. I did
> that on 3.2 and ended up with a hodge-podge of plugins that did not
> quite play together nicely. After those nightmares, I am not quite as
> cavalier :-(
Fair enough. However we pay a lot of attention to the backward
compatibility and you should be safe to use recent dev builds with
Eclipse 3.3. You will see detail on the download page about required
Eclipse versions and Update Manager would complain if you have an
incompatible one, so you should be safe and in worst case you can always
use Update Manager to roll back to the previous version.
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577349 is a reply to message #22378] |
Fri, 17 August 2007 20:09 |
|
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>> Thanks kindly for the speedy (and accurate;-) reply. A bit more
>> fodder for the mill though. For the XP installs I reused the Eclipse
>> workspaces from 3.2, but the Linux installs used freshly created
>> workspaces. So from the gist of message, I would not have thought
>> caching to be an issue in my Linux environs. Well guess what? Your
>> suggestion about "Update Attributes" fixed the problem on Linux but
>> not on XP. Now I get a message:
>>
>> Error parsing server response: The element "rss" must be
>> terminated by the matching end tag "</rss>"
>>
>> If you have fix for that great :-), otherwise I think I will simply
>> save the preferences from the XP installs and create fresh
>> workspaces. That may be the path of least resistance here.
> I never saw anything like that before. You can try to delete
> <workspace> \.metadata\.plugins\org.eclipse.mylyn.jira.core\serverCache\ repositoryConfigurations
> (while Eclipse is not running) and then refresh attributes again.
Did this and still had the same results.
> From the description it also could be either because your JIRA server
> returned incomplete XML or that XML has some stuff we don't expect.
> Anyways, please open a bug report for that and provide details on how
> can we reproduce it. :-)
That may well be, but the question then is why does it work on 3.2 and
now on Linux but not XP. I really do not have a clue on how to tell
describe how to reproduce it. Of course unless you fancy coming over to
visit; we are in Chichester, West Sussex, United Kingdom and it quite a
lovely place to visit. Be happy to buy you a pint or two. But
seriously, if you have any idea on how I give you more data to explore
or reproduce I would be happy to help.
>
> In a mean time you could also check that you can query the following
> public JIRA repositories:
>
> http://jira.codehaus.org
> http://issues.apache.org/jira/
> http://opensource.atlassian.com/projects/spring
I tried codehaus and had the same result, except that the project was
"MNG" in this case. I did not see much sense in trying the other. Let me
know if you really would like me too.
>> Oh, and I do understand where you are coming from on the dev builds,
>> but I am very reticent to do that on production environments. I did
>> that on 3.2 and ended up with a hodge-podge of plugins that did not
>> quite play together nicely. After those nightmares, I am not quite as
>> cavalier :-(
> Fair enough. However we pay a lot of attention to the backward
> compatibility and you should be safe to use recent dev builds with
> Eclipse 3.3. You will see detail on the download page about required
> Eclipse versions and Update Manager would complain if you have an
> incompatible one, so you should be safe and in worst case you can
> always use Update Manager to roll back to the previous version.
I will give this a try, simply to see if the problem goes away or not.
Actually being very jade after all of the time I spent fixing our
environment up in 3.2.x I take snapshots (tar balls) of all Eclipse
configuration changes at the moment so I can roll back. Not that I do
not trust the Update Manager :-)
I will let you know how that goes.
Cheers,
Joel
> regards,
> Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577398 is a reply to message #22423] |
Fri, 17 August 2007 20:48 |
|
Joel Rosi-Schwartz wrote:
> Eugene Kuleshov wrote:
>
>> Fair enough. However we pay a lot of attention to the backward
>> compatibility and you should be safe to use recent dev builds with
>> Eclipse 3.3. You will see detail on the download page about required
>> Eclipse versions and Update Manager would complain if you have an
>> incompatible one, so you should be safe and in worst case you can
>> always use Update Manager to roll back to the previous version.
> I will give this a try, simply to see if the problem goes away or not.
> Actually being very jade after all of the time I spent fixing our
> environment up in 3.2.x I take snapshots (tar balls) of all Eclipse
> configuration changes at the moment so I can roll back. Not that I do
> not trust the Update Manager :-)
>
> I will let you know how that goes.
I updated to latest dev build of both mylyn and extras. Still the same
result for both my jira and codehaus :-(
One idea I had if you are interested, is I could cut a CD of my install
and and workspace. It would take a week or so for it get to you by snail
mail. Seeing as Codehaus is reproducible that should give you something
to explore. Would you like me to do that?
Joel
|
|
| |
| Re: Problem with Jira and Mylyn on 3.3 [message #577459 is a reply to message #22554] |
Sat, 18 August 2007 10:21 |
|
This is a multi-part message in MIME format.
--------------000903000604010501040300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>> I updated to latest dev build of both mylyn and extras. Still the
>> same result for both my jira and codehaus :-(
>>
>> One idea I had if you are interested, is I could cut a CD of my
>> install and and workspace. It would take a week or so for it get to
>> you by snail mail. Seeing as Codehaus is reproducible that should
>> give you something to explore. Would you like me to do that?
> The thing is that I don't see such problem with the Codehaus and I am
> using it all the time. So, it doesn't seem like it is going to help.
Possibly I was not clear. If I send you my Eclipse installation and
workspace then you should be able to start *my* Eclipse configuration
against *my* workspace. If you cannot then reproduce my problem locally,
then it would point to an environmental issue, e.g. the version of Java
I am using, etc. If you can, then you may have a shot at diagnosing it.
> BTW, can you open repository task for Codehaus or your jira
> repository (from the popup menu on jira repository in the task
> repositories view)? How about Search (Ctrl-H)?
Yes I can do both of these. One oddity I found is that when I opened an
issue that was located by the search, that on the top of the task editor
was a notice that there were incoming changes and that the task should
be synchronised to see them. I synchronised this one task from the task
editor and it succeeded without problem.
> Anyways, the best would be to open a bug report and attach the full
> stack trace for that error. See some pointers at
> http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues
> Please also attach to the report info about your Eclipse install from
> Help / About Eclipse SDK / Configuration Details
There is no stack trace. The only indication of the problem is the error
dialog.
I have enabled debug as suggested in the FAQ, but the output is less
than illuminating. BTW, does the first line mean I do not have Mylyn
attachment support, I have not tried that yet?
[WARN] JavaUtils - Unable to find required classes
(javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
Without a stack trace or a way to describe how to reproduce is it
desirable to open a bug? My experience is that these reports linger for
a few releases and then are summarily closed :-(
Thanks,
Joel
> regards,
> Eugene
--------------000903000604010501040300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene Kuleshov wrote:
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<blockquote type="cite">I updated to latest dev build of both mylyn
and extras. Still the same result for both my jira and codehaus :-(
<br>
<br>
One idea I had if you are interested, is I could cut a CD of my install
and and workspace. It would take a week or so for it get to you by
snail mail. Seeing as Codehaus is reproducible that should give you
something to explore. Would you like me to do that?
<br>
</blockquote>
The thing is that I don't see such problem with the Codehaus and I am
using it all the time. So, it doesn't seem like it is going to help.
<br>
</blockquote>
Possibly I was not clear. If I send you my Eclipse installation and
workspace then you should be able to start *my* Eclipse configuration
against *my* workspace. If you cannot then reproduce my problem
locally, then it would point to an environmental issue, e.g. the
version of Java I am using, etc. If you can, then you may have a shot
at diagnosing it.<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite"> BTW,
can you open repository task for Codehaus or your jira repository (from
the popup menu on jira repository in the task repositories view)? How
about Search (Ctrl-H)?
<br>
</blockquote>
Yes I can do both of these. One oddity I found is that when I opened an
issue that was located by the search, that on the top of the task
editor was a notice that there were incoming changes and that the task
should be synchronised to see them. I synchronised this one task from
the task editor and it succeeded without problem.<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">Anyways,
the best would be to open a bug report and attach the full stack trace
for that error. See some pointers at
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues">http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues</a>
<br>
Please also attach to the report info about your Eclipse install from
Help / About Eclipse SDK / Configuration Details
<br>
</blockquote>
There is no stack trace. The only indication of the problem is the
error dialog. <br>
<br>
I have enabled debug as suggested in the FAQ, but the output is less
than illuminating. BTW, does the first line mean I do not have Mylyn
attachment support, I have not tried that yet?<br>
<blockquote>[WARN] JavaUtils - Unable to find required classes
(javax.activation.DataHandler and javax.mail.internet.MimeMultipart).
Attachment support is disabled.<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".<br>
</blockquote>
Without a stack trace or a way to describe how to reproduce is it
desirable to open a bug? My experience is that these reports linger for
a few releases and then are summarily closed :-(<br>
<br>
Thanks,<br>
Joel<br>
<blockquote cite="mid:fa53n8$v8l$1@build.eclipse.org" type="cite">regards,
<br>
Eugene
<br>
</blockquote>
</body>
</html>
--------------000903000604010501040300--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577477 is a reply to message #22641] |
Sat, 18 August 2007 11:01 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
>> The thing is that I don't see such problem with the Codehaus and I
>> am using it all the time. So, it doesn't seem like it is going to help.
> Possibly I was not clear. If I send you my Eclipse installation and
> workspace then you should be able to start *my* Eclipse configuration
> against *my* workspace. If you cannot then reproduce my problem
> locally, then it would point to an environmental issue, e.g. the
> version of Java I am using, etc. If you can, then you may have a shot
> at diagnosing it.
I got that, but still doubt it would allow to reproduce. You have more
chances debugging it yourself. :-)
The setup isn't really that difficult. See
http://wiki.eclipse.org/Mylyn_Contributor_Reference#Workspac e
>> BTW, can you open repository task for Codehaus or your jira
>> repository (from the popup menu on jira repository in the task
>> repositories view)? How about Search (Ctrl-H)?
> Yes I can do both of these. One oddity I found is that when I opened
> an issue that was located by the search, that on the top of the task
> editor was a notice that there were incoming changes and that the task
> should be synchronised to see them. I synchronised this one task from
> the task editor and it succeeded without problem.
The odd part is that both search and task retrieval are using
practically the same code as query.
Can you please export query definition you are using for the Codehaus
and send it to me? I assume you are getting the same error up there?
>> Anyways, the best would be to open a bug report and attach the full
>> stack trace for that error. See some pointers at
>> http://wiki.eclipse.org/Mylyn_FAQ#Reporting_issues
>> Please also attach to the report info about your Eclipse install
>> from Help / About Eclipse SDK / Configuration Details
> There is no stack trace. The only indication of the problem is the
> error dialog.
>
> I have enabled debug as suggested in the FAQ, but the output is less
> than illuminating. BTW, does the first line mean I do not have Mylyn
> attachment support, I have not tried that yet?
>
> [WARN] JavaUtils - Unable to find required classes
> (javax.activation.DataHandler and
> javax.mail.internet.MimeMultipart). Attachment support is disabled.
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
>
You can ignore message about DataHandler, but it is weird that other
error go to the system console.
The errors and stacktraces should be in the Error Log view or directly
in the Eclipse .log at <workspace>/metadata
>
> Without a stack trace or a way to describe how to reproduce is it
> desirable to open a bug? My experience is that these reports linger
> for a few releases and then are summarily closed :-(
We usually don't close bugs that are reproduceable by someone and it
is good to have report, so the issue will be accounted for.
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577499 is a reply to message #22684] |
Sat, 18 August 2007 14:07 |
|
This is a multi-part message in MIME format.
--------------090300090005000507060407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>
> Can you please export query definition you are using for the Codehaus
> and send it to me? I assume you are getting the same error up there?
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results.
Sorry to muddy the waters further, but this in the debug console:
[Fatal Error] :82707:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
[Fatal Error] :82711:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".
>
> The errors and stacktraces should be in the Error Log view or
> directly in the Eclipse .log at <workspace>/metadata
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------090300090005000507060407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Eugene Kuleshov wrote:
<blockquote cite="mid:fa6jj8$loh$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<br>
Can you please export query definition you are using for the Codehaus
and send it to me? I assume you are getting the same error up there?<br>
</blockquote>
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results.
Sorry to muddy the waters further, but this in the debug console:<br>
<blockquote>[Fatal Error] :82707:3: The element type "rss" must be
terminated by the matching end-tag "</rss>".<br>
[Fatal Error] :82711:3: The element type "rss" must be terminated by
the matching end-tag "</rss>".</blockquote>
<blockquote cite="mid:fa6jj8$loh$1@build.eclipse.org" type="cite"><br>
The errors and stacktraces should be in the Error Log view or directly
in the Eclipse .log at <workspace>/metadata
<br>
</blockquote>
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.<br>
<br>
Thanks,<br>
Joel<br>
<pre class="moz-signature" cols="72">--
Joel Rosi-Schwartz
Etish Limited [<a class="moz-txt-link-freetext" href="http://www.etish.org">http://www.etish.org</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [<a class="moz-txt-link-freetext" href="https://useme.dev.java.net">https://useme.dev.java.net</a>]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
</pre>
</body>
</html>
--------------090300090005000507060407--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577519 is a reply to message #22727] |
Sat, 18 August 2007 15:08 |
Eugene Kuleshov
Messages: 504
Registered: July 2009 |
Senior Member |
|
|
Joel Rosi-Schwartz wrote:
>> Can you please export query definition you are using for the
>> Codehaus and send it to me? I assume you are getting the same error
>> up there?
> I am sending it under to your email address. Note that I no longer get
> the original error message from Codehause and I *do* now get results.
So, it works for the Codehaus then?
> Sorry to muddy the waters further, but this in the debug console:
>
> [Fatal Error] :82707:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
> [Fatal Error] :82711:3: The element type "rss" must be terminated
> by the matching end-tag "</rss>".
>
When exactly those happens? Are those happens only on your own JIRA
repository and on which operation exactly?
>> The errors and stacktraces should be in the Error Log view or
>> directly in the Eclipse .log at <workspace>/metadata
> Yes I know that, and there is no stack trace. I reiterate, the *only*
> indication of the problem is the error dialog and the lack of results.
I don't see anything like that for the Codehaus query you've sent to
me (and btw, it wasn't using MNG project you've mentioned, it was using
some query saved on JIRa server).
Anyways, we should be having this conversation on the bug report, so
can you please create one and provide details about issues you have
(step by step if necessary). Also attach info about your Eclipse
environment there (Help / About Eclipse SDK / Configuration Details...).
If you can't get the stack trace, please attach screenshot for the error
dialog you getting, but specify when exactly it happens.
Any chance I can access that JIRA instance or get exported
configuration for your JIRA server, that I could import locally?
regards,
Eugene
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577535 is a reply to message #22771] |
Sat, 18 August 2007 16:14 |
|
This is a multi-part message in MIME format.
--------------010608040002080708080609
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Eugene Kuleshov wrote:
> Joel Rosi-Schwartz wrote:
>>> Can you please export query definition you are using for the
>>> Codehaus and send it to me? I assume you are getting the same error
>>> up there?
>> I am sending it under to your email address. Note that I no longer
>> get the original error message from Codehause and I *do* now get
>> results.
> So, it works for the Codehaus then?
Now, but not the first two times I tried.
>> Sorry to muddy the waters further, but this in the debug console:
>>
>> [Fatal Error] :82707:3: The element type "rss" must be terminated
>> by the matching end-tag "</rss>".
>> [Fatal Error] :82711:3: The element type "rss" must be terminated
>> by the matching end-tag "</rss>".
>>
> When exactly those happens? Are those happens only on your own JIRA
> repository and on which operation exactly?
The above messages are from a synchronization on Codehaus. The first
message shows up about a minute after the I start the synchronization,
the second shows up right before the synchronization either completes
(Codehaus now) or fails (my Jira).
>>> The errors and stacktraces should be in the Error Log view or
>>> directly in the Eclipse .log at <workspace>/metadata
>> Yes I know that, and there is no stack trace. I reiterate, the *only*
>> indication of the problem is the error dialog and the lack of results.
> I don't see anything like that for the Codehaus query you've sent to
> me (and btw, it wasn't using MNG project you've mentioned, it was
> using some query saved on JIRa server).
Yes on that test I chose
1.3.0 fixed issues
http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511
>
> Anyways, we should be having this conversation on the bug report, so
> can you please create one and provide details about issues you have
> (step by step if necessary). Also attach info about your Eclipse
> environment there (Help / About Eclipse SDK / Configuration
> Details...). If you can't get the stack trace, please attach
> screenshot for the error dialog you getting, but specify when exactly
> it happens.
Okay, will do.
>
> Any chance I can access that JIRA instance or get exported
> configuration for your JIRA server, that I could import locally?
I can export the entire Jira instance for you. Do you want that attached
to the bug report or to you personally? But I doubt this is going to
help much seeing how I can create a clean workspace using the same
Eclipse install and everything works fine. Well almost, I still have to
Update Attributes before it the query succeeds, which I find strange.
Also it works fine against 3.2 on XP and against 3.2 and 3.3. on Linux.
This would seem to indicate that issue is with my old (3.2) workspace
not my Jira.
Joel
--------------010608040002080708080609
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Eugene Kuleshov wrote:
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">Joel
Rosi-Schwartz wrote:
<br>
<blockquote type="cite">
<blockquote type="cite"> Can you please export query definition
you are using for the Codehaus and send it to me? I assume you are
getting the same error up there?
<br>
</blockquote>
I am sending it under to your email address. Note that I no longer get
the original error message from Codehause and I *do* now get results. </blockquote>
So, it works for the Codehaus then?
<br>
</blockquote>
Now, but not the first two times I tried.<br>
<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">
<blockquote type="cite">Sorry to muddy the waters further, but this
in the debug console:
<br>
<br>
[Fatal Error] :82707:3: The element type "rss" must be terminated
<br>
by the matching end-tag "</rss>".
<br>
[Fatal Error] :82711:3: The element type "rss" must be terminated
<br>
by the matching end-tag "</rss>".
<br>
<br>
</blockquote>
When exactly those happens? Are those happens only on your own JIRA
repository and on which operation exactly?
<br>
</blockquote>
The above messages are from a synchronization on Codehaus. The first
message shows up about a minute after the I start the synchronization,
the second shows up right before the synchronization either completes
(Codehaus now) or fails (my Jira).<br>
<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite">
<blockquote type="cite">
<blockquote type="cite"> The errors and stacktraces should be in
the Error Log view or directly in the Eclipse .log at
<workspace>/metadata
<br>
</blockquote>
Yes I know that, and there is no stack trace. I reiterate, the *only*
indication of the problem is the error dialog and the lack of results.
<br>
</blockquote>
I don't see anything like that for the Codehaus query you've sent to
me (and btw, it wasn't using MNG project you've mentioned, it was using
some query saved on JIRa server).
<br>
</blockquote>
Yes on that test I chose <br>
<blockquote>1.3.0 fixed issues<br>
<a class="moz-txt-link-freetext" href=" http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511"> http://jira.codehaus.org/secure/IssueNavigator.jspa?mode=hid e&requestId=11511</a><br>
</blockquote>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite"><br>
Anyways, we should be having this conversation on the bug report, so
can you please create one and provide details about issues you have
(step by step if necessary). Also attach info about your Eclipse
environment there (Help / About Eclipse SDK / Configuration
Details...). If you can't get the stack trace, please attach screenshot
for the error dialog you getting, but specify when exactly it happens.
<br>
</blockquote>
Okay, will do.<br>
<blockquote cite="mid:fa7216$fjc$1@build.eclipse.org" type="cite"><br>
Any chance I can access that JIRA instance or get exported
configuration for your JIRA server, that I could import locally?
<br>
</blockquote>
I can export the entire Jira instance for you. Do you want that
attached to the bug report or to you personally? But I doubt this is
going to help much seeing how I can create a clean workspace using the
same Eclipse install and everything works fine. Well almost, I still
have to Update Attributes before it the query succeeds, which I find
strange. Also it works fine against 3.2 on XP and against 3.2 and 3.3.
on Linux.<br>
<br>
This would seem to indicate that issue is with my old (3.2) workspace
not my Jira.<br>
<br>
Joel<br>
</body>
</html>
--------------010608040002080708080609--
|
|
|
| Re: Problem with Jira and Mylyn on 3.3 [message #577660 is a reply to message #22154] |
Sun, 19 August 2007 22:08 |
Stefan Engel
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
Hi,
as far as i can see, the problem with "No project with key "UME" found"
lies in the parsing of the rss data - at least in the Europa version of
Mylyn.
I reproduced this with Jira 3.10 and Mylyn (Europa) using a project
with name "Xyz" and a key of "XYZ". When building a query I got the
mentioned error. When I renamed the project into XYZ too (same value
as the project key which is used for numbering the issues), then
everything worked fine. A little further investigation showed that
Mylyn parses the rss data for an issue looking for the project key
(as the project name is not delivered whithin the rss data).
A side note: Jira always converts the project key to be uppercase.
In Mylyn the project name is extracted using the key and stripping off
the issue number, thus XYZ-123 leads to XYZ, but no project with name
XYZ could be found as the project is Xyz. This is still more confusing,
if project name and project key are not obviously related to each
other, e.g. project name "Hubba" with key "XYZZY" will result in
"No project with key "XYZZY" found" when using a saved filter from
the Jira repository.
As I have seen, there has been some work in the Jira part of Mylyn
and especially in the handling of the project key, maybe this is
fixed now (couldn't test yet).
Looking further into the Jira part of Mylyn, I saw that there are
at least two ways in which Mylyn and Jira talk to each other:
first using the web interface for login and filter queries looking
directly to the rss data of an issue and second using the RPC/SOAP
interface of Jira. Wouldn't it be better to completely skip the
handling of the web-interface access and just use the SOAP interface?
Using the SOAP interface there are some nice features available
which are easier to deal with than using the web interface (worklogs,
setting correct estimates, getting the project name from issue data of
a filter query, ...).
Regards,
Stefan
Joel Rosi-Schwartz wrote:
> Hi,
>
> I have four Europa installations two on XP an two on RH Linux. On all
> four I am having the same problem with getting Mylyn speaking with our
> in house Jira (Professional Edition, Version: 3.3.3-#99). I am migrating
> from an Eclipse 3.2.x / Mylar environment where this has worked fine for
> near a year. I went back today to the 3.2 systems and confirmed that
> they do indeed still work.
>
> I can configure and validate the repository. When I try to create a
> query I get an error dialog saying:
>
> Error parsing server response: No project with key "UME" found'
>
> For the fun of it I set up a task repository into
> http://jira.jboss.com/jira and have the same problem.
>
> I have checked the Eclipse logs, but there are no relevant items.
>
> What really concerns me is that I have searched the e.t.mylyn news group
> and the web, and have come up empty handed with similar problems being
> reported.
>
> Any ideas on how to track this down would be very welcome.
>
> Thanks,
> Joel
>
|
|
|
Goto Forum:
Current Time: Fri Dec 27 07:51:20 GMT 2024
Powered by FUDForum. Page generated in 0.06232 seconds |
] 
Search
Help
Register
Login
Home
