August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20459) Create automated test for WildFly 10

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20459?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20459: ------------------------------------- Tests updated via this commit: https://github.com/jbosstools/jbosstools-server/commit/28909ba712f5e422f2... Leaving open to update for future releases > Create automated test for WildFly 10 > ------------------------------------ > > Key: JBIDE-20459 > URL: https://issues.jboss.org/browse/JBIDE-20459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > Currently we don't have a dedicated server adapter for WildFly 10. WildFly 10 is still in development and is planned to be released at the same time as JBDS 9.0.0 - https://issues.jboss.org/browse/wfly/?selectedTab=com.atlassian.jira.jira... > We expect WildFly 9 adapter to work with WildFly 10 runtime. > Let's create an automated test for WF 10 runtime. We should update it after every WF runtime milestone release to make sure it works. > Then we switch to a new WF 10 adapter when it's ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19964) Wildfly 10 / EAP 7 server adapter

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19964?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19964: -------------------------------------- Assignee: Rob Stryker > Wildfly 10 / EAP 7 server adapter > --------------------------------- > > Key: JBIDE-19964 > URL: https://issues.jboss.org/browse/JBIDE-19964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.x > > > It'd be a good idea to begin making an EAP7 / WF10 server adapter pair, or at least preparing. > Looking at the versions of jars that we care about for management commands, Jars in EAP7 current DR3 are: > wildfly-controller-client-2.0.0.Alpha3.jar > wildfly-protocol-2.0.0.Alpha3.jar > jboss-dmr-1.3.0.Final.jar > jboss-logging-3.2.1.Final.jar > jboss-marshalling-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-remoting-4.0.9.Final.jar > jboss-sasl-1.0.5.Final.jar > jboss-threads-2.2.0.Final.jar > xnio-api-3.3.1.Final.jar > xnio-nio-3.3.1.Final.jar > These jars are identical to those in WF9-CR1 *except* for wildfly-protocol and wildfly-controller-client, which are at 1.0.0.CR1 in wf9. So wildfly-core (repository) has undergone a 'major' version bump, and is likely undergoing significant API cleanup. It would be smart to expect that we probably will require a new management plugin on our side to compensate. > Also, it's worth noting that in WF8 / WF 8.1, these jars are actually versioned 8.0 / 8.1 respectively, and so the version has actually decreased as we've moved forward. I've brought this up on wildfly-dev, though it may be a bit late since WF is already ar RC3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19964) Wildfly 10 / EAP 7 server adapter

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19964?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19964: ----------------------------------- Fix Version/s: 4.3.x > Wildfly 10 / EAP 7 server adapter > --------------------------------- > > Key: JBIDE-19964 > URL: https://issues.jboss.org/browse/JBIDE-19964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.x > > > It'd be a good idea to begin making an EAP7 / WF10 server adapter pair, or at least preparing. > Looking at the versions of jars that we care about for management commands, Jars in EAP7 current DR3 are: > wildfly-controller-client-2.0.0.Alpha3.jar > wildfly-protocol-2.0.0.Alpha3.jar > jboss-dmr-1.3.0.Final.jar > jboss-logging-3.2.1.Final.jar > jboss-marshalling-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-marshalling-river-1.4.10.Final.jar > jboss-remoting-4.0.9.Final.jar > jboss-sasl-1.0.5.Final.jar > jboss-threads-2.2.0.Final.jar > xnio-api-3.3.1.Final.jar > xnio-nio-3.3.1.Final.jar > These jars are identical to those in WF9-CR1 *except* for wildfly-protocol and wildfly-controller-client, which are at 1.0.0.CR1 in wf9. So wildfly-core (repository) has undergone a 'major' version bump, and is likely undergoing significant API cleanup. It would be smart to expect that we probably will require a new management plugin on our side to compensate. > Also, it's worth noting that in WF8 / WF 8.1, these jars are actually versioned 8.0 / 8.1 respectively, and so the version has actually decreased as we've moved forward. I've brought this up on wildfly-dev, though it may be a bit late since WF is already ar RC3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20459) Create automated test for WildFly 10

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20459?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20459: ---------------------------------------- cc: [~mmalina] > Create automated test for WildFly 10 > ------------------------------------ > > Key: JBIDE-20459 > URL: https://issues.jboss.org/browse/JBIDE-20459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > Currently we don't have a dedicated server adapter for WildFly 10. WildFly 10 is still in development and is planned to be released at the same time as JBDS 9.0.0 - https://issues.jboss.org/browse/wfly/?selectedTab=com.atlassian.jira.jira... > We expect WildFly 9 adapter to work with WildFly 10 runtime. > Let's create an automated test for WF 10 runtime. We should update it after every WF runtime milestone release to make sure it works. > Then we switch to a new WF 10 adapter when it's ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20459) Create automated test for WildFly 10

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-20459: -------------------------------------- Summary: Create automated test for WildFly 10 Key: JBIDE-20459 URL: https://issues.jboss.org/browse/JBIDE-20459 Project: Tools (JBoss Tools) Issue Type: Task Components: server Reporter: Alexey Kazakov Assignee: Rob Stryker Priority: Critical Fix For: 4.3.0.CR1 Currently we don't have a dedicated server adapter for WildFly 10. WildFly 10 is still in development and is planned to be released at the same time as JBDS 9.0.0 - https://issues.jboss.org/browse/wfly/?selectedTab=com.atlassian.jira.jira... We expect WildFly 9 adapter to work with WildFly 10 runtime. Let's create an automated test for WF 10 runtime. We should update it after every WF runtime milestone release to make sure it works. Then we switch to a new WF 10 adapter when it's ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20152: ---------------------------------------- Looks good to me. > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20453) Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20453?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20453: ------------------------------------ Additional +1 from Alexey: {quote} (2015-08-13 16:38:43) akazakov: nickboldt, let me summarize and you will correct me if I wrong (2015-08-13 16:42:39) akazakov: nickboldt, you want to have the same zips (Central zip in jboss.org and Central ZIP + EA zip in https://devstudio.redhat.com/9.0/staging/updates/) and we had for JBDS 8. The content will be the same. But you changed the way update sites and zips are built. You had to do it to fix JBIDE-19336. Central update sites does not include staff included in JBT/JBDS update sites. But you merge everything you need when building zips. Not update sites. (2015-08-13 16:42:56) akazakov: nickboldt, correct? (2015-08-13 16:44:30) nickboldt: akazakov: correct, the only thing affected here are the ZIPs of the update sites, which are then used to produce JBDS (need TestNG in the installer, pulled from Central zip). the raw update sites (not zipped) arent' changed here (2015-08-13 16:44:58) nickboldt: we could do that as well - would make the composite sites slightly simpler (2015-08-13 16:45:25) nickboldt: but that's a change I'd prefer to do in 9.1 since it doesn't impact performance or offline experience. it's not a regression (2015-08-13 16:45:38) akazakov: nickboldt, then I +1 to fix it in CR1{quote} > Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20453 > URL: https://issues.jboss.org/browse/JBIDE-20453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.CR1 > > > Today the offline solution [1], [2] for installing stuff from Central or Early Access requires a pair of zips: the 3rd party content (target platform), and the stuff from JBoss Tools. > [1] http://www.jboss.org/products/devstudio/download/ (Central Zip doesn't include the JBT stuff, just the 3rd party / TP content) > [2] https://devstudio.redhat.com/9.0/staging/updates/ (both zips shown) > We should combine these into a single, larger zip, such that the offline solution requires only a single zip and there's no confusion about what a Central Zip is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20453) Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20453?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20453 at 8/13/15 4:37 PM: ------------------------------------------------------------- PR applied after explaining it again to Alexey in IRC, Denis *mostly* agreeing in Skype, and Fred +1'ing it above. * The Central update zip will contain all the 3rd party stuff, plus these missing features: {quote}org.jboss.tools.common.mylyn.feature_3.7.0.CR1-v20150811-1720-B450001.jar org.jboss.tools.cordovasim.feature_3.7.0.CR1-v20150812-1235-B504.jar org.jboss.tools.forge.ext.feature_2.0.0.CR1-v20150729-2245-B913.jar org.jboss.tools.jst.angularjs.feature_3.7.0.CR1-v20150805-1857-B920.jar org.jboss.tools.maven.jbosspackaging.feature_1.7.0.CR1-v20150805-0334-B750.jar{quote} * The EA update zip will contain all the 3rd party stuff, plus this missing feature: {quote}org.jboss.tools.arquillian.feature_1.2.0.CR1-v20150811-1131-B318.jar{quote} Next, I'll make sure the builds work & publishes correctly, the downstream JBDS build picks the correct zip file, JBDS continues to include TestNG, and the release guide is updated accordingly. was (Author: nickboldt): PR applied after explaining it again to Alexey in IRC, Denis *mostly* agreeing in Skype, and Fred +1'ing it above. * The Central update zip will contain all the 3rd party stuff, plus these missing features: {quote} org.jboss.tools.common.mylyn.feature_3.7.0.CR1-v20150811-1720-B450001.jar org.jboss.tools.cordovasim.feature_3.7.0.CR1-v20150812-1235-B504.jar org.jboss.tools.forge.ext.feature_2.0.0.CR1-v20150729-2245-B913.jar org.jboss.tools.jst.angularjs.feature_3.7.0.CR1-v20150805-1857-B920.jar org.jboss.tools.maven.jbosspackaging.feature_1.7.0.CR1-v20150805-0334-B750.jar{quote} * The EA update zip will contain all the 3rd party stuff, plus this missing feature: {quote} org.jboss.tools.arquillian.feature_1.2.0.CR1-v20150811-1131-B318.jar{quote} Next, I'll make sure the builds work & publishes correctly, the downstream JBDS build picks the correct zip file, JBDS continues to include TestNG, and the release guide is updated accordingly. > Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20453 > URL: https://issues.jboss.org/browse/JBIDE-20453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.CR1 > > > Today the offline solution [1], [2] for installing stuff from Central or Early Access requires a pair of zips: the 3rd party content (target platform), and the stuff from JBoss Tools. > [1] http://www.jboss.org/products/devstudio/download/ (Central Zip doesn't include the JBT stuff, just the 3rd party / TP content) > [2] https://devstudio.redhat.com/9.0/staging/updates/ (both zips shown) > We should combine these into a single, larger zip, such that the offline solution requires only a single zip and there's no confusion about what a Central Zip is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20453) Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20453?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20453: ------------------------------------ PR applied after explaining it again to Alexey in IRC, Denis *mostly* agreeing in Skype, and Fred +1'ing it above. * The Central update zip will contain all the 3rd party stuff, plus these missing features: {quote} org.jboss.tools.common.mylyn.feature_3.7.0.CR1-v20150811-1720-B450001.jar org.jboss.tools.cordovasim.feature_3.7.0.CR1-v20150812-1235-B504.jar org.jboss.tools.forge.ext.feature_2.0.0.CR1-v20150729-2245-B913.jar org.jboss.tools.jst.angularjs.feature_3.7.0.CR1-v20150805-1857-B920.jar org.jboss.tools.maven.jbosspackaging.feature_1.7.0.CR1-v20150805-0334-B750.jar{quote} * The EA update zip will contain all the 3rd party stuff, plus this missing feature: {quote} org.jboss.tools.arquillian.feature_1.2.0.CR1-v20150811-1131-B318.jar{quote} Next, I'll make sure the builds work & publishes correctly, the downstream JBDS build picks the correct zip file, JBDS continues to include TestNG, and the release guide is updated accordingly. > Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20453 > URL: https://issues.jboss.org/browse/JBIDE-20453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.CR1 > > > Today the offline solution [1], [2] for installing stuff from Central or Early Access requires a pair of zips: the 3rd party content (target platform), and the stuff from JBoss Tools. > [1] http://www.jboss.org/products/devstudio/download/ (Central Zip doesn't include the JBT stuff, just the 3rd party / TP content) > [2] https://devstudio.redhat.com/9.0/staging/updates/ (both zips shown) > We should combine these into a single, larger zip, such that the offline solution requires only a single zip and there's no confusion about what a Central Zip is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20453) Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20453?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20453: ------------------------------- Summary: Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8) (was: Instead of 4 zips, merge Central+TP and EA+TP into combined repos for easier offline use) > Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8) > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20453 > URL: https://issues.jboss.org/browse/JBIDE-20453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, updatesite > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.CR1 > > > Today the offline solution [1], [2] for installing stuff from Central or Early Access requires a pair of zips: the 3rd party content (target platform), and the stuff from JBoss Tools. > [1] http://www.jboss.org/products/devstudio/download/ (Central Zip doesn't include the JBT stuff, just the 3rd party / TP content) > [2] https://devstudio.redhat.com/9.0/staging/updates/ (both zips shown) > We should combine these into a single, larger zip, such that the offline solution requires only a single zip and there's no confusion about what a Central Zip is. -- 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 August 2015