July 2015 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20208: ------------------------------------ There should no longer be a license.html in the feature. https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... says:{quote} * Remove all license.html files, then remove references to license.html in your build.properties files * Remove references to licenseURL in your feature.xml files. {quote} > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Birt] > -------------------------------------------------------------------------------- > > Key: JBIDE-20208 > URL: https://issues.jboss.org/browse/JBIDE-20208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > Attachments: birt-no-license.png > > > For JBIDE 4.3.0.CR1 [Birt]: 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 Birt 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, 9 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 updated JBIDE-20394: ------------------------------- Fix Version/s: 4.3.0.Beta2 4.3.0.CR1 > 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 > 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, 9 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 reassigned JBIDE-20394: ---------------------------------- Assignee: Martin Malina > 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 > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20231) Freemarker New and Noteworthy for 4.3.0.Beta2

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20231?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-20231: -------------------------------------- To add some details for Freemarker: #include navigation works just partially: <#include "file.ftl> // this works <#include "subdir/file.ftl> // this doesn't work <#include "/opt/file.ftl> // this doesn't work <#include "file:////opt/file.ftl> // this works but opens file in internal browser instead of ftl editor Currently opened JIRA is https://issues.jboss.org/browse/JBIDE-20395 > Freemarker New and Noteworthy for 4.3.0.Beta2 > --------------------------------------------- > > Key: JBIDE-20231 > URL: https://issues.jboss.org/browse/JBIDE-20231 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

by Kevin Formsma (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Kevin Formsma edited comment on JBIDE-15250 at 7/28/15 9:40 AM: ---------------------------------------------------------------- I'll test this out with Beta2 on my use case, but it looks like it's going to work. Thanks [~rob.stryker] and [~vsevolodgolovanov]. was (Author: arothian): I'll test this out once Beta2 on my use case, but it looks like it's going to work. Thanks [~rob.stryker] and [~vsevolodgolovanov]. > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

by Kevin Formsma (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Kevin Formsma commented on JBIDE-15250: --------------------------------------- I'll test this out once Beta2 on my use case, but it looks like it's going to work. Thanks [~rob.stryker] and [~vsevolodgolovanov]. > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20395) Navigation of #assert directive doesn't work for nested relative path and absolute file path

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-20395: ------------------------------------ Summary: Navigation of #assert directive doesn't work for nested relative path and absolute file path Key: JBIDE-20395 URL: https://issues.jboss.org/browse/JBIDE-20395 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.3.0.Beta2 Environment: JBDS 9.0.0.Beta2b, L64 Reporter: Jiri Peterka Fix For: 4.3.0.CR1 Have Java Project in eclipse called "testprj": Create four ftl files: 1) testprj/first.ftl 2) testprj/second.ftl 3) testprj/dir/third.ftl 4) /opt/fourth.ftl Put this into first.ftl <#include "second.ftl"> <#include "dir/third.ftl"> <#include "/opt/fourth.ftl"> Try to click on each to navigate. First case works. Nested relative and absolute navigation doesn't work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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: ---------------------------------------- Thanks, [~mhusnain]. In New Features, there is a section about JST/JSF/HTML Editor: {quote}Target Platform is updated with the lates Tern.java and AngularJS-Eclipse in order to bring the latest improvements and fixes of JavaScript Content Assistant into JBoss Tools: Tern.java v.0.10.0.201506020610 AngularJS-Eclipse v.0.10.0.201506020622 These features are available via JBoss Central - Early Access as a part of AngularJS for Web Tools {quote} These versions are not correct. The correct versions are: Tern.java v.0.10.0.20150617215 AngularJS-Eclipse v.0.10.0.201506182210 Also, there is a typo: is updated with the *lates* Tern.java - should be "latest" The section on new features for OpenShift needs review by [~mlabuda], hopefully he can do that tomorrow. For Freemarker, [~jpeterka] checked the functionality and according to him, it only works for relative path, so I reopened the corresponding N&N JIRA: JBIDE-20231 Once the JIRA is resolved again, we should adopt the same new text for the release notes. 5. Apply this Release To update an existing JBoss Developer Studio or JBoss Developer Studio BYOE 8.x installation to version 9.0.0, apply the update available from the JBoss Developer Studio update site through the IDE. - this is not possible. I can see that we had the same text in Beta1 Release Notes. But (as we explain in the Update document) it is not possible to update JBDS 8.x to JBDS 9.x. > 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, 9 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)

Nick Boldt created JBIDE-20394: ---------------------------------- Summary: 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 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20130) Use Mars R for JBT 4.3/JBDS 9 Beta2 TP

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20130?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20130. ------------------------------------ verified in JBDS 9.0.0.Beta2-v20150717-1420-B67 > Use Mars R for JBT 4.3/JBDS 9 Beta2 TP > -------------------------------------- > > Key: JBIDE-20130 > URL: https://issues.jboss.org/browse/JBIDE-20130 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > Migrate to latest Mars R bits. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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