[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-15640:
--------------------------------
Description:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
- Disable switcher for Linux platform - *Done*
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
# Port for debugging should not be hardcoded
was:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
## Disable switcher for Linux platform
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
# Port for debugging should not be hardcoded
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
> *Pros:*
> # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
> # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
> # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
> *Cons:*
> # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
> # window.localStorage is not supported (may be a problem for CordovaSim)
> # Character encoding problems on some installations
> # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
> *On the high level our plan is to:*
> # Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
> - Disable switcher for Linux platform - *Done*
> # Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
> # Mock javaFX dependencies - *Done*
> # Fix LiveReload and Touch Events for JavaFx WebView - *Done*
> # Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
> # Port for debugging should not be hardcoded
--
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, 5 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-15640:
--------------------------------
Description:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
- Disable switcher for Linux platform - *Done*
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Done*
# Port for debugging should not be hardcoded
was:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
- Disable switcher for Linux platform - *Done*
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
# Port for debugging should not be hardcoded
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
> *Pros:*
> # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
> # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
> # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
> *Cons:*
> # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
> # window.localStorage is not supported (may be a problem for CordovaSim)
> # Character encoding problems on some installations
> # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
> *On the high level our plan is to:*
> # Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
> - Disable switcher for Linux platform - *Done*
> # Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
> # Mock javaFX dependencies - *Done*
> # Fix LiveReload and Touch Events for JavaFx WebView - *Done*
> # Move Dev tools front-end source code to the separate plugin / git submodule - *Done*
> # Port for debugging should not be hardcoded
--
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, 5 months
[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-15640:
--------------------------------
Description:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
## Disable switcher for Linux platform
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
# Port for debugging should not be hardcoded
was:
JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
*Pros:*
# WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
# It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
# Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
*Cons:*
# Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
# window.localStorage is not supported (may be a problem for CordovaSim)
# Character encoding problems on some installations
# Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
*On the high level our plan is to:*
# Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Partly done*
## Disable switcher for Linux platform
# Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
# Mock javaFX dependencies - *Done*
# Fix LiveReload and Touch Events for JavaFx WebView - *Done*
# Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
# Port for debugging should not be hardcoded
> BrowserSim: use JavaFX WebView as a browser engine
> --------------------------------------------------
>
> Key: JBIDE-15640
> URL: https://issues.jboss.org/browse/JBIDE-15640
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.2.x
>
>
> JavaFX [WebView|http://docs.oracle.com/javafx/2/api/javafx/scene/web/WebView.html] supports Debugger API and could be embedded into BrowserSim as an alternative to the SWT Browser.
> *Pros:*
> # WebView supports Debugger API - we can enable full featured [DevTools|https://developers.google.com/chrome-developer-tools/] and/or integrate it with [EclipseDebugger|https://code.google.com/p/chromedevtools/wiki/EclipseDebu...]
> # It is available on all OSes where Oracle JVM 7 is installed - no requirement to install Safari and 32-bit JVM on Windows
> # Can be used together with the SWT Browser (i.e. if there is no JavaFX present, we can fallback to the SWT Browser in runtime)
> *Cons:*
> # Not a part of OpenJDK, Oracle JVM 7 only (not sure if JavaFX could be installed standalone)
> # window.localStorage is not supported (may be a problem for CordovaSim)
> # Character encoding problems on some installations
> # Debugger API bindings to Java are not final now - we can face Java run-time errors with later versions of Oracle JVMs
> *On the high level our plan is to:*
> # Implement possibility of switching BrowserSim's web engine SWT.WEBKIT / JavaFx WebView. This possibility will be enabled only for windows and mac os users. Due to native errors coupled with gtk3 usage (related jira https://javafx-jira.kenai.com/browse/RT-35264 ) there will be only one web engine on Linux - SWT.WEBKIT. - *Done*
> ## Disable switcher for Linux platform
> # Solve perfomance issues. Debugger freezes rather often - *Coding in progress*
> # Mock javaFX dependencies - *Done*
> # Fix LiveReload and Touch Events for JavaFx WebView - *Done*
> # Move Dev tools front-end source code to the separate plugin / git submodule - *Coding in progress*
> # Port for debugging should not be hardcoded
--
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, 5 months
[JBoss JIRA] (JBDS-2745) Support installation of Early Access / Experimental / Incubating plugins
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2745?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2745:
--------------------------------------
See JBIDE-16375 for implementation in JBoss Tools
> Support installation of Early Access / Experimental / Incubating plugins
> ------------------------------------------------------------------------
>
> Key: JBDS-2745
> URL: https://issues.jboss.org/browse/JBDS-2745
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Burr Sutter
>
> It's been suggested that it would be nice to have Central available to install non-GA content. How might this appear?
> [~burrsutter], [~maxandersen], are we talking about:
> * an additional dialog warning users about untested content? (that might be ignored / blindclicked)
> * an additional tab in Central for this type of content (what label would you use?)
> * relabelling the content's feature descriptions / titles / copyright / license terms to be clear it's unstable content? (might be ignored)
> * some other workflow?
> See also JBDS-2068.
--
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, 5 months
[JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15918:
---------------------------------------------
which build page are you referring to ? the one behind vpn and the one that dissapears eventually if you don't look there early enough ?
This is not about getting tags promoted - just about having a history of which commit was used for a certain build.
> Could Jenkins perform tagging of its own repo?
> ----------------------------------------------
>
> Key: JBIDE-15918
> URL: https://issues.jboss.org/browse/JBIDE-15918
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Priority: Minor
>
> [~maxandersen] said:
> {quote}
> Project leads, please tag your projects!
> {code}
> co jbosstools-4.1.1.Beta1x
> git tag jbosstools-4.1.1.Beta1
> git push origin jbosstools-4.1.1.Beta1
> {code}
> {quote}
> Then asked:
> {quote}
> Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
> {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
12 years, 5 months
[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Mickael Istria commented on JBIDE-3937:
---------------------------------------
A few questions:
* What do you mean by "Stress test", do you mean "performance tests"? If so, it would make more sense to create a real usage scenario and execute it on a static environment and look at execution time trends to see how this evolves.
* What would be the goal of such a "master" test suite?
* Who would be in charge of it?
* Is it about unit tests or integration tests ?
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
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, 5 months
[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Mickael Istria updated JBIDE-3937:
----------------------------------
Component/s: qa
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
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, 5 months
[JBoss JIRA] (JBIDE-14932) p2 stats urls are broken when built locally
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14932?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-14932.
----------------------------------
Resolution: Cannot Reproduce Bug
> p2 stats urls are broken when built locally
> -------------------------------------------
>
> Key: JBIDE-14932
> URL: https://issues.jboss.org/browse/JBIDE-14932
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Fix For: 4.1.x, 4.2.0.Alpha1
>
>
> when building site locally and installing from it you get this error:
> eclipse.buildId=4.3.0.I20130530-1430
> java.version=1.6.0_45
> java.vendor=Apple Inc.
> BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring -showlocation
> Command-line arguments: -os macosx -ws cocoa -arch x86 -product org.eclipse.epp.package.jee.product -keyring /Users/max/.eclipse_keyring -showlocation
> Warning
> Wed Jun 19 16:36:16 CEST 2013
> Unable to report download statistics due to invalid URL: http://download.jboss.org/jbosstools/usage/installs/3.7.0-SNAPSHOT/Beta2/... suffix: org.hibernate.eclipse.feature
> Should have that ${JOB_NAME} default to something "sensible" and we'll be able to track that too :)
> like JOB_NAME=_local_ if not otherwise specificed.
--
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, 5 months
[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-14642:
-----------------------------------
Labels: versioning (was: )
> How to automate process of bumping version for changed modules/submodules for every release
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14642
> URL: https://issues.jboss.org/browse/JBIDE-14642
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.1.0.Beta1
> Reporter: Denis Golovin
> Assignee: Max Rydahl Andersen
> Labels: versioning
> Fix For: 4.2.x
>
>
> The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped.
> We need two things:
> A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing)
> B) document/automate a process which every affected lead can follow to make this happen and if not See #A
--
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, 5 months