12:42 p.m.
Hi,
Using nightly build there is now GWT in there and its not installing.
Why did we add it in again ?
/max
http://about.me/maxandersen
3:16 p.m.
On 07/22/2011 12:42 PM, Max Rydahl Andersen wrote:
Hi,
Using nightly build there is now GWT in there and its not installing.
Why did we add it in again ?
/max
http://about.me/maxandersen
Nick enabled this build since it now is installable again: you have to
install the google plugins in a first step though as it is described in
our wiki:
http://community.jboss.org/wiki/CreateGWTProjectsWithJBossToolsAndEclipseWTP
This is how things actually worked before we decided to mirror the
google plugins which we stopped to do when we noticed that their licence
would not allow us to do so.
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
4:03 p.m.
> Using nightly build there is now GWT in there and its not
installing.
>
> Why did we add it in again ?
>
> /max
> http://about.me/maxandersen
>
Nick enabled this build since it now is installable again: you have to
install the google plugins in a first step though as it is described in
our wiki:
http://community.jboss.org/wiki/CreateGWTProjectsWithJBossToolsAndEclipseWTP
This is how things actually worked before we decided to mirror the
google plugins which we stopped to do when we noticed that their licence
would not allow us to do so.
The only time I had to add google gwt update site (As I recall) was when I needed their
SDK.
It fetched the gwt plugin we had an direct dependency on via an associated site url.
Can't we at least do that ? or is there any problems with that ?
/max
http://about.me/maxandersen
4:09 p.m.
On 07/22/2011 04:03 PM, Max Rydahl Andersen wrote:
>> Using nightly build there is now GWT in there and its not
installing.
>>
>> Why did we add it in again ?
>>
>> /max
>> http://about.me/maxandersen
>>
> Nick enabled this build since it now is installable again: you have to
> install the google plugins in a first step though as it is described in
> our wiki:
>
> http://community.jboss.org/wiki/CreateGWTProjectsWithJBossToolsAndEclipseWTP
>
> This is how things actually worked before we decided to mirror the
> google plugins which we stopped to do when we noticed that their licence
> would not allow us to do so.
The only time I had to add google gwt update site (As I recall) was when I needed their
SDK.
afaik that's exactly what obviously happened to you now: there was no
SDK for indigo so far, so you had to add their new update site for 3.7. no?
It fetched the gwt plugin we had an direct dependency on via an
associated site url.
This approach broke each time they released a new version with a new
name and removed the old plugin. Right, since they now removed the
version from the name we could try that again.
Can't we at least do that ? or is there any problems with that ?
/max
http://about.me/maxandersen
4:48 p.m.
>> This is how things actually worked before we decided to
mirror the
>> google plugins which we stopped to do when we noticed that their licence
>> would not allow us to do so.
> The only time I had to add google gwt update site (As I recall) was when I needed
their SDK.
afaik that's exactly what obviously happened to you now: there was no SDK for indigo
so far, so you had to add their new update site for 3.7. no?
No - the SDK have never been a dependency (except the time you added it in which caused
other problems).
It's just the google core/ui that is missing afaics.
> It fetched the gwt plugin we had an direct dependency on via an associated site url.
This approach broke each time they released a new version with a new name and removed the
old plugin. Right, since they now removed the version from the name we could try that
again.
Exactly!
/max
http://about.me/maxandersen
4:52 p.m.
Since we can't redistribute, we can't put the GWT stuff INTO our update
site(s).
However, I can link the Indigo SR0 site (which is preloaded when you add
the JBT nightly trunk update site into Eclipse) to the GWT for e37 site
like this.
See https://issues.jboss.org/browse/JBIDE-9386
Ca va mieux?
On 07/22/2011 10:48 AM, Max Rydahl Andersen wrote:
>>> This is how things actually worked before we decided to
mirror the
>>> google plugins which we stopped to do when we noticed that their licence
>>> would not allow us to do so.
>> The only time I had to add google gwt update site (As I recall) was when I needed
their SDK.
>
> afaik that's exactly what obviously happened to you now: there was no SDK for
indigo so far, so you had to add their new update site for 3.7. no?
No - the SDK have never been a dependency (except the time you added it in which caused
other problems).
It's just the google core/ui that is missing afaics.
>
>> It fetched the gwt plugin we had an direct dependency on via an associated site
url.
>
> This approach broke each time they released a new version with a new name and removed
the old plugin. Right, since they now removed the version from the name we could try that
again.
Exactly!
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4915
days inactive
4915
days old
jbosstools-dev@lists.jboss.org
5 comments
3 participants
participants (3)
-
André Dietisheim -
Max Rydahl Andersen -
Nick Boldt