Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [mylar-dev] dev build with JIRA integration 
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
...
>   Mik, there is some trouble with packaging of org.tigris.jira.core
> feature.
>   I've updated Mylar from dev site earlier today and now it don't let me
> to update because org.tigris.jira.core feature already been updated. It
> looks like bug in the update manager, but for time being, can you please
> declare that feature in site.xml, so it will be possible to not select
> it when updating.

I just replicated this, and believe that switching the update site that
these "archived features" come from is what causes the update manager to
fail.  We can't declare that feature in site.xml because it isn't on our
site, so if the current approach can't be made to work reliably it will mean
having to manually download the jira core feature from tigris.org.  But I'll
do everything I can to keep the single install.  If anyone knows of a better
mechanism than "archived features" for making update sites depend on each
other please post.

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=128831
 
>   I also wonder why refreshing issues from Jira is so slow (it takes
> nearly 5 minutes to get 29 issues from Codehaus repository). I haven't
> look in the code yet, but it smell  like server is being queried
> multiple times to get details for each issue...

I just replicated by connecting to jira.codehaus.org, and it was insanely
slow to refresh as you indicate (more than a couple of minutes).  Took that
long each time I refreshed.  Queries with developer.atlassian.com only take
a fraction of that time to refresh, so it probably has to do with checking
products as Brock indicated.  I'm considering this to be a major bug, either
on the Mylar or the JIRA dashboard side, and opened the following report to
investigate:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=128835

Note that I also found another major bug (multiple JIRA repositories can
fail) which is also on the table for today:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=128828

Mik

Back to the top