every code that used socket programming is affected.
Snjeza
On 11/1/2012 11:02 AM, Max Rydahl Andersen wrote:
so not only our central downloads but also basic P2 is affected by
this Java 7/ipv6 bug ?!
/max
On 01 Nov 2012, at 10:13, Snjezana Peco <snjezana.peco(a)redhat.com> wrote:
> Hi,
>
> It is not possible to run 32-bit eclipse with 64 bit jvm.
> The user probably has 32-bit JVM installed that is used automatically when starting
Eclipse on Windows 7.
> I think the user faced the issue described in
https://issues.jboss.org/browse/JBDS-2370
>
> Snjeza
>
> On 11/1/2012 9:01 AM, Max Rydahl Andersen wrote:
>> Hey,
>>
>> I spotted this comment on our blog from Alpha2:
https://community.jboss.org/en/tools/blog/2012/10/09/jboss-tools-4-alpha-...
>>
>> "Nick, you are right. I was using a 32-bit Eclipse with a 64-bit JDK 7 in a
Windows 7. I tried now with a 64-bit Eclipse and I was able to install Jboss Tools.
>> I was using a 32-bit Eclipse because the problem originated in another machine
with a 32-bit Eclipse, 32-bit JDK 7 and Windows XP. Do you know if it´s possible to
install JBoss Tools in a 32-bit Eclipse even with a 32-bit JDK? Anyways, tomorrow I will
double check this other machine configuration (I don´t have it with me now).
>> thank you"
>>
>> What am I missing here that triggers he cannot see our jboss tools updatesite
content when he is running a 32-bit eclipse with a 64-bit JVM ? (how is that even possible
- running 32-bit eclipse with 64 bit jvm ?)
>>
>> /max
>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev