November 2017 - jbosstools-issues

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25303: ------------------------------------ I managed to move my Windows home folder from "Jeff MAURY" to "JeffMAURY" without reinstall. Google is your friend > 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: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

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

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-25303: ----------------------------------------- {quote}1) is not permanent for me{quote} --> it has failed several times in a row for me. Only workaround found is to use a workspace in user home {quote}2) workaround exists: don't use Eclipse workspaces and projects with spaces{quote} --> I'm forced to use a path with space as I need to be in my user home to workaround the issue 1 so unless reinstalling my PC, I have no workaround working for both the issue > 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: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25303: ------------------------------------ 1) is not permanent for me 2) workaround exists: don't use Eclipse workspaces and projects with spaces > 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: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

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

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Aurélien Pupier edited comment on JBIDE-25303 at 11/3/17 11:46 AM: ------------------------------------------------------------------- I'm a bit blocked by these 2 upstream bugs [Permission problems after "oc rsync" on Windows|https://github.com/openshift/origin/issues/13864] [Rsync is not working when the local folder path contains a space|https://github.com/openshift/openshift-restclient-java/issues/300] to finish implementation and test the flow from end to end. was (Author: aurelien.pupier): I'm a bit blocked by these 2 upstream bugs https://github.com/openshift/origin/issues/13864 https://github.com/openshift/openshift-restclient-java/issues/300 to finish implementation and test the flow from end to end. > 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: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4622) For JBDS 11.2.0.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [installer]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4622?page=com.atlassian.jira.plugin.... ] Jeff MAURY closed JBDS-4622. ---------------------------- Resolution: Done > For JBDS 11.2.0.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4622 > URL: https://issues.jboss.org/browse/JBDS-4622 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.2.0.AM1 > > > For JBDS 11.2.0.AM1 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.2.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.2.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.Final > > {code} > mvn clean verify -Dtpc.version=4.70.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.Final > > {code} > mvn clean verify -Dtpc.version=4.71.0.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

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

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-25303: ----------------------------------------- I'm a bit blocked by these 2 upstream bugs https://github.com/openshift/origin/issues/13864 https://github.com/openshift/openshift-restclient-java/issues/300 to finish implementation and test the flow from end to end. > 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: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > 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) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24799) Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24799?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24799: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.1.Final) > Testing: add tests to configuration/pom.xml to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final, dev instead of stable, 4.5.0.Final instead of 4.5) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-24799 > URL: https://issues.jboss.org/browse/JBIDE-24799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.5.2.AM2 > > > * add tests to configuration/pom.xml [1] to avoid invalid links (eg., 4.5.0.GA instead of 4.5.0.Final) > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > Should also verify that development and stable are used correctly. > * For example, this is wrong: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't have a dev milestone 4.5.0.Final taking priority over 4.5) > * And this it wrong too: > https://github.com/jbosstools/jbosstools-download.jboss.org/commit/7e7662... > (we shouldn't use the /development/ URLs for stable releases) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25371) For JBIDE 4.5.2.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25371?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25371: ------------------------------------ bump up to parent pom version = 4.5.2.AM1-SNAPSHOT > For JBIDE 4.5.2.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25371 > URL: https://issues.jboss.org/browse/JBIDE-25371 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.2.AM1 > > > For JBIDE 4.5.2.AM1 [central-update]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.2.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.2.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.Final > > {code} > mvn clean verify -Dtpc.version=4.70.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.Final > > {code} > mvn clean verify -Dtpc.version=4.71.0.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25371) For JBIDE 4.5.2.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25371?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-25371. ------------------------------ Resolution: Done > For JBIDE 4.5.2.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-25371 > URL: https://issues.jboss.org/browse/JBIDE-25371 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.2.AM1 > > > For JBIDE 4.5.2.AM1 [central-update]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.2.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.2.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.Final > > {code} > mvn clean verify -Dtpc.version=4.70.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.Final > > {code} > mvn clean verify -Dtpc.version=4.71.0.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4622) For JBDS 11.2.0.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [installer]

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4622: -------------------------------- Summary: For JBDS 11.2.0.AM1: Prepare for 4.5.2.AM1 / 11.2.0.AM1 [installer] Key: JBDS-4622 URL: https://issues.jboss.org/browse/JBDS-4622 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 11.2.0.AM1 For JBDS 11.2.0.AM1 [installer]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.2.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.2.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.2.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.Final {code} mvn clean verify -Dtpc.version=4.70.3.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.Final {code} mvn clean verify -Dtpc.version=4.71.0.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017