[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19473:
----------------------------------------
Error is still there. I don't think it's related to udpate-sites. It seems to be clearly inside the catalog.
> Central can't load Discovery catalog
> ------------------------------------
>
> Key: JBIDE-19473
> URL: https://issues.jboss.org/browse/JBIDE-19473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.
> The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content.
> Log says
> {quote}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
> !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar
> {quote}
> I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19473:
------------------------------------
[~mickael_istria] I believe this is now fixed, since the composite site contains both the Central TP (3rd party) and Central update site (JBT content):
http://download.jboss.org/jbosstools/discovery/nightly/core/master/compos...
Please re-test and confirm.
> Central can't load Discovery catalog
> ------------------------------------
>
> Key: JBIDE-19473
> URL: https://issues.jboss.org/browse/JBIDE-19473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.
> The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content.
> Log says
> {quote}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
> !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar
> {quote}
> I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19473:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
> Central can't load Discovery catalog
> ------------------------------------
>
> Key: JBIDE-19473
> URL: https://issues.jboss.org/browse/JBIDE-19473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Alpha2
>
>
> Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.
> The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content.
> Log says
> {quote}
> !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
> !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar
> {quote}
> I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19579) Context vs Contexts
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19579?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19579:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Context vs Contexts
> --------------------
>
> Key: JBIDE-19579
> URL: https://issues.jboss.org/browse/JBIDE-19579
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Just a small inconsistency - sometimes in JBT there's Context and Dependency Injection or Context*s* and Dependency Injection.
> Most references use Context not Context*s*. The correct one is the second one.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19579) Context vs Contexts
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19579?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19579:
--------------------------------------
Assignee: Viacheslav Kabanovich
> Context vs Contexts
> --------------------
>
> Key: JBIDE-19579
> URL: https://issues.jboss.org/browse/JBIDE-19579
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
>
> Just a small inconsistency - sometimes in JBT there's Context and Dependency Injection or Context*s* and Dependency Injection.
> Most references use Context not Context*s*. The correct one is the second one.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19416) JBDS update site zip should not include both packed and unpacked artifacts
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19416?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19416:
------------------------------------
You edited my comment instead of adding a new one, but ... sure, until someone like Max or Denis ask for smaller offline footprints we can defer this to later. Set fixversion to Beta1 in case we decide to reprioritize this later in the cycle. I'm still +1 for doing this.
> JBDS update site zip should not include both packed and unpacked artifacts
> --------------------------------------------------------------------------
>
> Key: JBIDE-19416
> URL: https://issues.jboss.org/browse/JBIDE-19416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.3.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.3.0.Beta1
>
>
> JBDS 8.1.0.Beta1 update site zip is 524M and contains both packed (.pack.gz) and regular jars; no need to include both. Ideally we'd include ONLY the packed ones.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19416) JBDS update site zip should not include both packed and unpacked artifacts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19416?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-19416 at 4/13/15 12:53 PM:
------------------------------------------------------------------
{quote}Disagree - zip should be smallest foot print needed for an offline install.{quote}
I don't think there is such a rule in general.
{quote}So, +1 for closing this as invalid and opening a new issue to purge duplicate .jar artifacts from the update site for which a .jar.pack.gz artifact exists (making sure metadata is updated too!). Or +1 for renaming this issue.{quote}
IMO, let's just focus on other things that deliver more value. This kind of optimization doesn't provide much to users/contributors.
was (Author: nickboldt):
Disagree - zip should be smallest foot print needed for an offline install.
But a better solution would be to have the update site (and zip) contain ONLY the packed artifacts (except for cases where there is no pack.gz version of a jar due to an exclusion rule), so that BOTH the site and the zip are smaller... and also identical in content.
So, +1 for closing this as invalid and opening a new issue to purge duplicate .jar artifacts from the update site for which a .jar.pack.gz artifact exists (making sure metadata is updated too!). Or +1 for renaming this issue.
> JBDS update site zip should not include both packed and unpacked artifacts
> --------------------------------------------------------------------------
>
> Key: JBIDE-19416
> URL: https://issues.jboss.org/browse/JBIDE-19416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.3.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.3.x
>
>
> JBDS 8.1.0.Beta1 update site zip is 524M and contains both packed (.pack.gz) and regular jars; no need to include both. Ideally we'd include ONLY the packed ones.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years