September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20776) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central Discovery]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20776?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20776. ------------------------------ Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central Discovery] > --------------------------------------------------------------------- > > Key: JBIDE-20776 > URL: https://issues.jboss.org/browse/JBIDE-20776 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: discovery > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Central Discovery]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20600) document how to use Deploy to OpenShift

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20600: ---------------------------------------- Is it done? What is the proper link to this document? > document how to use Deploy to OpenShift > --------------------------------------- > > Key: JBIDE-20600 > URL: https://issues.jboss.org/browse/JBIDE-20600 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.0.Final > > > Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works. > What I did was trying to just take jboss/wildfly:latest and deploy to openshift. > First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog. > Once I have done that the dialog is asking for a lot of questions but very little hints about what they are. > One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ? > But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started. > neither in webconsole nor in eclipse views. > Should there not be access to some console logs or similar to things created by a project ? > anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-504: ----------------------------- Attachment: is-in-dev.png is-in-dev_JBDS.png Thanks to new script doc'd in JBIDE-20803, and some fancypants synching between /staging/ and /development/ (using Beyond Compare), I've copied the files I updated in /staging/ (and tested locally to verify) into these places: /media/TOOLS-ssh/9.0/staging/updates/discovery.central/4.3.0.CR1a -> /media/TOOLS-ssh/9.0/development/updates/discovery.central/4.3.0.CR1 /media/TOOLS-ssh/9.0/staging/updates/discovery.earlyaccess/4.3.0.CR1a -> /media/TOOLS-ssh/9.0/development/updates/discovery.earlyaccess/4.3.0.CR1 /media/JBDS-ssh/9.0/staging/updates/discovery.central/9.0.0.CR1a -> /media/JBDS-ssh/9.0/development/updates/discovery.central/9.0.0.CR1 /media/JBDS-ssh/9.0/staging/updates/discovery.earlyaccess/9.0.0.CR1a -> /media/JBDS-ssh/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1 So, now in JBDS 9 CR1 and JBT 4.3 CR1, you can see this right out of the box (no -D flag overrides needed): !is-in-dev_JBDS.png! !is-in-dev.png! \o/ \m/ \o/ \m/ > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: is-in-dev.png, is-in-dev_JBDS.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20804: ---------------------------------------- Not blocker, but would be nice to have it fixed. How common is this problem? I mean does it happen for a few not so much used jars/classes or you have a pretty big chance to see that problem while debugging on WildFly? > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.Predicate, no source can be found > The problem is caused by the class file being found in the wildfly-cli jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20803: ------------------------------------ {quote} (2015-09-24 13:30:34) nickboldt: pleacu: we have a new problem w/ IS "not available" connectors (2015-09-24 13:31:28) nickboldt: pleacu: maxandersen: akazakov: if we include them in the development site we MUST have a valid jboss.discovery.site.integration-stack.url (can point anywhere as long as it's an update site; doesn't need to have IS content in it) (2015-09-24 13:34:27) pleacu: nickboldt1: what happens if there's no URL assoc with jboss.discovery.site.integration-stack.url in ide-config.prop? (2015-09-24 13:34:54) nickboldt: pleacu: https://issues.jboss.org/browse/JBIDE-20803 << details (2015-09-24 13:43:57) maxandersen: Nickboldt1: point it where it should be pointing at release. On our main updatesite. (2015-09-24 13:44:59) nickboldt: maxandersen: yep, ok (2015-09-24 13:45:40) maxandersen: Btw why is it needed? {quote} So I updated http://download.jboss.org/jbosstools/configuration/ide-config.properties as follows, to set the `jboss.discovery.site.integration-stack.url` at the same URL as `jboss.discovery.site.url` for now. https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-20803: ------------------------------------ yes - I was about to suggest that. Makes sense. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20790) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Webservices]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20790?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20790. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Webservices] > --------------------------------------------------------------- > > Key: JBIDE-20790 > URL: https://issues.jboss.org/browse/JBIDE-20790 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Webservices]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20794) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [LiveReload]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20794?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20794. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [LiveReload] > -------------------------------------------------------------- > > Key: JBIDE-20794 > URL: https://issues.jboss.org/browse/JBIDE-20794 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [LiveReload]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20803: ------------------------------------ Having pushed these into staging site, I can test them like this: 1. Install Eclipse 2. install JBT or JBDS 3. Launch Eclipse using vmargs set below. {code} # JBoss Tools url=http://download.jboss.org/jbosstools/mars/staging/updates/discovery.c... ./eclipse -vmargs -Djboss.discovery.directory.url=${url}jbosstools-directory.xml -Djboss.discovery.site.integration-stack.url=${url} # JBDS url=https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyacces... ./eclipse -vmargs -Djboss.discovery.directory.url=${url}devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=${url} {code} If you don't include the `jboss.discovery.site.integration-stack.url` property, JBT/JBDS will read the value from ide-config.properties, which is currently set to "" (null string) and return this error: {code} !MESSAGE org.jboss.tools.central.discovery.integration_stack_4.3.0.Alpha2_v20150922_1058_B430.jar_4644660859188953740.jar: Must specify connectorDescriptor/@siteUrl !STACK 1 org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Must specify connectorDescriptor/@siteUrl {code} And, because of that error, none of the IS "notavailable" connectors are shown. So, TL;DR, can we point the `jboss.discovery.site.integration-stack.url` at the same URL as `jboss.discovery.site.url` for now? > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20804: ------------------------------------- [~maxandersen], [~akazakov] we could consider applying https://github.com/jbosstools/jbosstools-central/commit/c096ec90491e7e5d0... to CR2 > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.Predicate, no source can be found > The problem is caused by the class file being found in the wildfly-cli jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015