July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20396) commits missing in master branch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20396?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20396: --------------------------------------- As discussed on irc, this is expected. We are trying a new approach with Beta2: Right now all fixes and changes are being pushed to the Beta2x branch only and once Beta2 is release, we will push everything in bulk to master. > commits missing in master branch > -------------------------------- > > Key: JBIDE-20396 > URL: https://issues.jboss.org/browse/JBIDE-20396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > > I'm seeing some fixes done in Beta2x branch but not in master. > For example... > https://github.com/jbosstools/jbosstools-integration-tests/blob/98f87964c... (Beta2x) > but > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/pl... (master) > There are several commits that have ONLY gone to Beta2x branch. Compare these lists: > https://github.com/jbosstools/jbosstools-integration-tests/commits/jbosst... (includes stuff on Jul 27, Jul 17) > vs. > https://github.com/jbosstools/jbosstools-integration-tests/commits/master > Here are 4 commits that appear to have been missed from master: > 1. https://github.com/jbosstools/jbosstools-integration-tests/commit/bd5ed07... > 2. https://github.com/jbosstools/jbosstools-integration-tests/commit/84a4159... > 3. https://github.com/jbosstools/jbosstools-integration-tests/commit/98f8796... > 4. https://github.com/jbosstools/jbosstools-integration-tests/commit/f30275e... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20396) commits missing in master branch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20396?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-20396 at 7/28/15 12:30 PM: ----------------------------------------------------------------- As discussed on irc, this is expected. We are trying a new approach with Beta2: Right now all fixes and changes are being pushed to the Beta2x branch only and once Beta2 is release, we will push everything in bulk to master. Update: And now I'm too late with this comment. was (Author: mmalina): As discussed on irc, this is expected. We are trying a new approach with Beta2: Right now all fixes and changes are being pushed to the Beta2x branch only and once Beta2 is release, we will push everything in bulk to master. > commits missing in master branch > -------------------------------- > > Key: JBIDE-20396 > URL: https://issues.jboss.org/browse/JBIDE-20396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > > I'm seeing some fixes done in Beta2x branch but not in master. > For example... > https://github.com/jbosstools/jbosstools-integration-tests/blob/98f87964c... (Beta2x) > but > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/pl... (master) > There are several commits that have ONLY gone to Beta2x branch. Compare these lists: > https://github.com/jbosstools/jbosstools-integration-tests/commits/jbosst... (includes stuff on Jul 27, Jul 17) > vs. > https://github.com/jbosstools/jbosstools-integration-tests/commits/master > Here are 4 commits that appear to have been missed from master: > 1. https://github.com/jbosstools/jbosstools-integration-tests/commit/bd5ed07... > 2. https://github.com/jbosstools/jbosstools-integration-tests/commit/84a4159... > 3. https://github.com/jbosstools/jbosstools-integration-tests/commit/98f8796... > 4. https://github.com/jbosstools/jbosstools-integration-tests/commit/f30275e... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20396) commits missing in master branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20396?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20396: ------------------------------------ Martin explains the logic here and why pushing to both branches was not (yet) done: {quote} (2015-07-28 12:18:39) nickboldt: surely some of those recent changes should be done in master too? 12:20 (2015-07-28 12:22:32) mmalina: nickboldt: to save work :) (2015-07-28 12:23:05) mmalina: nickboldt: we started branching because you wanted it basically (because it was breaking some things) (2015-07-28 12:23:33) nickboldt: sure but now master is out of date relative to Beta2x (2015-07-28 12:23:49) mmalina: nickboldt: but we still don't really need two branches. or so we think. so we agreed to push only to Beta2x now and then take all the changes and push them to master once Beta2 is released (2015-07-28 12:23:59) nickboldt: oic (2015-07-28 12:24:26) mmalina: nickboldt: hopefully there won't be any conflicts :){quote} > commits missing in master branch > -------------------------------- > > Key: JBIDE-20396 > URL: https://issues.jboss.org/browse/JBIDE-20396 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > > I'm seeing some fixes done in Beta2x branch but not in master. > For example... > https://github.com/jbosstools/jbosstools-integration-tests/blob/98f87964c... (Beta2x) > but > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/pl... (master) > There are several commits that have ONLY gone to Beta2x branch. Compare these lists: > https://github.com/jbosstools/jbosstools-integration-tests/commits/jbosst... (includes stuff on Jul 27, Jul 17) > vs. > https://github.com/jbosstools/jbosstools-integration-tests/commits/master > Here are 4 commits that appear to have been missed from master: > 1. https://github.com/jbosstools/jbosstools-integration-tests/commit/bd5ed07... > 2. https://github.com/jbosstools/jbosstools-integration-tests/commit/84a4159... > 3. https://github.com/jbosstools/jbosstools-integration-tests/commit/98f8796... > 4. https://github.com/jbosstools/jbosstools-integration-tests/commit/f30275e... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20396) commits missing in master branch

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20396: ---------------------------------- Summary: commits missing in master branch Key: JBIDE-20396 URL: https://issues.jboss.org/browse/JBIDE-20396 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform Affects Versions: 4.3.0.Beta2 Reporter: Nick Boldt I'm seeing some fixes done in Beta2x branch but not in master. For example... https://github.com/jbosstools/jbosstools-integration-tests/blob/98f87964c... (Beta2x) but https://github.com/jbosstools/jbosstools-integration-tests/blob/master/pl... (master) There are several commits that have ONLY gone to Beta2x branch. Compare these lists: https://github.com/jbosstools/jbosstools-integration-tests/commits/jbosst... (includes stuff on Jul 27, Jul 17) vs. https://github.com/jbosstools/jbosstools-integration-tests/commits/master Here are 4 commits that appear to have been missed from master: 1. https://github.com/jbosstools/jbosstools-integration-tests/commit/bd5ed07... 2. https://github.com/jbosstools/jbosstools-integration-tests/commit/84a4159... 3. https://github.com/jbosstools/jbosstools-integration-tests/commit/98f8796... 4. https://github.com/jbosstools/jbosstools-integration-tests/commit/f30275e... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3359: ------------------------------------ Is there anything else needs to be on this one. Does anyone mind if I close this? > Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.1.1.GA > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20305) Create tests for the ClassMetadataFacade implementations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20305?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20305. ------------------------------- Resolution: Done > Create tests for the ClassMetadataFacade implementations > --------------------------------------------------------- > > Key: JBIDE-20305 > URL: https://issues.jboss.org/browse/JBIDE-20305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-669) Document the consequences of creating a remote server without a runtime

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-669?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-669: ---------------------------------------- [~mhusnain], thanks for the update. The text seems fine. Good to go. > Document the consequences of creating a remote server without a runtime > ----------------------------------------------------------------------- > > Key: TOOLSDOC-669 > URL: https://issues.jboss.org/browse/TOOLSDOC-669 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Misha Ali > > In a recent discussion in JBIDE-19463, we talked about some limitations that result from creating of a remote server without a runtime. > For example, the jmx connection does not work because we use libs from the runtime to connect via jmx. > We have this document about setting up a remote server: > https://access.redhat.com/articles/1515503 > There is this: > {quote} > d. A remote server can now be created without assigning a runtime to it. Depending on the requirements, select the Assign a runtime to this server check box (and select an existing runtime or create a new one) or leave the box unselected and then click Next. > {quote} > So I think it would make sense to add these details somewhere in there. > From JBIDE-19463: > {quote} > Autodetection of ports by scanning your standalone.xml (or your selected configuration file). Since there's no local runtime, and no local standalone.xml, we can't notice that you've modified your ports to be non-standard. > Also, without a local runtime, some small behavior changes might be default values. For example, sometimes we hard-code different behavior between minor or micro versions if we notice there's a bug in some previous release. For example, some of the early jboss-7 releases didn't support the -b flag. > Without a local runtime to scan, we can't know the exact version you're running against, and can't customize args (or other things) to work around bugs in those specific runtime versions. > {quote} > On top of that, you won't be able to create a JMX connection to the server. > I'll leave it to you to decide how much details we need in the article. Maybe it's not necessary to talk about early versions of jboss-7 and that part. But it makes sense to at least mention that some things may be missing, mainly JMX connection, detection of ports from standalone.xml and perhaps several more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20394 at 7/28/15 11:23 AM: -------------------------------------------------------------- After discussion in IRC and experimentation offline, I've found that the hudson profile won't work: https://github.com/nickboldt/jbosstools-integration-tests/commit/5083dc16... Found a better solution & have updated the PR, which should now also fix seemingly circular dep problem, #1 listed above. https://github.com/jbosstools/jbosstools-integration-tests/pull/1091 was (Author: nickboldt): After discussion in IRC and experimentation offline, I've found that the hudson profile won't work: https://github.com/nickboldt/jbosstools-integration-tests/commit/5083dc16... Found a better solution & have updated the PR https://github.com/jbosstools/jbosstools-integration-tests/pull/1091 > jbosstools integration tests site depends on itself to build; site is not self-cleaning > --------------------------------------------------------------------------------------- > > Key: JBIDE-20394 > URL: https://issues.jboss.org/browse/JBIDE-20394 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > I've found some problems today: > 1. building JBT integration tests requires the JBT integration tests site [circular dependency] > {code} > [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > {code} > 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1] > [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/mas... > 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts. > [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time. > 5. The check that the build does to determine if it should publish the new bits is failing to find the check script. > 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical. > [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-t... > [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3... > This is because we have symlinks: > {code} > updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/ > updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/ > {code} > So this is OK but we should migrate to use the new correct URLs instead of the old ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-663) JBDS 9 Beta2: Create Release Notes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-663?page=com.atlassian.jira.plug... ] Marián Labuda commented on TOOLSDOC-663: ---------------------------------------- OpenShift: - link to retrieve token opens internal browser in a new shell with page providing token - second para could have also double arrow sign in the beginning. This information could probably precede the previous para and it is not related to OAuth which is described in first para - could you please rephrase "You can easily point your browser to your OpenShift v3 application via the context menu."? Because we are not pointing browser to OS v3 app via context menu but we are showing an application in browser via this context menu. Since Beta2 it is also possible to use Show in Browser from context menu of a specific routing - "JBoss Developer Studio 9.0 Beta1 will show you OpenShift v3 routes " maybe there should be Beta2? I would like to ask you to modify "Web Service Tools " section. Proper heading would be "WebSockets". We just have it in tooling under webservices component. Listing websockets methods from content assist proposal is in my humble opinion not required. Thanks > JBDS 9 Beta2: Create Release Notes > ---------------------------------- > > Key: TOOLSDOC-663 > URL: https://issues.jboss.org/browse/TOOLSDOC-663 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Essentially update the Beta1 release notes to include all new known and resolved issues for Beta2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20392) Browsersim feature not shown in Installation details

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20392?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-20392. ----------------------------------- Resolution: Rejected Rejecting since this looks like a non-issue. Feel free to reopen. > Browsersim feature not shown in Installation details > ---------------------------------------------------- > > Key: JBIDE-20392 > URL: https://issues.jboss.org/browse/JBIDE-20392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > I can't find the org.jboss.tools.browsersim.feature under Help -> Installation Details -> Features. > In both JBDS 9.0.0.Beta2 and JBoss Tools 4.3.0.Beta2. > Maybe there is an explanation for this, but I asked around and nobody knows why this happens. > Browsersim is working fine and I can see browsersim feature in the filesystem in features/ and also I can see browsersim plugins in Help -> Installation Details -> Plugins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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