May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4367) Problems with Red Hat Central/Spring MVC Project

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4367?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4367: ----------------------------- Component/s: platform-installer > Problems with Red Hat Central/Spring MVC Project > ------------------------------------------------ > > Key: JBDS-4367 > URL: https://issues.jboss.org/browse/JBDS-4367 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: 3rd-party-dependencies, platform-installer > Affects Versions: 10.3.0.GA > Environment: Creation of Spring MVC Project from Red Hat Central in Eclipse (Neon) > Reporter: Giuseppe Cavallo > Assignee: Fred Bricon > Priority: Critical > Attachments: Cattura1.JPG > > > Hi everybody, > recently i had install Red Hat Developer Sudio on Eclipse (version Neon) and some plugin (ie Spring, Maven ecc.). > In the Project menu creation there is a section named 'Red Hat Central'. Under this section there is a 'Spring Mvc Project'. > I have a Jboss EAP 7.x installed like Server. > When i try to create Spring Project by this menu, there is an error on dependency Maven Artifact, like the snapshot attach. I try to install this dependency but the jar of this feature seems not have a correct xml descriptor to insert in Maven add Repository (local o remote). > Any suggest. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4321: ---------------------------------- Because of this limitation I *HIGHLY* recommend we document the need to run with *-clean* in the usage guide for the devstudio rpm. See RHDEVDOCS-398 > Unable to start Devstudio without -clean after install of any stuff from RH Central > ----------------------------------------------------------------------------------- > > Key: JBDS-4321 > URL: https://issues.jboss.org/browse/JBDS-4321 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.4.0.AM2 > Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.4.0.GA > > Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_Fedora24_strict.txt, rh-eclipse46-devstudio10.4-0.20170428.0013.el7.log.All_from_central_without_clean_RHEL7_strict.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt > > > When I install something from Red Hat Central and then start Devstudio without -clean then I get this error: > {code} > !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689 > !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi > !STACK 0 > java.lang.NullPointerException > {code} > There are multiple errors but this one seems to be common for multiple items. > And this window appear: > !Start_without_clean.png|thumbnail! > There is easy workaround but user won't start Devstudio with -clean and many of them could be upset. > Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean. > CC: [~psrna] [~vkadlcik] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24417) getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24417?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24417. ------------------------------ Resolution: Done Fixed [0]. [0] https://github.com/jbosstools/jbosstools-build-ci/commit/8e6cf9d179d45950... Also updated the jenkins job [1] to add a 4th step (verifying all is done) and removed Jeff and Mat from the email recipient list as I can just run this myself as part of pre-staging [2]. [1] https://github.com/jbdevstudio/jbdevstudio-ci/commit/f5f35b1a0c4e74196dc3... [2] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... cc: [~jeffmaury] [~mat.booth] > getProjectRootPomParents.sh should support released parent pom versions (not just SNAPSHOTs) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24417 > URL: https://issues.jboss.org/browse/JBIDE-24417 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.4.Final > > > Ran this: > {code} > /tmp/jbt.github/jbosstools-build-ci/util/getProjectRootPomParents.sh -updateRootPom -b jbosstools-4.4.x -b2 jbosstools-4.4.x -pv 4.4.4.Final -w1 /tmp/jbt.github -vjbt 4.4.4.Final -vds 10.4.0.GA -tpmin 4.60.3.Final -tpmax 4.63.0.Final -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" -jirahost https://issues.jboss.org{code} > and the output suggested that all the root poms are already updated because they have 4.4.4.Final-SNAPSHOT (not 4.4.4.Final). > So... need to fix this ASAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24383: ------------------------------------------ merged into jbosstools-4.4.x and cherry-picked into master > Connection wizard: offer openshift.com as default server > -------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: connection-wizard-signup-link.png > > > now that https://openshift.com is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4391) For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4391?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4391: ---------------------------------- bump up to parent pom version = 4.4.4.Final > For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer] > ------------------------------------------------------------------- > > Key: JBDS-4391 > URL: https://issues.jboss.org/browse/JBDS-4391 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 10.4.0.GA > > > For JBDS 10.4.0.GA [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: > > {code} > git checkout jbosstools-4.4.x > {code} > > 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.Final</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final > > {code} > mvn clean verify -Dtpc.version=4.60.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final > > {code} > mvn clean verify -Dtpc.version=4.63.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.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4391) For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4391?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4391. ---------------------------- Resolution: Done > For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer] > ------------------------------------------------------------------- > > Key: JBDS-4391 > URL: https://issues.jboss.org/browse/JBDS-4391 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 10.4.0.GA > > > For JBDS 10.4.0.GA [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: > > {code} > git checkout jbosstools-4.4.x > {code} > > 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.Final</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final > > {code} > mvn clean verify -Dtpc.version=4.60.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final > > {code} > mvn clean verify -Dtpc.version=4.63.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.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4391) For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4391?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4391: -------------------------------- Assignee: Jeff MAURY > For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer] > ------------------------------------------------------------------- > > Key: JBDS-4391 > URL: https://issues.jboss.org/browse/JBDS-4391 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 10.4.0.GA > > > For JBDS 10.4.0.GA [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: > > {code} > git checkout jbosstools-4.4.x > {code} > > 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.Final</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final > > {code} > mvn clean verify -Dtpc.version=4.60.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final > > {code} > mvn clean verify -Dtpc.version=4.63.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.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4391) For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer]

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4391: -------------------------------- Summary: For JBDS 10.4.0.GA: Prepare for 4.4.4.Final / 10.4.0.GA [installer] Key: JBDS-4391 URL: https://issues.jboss.org/browse/JBDS-4391 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 10.4.0.GA For JBDS 10.4.0.GA [installer]: Please perform the following tasks: 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: {code} git checkout jbosstools-4.4.x {code} 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.4.Final</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final {code} mvn clean verify -Dtpc.version=4.60.3.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final {code} mvn clean verify -Dtpc.version=4.63.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.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24435) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24435?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24435. ------------------------------ Resolution: Done > For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-24435 > URL: https://issues.jboss.org/browse/JBIDE-24435 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.4.Final > > > For JBIDE 4.4.4.Final [central-update]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: > > {code} > git checkout jbosstools-4.4.x > {code} > > 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.4.Final</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final > > {code} > mvn clean verify -Dtpc.version=4.60.3.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final > > {code} > mvn clean verify -Dtpc.version=4.63.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.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24433) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [integration-tests]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24433: ---------------------------------- Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [integration-tests] Key: JBIDE-24433 URL: https://issues.jboss.org/browse/JBIDE-24433 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Reporter: Nick Boldt Priority: Blocker Fix For: 4.4.4.Final For JBIDE 4.4.4.Final [integration-tests]: Please perform the following tasks: 1. Check out your existing *{color:orange}jbosstools-4.4.x{color}* branch: {code} git checkout jbosstools-4.4.x {code} 2. Update your *{color:orange}jbosstools-4.4.x branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.4.Final</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.4.Final{color}* in your *{color:orange}jbosstools-4.4.x{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.60.3.Final {code} mvn clean verify -Dtpc.version=4.60.3.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final {code} mvn clean verify -Dtpc.version=4.63.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 integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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 May 2017