January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1010) Create UI test to ensure user cannot left xml editor with an invalid xml

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBTIS-1010: -------------------------------------- Summary: Create UI test to ensure user cannot left xml editor with an invalid xml Key: JBTIS-1010 URL: https://issues.jboss.org/browse/JBTIS-1010 Project: JBoss Tools Integration Stack Issue Type: Task Reporter: Aurélien Pupier see [FUSETOOLS-2224] for context and exact scenario -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1010) Create UI test to ensure user cannot left xml editor with an invalid xml

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1010?page=com.atlassian.jira.plugin... ] Aurélien Pupier updated JBTIS-1010: ----------------------------------- Component/s: Fuse IDE QE > Create UI test to ensure user cannot left xml editor with an invalid xml > ------------------------------------------------------------------------- > > Key: JBTIS-1010 > URL: https://issues.jboss.org/browse/JBTIS-1010 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Reporter: Aurélien Pupier > > see [FUSETOOLS-2224] for context and exact scenario -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- none of these suggestions are working. * path to a zip: jar:file:/C:/Data/<therestofmypath>.zip!/ --> same error * path using 3 prefix slashes to avoid access violations: file:///C:/Data/<therestofmypath> --> the 3 slashes are stripped down to a single one * path replacing c:/ with just one slash: file:///Data/<therestofmypath> --> the 3 slashes are stripped down to a single one * shorter path (because Windows sucks for long file paths): file:///tp/ --> same error also tried to set the "correct JRE environment" in target platfrom configuration --> no effect the only workaround for now is to not use a local TP and get back to dark age of always use remote repo which takes a lot of time when switching > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23294) Console is badly rendering some characters when starting Container Development Environment

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23294?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23294: ------------------------------------ Which process is launching the console view instead of the terminal view? Some steps to reproduce (including operating system details and JVM version) would be useful here. > Console is badly rendering some characters when starting Container Development Environment > ------------------------------------------------------------------------------------------ > > Key: JBIDE-23294 > URL: https://issues.jboss.org/browse/JBIDE-23294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > Fix For: LATER > > Attachments: screenshot-1.png > > > - there is a special character before the [KProgress > - what means K for KProgress? > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > [KProgress: 10% > [KProgress: 20% > [KProgress: 90% > [K==> default: Matching MAC address for NAT networking... > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBTIS-1008: ----------------------------------- Could be pointless, but you could also try accessing the target platform using different URI formats: * file:/C:/Data/<therestofmypath> ... not working So try: * path to a zip: jar:file:/C:/Data/<therestofmypath>.zip!/ * path using 3 prefix slashes to avoid access violations: file:///C:/Data/<therestofmypath> * path replacing c:/ with just one slash: file:///Data/<therestofmypath> * shorter path (because Windows sucks for long file paths): file:///tp/ > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBTIS-1008 at 1/3/17 9:58 AM: ----------------------------------------------------------- Since the full fuse TP builds okay it seems to be more related to WIndows? I did see this which seems relevant to your screen capture: https://bugs.eclipse.org/bugs/show_bug.cgi?id=434959 was (Author: pleacu): Since the full fuse TP builds okay it seems to be more related to WIndows? I did see this which seems relevant to your screen capture: ttps://bugs.eclipse.org/bugs/show_bug.cgi?id=434959 > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- Current state of understanding: There are 2 different bugs: * when using local "Directory": the jars which should be exploded in folder stay in jars ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? ** the implication is that we can't start a CDK server with such a TP * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) ** looks like a p2 bugs ** the implication is that the TP doesn't resolve at all If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: IncludeWhateverPluginFromRemoteRepoFixjavax.cryptoIssue.png, screenshot-1.png > > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4233: ----------------------------- Fix Version/s: 10.3.0.AM2 11.0.0.AM1 > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Fix For: 10.3.0.AM2, 11.0.0.AM1 > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4233) Migrate jbosstools, devstudio, and release process jobs to Central CI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4233?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4233: -------------------------------- Assignee: Nick Boldt > Migrate jbosstools, devstudio, and release process jobs to Central CI > --------------------------------------------------------------------- > > Key: JBDS-4233 > URL: https://issues.jboss.org/browse/JBDS-4233 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.AM2, 11.0.0.AM1 > > > As Bos MW Jenkins is deprecated, it's time to migrate all the jbt 4.4.x and devstudio 10.x jobs to the new server infrastructure. Old jobs from jbt 4.3 / devstudio 9.x will not be migrated. > Installed plugins are not the same on Bos MW and CCI. We'll need to get more plugins installed on CCI to support devstudio jobs. > https://docs.google.com/spreadsheets/d/1WJV3bOdlY1unOH5i23v33V7dZKIqTbo1A... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4234) <Reading Schema Error:null>

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4234?page=com.atlassian.jira.plugin.... ] Jeff MAURY closed JBDS-4234. ---------------------------- Resolution: Duplicate Issue > <Reading Schema Error:null> > --------------------------- > > Key: JBDS-4234 > URL: https://issues.jboss.org/browse/JBDS-4234 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: hibernate > Reporter: kokila vishwa > Fix For: LATER > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017