July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20201) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20201?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20201. ------------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Hibernate] > ------------------------------------------------------------------------------------- > > Key: JBIDE-20201 > URL: https://issues.jboss.org/browse/JBIDE-20201 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Hibernate]: 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.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-663?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-663: ---------------------------------------- [~mhusnain], thanks. It's all good except this one thing that I just noticed in 5. Apply this Release: To install JBoss Developer Studio BYOE 9.0.0 in Eclipse Luna, use Eclipse Marketplace, the JBoss Developer Studio update site or the update .zip file available from the Red Hat Customer Portal. - Eclipse Luna -> Eclipse Mars > 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] (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: ---------------------------------------- >From my point of view it's now ok. > 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] (TOOLSDOC-663) JBDS 9 Beta2: Create Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-663?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-663: ------------------------------------ Thanks [~mlabuda] and [~mmalina]. Could you please have a look at the same link and let me know if this is now approved for release? > 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-15250) Explode utility jars in EAR/WAR deployments

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15250. --------------------------------- Hmm, I thought the normal thing for a jar is to be zipped so to have it unzipped is a special case that needs to be explicitly configured. OK then. I suppose it works as expected then and I can close this JIRA. Verified in JBDS 9.0.0.Beta2 B93 (see my previous comment). > Explode utility jars in EAR/WAR deployments > ------------------------------------------- > > Key: JBIDE-15250 > URL: https://issues.jboss.org/browse/JBIDE-15250 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.0.1.Final > Reporter: Kevin Formsma > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: test-ear.zip > > > For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects. > A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded. -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-20394: ---------------------------------- Component/s: qa (was: integration-platform) Thanks for the help, [~nickboldt]. Removing the integration-platform component (i.e. JBTIS) and adding qa instead. > 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, qa > 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] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20394. --------------------------------- All done, closing. > 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, qa > 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] (JBDS-3468) Consider using Eclipse-CS 6.5.0

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3468?page=com.atlassian.jira.plugin.... ] Jiri Peterka reassigned JBDS-3468: ---------------------------------- Assignee: Nick Boldt (was: Jiri Peterka) > Consider using Eclipse-CS 6.5.0 > ------------------------------- > > Key: JBDS-3468 > URL: https://issues.jboss.org/browse/JBDS-3468 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.CR1 > > > New Checkstyle plugin for Eclipse (Eclipse-CS) exists: > {code:title=http://eclipse-cs.sf.net/update/} > net.sf.eclipsecs.feature.jar 6.5.0.201504121610 > {code} > Current version: > http://download.jboss.org/jbosstools/updates/requirements/eclipsecs/5.7.0... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3468) Consider using Eclipse-CS 6.5.0

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-3468?page=com.atlassian.jira.plugin.... ] Jiri Peterka commented on JBDS-3468: ------------------------------------ [~nickboldt], cs-eclipse 6.5.0.201504121610 was tested with JBDS 9.0.0.Beta2 and works fine. Feel free to update. > Consider using Eclipse-CS 6.5.0 > ------------------------------- > > Key: JBDS-3468 > URL: https://issues.jboss.org/browse/JBDS-3468 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Fix For: 9.0.0.CR1 > > > New Checkstyle plugin for Eclipse (Eclipse-CS) exists: > {code:title=http://eclipse-cs.sf.net/update/} > net.sf.eclipsecs.feature.jar 6.5.0.201504121610 > {code} > Current version: > http://download.jboss.org/jbosstools/updates/requirements/eclipsecs/5.7.0... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-17686: --------------------------------------- [~rob.stryker], is there something more for me to verify other than not having multiple terminal views available? Right now I can see Remote Systems -> Terminals and Terminal -> Terminal. Seems ok? > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- 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