[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18678:
----------------------------------------
{quote}
I thought the intent was that if the updatesite containts the usage plugin it will get installed, the third party would simply just exclude it from their updatesite? did that not work ?
{quote}
It would work if we added this new impl usage plugin as an optional (greedy) dependency to browsersim plugin.xml (and the rest of plugins which use usage) instead of adding that feature requirement. But it still requires to update every JBT component.
It seems that if we introduce this new usage impl plugin we can't provide a full backwards compatibility. We have to update usage clients (feature.xml's or plugins.xmls).
As alternative we could create an extension point which would disable that dialog. No need to introduce new plugin and no need to change anything in our components which use usage but any plugin would be able to disable usage dialog and the only way to enable usage for the user would be manual enabling via preferences (or uninstalling that plugin which disables the dialog via our new extension point).
WDYT?
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Alexey Kazakov
> Fix For: 4.3.x
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3289:
-----------------------------------
After discussing with max, we agreed on renaming the category attribute to tags, an optional attribute which would allow a comma-separated list of tags.
> JBoss Central proxy wizards need to recognize early access.
> -----------------------------------------------------------
>
> Key: JBDS-3289
> URL: https://issues.jboss.org/browse/JBDS-3289
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.2.GA
> Reporter: Paul Leacu
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18878:
----------------------------------------
Fix Version/s: 4.2.3.Final
(was: 4.2.2.Final)
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months