May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-22317: -------------------------------------- Summary: Cannot build jbosstools-central locally Key: JBIDE-22317 URL: https://issues.jboss.org/browse/JBIDE-22317 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, central Affects Versions: 4.4.0.Alpha1 Reporter: Mickael Istria Priority: Blocker With a clean jbosstools-central, "mvn clean verify" fails locally with {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) [ERROR] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21105) Deprecate BIRT

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21105: ---------------------------------------- I simply disabled this job at the moment: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_mast... Should we just remove it? > Deprecate BIRT > -------------- > > Key: JBIDE-21105 > URL: https://issues.jboss.org/browse/JBIDE-21105 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: birt, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png > > > {quote} > (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there > (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site > (2015-11-17 11:43:21) nickboldt: because Birt needs it > (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars > (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ? > (2015-11-17 11:43:44) maxandersen: afaik birt is dead. > (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik. > (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4? > (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy. > (2015-11-17 11:44:38) akazakov: +1 > (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in. > (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/ > (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/ > {quote} > So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > But we could also just use the old one from Mars.0: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL. > *DISCUSS*. > *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-684) Removed org.eclipse.swtbot.swt.finder.keyboard dependency + more refactoring

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-684?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-684: ------------------------------------ Fix Version/s: 4.3.0.Final (was: 4.3.0.Beta1) > Removed org.eclipse.swtbot.swt.finder.keyboard dependency + more refactoring > ---------------------------------------------------------------------------- > > Key: JBTIS-684 > URL: https://issues.jboss.org/browse/JBTIS-684 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Final, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-684) Removed org.eclipse.swtbot.swt.finder.keyboard dependency + more refactoring

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-684?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-684. ----------------------------------- pushed to master and jbtis-4.2.x > Removed org.eclipse.swtbot.swt.finder.keyboard dependency + more refactoring > ---------------------------------------------------------------------------- > > Key: JBTIS-684 > URL: https://issues.jboss.org/browse/JBTIS-684 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Final, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-693) Create new smoke tests for Drools plugin test suite

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-693?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-693: ------------------------------------ Fix Version/s: 4.3.0.Final > Create new smoke tests for Drools plugin test suite > --------------------------------------------------- > > Key: JBTIS-693 > URL: https://issues.jboss.org/browse/JBTIS-693 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.3.0.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.3.0.Final > > > Create at least two smoke tests: > * create new project smoke test > * open kie navigator view smoke test -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-693) Create new smoke tests for Drools plugin test suite

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-693?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-693. ----------------------------------- pushed to master > Create new smoke tests for Drools plugin test suite > --------------------------------------------------- > > Key: JBTIS-693 > URL: https://issues.jboss.org/browse/JBTIS-693 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.3.0.Final > Reporter: Tomas David > Assignee: Tomas David > Fix For: 4.3.0.Final > > > Create at least two smoke tests: > * create new project smoke test > * open kie navigator view smoke test -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- IMO, the recommended pattern would be something like REPO_NAME__pull-request On another topic, Is it necessary to publish e p2 repo for the topic branch? I see the configuration is jbosstools-server__pull-request_master is now much more complicated than a simple "mvn clean verify", introducing an intermediary script to orchestrate Maven ( https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... ). Do we need all that complexity? Do all those build flags need to be overriden? Shouldn't we be using the default from pom.xml instead? It seems to me that at the moment, the request from our dev is only to have "mvn clean verify" running. It seems to me that as part of this issue we're trying to do too much too early. > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21861) Include Docker tooling 2.0.0 in JBT 4.4.x TP

by Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Alexander Kurtakov commented on JBIDE-21861: -------------------------------------------- I believe so. A lot of effort has been put into it and following the same workflow/UX as docker tools should make quite familiar to people. It's probably not tested as well as the docker plugin but there shouldn't be severe bugs. > Include Docker tooling 2.0.0 in JBT 4.4.x TP > -------------------------------------------- > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3850: ------------------------------------- [~dgolovin], technically it is possible but JSPM causes more problems in tests than in production so it doesn't make sense. I have a new branch with a dummy component and test where I solved all configuration for non-Angular tests. https://github.com/ppitonak/developer-platform-install/tree/calculator_test Now we need to fix existing tests for Angular directives, [~jrichter1] can you have a look on that? > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha2 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3850: ------------------------------------- [~ppitonak]I see that removing JSPM and adding CC is easy, but I do get problems related to ES6 syntax in directive tests. Tried to use different approaches to make it work but that failed for me. Crazy question, though. Could we remove JSPM from production and still keep it in browser tests? > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha2 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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