[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23092:
------------------------------------
well, we don't build from many of those repos, but surely if we are expected to tag repos we should also be branching them at the same time?
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3981 at 9/1/16 5:52 PM:
----------------------------------------------------------
Tried again with -clean, and Eclipse DOES start, though I suspect that git, docker, browsersim won't work due to constraint violations / two dependency chain issues.
{code}
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse -clean -data /tmp/newworkspace -consolelog | tee ~/tmp/rheclipse_20160901_0950.log.txt
{code}
[^rheclipse_20160901_0950.log.txt]
was (Author: nickboldt):
Tried again with -clean, and Eclipse DOES start.
{code}
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse -clean -data /tmp/newworkspace -consolelog | tee ~/tmp/rheclipse_20160901_0950.log.txt
{code}
[^rheclipse_20160901_0950.log.txt]
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3981:
-----------------------------
Attachment: rheclipse_20160901_1720.log.txt
Some blacklisting and better doc of what's being removed: https://github.com/jbdevstudio/jbdevstudio-product/pull/398
But, I'm still getting lots of singleton warnings (multiple versions of the same IUs)... and having removed javax.ws.rs in favour of javax.ws.rs-api, there's this new problem, because linuxtools needs a specific BUNDLE, not just a specific PACKAGE:
{code}org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.openshift.cdk.server [1189]
Unresolved requirement: Require-Bundle: org.eclipse.linuxtools.docker.core; bundle-version="2.0.0"
-> Bundle-SymbolicName: org.eclipse.linuxtools.docker.core; bundle-version="2.1.0.201608310043"; singleton:="true"
org.eclipse.linuxtools.docker.core [945]
Unresolved requirement: Require-Bundle: javax.ws.rs; bundle-version="2.0.1"
{code}
Also getting this crash:
{code}org.eclipse.e4.ui.css.core.sac.ParserNotFoundException: java.lang.ClassCastException: org.apache.batik.css.parser.Parser cannot be cast to org.w3c.css.sac.Parser{code}
[^rheclipse_20160901_1720.log.txt]
So... this isn't better. :(
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23033) Sprint Planning Script
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23033?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-23033:
--------------------------------------
4b) And, no one should forget to think about the integrations between components, and the integration with the CDK.
> Sprint Planning Script
> ----------------------
>
> Key: JBIDE-23033
> URL: https://issues.jboss.org/browse/JBIDE-23033
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
> 1) Devs should give a general idea of the main issues they are targeting for the sprint
> 2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
> 3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
> 4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
> 4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23035) Support WildFly 10.1 - change server adapter name
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23035?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23035.
---------------------------------
Resolution: Done
Added management unit tests, changed the name. Ran through smoke tests. Seems ok.
Also, I tested the (unreleased) upstream patch to stacks.yaml by using:
-Dorg.jboss.tools.stacks.url_stacks=https://raw.githubusercontent.com/jamezp/jdf-stack/43287525f194c246c1850449f6542798e1e210b6/stacks.yaml
> Support WildFly 10.1 - change server adapter name
> -------------------------------------------------
>
> Key: JBIDE-23035
> URL: https://issues.jboss.org/browse/JBIDE-23035
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> WildFly 10.1 has been released.
> We need to make sure it works properly.
> My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1.
> AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23033) Sprint Planning Script
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23033?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23033:
--------------------------------
Summary: Sprint Planning Script (was: Spring Planning Script)
> Sprint Planning Script
> ----------------------
>
> Key: JBIDE-23033
> URL: https://issues.jboss.org/browse/JBIDE-23033
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
> 1) Devs should give a general idea of the main issues they are targeting for the sprint
> 2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
> 3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
> 4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
> 4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23045:
-----------------------------------------------
[~jludvice], no, xsi:schemaLocation is only one way to do it. As a user you can make a local copy of the schema and add an entry to XML Catalog for URI of the schema. As a developer you can provide a copy of schema with some Eclipse plugin and add the entry to XML Catalog with extension point "org.eclipse.wst.xml.core.catalogContributions".
So yes, the Eclipse's XML validator is smart and looks into the XML catalog, but to be found schemas must be registered for exactly the same URI as is referenced in XML file.
> xml validator can't find xsd even though it's specified in xml file
> -------------------------------------------------------------------
>
> Key: JBIDE-23045
> URL: https://issues.jboss.org/browse/JBIDE-23045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.4.0.Final
> Reporter: Josef Ludvicek
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
> Attachments: examle-blueprint.xml
>
>
> RHDS xml validator can't find xsd schema in following xml file => validation doesn't work
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor
> license agreements. See the NOTICE file distributed with this work for additional
> information regarding copyright ownership. The ASF licenses this file to
> You under the Apache License, Version 2.0 (the "License"); you may not use
> this file except in compliance with the License. You may obtain a copy of
> the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required
> by applicable law or agreed to in writing, software distributed under the
> License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS
> OF ANY KIND, either express or implied. See the License for the specific
> language governing permissions and limitations under the License. -->
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
> xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0">
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23092:
----------------------------------------
Not sure we actually need to branch all these repos. We do need to branch jbosstools-integration-tests. But stuff like bdevstudio-website or jbdevstudio-artwork we don't.
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months