2:17 p.m.
evaluate options that removes dependency to GWT SDK bundle
----------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Nick Boldt
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into the
plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8012:
------------------------------------
Summary: evaluate options that remove dependency to GWT SDK bundle (was: evaluate
options that removes dependency to GWT SDK bundle)
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Nick Boldt
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:45 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8012:
-----------------------------------
Can you depend on their plugins instead of their features?
Or... can we rebuild their bits from source ourselves, and re-release it using
osgi-friendly feature names (instead of their insanity), with plugins that export packages
correctly?
Are sources available? If not, we could simply rebuild their features like I do for
Drools, and publish that in a way that we can then depend on. We'd still need to
rebuild when they rename their features, but we might be able to automate that using a
script that culls information from their site.xml.
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Nick Boldt
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-8012:
-------------------------------------
we shouldn't rebuild GWT google plugins - google should simply just be informed about
this problem and if we can't depend on them we'll have to remove GWT plugins.
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Nick Boldt
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8012:
-----------------------------------------
max will mention this stuff to google in his mail to them. I guess this is the best I can
do for now.
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8012:
-----------------------------------------
I now set the dependency to the gwt sdk plugin to be optional. This allows existing
installations not to break as soon as new sdk's get installed. On the other hand this
does not solve the problem where new users try to install our facet and dont get a sdk
plugin pulled when the gwt sdk version changes (and the sdk we depend on disappears from
the google update site).
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim resolved JBIDE-8012.
-------------------------------------
Resolution: Done
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim edited comment on JBIDE-8012 at 1/7/11 11:42 AM:
------------------------------------------------------------------
thanks nick! pretty good suggestions. I now sat with max and we decided to set the
dependency to the gwt sdk plugin to be optional. This allows existing installations not to
break as soon as new sdk's get installed. On the other hand this does not solve the
problem where new users try to install our facet and dont get a sdk plugin pulled when the
gwt sdk version changes (and the sdk we depend on disappears from the google update site).
was (Author: adietish):
I now set the dependency to the gwt sdk plugin to be optional. This allows existing
installations not to break as soon as new sdk's get installed. On the other hand this
does not solve the problem where new users try to install our facet and dont get a sdk
plugin pulled when the gwt sdk version changes (and the sdk we depend on disappears from
the google update site).
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.x
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8012:
------------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.x)
committed to TRUNK (CR1)
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.0.CR1
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:40 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8012) evaluate options that remove dependency to GWT SDK bundle
[
https://issues.jboss.org/browse/JBIDE-8012?page=com.atlassian.jira.plugin...
]
Vlado Pakan closed JBIDE-8012.
------------------------------
Verified on JBT 2011-01-11_22-57-02-H898.
evaluate options that remove dependency to GWT SDK bundle
---------------------------------------------------------
Key: JBIDE-8012
URL: https://issues.jboss.org/browse/JBIDE-8012
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: GWT
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: googlebug
Fix For: 3.2.0.CR1
nick, I thought about possibilities to remove the dependency to the gwt sdk bundle since
our integration plugin gets uninstallable as soon as google releases a new version. We
currently have no choice but to track their updates and release a new version.
The basic problem is that google had the great idea to include the plugin version into
the plugin name and that they remove old version from their update site.
I currently don't see any viable solution (optional dependencies dont help for new
versions; I cannot depend on packages instead of the bundle since their bundle does not
export any package).
Do you see any option that would allow us to trigger the installation of the gwt-sdk
bundle when someone installs our integration plugin?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5571
days inactive
5587
days old
jbosstools-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Andre Dietisheim (JIRA) -
Max Andersen (JIRA)
-
Nick Boldt (JIRA)
-
Vlado Pakan (JIRA)