July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22726?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22726: ---------------------------------- Assignee: Alexey Kazakov > Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22726 > URL: https://issues.jboss.org/browse/JBIDE-22726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > > I need a list of file extensions we want associated with JBT/devstudio. > Then I can add those to the list of tags on the marketplace entries: > https://marketplace.eclipse.org/content/jboss-tools > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio > eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] > ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... > ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) > [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22685) Eclipse marketplace entry for Freemarker IDE plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22685?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22685: ------------------------------------ Searching marketplace for "freemarker": http://marketplace.eclipse.org/search/site/freemarker Only one useful hit found. But if we do a tag search... https://marketplace.eclipse.org/category/free-tagging/freemarker Now we find JBT, JBDS, and the Freemarker hit too. > Eclipse marketplace entry for Freemarker IDE plugin > --------------------------------------------------- > > Key: JBIDE-22685 > URL: https://issues.jboss.org/browse/JBIDE-22685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker, marketplace > Reporter: Paul Verest > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.1.AM3 > > > As initially proposed at https://github.com/jbosstools/jbosstools-freemarker issues, > just created https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools , it should appear within days. > Note, that this is now the only way for Eclipse to automatically discover and install Editor for .ftl files (and later for .ftlh and .fltx https://github.com/jbosstools/jbosstools-freemarker/pull/62) > Also it makes freemarker plugin searchable on marketplace, so solves new users questions http://stackoverflow.com/questions/9385561/freemarker-eclipse-plug-in -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22716) PR builder jobs don't log itests/, only tests/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22716?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22716: ------------------------------------ Job configs backed up to github: https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/cache/https/dev... Then fixed: https://github.com/jbdevstudio/jbdevstudio-ci/commit/a3b746aaf7a7f4dcc26e... > PR builder jobs don't log itests/, only tests/ > ---------------------------------------------- > > Key: JBIDE-22716 > URL: https://issues.jboss.org/browse/JBIDE-22716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM2 > > > Seems that the PR builds aren't collecting all the JUnit logs, because they only look for: > {code} > <testResults>tests/*/target/surefire-reports/*.xml,*/tests/*/target/surefire-reports/*.xml</testResults> > {code} > instead of > {code} > <testResults>*tests/*/target/surefire-reports/*.xml,*/*tests/*/target/surefire-reports/*.xml</testResults> > {code} > I've updated one job like this: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Can the same change (adding * to tests/ => *tests/) be done easily for all the jobs? Where are the templates for these stored? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22716) PR builder jobs don't log itests/, only tests/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22716?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22716. -------------------------------- Fix Version/s: 4.4.1.AM2 Resolution: Done > PR builder jobs don't log itests/, only tests/ > ---------------------------------------------- > > Key: JBIDE-22716 > URL: https://issues.jboss.org/browse/JBIDE-22716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.1.AM2 > > > Seems that the PR builds aren't collecting all the JUnit logs, because they only look for: > {code} > <testResults>tests/*/target/surefire-reports/*.xml,*/tests/*/target/surefire-reports/*.xml</testResults> > {code} > instead of > {code} > <testResults>*tests/*/target/surefire-reports/*.xml,*/*tests/*/target/surefire-reports/*.xml</testResults> > {code} > I've updated one job like this: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > Can the same change (adding * to tests/ => *tests/) be done easily for all the jobs? Where are the templates for these stored? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-22274: --------------------------------------- Bugzilla: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=492725] > Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22274 > URL: https://issues.jboss.org/browse/JBIDE-22274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.4.0.Alpha1 > Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247 > Reporter: Radim Hopp > Assignee: Jeff Johnston > Fix For: 4.4.1.AM1 > > > Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2" > Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged: > {noformat:title=Failed to open in Web Browser} > java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96) > at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: error=20, Not a directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:248) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22552: ------------------------------- Fix Version/s: 4.4.1.AM1 (was: 4.4.1.AM2) > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 > ------------------------------------------------ > > Key: JBIDE-22552 > URL: https://issues.jboss.org/browse/JBIDE-22552 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM1 > > > For JBIDE 4.4.1.Alpha1: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3930 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22552: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 > ------------------------------------------------ > > Key: JBIDE-22552 > URL: https://issues.jboss.org/browse/JBIDE-22552 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM1 > > > For JBIDE 4.4.1.Alpha1: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3930 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22552. ------------------------------ Resolution: Done > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 > ------------------------------------------------ > > Key: JBIDE-22552 > URL: https://issues.jboss.org/browse/JBIDE-22552 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM1 > > > For JBIDE 4.4.1.Alpha1: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3930 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22554) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22554?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22554. ------------------------------ Fix Version/s: 4.4.1.AM1 (was: 4.4.1.AM2) Resolution: Rejected Nothing to do, as there are no changes in Central discovery since 4.4.0. > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central Discovery] > -------------------------------------------------------------------- > > Key: JBIDE-22554 > URL: https://issues.jboss.org/browse/JBIDE-22554 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM1 > > > For JBIDE 4.4.1.Alpha1 [Central Discovery]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22562. ------------------------------ Resolution: Done I've updated the two python scripts, deleted the job, and added a note to the JIRA component description making it deprecated. There's no way to archive a component in JIRA, but I could delete it. That would mean all the JIRAs for this component would have to be moved somewhere else (or lose their component, which might cause jiralint to complain). > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.AM2 > > > For JBIDE 4.4.1.Alpha1 [Playground]: 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{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016