October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18571) org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18571: ----------------------------------- Attachment: p2diff_SR1_SR1a See attached p2diff {code}mistria@mistria--rh:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://download.jboss.org/jbosstools/updates/requirements/luna/2014091809... http://download.eclipse.org/releases/luna/201409261001 > p2diff_SR1_SR1a{code} Unfortunately, I made wrong assumption about platform build: other bundles that contain branding (ie with their about.properties modified to show another build timestamp) are modified too. There is no functional changes, but it affects for example bundles such as org.eclipse.jdt... It may be worth updating it for GA. > org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-a > Fix For: 4.2.0.CR2 > > Attachments: p2diff_SR1_SR1a > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18628) NPE when creating Connection Profile using forge wizard

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18628?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-18628: ------------------------------------ It turned out that I can reproduce only in JBDS. Can you please try on JBDS? > NPE when creating Connection Profile using forge wizard > ------------------------------------------------------- > > Key: JBIDE-18628 > URL: https://issues.jboss.org/browse/JBIDE-18628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > Priority: Blocker > Labels: regression > Fix For: 4.2.0.CR2 > > > {code} > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:459) > at java.util.Properties.setProperty(Properties.java:166) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.createProperties(ConnectionProfileManagerImpl.java:172) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveExistingProfile(ConnectionProfileManagerImpl.java:82) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfile(ConnectionProfileManagerImpl.java:73) > at org.jboss.tools.forge.ui.internal.ext.database.ConnectionProfileManagerImpl.saveConnectionProfiles(ConnectionProfileManagerImpl.java:142) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.database.tools.connections.ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.saveConnectionProfiles(ConnectionProfileManager_$$_javassist_38d8b832-4a59-46f2-bc9d-eb9ff785daba.java) > at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl.execute(CreateConnectionProfileCommandImpl.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103) > at org.jboss.forge.addon.database.tools.connections.ui.CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.execute(CreateConnectionProfileCommandImpl_$$_javassist_e7993baf-c96e-4b2e-9196-875229a146df.java) > at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96) > at org.jboss.forge.addon.ui.controller.CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.execute(CommandController_$$_javassist_7a19049c-bb8a-4bcc-9fab-671730e3e0e2.java) > at org.jboss.tools.forge.ui.internal.ext.wizards.ForgeWizard$1.run(ForgeWizard.java:113) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18577) Examples - Hybrid Mobile Tools requirement is not fulfilled even when installed

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18577?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-18577. ------------------------------------ verified in JBDS 8.0.0 CR2a > Examples - Hybrid Mobile Tools requirement is not fulfilled even when installed > ------------------------------------------------------------------------------- > > Key: JBIDE-18577 > URL: https://issues.jboss.org/browse/JBIDE-18577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.2.0.CR2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.2.0.CR2 > > Attachments: 18577-avail-sites.png, 18577-wizard-to-install-hybrid.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18577) Examples - Hybrid Mobile Tools requirement is not fulfilled even when installed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18577?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-18577. --------------------------------- Assignee: Fred Bricon Resolution: Done Fixed > Examples - Hybrid Mobile Tools requirement is not fulfilled even when installed > ------------------------------------------------------------------------------- > > Key: JBIDE-18577 > URL: https://issues.jboss.org/browse/JBIDE-18577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.2.0.CR2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.2.0.CR2 > > Attachments: 18577-avail-sites.png, 18577-wizard-to-install-hybrid.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3181) Include EAP 6.3.1 in JBDS 8.0.0 installer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3181?page=com.atlassian.jira.plugin.... ] Martin Malina edited comment on JBDS-3181 at 10/15/14 9:02 AM: --------------------------------------------------------------- I had this idea as well, but then I realized there is no such thing as EAP 6.3.1 binary (I mean available publicly - internally there is the full build), so I dismissed the idea. And I believe this JIRA should be dismissed also :) And Nick, it's not available under $0 either AFAIK. Only 6.2.0, 6.3.0 and so on. The 6.3.1 patch (and soon there will be 6.3.2) are available only separately from the customer portal and need to be applied on top of 6.3.0 was (Author: mmalina): I had this idea as well, but then I realized there is no such thing as EAP 6.3.1 binary, so I dismissed the idea. And I believe this JIRA should be dismissed also :) And Nick, it's not available under $0 either AFAIK. Only 6.2.0, 6.3.0 and so on. The 6.3.1 patch (and soon there will be 6.3.2) are available only separately from the customer portal and need to be applied on top of 6.3.0 > Include EAP 6.3.1 in JBDS 8.0.0 installer > ----------------------------------------- > > Key: JBDS-3181 > URL: https://issues.jboss.org/browse/JBDS-3181 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.CR2 > Reporter: Nick Boldt > Assignee: Burr Sutter > Priority: Blocker > Fix For: 8.0.1.GA > > > EAP 6.3.1 is available [1]. > Should we include it in the JBDS 8.0.0.GA installer as part of this week's respin-b / rename for GA dance, or are we prevented from doing so by some sort of subscription rules? > [1] http://download.devel.redhat.com/released/JBEAP-6/6.3.1/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3181) Include EAP 6.3.1 in JBDS 8.0.0 installer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3181?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3181: ------------------------------------- I had this idea as well, but then I realized there is no such thing as EAP 6.3.1 binary, so I dismissed the idea. And I believe this JIRA should be dismissed also :) And Nick, it's not available under $0 either AFAIK. Only 6.2.0, 6.3.0 and so on. The 6.3.1 patch (and soon there will be 6.3.2) are available only separately from the customer portal and need to be applied on top of 6.3.0 > Include EAP 6.3.1 in JBDS 8.0.0 installer > ----------------------------------------- > > Key: JBDS-3181 > URL: https://issues.jboss.org/browse/JBDS-3181 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.CR2 > Reporter: Nick Boldt > Assignee: Burr Sutter > Priority: Blocker > Fix For: 8.0.1.GA > > > EAP 6.3.1 is available [1]. > Should we include it in the JBDS 8.0.0.GA installer as part of this week's respin-b / rename for GA dance, or are we prevented from doing so by some sort of subscription rules? > [1] http://download.devel.redhat.com/released/JBEAP-6/6.3.1/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18571: ----------------------------------- Summary: org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds (was: Old Eclipse Platform in CR2 builds (should be Luna SR1)) > org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR2 > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18571) org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18571?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18571: ----------------------------------- Priority: Minor (was: Critical) > org.eclipse.platform bundle comes from pre-SR1 build in CR2 builds > ------------------------------------------------------------------ > > Key: JBIDE-18571 > URL: https://issues.jboss.org/browse/JBIDE-18571 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Mickael Istria > Priority: Minor > Labels: respin-a > Fix For: 4.2.0.CR2 > > > JBoss Tools 4.2.0.CR2 / JBDS 8.0.0.CR2 should use Eclipse Luna SR1 (4.4.1), but everywhere we look, we see this Eclipse Platform feature: > org.eclipse.platform_4.4.0.v20140911-0143.jar > In both JBT and JBDS target platforms: > http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > Also, I can see this version in my local installation of JBDS 8.0.0.CR1 B286. > I know about JBIDE-18539 - that Eclipse didn't upversion the platform, so it's still 4.4.0 for SR1, but at least the time stamp should be v20140925 as mentioned in that JIRA. This seems like we don't have SR1 at all. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18625) Prepare for 4.2.0.Final/8.0.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18625?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18625: ------------------------------------ There IS a CR2b coming but it'll be CALLED "Final" so that we don't have to THEN do another round of renames. > Prepare for 4.2.0.Final/8.0.0.GA > -------------------------------- > > Key: JBIDE-18625 > URL: https://issues.jboss.org/browse/JBIDE-18625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.CR2, 4.2.0.Final > > > Steps to do: > 1. respin JBT/JBDS CR2 target platforms w/ Final-SNAPSHOT in their name > * https://github.com/jbosstools/jbosstools-target-platforms/pull/102 > * https://github.com/jbosstools/jbosstools-target-platforms/pull/101 > 2. respin parent pom w/ Final-SNAPSHOT as version, pointing to above TPs (depends on step 1) > * https://github.com/jbosstools/jbosstools-build/pull/150 merged; https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.par... >=40 spinning > 3. respin Central/EA CR2 target platforms w/ Final-SNAPSHOT in their name (depends on step 2) > * https://github.com/jbosstools/jbosstools-discovery/pull/237 (waiting on step 2 to be complete) > 4. send task jiras out reminding people to update their root poms to use latest parent pom, in order that their bits will be called "Final" instead of "CR2" > * TODO -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18625) Prepare for 4.2.0.Final/8.0.0.GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18625?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18625: ------------------------------- Description: Steps to do: 1. respin JBT/JBDS CR2 target platforms w/ Final-SNAPSHOT in their name * https://github.com/jbosstools/jbosstools-target-platforms/pull/102 * https://github.com/jbosstools/jbosstools-target-platforms/pull/101 2. respin parent pom w/ Final-SNAPSHOT as version, pointing to above TPs (depends on step 1) * https://github.com/jbosstools/jbosstools-build/pull/150 merged; https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.par... >=40 spinning 3. respin Central/EA CR2 target platforms w/ Final-SNAPSHOT in their name (depends on step 2) * https://github.com/jbosstools/jbosstools-discovery/pull/237 (waiting on step 2 to be complete) 4. send task jiras out reminding people to update their root poms to use latest parent pom, in order that their bits will be called "Final" instead of "CR2" * TODO was: Steps to do: 1. respin JBT/JBDS CR2 target platforms w/ Final-SNAPSHOT in their name * https://github.com/jbosstools/jbosstools-target-platforms/pull/102 * https://github.com/jbosstools/jbosstools-target-platforms/pull/101 2. respin parent pom w/ Final-SNAPSHOT as version, pointing to above TPs (depends on step 1) * https://github.com/jbosstools/jbosstools-build/pull/150 (waiting on step 1 to be complete) 3. respin Central/EA CR2 target platforms w/ Final-SNAPSHOT in their name (depends on step 2) * https://github.com/jbosstools/jbosstools-discovery/pull/237 (waiting on step 2 to be complete) 4. send task jiras out reminding people to update their root poms to use latest parent pom, in order that their bits will be called "Final" instead of "CR2" * TODO > Prepare for 4.2.0.Final/8.0.0.GA > -------------------------------- > > Key: JBIDE-18625 > URL: https://issues.jboss.org/browse/JBIDE-18625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.CR2, 4.2.0.Final > > > Steps to do: > 1. respin JBT/JBDS CR2 target platforms w/ Final-SNAPSHOT in their name > * https://github.com/jbosstools/jbosstools-target-platforms/pull/102 > * https://github.com/jbosstools/jbosstools-target-platforms/pull/101 > 2. respin parent pom w/ Final-SNAPSHOT as version, pointing to above TPs (depends on step 1) > * https://github.com/jbosstools/jbosstools-build/pull/150 merged; https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.par... >=40 spinning > 3. respin Central/EA CR2 target platforms w/ Final-SNAPSHOT in their name (depends on step 2) > * https://github.com/jbosstools/jbosstools-discovery/pull/237 (waiting on step 2 to be complete) > 4. send task jiras out reminding people to update their root poms to use latest parent pom, in order that their bits will be called "Final" instead of "CR2" > * TODO -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014