October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18646) For JBIDE 4.2.0.Final: Prepare for Final/GA release [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18646?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-18646: ----------------------------------- Assignee: Fred Bricon > For JBIDE 4.2.0.Final: Prepare for Final/GA release [Central] > ------------------------------------------------------------- > > Key: JBIDE-18646 > URL: https://issues.jboss.org/browse/JBIDE-18646 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final [Central]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-546) Update JBDS GSG for 8.0

by Michelle Murray (JIRA)

Michelle Murray created TOOLSDOC-546: ---------------------------------------- Summary: Update JBDS GSG for 8.0 Key: TOOLSDOC-546 URL: https://issues.jboss.org/browse/TOOLSDOC-546 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Components: Getting Started Guide Reporter: Michelle Murray Assignee: Michelle Murray Fix For: 4.2.0.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-546) Update JBDS GSG for 8.0

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-546?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-546: ------------------------------------- Sprint: 2014/S19 (13-Oct > 26-Oct) > Update JBDS GSG for 8.0 > ----------------------- > > Key: TOOLSDOC-546 > URL: https://issues.jboss.org/browse/TOOLSDOC-546 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Getting Started Guide > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18652) Random NPE in Eclipse Error Log View

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18652?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18652: ---------------------------------- Description: Could be related to Central Update Site not being available, but it should not fail with NPE in this case. {code}java.lang.NullPointerException at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} was: {code}java.lang.NullPointerException at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} > Random NPE in Eclipse Error Log View > ------------------------------------ > > Key: JBIDE-18652 > URL: https://issues.jboss.org/browse/JBIDE-18652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Denis Golovin > Fix For: 4.3.x > > > Could be related to Central Update Site not being available, but it should not fail with NPE in this case. > {code}java.lang.NullPointerException > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18652) Random NPE in Eclipse Error Log View

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18652: ------------------------------------- Summary: Random NPE in Eclipse Error Log View Key: JBIDE-18652 URL: https://issues.jboss.org/browse/JBIDE-18652 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.2.0.CR2 Reporter: Denis Golovin {code}java.lang.NullPointerException at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18652) Random NPE in Eclipse Error Log View

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18652?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18652: ---------------------------------- Fix Version/s: 4.3.x > Random NPE in Eclipse Error Log View > ------------------------------------ > > Key: JBIDE-18652 > URL: https://issues.jboss.org/browse/JBIDE-18652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.CR2 > Reporter: Denis Golovin > Fix For: 4.3.x > > > {code}java.lang.NullPointerException > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:101) > at org.eclipse.equinox.internal.p2.metadata.OSGiVersion.compareTo(OSGiVersion.java:1) > at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:316) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3163: ---------------------------------- As per the work done in JBIDE-18594, we should also make the staging/ and development/ URLs consistent for JBDS: Today we have this: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.CR2a-build... http://www.qa.jboss.com/binaries/RHDS/updates/staging/ *[EMPTY, not used]* http://www.qa.jboss.com/binaries/RHDS/updates/development/8.0.0.CR2b-upda... http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.2.luna/ http://www.qa.jboss.com/binaries/RHDS/discovery/development/8.0.0.CR2a/ > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18594: ------------------------------------ Similar work to be done for JBDS URL consistency: JBDS-3163 > Create a consistent /staging/ URL for JBT > ----------------------------------------- > > Key: JBIDE-18594 > URL: https://issues.jboss.org/browse/JBIDE-18594 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.CR2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Labels: respin-a, respin-b > Fix For: 4.2.0.CR2 > > > Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless. > We need to rework the staging process so that its output is similar to what will be the output of a release: > * updates/staging/luna , compositing > ** target-platform > ** JBT core > ** Central TP > * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... > Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties > Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: ------------------------------------ More steps: 5. Update jobs in Jenkins to use new Final-SNAPSHOT target platforms: https://github.com/jbdevstudio/jbdevstudio-ci/pull/138 https://github.com/jbdevstudio/jbdevstudio-ci/pull/139 > 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 > * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > * http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > * http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > * http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... > 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 done > * https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > 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 merged; https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... >=65 done > * http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.4... > * http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... > 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" > * https://github.com/jbdevstudio/jbdevstudio-ci/pull/137 > * http://lists.jboss.org/pipermail/jbosstools-dev/2014-October/009414.html -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18651) Image dropped to VPE is not rendered on server

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18651: -------------------------------------- Summary: Image dropped to VPE is not rendered on server Key: JBIDE-18651 URL: https://issues.jboss.org/browse/JBIDE-18651 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.CR2 Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.1.Final, 4.3.x 1. Import HTML 5 project from JBoss Central 2. Open index.html page 3. Drag&drop some image from img subdirectory to source part of VPE ASSERT: Image is displayed in visual part of VPE 4. Run project on server ERROR: Dropped Image is not rendered in web browser Once leading "/" is removed from img tag source attribute droped image is rendered on web page deployed to server -- 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