February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12282?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12282: -------------------------------- Labels: (was: help_wanted) > Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really > ---------------------------------------------------------------------------------------- > > Key: JBIDE-12282 > URL: https://issues.jboss.org/browse/JBIDE-12282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.Final > Environment: JBDS 5.0.0.GA > Fedora 17 / OS X 10.7 Lion > JBoss EAP 6.0.0.GA > Reporter: Martin Malina > Fix For: LATER > > > When you set up your server to be bound to IPv6 (but you don't bind the management port to anything), the server fails to stop. Second attempt will force the server to stop. > This is the error in the log: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2012-07-02 16:49:05.284 > !MESSAGE Server jboss-eap-6.0.0.GA failed to stop. > {code} > This happens most probably because in such scenario, the management port is bound to IPv4 localhost (127.0.0.1). > Indeed I just verified that this is not related to IPv6 specifically but any host name other than localhost - if you don't check "Expose your management port" (and don't set -Dmanagement manually) and the hostname is something else than localhost, then this issue will arise. Note that with remote servers you don't need to bind the management port to anything for server stop to work. So we either need to set -Dmanagement always or make sure it is not needed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19129) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19129?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-19129. ------------------------------- Closing > For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Server] > ------------------------------------------------------------------ > > Key: JBIDE-19129 > URL: https://issues.jboss.org/browse/JBIDE-19129 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.2.3.Beta1 > > > For JBIDE 4.2.3.Beta1 [Server]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3. > Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT > {code} > 2. 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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19129) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19129?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19129. --------------------------------- Resolution: Done Resolving bc for some reason I don't see a close button (?). Will close next. > For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Server] > ------------------------------------------------------------------ > > Key: JBIDE-19129 > URL: https://issues.jboss.org/browse/JBIDE-19129 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.2.3.Beta1 > > > For JBIDE 4.2.3.Beta1 [Server]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3. > Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT > {code} > 2. 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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19137) FeedHenry Import Wizard doesn't list any projects to import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19137?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19137: --------------------------------------------- I can second that I thought we would allow importing all projects and just add special handling for project types we know ? (like cordova) do we really need a specific import wizard for every feedhenry app type? > FeedHenry Import Wizard doesn't list any projects to import > ----------------------------------------------------------- > > Key: JBIDE-19137 > URL: https://issues.jboss.org/browse/JBIDE-19137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.2.3.Beta1 > > Attachments: fh-preferences.png, fh-site.png, nothing-to-import.png > > > The FeedHenry import wizard can't find any projects to import. > There is no stacktrace in error log. > Please look at the attached screenshots for demonstration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19056: --------------------------------------------- [~mickael_istria] they are available - that is what the steps to reproduce does. first build one branch, then another - boom, baseline is including ~/.m2 content which is broken/not expected. > A Mojo to validate a version (compared to baseline) > --------------------------------------------------- > > Key: JBIDE-19056 > URL: https://issues.jboss.org/browse/JBIDE-19056 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > Attachments: build.out > > > We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released. > Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-583) Add Section for OpenShift v3

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-583?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-583: ---------------------------------------------- we don't really have docs grouped by components. maybe we should "tag" the docs and generate a page with those related to openshift ? it won't be a "get from A to B" kind of page though ...is that usable ? > Add Section for OpenShift v3 > ---------------------------- > > Key: TOOLSDOC-583 > URL: https://issues.jboss.org/browse/TOOLSDOC-583 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: User Guide - OpenShift Tools > Affects Versions: 4.3.0 > Reporter: Jeff Cantrill > Assignee: Michelle Murray > Fix For: 4.3.0 > > > Add Section for OpenShift that is specific to architecture v3 which is based on Kubernetes and Docker. Should include similar section to what exists for v2 http://tools.jboss.org/documentation/howto/#developing-apps-for-the-cloud -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3338: --------------------------------- Fix Version/s: 9.0.0.Alpha1 > JBDS Build fails with Tycho 0.22 > -------------------------------- > > Key: JBDS-3338 > URL: https://issues.jboss.org/browse/JBDS-3338 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Reporter: Mickael Istria > Priority: Blocker > Fix For: 9.0.0.Alpha1 > > > JBDS build is failing with Tycho 0.22 > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer: > Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed: > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at > file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/. > No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22

by Mickael Istria (JIRA)

Mickael Istria created JBDS-3338: ------------------------------------ Summary: JBDS Build fails with Tycho 0.22 Key: JBDS-3338 URL: https://issues.jboss.org/browse/JBDS-3338 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Mickael Istria Priority: Blocker JBDS build is failing with Tycho 0.22 {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer: Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed: org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/. No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/. {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18965) use Tycho 0.22 to build JBT 4.3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18965?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18965: ----------------------------------- Summary: use Tycho 0.22 to build JBT 4.3 (was: use Tycho 0.22 to build JBT 4.3/JBDS 9) > use Tycho 0.22 to build JBT 4.3 > ------------------------------- > > Key: JBIDE-18965 > URL: https://issues.jboss.org/browse/JBIDE-18965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Tycho 0.22 is out; we should use it to build JBT 4.3/JBDS 9, and see what new fun goodies we can take advantage of, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18965) use Tycho 0.22 to build JBT 4.3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18965?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-18965. ---------------------------------- Resolution: Done > use Tycho 0.22 to build JBT 4.3 > ------------------------------- > > Key: JBIDE-18965 > URL: https://issues.jboss.org/browse/JBIDE-18965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Tycho 0.22 is out; we should use it to build JBT 4.3/JBDS 9, and see what new fun goodies we can take advantage of, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015