August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1159) Composite files refer to old bundles

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1159: ---------------------------------------- Summary: Composite files refer to old bundles Key: JBTIS-1159 URL: https://issues.jboss.org/browse/JBTIS-1159 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 11.0.0.GA Reporter: Andrej Podhradsky Priority: Blocker Fix For: 11.0.0.GA Composite files refer to old bundles. {code:title=view-source:https://devstudio.redhat.com/11/staging/updates/integration-stack/compositeArtifacts.xml} <children size='2'> <child location='11.0.0.CR3-SNAPSHOT/'/> <child location='11.0.0.CR3-SNAPSHOT/targetplatform/'/> </children> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

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

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4367?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4367: ------------------------------ Component/s: (was: 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 > 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 > Fix For: 11.x > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24854) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24854?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-24854: ---------------------------------------- using 4.70.2.Final now > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-24854 > URL: https://issues.jboss.org/browse/JBIDE-24854 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.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 fusetools 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24854) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24854?page=com.atlassian.jira.plugi... ] Lars Heinemann resolved JBIDE-24854. ------------------------------------ Resolution: Done > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-24854 > URL: https://issues.jboss.org/browse/JBIDE-24854 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.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 fusetools 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24796: --------------------------------------- [~rob.stryker], you wanted me to try the PR and that's exactly what I did and then I reported what I saw, I'm not sure what was unclear. Yes, it took me very long, sorry about that. The last week was a bit hectic with the final GA bits testing and then the respin. {quote} It seems that what remains here is that the default username is incorrect? Is that all that's left to fix? {quote} Yes, that's exactly what I was trying to say - it starts ok, the only problem I'm still seeing is with the username. Let me know when you have an update so I can test it. > Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24796 > URL: https://issues.jboss.org/browse/JBIDE-24796 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.0.Final > Environment: Fedora > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png > > > In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See > !cdk3_sa-manual_wrong-mhome2.png|thumbnail! > In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See > !cdk3_sa-manual_correct-mhome.png|thumbnail! > Cc: [~adietish] [~rob.stryker]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24871) checkStagingURLs should verify children of composite*.xml are valid URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24871?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24871: ---------------------------------- Assignee: Nick Boldt > checkStagingURLs should verify children of composite*.xml are valid URLs > ------------------------------------------------------------------------ > > Key: JBIDE-24871 > URL: https://issues.jboss.org/browse/JBIDE-24871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: new-checks.png > > > Currently, checkStagingURLs.sh will verify that a given composite*.xml file EXISTS. > But it won't check if the contents of that site are VALID. So, we should parse these files and check that the <child location=""> are valid URLs too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24871) checkStagingURLs should verify children of composite*.xml are valid URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24871?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24871: ------------------------------- Fix Version/s: 4.5.0.Final > checkStagingURLs should verify children of composite*.xml are valid URLs > ------------------------------------------------------------------------ > > Key: JBIDE-24871 > URL: https://issues.jboss.org/browse/JBIDE-24871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: new-checks.png > > > Currently, checkStagingURLs.sh will verify that a given composite*.xml file EXISTS. > But it won't check if the contents of that site are VALID. So, we should parse these files and check that the <child location=""> are valid URLs too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24871) checkStagingURLs should verify children of composite*.xml are valid URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24871?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24871 at 8/11/17 6:23 PM: ------------------------------------------------------------- New checks added: !new-checks.png|thumbnail! Before: {code} [INFO] development URLs found: 176 () [INFO] stable URLs found: 182 () {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... After: {code} development URLs found: 278 () stable URLs found: 274 () {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... was (Author: nickboldt): New checks added: !new-checks.png|thumbnail! Before: {code} [INFO] development URLs found: 176 () [INFO] stable URLs found: 182 () {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... After: {code} {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > checkStagingURLs should verify children of composite*.xml are valid URLs > ------------------------------------------------------------------------ > > Key: JBIDE-24871 > URL: https://issues.jboss.org/browse/JBIDE-24871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: new-checks.png > > > Currently, checkStagingURLs.sh will verify that a given composite*.xml file EXISTS. > But it won't check if the contents of that site are VALID. So, we should parse these files and check that the <child location=""> are valid URLs too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24871) checkStagingURLs should verify children of composite*.xml are valid URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24871?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24871: ------------------------------- Attachment: new-checks.png > checkStagingURLs should verify children of composite*.xml are valid URLs > ------------------------------------------------------------------------ > > Key: JBIDE-24871 > URL: https://issues.jboss.org/browse/JBIDE-24871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Attachments: new-checks.png > > > Currently, checkStagingURLs.sh will verify that a given composite*.xml file EXISTS. > But it won't check if the contents of that site are VALID. So, we should parse these files and check that the <child location=""> are valid URLs too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24871) checkStagingURLs should verify children of composite*.xml are valid URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24871?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24871: ------------------------------------ New checks added: !new-checks.png|thumbnail! Before: {code} [INFO] development URLs found: 176 () [INFO] stable URLs found: 182 () {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... After: {code} {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > checkStagingURLs should verify children of composite*.xml are valid URLs > ------------------------------------------------------------------------ > > Key: JBIDE-24871 > URL: https://issues.jboss.org/browse/JBIDE-24871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Attachments: new-checks.png > > > Currently, checkStagingURLs.sh will verify that a given composite*.xml file EXISTS. > But it won't check if the contents of that site are VALID. So, we should parse these files and check that the <child location=""> are valid URLs too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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