June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-24140: ------------------------------------- Assignee: Ondrej Dockal (was: Jeff MAURY) > Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24140 > URL: https://issues.jboss.org/browse/JBIDE-24140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Ondrej Dockal > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.Final > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* > http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 0.56 sec 5 > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 15 ms 11 > {code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 11 builds (Since #69 ) > Took 15 ms. > add description > Error Message > Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > Stacktrace > junit.framework.AssertionFailedError: Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:200) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:413) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:409) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments(WebXMLValidationTest.java:55){code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 5 builds (Since Unstable#75 ) > Took 0.56 sec. > add description > Stacktrace > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig(WebXMLValidationTest.java:103){code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24517) Provision windows on bare metal machine

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24517?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24517: ---------------------------------- Fix Version/s: 4.5.x > Provision windows on bare metal machine > --------------------------------------- > > Key: JBIDE-24517 > URL: https://issues.jboss.org/browse/JBIDE-24517 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci, devsuite > Fix For: 4.5.x > > > * Configure foreman for provisioning machines in the same subnet > * Prepare image for provisioning > * Provision basic image to local machine -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4440: ------------------------------------ There is p2 diff comparing JBDS a JBT target platform: {code} p2diff -console -mode=all -query=all http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... {code} Output: [^p2diff_JBT_JBDS_TPs.txt] And there is what I got when I excluded sources: {code} p2diff -console -mode=all -query=all http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... | grep -v source {code} Output: [^p2diff_JBT_JBDS_TPs_filtered.txt] > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4440: ------------------------------- Attachment: p2diff_JBT_JBDS_TPs.txt > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4440?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4440: ------------------------------- Attachment: p2diff_JBT_JBDS_TPs_filtered.txt > Add sources to the JBDS target platform > --------------------------------------- > > Key: JBDS-4440 > URL: https://issues.jboss.org/browse/JBDS-4440 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.AM1 > > Attachments: p2diff_JBT_JBDS_TPs.txt, p2diff_JBT_JBDS_TPs_filtered.txt > > > We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. > Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... > If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. > I will ask people at jbosstools-dev for their opinions. > CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4440) Add sources to the JBDS target platform

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4440: ---------------------------------- Summary: Add sources to the JBDS target platform Key: JBDS-4440 URL: https://issues.jboss.org/browse/JBDS-4440 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Components: target-platform Affects Versions: 11.0.0.AM1 Reporter: Lukáš Valach Assignee: Nick Boldt Fix For: 11.0.0.AM1 We are maintaining target platfroms for JBT [1] and for JBDS [2] separatelly. The only difference is that TP for JBT includes sources but TP for JBDS doesn't. Consequently, JBT users can install plugins including sources but JBDS users can't. In my opinion both should have sources. [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... [2] https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.70.0.AM1... If we decide to add sources to JBDS TP, we'd be able to drop one of the TPs entirely and just build one for both JBT and JBDS, saving time and disk. I will ask people at jbosstools-dev for their opinions. CC: [~nickboldt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4430: -------------------------------- Sprint: devex #133 Jun 2017 > EAP is not added to runtime locations > ------------------------------------- > > Key: JBDS-4430 > URL: https://issues.jboss.org/browse/JBDS-4430 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties. > On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code). > And btw. it could use some logging as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4430: -------------------------------- Story Points: 5 > EAP is not added to runtime locations > ------------------------------------- > > Key: JBDS-4430 > URL: https://issues.jboss.org/browse/JBDS-4430 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties. > On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code). > And btw. it could use some logging as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4430: -------------------------------- Component/s: platform-installer > EAP is not added to runtime locations > ------------------------------------- > > Key: JBDS-4430 > URL: https://issues.jboss.org/browse/JBDS-4430 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties. > On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code). > And btw. it could use some logging as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4430) EAP is not added to runtime locations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4430?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4430: -------------------------------- Affects Version/s: 11.0.0.AM1 > EAP is not added to runtime locations > ------------------------------------- > > Key: JBDS-4430 > URL: https://issues.jboss.org/browse/JBDS-4430 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 11.0.0.AM1 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > The event handler responsible for adding EAP to devstudio runtime locations gets called immediately after the main installation, no matter what state devstudio is in. Hence, EAP is not usually added to runtime_locations.properties. > On windows, runtime detection can still somehow get past this and finds EAP on its own. But on mac it doesn't. Plus the location of runtime_locations.properties file on mac is different to other platforms (needs update in the code). > And btw. it could use some logging as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017