April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1067: ------------------------------------- Fix Version/s: 10.2.0.GA > Clean update site files for stable/development/staging branch > ------------------------------------------------------------- > > Key: JBTIS-1067 > URL: https://issues.jboss.org/browse/JBTIS-1067 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.2.0.GA > > > Please clean update site files in stable/development/staging branch so that there are only html and p2 files at > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/ > {code} > and all binaries are in relevant folders such as > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/ > {code} > Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following > || What we are working on? || Obsolete files || Files I'd like to keep || > | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA| > EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1067. ------------------------------------ Verified > Clean update site files for stable/development/staging branch > ------------------------------------------------------------- > > Key: JBTIS-1067 > URL: https://issues.jboss.org/browse/JBTIS-1067 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.2.0.GA > > > Please clean update site files in stable/development/staging branch so that there are only html and p2 files at > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/ > {code} > and all binaries are in relevant folders such as > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/ > {code} > Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following > || What we are working on? || Obsolete files || Files I'd like to keep || > | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA| > EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24280) Support converted types in JolokiaMBeanServerConnection

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24280?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24280: ----------------------------------------- {quote}This has the potential to be a pretty huge endeavor. A lot of jmx returned types are classes that are not available in eclipse or on the classpath. This would basically require temporarily loading jars on the classpath to generate these objects. I'm not sure to what extent this is a good idea. {quote} The purpose of this JIRA is not for classes defined in extra libraries. For stuff defined in extra libraries it will be required to be handled in Jolokia itself. Having a requirement of the class on the client side classpath seems fien for me, i think that it is the same for RMI connection. Anyway, the prupose here is to provide the correct type for "converted" type due to some basic limitatiosn of JSON, for instance: - all numerics Integer, Double, BigInteger are converted to long - Date are converted to long timestamp - Set are converted to List As we can retrieve the exact type, it is possible to convert back to the correct type. it would be even nicer to ghave it directly in the java jolokia client but it would break the API and so can be done only in a Jolokia 2.0 version. {quote} Since this is blocking other issues we really should discuss how important this is for you? {quote} Currently, I detected few values not displayed in properties due to this issue for which I'm not sure a workaround is easily possible because reflection is used to retrieve elements. Implementing this improved behavior in JolokiaMBeanServerConnection would be far easier and will benefit to everyone. I don't think that i will have time to work on it for 4.4.4 but I think that it can wait for the first Oxygen release and we will mention as "know issues" in release notes. On the other hand, I think that a minimal implementation for Integer, Date and Set might be sufficient for Camel use case (at least i have not detected other cases currently). So considering only this subset we might be able to integrate it in 4.4.4. > Support converted types in JolokiaMBeanServerConnection > ------------------------------------------------------- > > Key: JBIDE-24280 > URL: https://issues.jboss.org/browse/JBIDE-24280 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > > currently if you are trying to invoke methods/get attributes of (returning) type Integer or Date, there is a ClassCastException > i should be the case for all types converted by Jolokia/Json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4221) User can install JBDS from market without acceptation license agreements

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4221?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4221. ------------------------------ Resolution: Done Upstream bug is tracked in eclipse bugzilla, closing this jira. > User can install JBDS from market without acceptation license agreements > ------------------------------------------------------------------------ > > Key: JBDS-4221 > URL: https://issues.jboss.org/browse/JBDS-4221 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, openjdk 1.8.0_102 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.GA > > Attachments: Install_JBDS_from_marketplace.png > > > User can install Developer Studio from eclipse marketplace without acceptation terms of the licence agreements. > Step to reproduce: > # Download, unpack and start Eclipse Neon 1 > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... > # Market -> Search form "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install > # The window "Review Licenses" looks like on screenshot !Install_JBDS_from_marketplace.png|thumbnail! > # Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install JBDS. > When I check "I accept" radio button and then switch back to "I do not accept" it start works correctly. > This problem doesn't occur when installing JBoss Tools. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1064) Remove ModeShape from JBoss Tools website features

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1064?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1064. ------------------------------------ Verified > Remove ModeShape from JBoss Tools website features > -------------------------------------------------- > > Key: JBTIS-1064 > URL: https://issues.jboss.org/browse/JBTIS-1064 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.2.0.GA > > > Remove ModeShape from JBoss Tools website features since the ModeShape tooling was removed in Devstudio IS 10.x. > http://tools.jboss.org/features/modeshape.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24214) LiveReload New and Noteworthy for 4.4.4.AM3

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24214?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-24214. --------------------------------- Resolution: Rejected > LiveReload New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24214 > URL: https://issues.jboss.org/browse/JBIDE-24214 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Xavier Coulon > Priority: Critical > > Xavier Coulon, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24190 #comment Create N&N for LiveReload 4.4.4.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for LiveReload for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24242) New application wizard, properties: properly display docker pipeline resource

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24242?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24242: ------------------------------------- Story Points: 24 > New application wizard, properties: properly display docker pipeline resource > ----------------------------------------------------------------------------- > > Key: JBIDE-24242 > URL: https://issues.jboss.org/browse/JBIDE-24242 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3, pipeline_build > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: jenkins-pipeline-properties.png, pipeline-buildconfig-entry.png > > > steps: > # ASSERT: use a cdk which has the "jenkins-pipeline-example" template > # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template > # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..." > # EXEC: hit the "Defined Resources..." button > # ASSERT: Details dialog pops up listing all the resources > # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}" > !pipeline-buildconfig-entry.png! > Then inspect the children that are displayed. There should be (as documented here: https://docs.openshift.org/latest/dev_guide/builds/build_strategies.html#...) > * jenkinsfile > * jenkinsfile path > * env vars > steps: > # ASSERT: have a jenkins pipeline in OpenShift. > # EXEC: select your project in the explorer and open up the properties view > # EXEC: in the properties view select the *Build Configs* tab and select the jenkins pipeline > !jenkins-pipeline-properties.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24242) New application wizard, properties: properly display docker pipeline resource

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24242?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24242: ------------------------------------------ merged into jbosstools-4.4.x and cherry-picked into master > New application wizard, properties: properly display docker pipeline resource > ----------------------------------------------------------------------------- > > Key: JBIDE-24242 > URL: https://issues.jboss.org/browse/JBIDE-24242 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3, pipeline_build > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > Attachments: jenkins-pipeline-properties.png, pipeline-buildconfig-entry.png > > > steps: > # ASSERT: use a cdk which has the "jenkins-pipeline-example" template > # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template > # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..." > # EXEC: hit the "Defined Resources..." button > # ASSERT: Details dialog pops up listing all the resources > # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}" > !pipeline-buildconfig-entry.png! > Then inspect the children that are displayed. There should be (as documented here: https://docs.openshift.org/latest/dev_guide/builds/build_strategies.html#...) > * jenkinsfile > * jenkinsfile path > * env vars > steps: > # ASSERT: have a jenkins pipeline in OpenShift. > # EXEC: select your project in the explorer and open up the properties view > # EXEC: in the properties view select the *Build Configs* tab and select the jenkins pipeline > !jenkins-pipeline-properties.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24221) CDK3 Server adapter editor: useless "Publishing" section should be removed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24221?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-24221. --------------------------------- Resolution: Rejected THis is an upstream issue. There's no API to get rid of it, and I don't expect there ever will be one. :( > CDK3 Server adapter editor: useless "Publishing" section should be removed > -------------------------------------------------------------------------- > > Key: JBIDE-24221 > URL: https://issues.jboss.org/browse/JBIDE-24221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3 > > Attachments: cdk3-server-adapter-editor.png > > > In the editor for a cdk3/minishift server adapter there's a section for "Publishing". IMHO it's useless since there's no publishing for the CDK3 server adapter. > !cdk3-server-adapter-editor.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24221) CDK3 Server adapter editor: useless "Publishing" section should be removed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24221?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24221: -------------------------------- Fix Version/s: 4.4.4.AM3 > CDK3 Server adapter editor: useless "Publishing" section should be removed > -------------------------------------------------------------------------- > > Key: JBIDE-24221 > URL: https://issues.jboss.org/browse/JBIDE-24221 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3 > > Attachments: cdk3-server-adapter-editor.png > > > In the editor for a cdk3/minishift server adapter there's a section for "Publishing". IMHO it's useless since there's no publishing for the CDK3 server adapter. > !cdk3-server-adapter-editor.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 April 2017