July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22269) Work with WildFly/EAP to generate unit tests on server installation layout

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22269: ------------------------------------- For EAP 7, these are the checks we make: 1) bin/product.conf exists 2) bin/product.conf has slot = "eap" 3) modules/system/layers/base/org/jboss/as/product/eap/dir/META-INF/MANIFEST.MF exists 4) JBoss-Product-Release-Name key in manifest.mf above has value "JBoss EAP" 5) JBoss-Product-Release-Version key in manifest.mf has value starting with "7.0" 6) jboss-modules.jar must exist 7) standalone/configuration/standalone.xml must exist Other checks most likely used by wildfly or older versions (but i'm not 100% sure) 8) modules/system/layers/base/org/jboss/as/server/main/anything.jar exists 9) anything.jar has proper manifest fields Wildfly 9/10 also check: 10) modules/system/layers/base/org/jboss/as/product/wildfly-full/dir/META-INF/MANIFEST.MF exists 11) the above manifest has proper fields JBoss-Product-Release-Name and JBoss-Product-Release-Version So basically, at this point we're introspecting likely places to find the wildfly / eap version and release-name strings. The keys are pretty well established, and I hope those never change. The values are what we compare against. Again, we can respond to key OR value changes, or even file-structure / location changes, if we have advance notice. It may hinder some of our 'tech-preview' functionality, but we should be able to get something up fairly quickly if we know whats' changed. > Work with WildFly/EAP to generate unit tests on server installation layout > -------------------------------------------------------------------------- > > Key: JBIDE-22269 > URL: https://issues.jboss.org/browse/JBIDE-22269 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > Attachments: JBIDE-22269.mock.zip > > > A task to track work on making sure changes to EAP don't inadvertently break tools when changing directory structure or important keys we read. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3961: ------------------------------------- >From log I see vagrant is installed at its default location c:\Hashicorp\vagrant. What version is it? > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.0.1.AM2 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22269) Work with WildFly/EAP to generate unit tests on server installation layout

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22269: -------------------------------- Attachment: JBIDE-22269.mock.zip Here is a zip file of what our test suite creates as mock servers. This does not mean this is the bare minimum we require. These mocks can probably be streamlined down further to have fewer checks than what's available in these mock folders. I'll work on being more clear, but it changes version-to-version. The important thing here is that we receive notification if an upcoming change to the runtime's folder structure would break one of these tests. We can always adjust to the new structure if given proper notice. > Work with WildFly/EAP to generate unit tests on server installation layout > -------------------------------------------------------------------------- > > Key: JBIDE-22269 > URL: https://issues.jboss.org/browse/JBIDE-22269 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > Attachments: JBIDE-22269.mock.zip > > > A task to track work on making sure changes to EAP don't inadvertently break tools when changing directory structure or important keys we read. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22673: ---------------------------------------- Ive added patches to https://bugs.eclipse.org/bugs/show_bug.cgi?id=497343 . And I ran it on the current TP, to discover that we also have a conflict of versions for asciidoc plugins {code} [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Tools Multiple (Composite) Target Platform 4.60.1.AM1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jbosstools-multiple --- [INFO] Deleting /home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target [INFO] [INFO] --- target-platform-validation-plugin:0.26.0-SNAPSHOT:validate-target-platform (default) @ jbosstools-multiple --- ... Cannot complete the install because of a conflicting dependency. Software being installed: Mylyn WikiText AsciiDoc UI 2.8.0.N20160111-1930 (org.eclipse.mylyn.wikitext.asciidoc.ui 2.8.0.N20160111-1930) Software being installed: Mylyn WikiText 2.9.0.v20160601-1831 (org.eclipse.mylyn.wikitext_feature.feature.group 2.9.0.v20160601-1831) Only one of the following can be installed at once: Mylyn WikiText AsciiDoc UI 2.9.0.v20160516-1451 (org.eclipse.mylyn.wikitext.asciidoc.ui 2.9.0.v20160516-1451) Mylyn WikiText AsciiDoc UI 2.8.0.N20160111-1930 (org.eclipse.mylyn.wikitext.asciidoc.ui 2.8.0.N20160111-1930) Cannot satisfy dependency: From: Mylyn WikiText 2.9.0.v20160601-1831 (org.eclipse.mylyn.wikitext_feature.feature.group 2.9.0.v20160601-1831) To: org.eclipse.mylyn.wikitext.asciidoc.ui [2.9.0.v20160516-1451] Application failed, log file location: /tmp/tycho8347762344740996402equinox/config/1467747349103.log [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:08 min [INFO] Finished at: 2016-07-05T21:37:55+02:00 [INFO] Final Memory: 76M/570M [INFO] ------------------------------------------------------------------------ {code} > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Fix For: 4.4.1.AM1 > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22690) Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22690?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-22690. ------------------------------------- Resolution: Done > Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-22690 > URL: https://issues.jboss.org/browse/JBIDE-22690 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > > To reproduce that, follow the steps as described by [~aurelien.pupier] in https://github.com/fabric8io/fabric8-forge/issues/360 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22690) Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22690?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-22690: ------------------------------------ Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-22690 > URL: https://issues.jboss.org/browse/JBIDE-22690 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.1.AM2 > > > To reproduce that, follow the steps as described by [~aurelien.pupier] in https://github.com/fabric8io/fabric8-forge/issues/360 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22690) Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-22690: --------------------------------------- Summary: Project is not refreshed if Ctrl+4 is fired inside an editor and "Link with Editor" is unchecked Key: JBIDE-22690 URL: https://issues.jboss.org/browse/JBIDE-22690 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.4.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.1.AM1 To reproduce that, follow the steps as described by [~aurelien.pupier] in https://github.com/fabric8io/fabric8-forge/issues/360 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3961) CDK installation failed with progress bar stuck in 99%

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3961?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3961: ------------------------------------- [~budhrg] What have you installed with DevSuite? Have you installed everything or some of components where detected? > CDK installation failed with progress bar stuck in 99% > ------------------------------------------------------ > > Key: JBDS-3961 > URL: https://issues.jboss.org/browse/JBDS-3961 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: h3. Operating System: > Windows 10 Pro 64 Bit > h3. Devstudio version > Devstudio 1.0 GA > Reporter: Budh Ram Gurung > Assignee: Denis Golovin > Labels: cdk > Fix For: 10.0.1.AM2 > > Attachments: dev_studio_installation.PNG, install.log > > > I was trying the "devstudio 1.0 GA build" ("development-suite-1.0.0-GA-bundle-installer.exe") and unable to get CDK installation after gone through the steps of authentication, vagrant, cygwin, jboss dev studio installations. > Observations: > CDK installation stuck in 99% with "failed" mark. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-801) JBTIS Target Platform - Neon - sync with 4.60.1.xxx

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-801: -------------------------------- Summary: JBTIS Target Platform - Neon - sync with 4.60.1.xxx Key: JBTIS-801 URL: https://issues.jboss.org/browse/JBTIS-801 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.4.0.Alpha1-TP Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.4.0.Alpha1-TP *Reason:* sync with 4.60.1.xxx-SNAPSHOT *Project page/sources:* *Version:* 4.4.0.Alpha1-SNAPSHOT *License and owner:* EPL *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* .DevstudioIS components *Include in JBDS:* Yes (DevstudioIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-795) JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBTIS-795?page=com.atlassian.jira.plugin.... ] Rick Wagner commented on JBTIS-795: ----------------------------------- Hi Brian and Lars, Yes, sure. Attached please find 'A_camel_service.tar.gz', which shows the problem. To make your own: - Start a SwitchYard project, make sure it allows use of the Camel component. - Add an XML Camel component. (This should give you a route named 'route.xml' by default.) Note that *immediately upon birth* the route is given an Id. This is changed behavior from past versions-- it's the problem. Note that this sample is based on the quickstart 'quickstarts/switchyard/camel-service'. The vanilla quickstart has a route.xml already, but it does not have the route id attribute. (It was not affected by the problem.) But when we added a new Camel component (route), we got the second route.xml that *does* have the Id/problem. Hope that helps, Rick > JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default > ---------------------------------------------------------------------------- > > Key: JBTIS-795 > URL: https://issues.jboss.org/browse/JBTIS-795 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1 with devstudio-integration-stack-9.0.0.Beta1-earlyaccess.zip > Reporter: Rick Wagner > Assignee: Brian Fitzpatrick > Attachments: A_camel_service.tar.gz > > > A user has noted that Camel routes used in SwitchYard are now being given an Id without user input. This is a changed behavior. > The same user complains of very slow loading of SwitchYard/Camel component routes, but this is still under investigation in the cited support ticket. -- 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