December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25513) update minimum target platform to Oxygen.1a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25513?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25513: ------------------------------------ [~jeffmaury] please confirm this is what you want, and assign back to me. > update minimum target platform to Oxygen.1a > ------------------------------------------- > > Key: JBIDE-25513 > URL: https://issues.jboss.org/browse/JBIDE-25513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite, upstream > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.AM3 > > > {quote} > Jeff: I'm wondering how do we manage this minimum requirement (Oxygen1A) then ? > Nick: would move to 4.71.0.Final or 4.72.0.AM3-SNAPSHOT > 4.71.0 = Oxygen.1a; 4.72.0 = Oxygen.2 > Jeff: 4.71.0.Final > Nick: if you're suggesting we need to do that now, please open a JIRA (and you can even attach a PR to fix the parent pom. It's one line. > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25513) update minimum target platform to Oxygen.1a

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25513: ---------------------------------- Summary: update minimum target platform to Oxygen.1a Key: JBIDE-25513 URL: https://issues.jboss.org/browse/JBIDE-25513 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform, updatesite, upstream Reporter: Nick Boldt {quote} Jeff: I'm wondering how do we manage this minimum requirement (Oxygen1A) then ? Nick: would move to 4.71.0.Final or 4.72.0.AM3-SNAPSHOT 4.71.0 = Oxygen.1a; 4.72.0 = Oxygen.2 Jeff: 4.71.0.Final Nick: if you're suggesting we need to do that now, please open a JIRA (and you can even attach a PR to fix the parent pom. It's one line. https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25513) update minimum target platform to Oxygen.1a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25513?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25513: ---------------------------------- Assignee: Nick Boldt > update minimum target platform to Oxygen.1a > ------------------------------------------- > > Key: JBIDE-25513 > URL: https://issues.jboss.org/browse/JBIDE-25513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite, upstream > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > {quote} > Jeff: I'm wondering how do we manage this minimum requirement (Oxygen1A) then ? > Nick: would move to 4.71.0.Final or 4.72.0.AM3-SNAPSHOT > 4.71.0 = Oxygen.1a; 4.72.0 = Oxygen.2 > Jeff: 4.71.0.Final > Nick: if you're suggesting we need to do that now, please open a JIRA (and you can even attach a PR to fix the parent pom. It's one line. > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25513) update minimum target platform to Oxygen.1a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25513?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25513: ------------------------------- Fix Version/s: 4.5.2.AM3 > update minimum target platform to Oxygen.1a > ------------------------------------------- > > Key: JBIDE-25513 > URL: https://issues.jboss.org/browse/JBIDE-25513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite, upstream > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > {quote} > Jeff: I'm wondering how do we manage this minimum requirement (Oxygen1A) then ? > Nick: would move to 4.71.0.Final or 4.72.0.AM3-SNAPSHOT > 4.71.0 = Oxygen.1a; 4.72.0 = Oxygen.2 > Jeff: 4.71.0.Final > Nick: if you're suggesting we need to do that now, please open a JIRA (and you can even attach a PR to fix the parent pom. It's one line. > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) TP: update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25427: ------------------------------- Description: Switch to the latest Oxygen.2, including Jetty 9.4.7 or later Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 was: Switch to the latest Oxygen.2, including Jetty 9.4.7 or later Also include RD 2.0.1? https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 > TP: update target platform & Central to Oxygen.2 > ------------------------------------------------ > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png, p2diff.all.txt, p2diff.ignoreVersions.txt > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 or later > Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25507) Move RHAMT tooling out of early access

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25507?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25507: ------------------------------------ Per conversation on MM, here's what needs doing: a) publish 4.0.0.Final to http://download.jboss.org/jbosstools/oxygen/stable/updates/rhamt/ b) if/when you release a 4.0.1.Final, push it to BOTH sites: * http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ * http://download.jboss.org/jbosstools/oxygen/stable/updates/rhamt/ c) meanwhile I'll prepare a PR for the changes needed in the central plugins, and build that as snapshot site we can test before pushing it live. > Move RHAMT tooling out of early access > -------------------------------------- > > Key: JBIDE-25507 > URL: https://issues.jboss.org/browse/JBIDE-25507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: John Steele > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > RHAMT 4.0.0.Final will be released December 15th, and now that it's GA, we'd like it be out of early access. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25303: ------------------------------------- 'Mark as deployable' will basically copy the entire folder or project you've selected, including any and all subfolders, exactly as-is. It will not ignore the src folders and just send the classes. It will copy the project exactly as it is structured in the project filesystem. It probably won't work for what you're trying to do. My opinion is as follows: Either the project needs to be configured to make a properly formed slim jar, and let the server adapter somehow turn it into the fat jar (or send it to openshift for openshift to redeploy into a new fat jar), or, the project needs to be configured to create a fat jar itself. Option 1 is easily accomplished by adding a maven configurator, which adds a utility facet and whatever default mappings are required. However, the problem then becomes how to get this data up into openshift, since openshift has already built the fat jar out of the initial slim jar, and no longer has a way to deal with the slim jar structure. Option 2, in my opinion, is probably very difficult. Without a huge amount of work, the odds of webtools being able to generate a fat jar is probably very small, without a huge amount of work. I'm still a bit confused (as I've always been) about the idea of structuring the project into a pseudo-fat-jar-without-all-the-spring-pieces. This seems very strange to me. We're then not making a fat jar, and we're not making a slim jar. We're making some bastard hybrid. If I had to make a choice right now, I'd suggest you always make the project structured to create a slim jar. The server adapter should then manipulate the output how it wants to make sure it gets rsync'd properly. However, even this structure still requires a maven configurator to install the utility facet and make sure the slim jar is properly generated. > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM3 > > Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25507) Move RHAMT tooling out of early access

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25507?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25507: ------------------------------------ I'll need the URL for the Final/GA release so I can reference it in the discovery plugin. I would expect to find your release here: http://download.jboss.org/jbosstools/oxygen/stable/updates/rhamt/ But I see it's in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ Shall I move it and update the links in the plugin.xml files? > Move RHAMT tooling out of early access > -------------------------------------- > > Key: JBIDE-25507 > URL: https://issues.jboss.org/browse/JBIDE-25507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: John Steele > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > > RHAMT 4.0.0.Final will be released December 15th, and now that it's GA, we'd like it be out of early access. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-574) Stage 2: Implement mechanism to open in last focused instance.

by Leo Ufimtsev (JIRA)

Leo Ufimtsev created ERT-574: -------------------------------- Summary: Stage 2: Implement mechanism to open in last focused instance. Key: ERT-574 URL: https://issues.jboss.org/browse/ERT-574 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Leo Ufimtsev -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-573) Stage 1: Implement very simple mechanism with gdbus to open file in any eclipse instance

by Leo Ufimtsev (JIRA)

Leo Ufimtsev created ERT-573: -------------------------------- Summary: Stage 1: Implement very simple mechanism with gdbus to open file in any eclipse instance Key: ERT-573 URL: https://issues.jboss.org/browse/ERT-573 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Leo Ufimtsev -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 December 2017