March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24112) document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24112. -------------------------------- Verified, documentation has been updated. Closing. > document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide > --------------------------------------------------------------------------------------- > > Key: JBIDE-24112 > URL: https://issues.jboss.org/browse/JBIDE-24112 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: jiralint.user.no.perms.to.assign.txt > > > Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs so heir creation is less error-prone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23677. -------------------------------- Verified, I tried to modify version in cirrentversion.properties and then build jbosstools-base, it was able to detect bad versions. Closing. > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4288) 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4288?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4288. ------------------------------ Verified > 'Rename artifacts to remove timestamp and buildID' should be a jenkins job, not manual step > ------------------------------------------------------------------------------------------- > > Key: JBDS-4288 > URL: https://issues.jboss.org/browse/JBDS-4288 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.3.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM2 > > > In https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... there's a step that's done manually on dev01. This should be replaced by a job so it can be part of the pipeline. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-24129: ---------------------------------- Summary: download-devstudio profile breaks component builds Key: JBIDE-24129 URL: https://issues.jboss.org/browse/JBIDE-24129 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.4.AM2 Reporter: Pavol Srna Assignee: Nick Boldt Priority: Critical Fix For: 4.4.4.AM2 We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently. {code} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935] [ERROR] [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24076) NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24076?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24076: ------------------------------------- Fix Version/s: 4.4.4.AM2 > NullPointerException in JaxrsApplicationCreationWizardPage.getWebxmlResource > ---------------------------------------------------------------------------- > > Key: JBIDE-24076 > URL: https://issues.jboss.org/browse/JBIDE-24076 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Automated Error Reporting Bot > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM2 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > java.lang.NullPointerException: null > at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizardPage.getWebxmlResource(JaxrsApplicationCreationWizardPage.java:596) > at org.jboss.tools.ws.jaxrs.ui.wizards.JaxrsApplicationCreationWizard.performFinish(JaxrsApplicationCreationWizard.java:84) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:790) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > Bundles: > | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 | > | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 | > | org.jboss.tools.ws.jaxrs.ui | 1.9.1.v20160608-0648 | 1.9.2.v20160922-1835 | > Operating Systems: > | Linux | 3.13.0 | 3.13.0 | > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/581152c0e4b00cfabf9... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24128) Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24128?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-24128: ---------------------------------- Assignee: Pavol Srna > Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT > ------------------------------------------------------------------ > > Key: JBIDE-24128 > URL: https://issues.jboss.org/browse/JBIDE-24128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Blocker > Fix For: 4.4.4.AM2 > > > {code} > [INFO] Scanning for projects... > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [FATAL] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 > @ > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.jboss.tools:as:3.2.4-SNAPSHOT (/Users/psrna/GitHub/jbosstools-server/as/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24128) Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24128?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-24128: ---------------------------------- Assignee: Rob Stryker (was: Pavol Srna) > Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT > ------------------------------------------------------------------ > > Key: JBIDE-24128 > URL: https://issues.jboss.org/browse/JBIDE-24128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM2 > Reporter: Pavol Srna > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.4.AM2 > > > {code} > [INFO] Scanning for projects... > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [FATAL] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 > @ > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project org.jboss.tools:as:3.2.4-SNAPSHOT (/Users/psrna/GitHub/jbosstools-server/as/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24128) Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-24128: ---------------------------------- Summary: Non resolvable parent pom 4.4.3-SNAPSHOT, should be 4.4.4-SNAPSHOT Key: JBIDE-24128 URL: https://issues.jboss.org/browse/JBIDE-24128 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.4.AM2 Reporter: Pavol Srna Priority: Blocker Fix For: 4.4.4.AM2 {code} [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jboss.tools:as:3.2.4-SNAPSHOT (/Users/psrna/GitHub/jbosstools-server/as/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.jboss.tools:as:3.2.4-SNAPSHOT: Could not find artifact org.jboss.tools:server.all:pom:4.4.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 4, column 10 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-23889: -------------------------------------- [~mickael_istria] [~nickboldt] Could you answer my previous question please? > jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.4.AM1 > > Attachments: composite.png > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token or set up downstream groovy listener

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4297?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4297. ------------------------------ Verified, PPM builds are triggered by groovy script. > ensure downstream jobs can trigger via script & token or set up downstream groovy listener > ------------------------------------------------------------------------------------------ > > Key: JBDS-4297 > URL: https://issues.jboss.org/browse/JBDS-4297 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM1 > > Attachments: groovy-listener.png > > > Seems that Bos MW can't see CCI: > {code} > 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' > 20:57:25 curl: (7) couldn't connect to host{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > So we need another way to hook this up until all jobs can be migrated to CCI. > Perhaps the listener hook used here will work: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !groovy-listener.png|thumbnail! > {code} > URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); > File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() > if (last.exists()) > { > File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() > check.delete(); check.createNewFile(); > check << xpath.openStream(); > print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; > boolean status = !check.text.equals(last.text); > java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); > return status; > } else { > last << xpath.openStream(); > print "Fetch lastBuildNumber = " + last.text; > return true; > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017