January 2017 - jbosstools-issues - Jboss List Archives

[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 reassigned JBIDE-23623: ---------------------------------- Assignee: Jeff MAURY (was: Nick Boldt) > 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-23653) Add eGit git flow plugin to devstudio and jbosstools?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23653?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23653: ------------------------------------ [~rhopp] Please bug [~jeffmaury] if you want this included in 10.3.0.AM2. Would you also want this added to JBoss Tools? Would it be an optional install via Central, or an OOTB install as part of some other feature (eg., openshift or com.jboss.devstudio.core) ? Please list the features/plugins to include, and how you'd like them made available. > Add eGit git flow plugin to devstudio and jbosstools? > ----------------------------------------------------- > > Key: JBIDE-23653 > URL: https://issues.jboss.org/browse/JBIDE-23653 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Affects Versions: 4.4.2.Final > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.3.AM2 > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23653) Add eGit git flow plugin to devstudio and jbosstools?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23653?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23653: ---------------------------------- Assignee: Radim Hopp (was: Jeff MAURY) > Add eGit git flow plugin to devstudio and jbosstools? > ----------------------------------------------------- > > Key: JBIDE-23653 > URL: https://issues.jboss.org/browse/JBIDE-23653 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Affects Versions: 4.4.2.Final > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.4.3.AM2 > > > I just noticed, that since ~june 2015 egit contains gitflow plugin (org.eclipse.egit.gitflow & org.eclipse.egit.gitflow.ui) making it easier to use egit with topic branches etc. > This was originally requested by [~gastaldi] here: JBIDE-9080 and initilally implemented here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=348610. Since then, gitflow plugin for egit has its own component in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?component=Gitflow&list_id=15354... and it seems like the it's used and developed actively. > I'd like to open discussion whether we want to include this plugin or not. I personally think we (and our users) can benefit from such feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23730) Update Central to include PMD 4.0.11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23730?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23730. -------------------------------- Resolution: Done Red Hat Central target platform version 4.62.0.AM2-SNAPSHOT updated to include latest pmd 4.0.11 > Update Central to include PMD 4.0.11 > ------------------------------------ > > Key: JBIDE-23730 > URL: https://issues.jboss.org/browse/JBIDE-23730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > To help with CVE vulnerability issues reported in JBDS-4237, we might want to move up to PMD 5.5 from this site: > https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4237 at 1/11/17 5:38 PM: ----------------------------------------------------------- For PMD specifically, we could move from PMD 4.0.7 (net.sourceforge.pmd.eclipse.plugin_4.0.7.v20150522-1709) to the latest release, which might resolve some of these issues. Haven't updated PMD since 2015/05, so we're past due for an update [1]. See JBIDE-23730 [1] https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ was (Author: nickboldt): For PMD specifically, we could move from PMD 4.0.7 (net.sourceforge.pmd.eclipse.plugin_4.0.7.v20150522-1709) to the latest 5.5 release, which might resolve some of these issues. Haven't updated PMD since 2015/05, so we're past due for an update [1]. See JBIDE-23730 [1] https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.AM2 > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23730) Update Central to include PMD 4.0.11

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23730?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23730: ------------------------------- Summary: Update Central to include PMD 4.0.11 (was: Update Central to include PMD 5.5 (instead of 4.0)) > Update Central to include PMD 4.0.11 > ------------------------------------ > > Key: JBIDE-23730 > URL: https://issues.jboss.org/browse/JBIDE-23730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > To help with CVE vulnerability issues reported in JBDS-4237, we might want to move up to PMD 5.5 from this site: > https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3244: ----------------------------------- Assignee: (was: Alexey Kazakov) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3244) As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3244?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3244: ----------------------------------- Assignee: Alexey Kazakov (was: Denis Golovin) > As a JavaEE or Mobile developer I would like to have fast and helpful HTML5 and JavaScript tooling so I can work on my projects that contain more and more html5/javascript code > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3244 > URL: https://issues.jboss.org/browse/JBDS-3244 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, jsp/jsf/xml/html-source-editing, requirements > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23737: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that there's a symlink on your filesystem jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/oc that points to a non-existing file # EXEC: launch some integration test that has the @OCBinary annotation (ex. PortForwardingTest) Result: The test will fail complaining that the symlink cannot be created because it already exists. {code} org.jboss.tools.openshift.reddeer.exception.OpenShiftToolsException: Could not symlink /Users/adietish/Documents/jboss-workspaces/jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/oc to /Users/adietish/Documents/jboss-workspaces/jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/openshift-origin-client-tools-v1.3.2-ac1d579-mac/oc: java.nio.file.FileAlreadyExistsException: binaries/oc at org.jboss.tools.openshift.reddeer.requirement.OpenShiftCommandLineToolsRequirement.createSymlink(OpenShiftCommandLineToolsRequirement.java:77) at org.jboss.tools.openshift.reddeer.requirement.OpenShiftCommandLineToolsRequirement.fulfill(OpenShiftCommandLineToolsRequirement.java:66) at org.jboss.reddeer.junit.internal.requirement.Requirements.fulfill(Requirements.java:105) at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:44) at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:72) at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:68) at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:44) at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:59) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:153) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:68) at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:125) at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) at java.lang.Thread.run(Thread.java:745) {code} was: # ASSERT: make sure that there's a symlink on your filesystem jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/oc that points to a non-existing file # EXEC: launch some integration test that has the @OCBinary annotation (ex. PortForwardingTest) Result: The test will fail complaining that the symlink cannot get created because it already exists. {code} org.jboss.tools.openshift.reddeer.exception.OpenShiftToolsException: Could not symlink /Users/adietish/Documents/jboss-workspaces/jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/oc to /Users/adietish/Documents/jboss-workspaces/jbosstools-integration-tests/tests/org.jboss.tools.openshift.ui.bot.test/binaries/openshift-origin-client-tools-v1.3.2-ac1d579-mac/oc: java.nio.file.FileAlreadyExistsException: binaries/oc at org.jboss.tools.openshift.reddeer.requirement.OpenShiftCommandLineToolsRequirement.createSymlink(OpenShiftCommandLineToolsRequirement.java:77) at org.jboss.tools.openshift.reddeer.requirement.OpenShiftCommandLineToolsRequirement.fulfill(OpenShiftCommandLineToolsRequirement.java:66) at org.jboss.reddeer.junit.internal.requirement.Requirements.fulfill(Requirements.java:105) at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:44) at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:72) at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:68) at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:44) at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:59) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:153) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:68) at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:125) at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73) at java.lang.Thread.run(Thread.java:745) {code} > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23737: ------------------------------------- Story Points: 2 Sprint: devex #126 January 2017 > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > -- 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