January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23623: ------------------------------------ I understand why they are not automatically closed. Because the JIRA script fails, then the JIRA number is not part of the comment this automatic close it not processed. The log is the same as before, the JIRA script complains about -D option not allowed. See [^run.log] > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23665) [central-update] Create Windup tooling connector

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23665?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23665: ------------------------------------ Waiting on Todd's signoff on this card. https://trello.com/c/Xdley1ny/37-add-windup-plugins-to-red-hat-central > [central-update] Create Windup tooling connector > ------------------------------------------------ > > Key: JBIDE-23665 > URL: https://issues.jboss.org/browse/JBIDE-23665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: John Steele > Assignee: John Steele > Fix For: 4.4.3.AM2 > > > For JBT 4.4.x / JBDS 10.x, Windup tooling should be made available from Red Hat Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) [central-update] include Buildship?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3510: ---------------------------------- To get Todd's eyeballs on this, I've opened https://trello.com/c/w4TTLXV5/36-add-buildship-plugins-to-jboss-tools-dev... > [central-update] include Buildship? > ----------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central-update > Affects Versions: 9.0.0.CR1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM1 > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ Here's an example of a smart commit which automatically closed a JIRA: 1. commmit: https://github.com/jbosstools/jbosstools-discovery/commit/262646ae614cab5... 2. JIRA: https://issues.jboss.org/browse/JBIDE-23755?focusedCommentId=13347315&pag... > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23755) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23755?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23755: ------------------------------------ bump up to parent pom version = 4.4.3.AM2-SNAPSHOT > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-23755 > URL: https://issues.jboss.org/browse/JBIDE-23755 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [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.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.adoc README.contributing.adoc README.discovery.sites.adoc build.xml jbdevstudio jbosstools jbtcentraltarget jbtearlyaccesstarget pom.xml pom.xml.orig publish-assembly.xml *{color:orange}4.4.3.AM2-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.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.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 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23755) For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23755?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23755. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM2: Prepare for 4.4.3.AM2 / 10.3.0.AM2 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-23755 > URL: https://issues.jboss.org/browse/JBIDE-23755 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM2 > > > For JBIDE 4.4.3.AM2 [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.4.3.AM2-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM2-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.adoc README.contributing.adoc README.discovery.sites.adoc build.xml jbdevstudio jbosstools jbtcentraltarget jbtearlyaccesstarget pom.xml pom.xml.orig publish-assembly.xml *{color:orange}4.4.3.AM2-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.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.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 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ Please define WHICH flag was reported missing. Can you attach your console log? I need tea leaves if you want me to read your future. My crystal ball's in the shop being repaired. :D JIRAs are automatically closed if your github commit email matches your JIRA email, and you use Smart Commits: https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html Thus pushing a commit to github with a comment like "JBIDE-23623 #close" will cause this JIRA to be closed. But only if the above condition is met (github email == JIRA email). > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23756) Moved/Refactored AS itests have lost the possibility to run against specific eap build

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-23756: ---------------------------------- Summary: Moved/Refactored AS itests have lost the possibility to run against specific eap build Key: JBIDE-23756 URL: https://issues.jboss.org/browse/JBIDE-23756 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests, server Reporter: Pavol Srna Priority: Critical Fix For: 4.4.3.AM2 AS itests have been moved to jbosstools-server component repo and refactored/optimized. But the refactored implementation in jbosstools-server doesn't support running itests against specific EAP build (as it has in integration-tests repo), which breaks eap team compatibility jobs listed here [1] [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-JBDS/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-JBDS/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1006) SY - Allow to use proxy maven settings

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1006?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1006: ------------------------------------- Summary: SY - Allow to use proxy maven settings (was: SY - Allow skipping maven settings) > SY - Allow to use proxy maven settings > -------------------------------------- > > Key: JBTIS-1006 > URL: https://issues.jboss.org/browse/JBTIS-1006 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Allow skipping maven settings. This is useful if we already have all needed repositories defined in maven settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1006) SY - Allow to use proxy maven settings

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1006?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1006: ------------------------------------- Description: Allow skipping maven settings. This is useful if we already have all needed repositories defined in maven settings. EDIT: skipping the mvn settings is not the solution, we need to allow to use proxy settings was:Allow skipping maven settings. This is useful if we already have all needed repositories defined in maven settings. > SY - Allow to use proxy maven settings > -------------------------------------- > > Key: JBTIS-1006 > URL: https://issues.jboss.org/browse/JBTIS-1006 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Allow skipping maven settings. This is useful if we already have all needed repositories defined in maven settings. > EDIT: skipping the mvn settings is not the solution, we need to allow to use proxy settings -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017