May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14472) [PERF] [INTEGRATION] New upstream fix renders child-module workaround outdated

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14472?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14472. --------------------------------- Resolution: Done Pushed to master! YAY! The workaround is dead! DING DONG, the witch is dead! > [PERF] [INTEGRATION] New upstream fix renders child-module workaround outdated > ------------------------------------------------------------------------------ > > Key: JBIDE-14472 > URL: https://issues.jboss.org/browse/JBIDE-14472 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > > To nest a SAR project or an ESB project inside a EAR and have it be recognized as a child project, a nasty inefficient workaround needed to be used. With the introduction of the upsteam GlobalHeirarchyParticipant and a global list to register yourself in, this wasteful workaround is no longer necessary. > Remove it. > To test: > 1) verify esb project and sar project can nest inside ear and be published correctly > 2) verify esb and sar project can have a Utility Project nested inside and be published correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14088) Generate TP source feature site + composite site merging matching TP with TP sources

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14088?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-14088. ------------------------------ I wasn't lying but feel free to re-open if a problem occurs or you see a wumpus hiding in the dark. > Generate TP source feature site + composite site merging matching TP with TP sources > ------------------------------------------------------------------------------------ > > Key: JBIDE-14088 > URL: https://issues.jboss.org/browse/JBIDE-14088 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > Attachments: JBIDE-14088.missing.txt, JBIDE14088.sources.list.txt > > > Every time we produce a target platform update site zip on download.jboss.org we should also produce an update site containing only sources. > Then the composite site http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... could include: > * REPO/ > * SRC-REPO/ *NEW* > * compositeArtifacts.xml, compositeContent.xml --> points to both REPO/ and SRC-REPO/ *NEW* > * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip > * jbosstoolstarget-4.30.5.Alpha4-SNAPSHOT.zip.MD5 > * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip *NEW* > * jbosstoolstarget-sources-4.30.5.Alpha4-SNAPSHOT.zip.MD5 *NEW* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14472) [PERF] [INTEGRATION] New upstream fix renders child-module workaround outdated

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-14472: ----------------------------------- Summary: [PERF] [INTEGRATION] New upstream fix renders child-module workaround outdated Key: JBIDE-14472 URL: https://issues.jboss.org/browse/JBIDE-14472 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.0.Beta1 To nest a SAR project or an ESB project inside a EAR and have it be recognized as a child project, a nasty inefficient workaround needed to be used. With the introduction of the upsteam GlobalHeirarchyParticipant and a global list to register yourself in, this wasteful workaround is no longer necessary. Remove it. To test: 1) verify esb project and sar project can nest inside ear and be published correctly 2) verify esb and sar project can have a Utility Project nested inside and be published correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13920) Reduce Jetty log verbosity

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13920?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-13920: ---------------------------------- Fix Version/s: 4.1.0.Beta2 (was: 4.1.0.Beta1) Workaround Description: Not critical for 4.1.0.Beta1 > Reduce Jetty log verbosity > --------------------------- > > Key: JBIDE-13920 > URL: https://issues.jboss.org/browse/JBIDE-13920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13927) Use PubSub pattern to notify browsers

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13927?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-13927. ----------------------------------- Resolution: Done Fixed in https://github.com/jbosstools/jbosstools-livereload/pull/8 With support for file extensions in uppercase > Use PubSub pattern to notify browsers > ------------------------------------- > > Key: JBIDE-13927 > URL: https://issues.jboss.org/browse/JBIDE-13927 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta1 > > > PubSub seems appropriate. > Use a filter to exclude irrelevant file (filter on file extension) > Manage disconnection > Avoid having to generate message for each browser -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14421) Conficting Birt for Kepler M7 and JEE bundle

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14421?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14421: --------------------------------------- {quote} Should we remove the birt chart wtp integration feature from the TP {quote} Not necessary. > Conficting Birt for Kepler M7 and JEE bundle > -------------------------------------------- > > Key: JBIDE-14421 > URL: https://issues.jboss.org/browse/JBIDE-14421 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Beta1 > > Attachments: JBT4.1Beta1-installed-with-o.j.t.birt.feature-into-Eclipse4.3M7.png > > > Dependency resolution in target platform fails because of a conflict between Birt and JST: > {quote} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612 > [ERROR] Software being installed: org.eclipse.jst.jee 1.0.600.v201305070100 > [ERROR] Missing requirement: org.eclipse.wst.ws_ui.feature.feature.group 3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL requires 'org.eclipse.wst.xml_ui.feature.feature.group [3.5.0.v201301022000-7H7IFisDxumVt037ridXmTt0LZaO8hpKpRz-T4SU]' but it could not be found > [ERROR] Only one of the following can be installed at once: [org.eclipse.jst.jee 1.0.600.v201305070100, org.eclipse.jst.jee 1.0.600.v201303142300] > [ERROR] Cannot satisfy dependency: org.eclipse.birt.chart.integration.wtp.feature.group 4.3.0.v20130507-1501-5117w3124161802612 depends on: org.eclipse.jst.web_ui.feature.feature.group 3.1.0 > [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_core.feature.feature.group 3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877 depends on: org.eclipse.jst.jee [1.0.600.v201303142300] > [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgi_3_iP75rjOs9WPy-5VkAg depends on: org.eclipse.jst.web_core.feature.feature.group [3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877] > [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_ui.feature.feature.group 3.5.0.v201303132100-7F7GFUGC27SvlcDqtgjb-_fhALqUqcxTpwxR8dsR depends on: org.eclipse.wst.ws_ui.feature.feature.group [3.5.0.v201303130455-7I7EFkYEtEo_L098-I7p2E7P2ryR5_y5VhjP9iqL] > {quote} > To highlight the specificity of this issue: > {quote} > [ERROR] Software being installed: org.eclipse.jst.jee 1.0.600.v201305070100 > ... > [ERROR] Only one of the following can be installed at once: [org.eclipse.jst.jee 1.0.600.v201305070100, org.eclipse.jst.jee 1.0.600.v201303142300] > ... > [ERROR] Cannot satisfy dependency: org.eclipse.jst.web_core.feature.feature.group 3.5.0.v201303132100-7Q7GGb8FE9LeBTMB1mgtJe1k1xz00tJ533877 depends on: org.eclipse.jst.jee [1.0.600.v201303142300] > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14454) setup build for jbosstools-arquillian

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14454?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14454: ---------------------------------------- Job built correctly. Site is http://download.jboss.org/jbosstools/builds/staging/jbosstools-arquillian... > setup build for jbosstools-arquillian > ------------------------------------- > > Key: JBIDE-14454 > URL: https://issues.jboss.org/browse/JBIDE-14454 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.1.0.Beta1 > > > start by using https://github.com/maxandersen/jbosstools-arquillian, we'll move it to jbosstools org shortly after. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14295) Should livereload clients always get all notifications ?

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14295?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-14295: ---------------------------------- Fix Version/s: 4.1.0.Beta2 (was: 4.1.0.Beta1) Not critical for 4.1.0.Beta1 > Should livereload clients always get all notifications ? > -------------------------------------------------------- > > Key: JBIDE-14295 > URL: https://issues.jboss.org/browse/JBIDE-14295 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta2 > > > From [~yradtsevich]: > livereload works great with cordovasim right now because livereload always sends *any* change to *all* livereload clients even if they are not interested. > That is great for cordovasim, but is this expected ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13950) Add support for Server Mode

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13950?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-13950 at 5/16/13 10:02 AM: ----------------------------------------------------------------- After discussing about it with Max, here are the way we'll implement the support for Server Mode: - At minimum, the LiveReload server accepts connection on the 35729 port (configurable). - The file:// scheme support remains unchanged: users can access local files and use the manually installed browser extension to connect to the LiveReload server and see updates as they save HTML/CSS/JS/Image files in their editors. - The LiveReload server should listen to other Servers events, in particular: Start/Stop/Restart on other servers. As soon as an App Server (JBoss AS, Tomcat, etc.) starts, the LiveReload server accept incoming requests on the 35729 port. - When the app server publishes some content, the Browser will be notified by the LiveReload server that some changes occurred. was (Author: xcoulon): After discussing about it with Max, here are the way we'll implement the support for Server Mode: - At minimum, the LiveReload server accepts connection on the 35729 port (configurable). - The file:// scheme support remains unchanged: users can access local files and use the manually installed browser extension to connect to the LiveReload server and see updates as they save HTML/CSS/JS/Image files in their editors. - The LiveReload server should listen to other Servers events, in particular: Start/Stop/Restart on other servers. As soon as an App Server (JBoss AS, Tomcat, etc.) starts, the LiveReload server accept incoming requests on the 35729 port (or anything else configured by the user), or open a socket on a high range port if reusing the same socket is not possible.Then, the LiveReload server should activate the "proxy" mode to forward all incoming requests to the app server. Returned HTML page should be modified on-the-fly to include the {noformat}<script src="http://localhost/livereload.js"></script>{noformat} element at the bottom of the page. - To access this proxy, a new "Show In>Web browser with LiveReload" action should be available on the Server and the Server Modules in the Servers View. - When the app server publishes some content, the Browser (restrict to those that are connected to this app server only) would be notified by the LiveReload server that some changes occurred. - If the user connects to the App Server without passing through the proxy mentionned above, he would have to enable the LiveReload support using his browser extension (as in case #2). If everything stated above works as expected, a single LiveReload server should cover all use-cases \o/ > Add support for Server Mode > ---------------------------- > > Key: JBIDE-13950 > URL: https://issues.jboss.org/browse/JBIDE-13950 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.1.0.Beta1 > > Attachments: LiveReload configuration.bmml, LiveReload configuration.png > > > Add support for livereload when the resources are accessed from an app server, as opposed to directory mode where the browser loads the resources using the file:// scheme -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13950) Add support for Server Mode

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13950?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-13950. ----------------------------------- Labels: new_and_noteworthy (was: ) Resolution: Done Fixed in https://github.com/jbosstools/jbosstools-livereload/pull/7 > Add support for Server Mode > ---------------------------- > > Key: JBIDE-13950 > URL: https://issues.jboss.org/browse/JBIDE-13950 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: LiveReload configuration.bmml, LiveReload configuration.png > > > Add support for livereload when the resources are accessed from an app server, as opposed to directory mode where the browser loads the resources using the file:// scheme -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

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 May 2013