October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15606: --------------------------------------------- For Kepler where this step was "missed" - why is it not enough to simply point to stable/kepler to get the freemarker 1.3.100 final versions ? You simply just put in the exact feature version. And wouldn't it be better to actually build these sites and aggregate them than this "reverse option" ? or do you mean this is just for the kepler release and we do something better/more reliable for future releases ? > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15506) Support Asciidoctor files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15506?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15506: --------------------------------------------- can we resolve this bug please ? afaics the feature works as expected (reloads are sent out when .adoc files are edited). There is only a specific browser that seem to have issues with combination of asciidoc plugins, but that is not jbide tooling side bug and the situation is not worse than before. > Support Asciidoctor files > ------------------------- > > Key: JBIDE-15506 > URL: https://issues.jboss.org/browse/JBIDE-15506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > Provide LiveReload support for Asciidoc (.adoc or .asciidoc) files in the browser. > If the user has both LiveReload browser extension AND the new asciidoc.js preview extension (http://asciidoctor.org/news/2013/09/18/introducing-asciidoctor-js-live-pr...), then changes in a workspace file could (should) be previewed in the 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15610) For 4.1.1.Beta1: since one forge plugin has bumped, so should they all

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15610?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15610: --------------------------------------------- note, this is not something new - we've always said if a component is released we shouldn't reuse the version numbers from previous releases since it makes it extremely hard to track down errors since the only difference is build timestamp which doesn't help tracking down which branch/master it was actually built from. the forge.runtime specific version is a grey-area case since it obviously is not intended to have any changes in it at all besides which runtime version it contains - but you could simply add a a or b to indiate it is a rebuild. > For 4.1.1.Beta1: since one forge plugin has bumped, so should they all > ---------------------------------------------------------------------- > > Key: JBIDE-15610 > URL: https://issues.jboss.org/browse/JBIDE-15610 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > [~maxandersen] would prefer that since a single forge plugin (forge.runtime) has bumped from 1.3.3 to 1.4.1, that all the forge plugins (and their containing features) also bump at least their service (micro) increment. > Thus: > 1.2.0 -> 1.2.1 > 1.0.0 -> 1.0.1 > 2.0.0 -> 2.0.1 > And in master branch [1], I'm guessing this is wrong: > {code}org.jboss.tools.forge2.runtime_2.0.1.Alpha1-v20130927-1755-B403.jar{code} > Shouldn't that be at version 2.1.0 or 2.0.100, not 2.0.1? > [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast... -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-183) Create SY bot test for domain settings

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-183?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-183: ------------------------------------ Description: * Check / uncheck Enable Message Trace * Add / Remove / Edit domain properties * Add / Remove / Edit security configurations > Create SY bot test for domain settings > -------------------------------------- > > Key: JBTIS-183 > URL: https://issues.jboss.org/browse/JBTIS-183 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.3 > > > * Check / uncheck Enable Message Trace > * Add / Remove / Edit domain properties > * Add / Remove / Edit security configurations -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-183) Create SY bot test for domain settings

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-183: --------------------------------------- Summary: Create SY bot test for domain settings Key: JBTIS-183 URL: https://issues.jboss.org/browse/JBTIS-183 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: QE Affects Versions: 4.1.3 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.1.3 -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15198) Move away from sonatype aether to eclipse aether

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15198?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-15198: ----------------------------------- Assignee: Fred Bricon > Move away from sonatype aether to eclipse aether > ------------------------------------------------ > > Key: JBIDE-15198 > URL: https://issues.jboss.org/browse/JBIDE-15198 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven, project-examples, testing-tools > Affects Versions: 4.1.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.x > > > With Maven 3.1.0, Sonatype Aether has been replaced with Eclipse Aether. m2e 1.5.0 will soon do the same. Currently, I've found that at least the following plugins have a dependency to the Sonatype version : > - org.jboss.tools.arquillian.core > - org.jboss.tools.maven.project.examples > - org.jboss.tools.maven.ui > Ideally the next m2e version won't embed the jars directly (but this is not guaranteed). Aether is available from this p2 repo : http://download.eclipse.org/aether/aether-core/milestones -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Add support for EAP 6.2

by Martin Malina (JIRA)

Martin Malina created JBIDE-15614: ------------------------------------- Summary: Add support for EAP 6.2 Key: JBIDE-15614 URL: https://issues.jboss.org/browse/JBIDE-15614 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime-detection, server Affects Versions: 4.1.0.Final Environment: JBDS 7.0.0.GA Reporter: Martin Malina Fix For: 4.1.1.Beta1 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 Let me know if you want subtasks for these two. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15578) BrowserSim Screen Capture Fail

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15578?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15578: ------------------------------------- Assignee: Konstantin Marmalyukov Reproducible on Mac. Not reproducible on Windows. > BrowserSim Screen Capture Fail > ------------------------------ > > Key: JBIDE-15578 > URL: https://issues.jboss.org/browse/JBIDE-15578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Attachments: 2013-09-27_1132.png, browsersim_2013-09-27-113159.png > > > This URL > http://mobile.walmart.com/m/phoenix;jsessionid=612BD65031620D8B8FFFBF9D3A... > See attached image for the screenshot captured - it loses the images in the page. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15613: --------------------------------------- hello [~vpakan], "I can get this error with Fedora. There is no error with Chrome." -> did you mean Firefox instead of Fedora ? In this case, which version of the Firefox extension do you use ? 2.0.8 or 2.0.9 ? Thanks > Error: Failed to send reload command to browser > ----------------------------------------------- > > Key: JBIDE-15613 > URL: https://issues.jboss.org/browse/JBIDE-15613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.1.Alpha2 > Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.1.1.Beta1 > > > 1. Import HTML 5 project from Central > 2. Run it on server > 3. Open project in Web Browser with LiveReload via Server View > 4. Update and save index.html file many times > ASSERT: Changes to index.html are reflected in Web Browser > ERROR: This error appear in Error Log: > Failed to send reload command to browser > {noformat} > java.io.IOException: closedOut 1001:null > at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437) > at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97) > at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177) > at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57) > at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131) > at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {noformat} -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15506) Support Asciidoctor files

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15506?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15506: --------------------------------------- I opened a discussion here: http://discuss.asciidoctor.org/Issues-with-the-Asciidoctor-preview-extens... > Support Asciidoctor files > ------------------------- > > Key: JBIDE-15506 > URL: https://issues.jboss.org/browse/JBIDE-15506 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > Provide LiveReload support for Asciidoc (.adoc or .asciidoc) files in the browser. > If the user has both LiveReload browser extension AND the new asciidoc.js preview extension (http://asciidoctor.org/news/2013/09/18/introducing-asciidoctor-js-live-pr...), then changes in a workspace file could (should) be previewed in the 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

12 years, 6 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 October 2013