January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16309: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186) > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16309: ---------------------------------------- Added a PR for jst - https://github.com/jbosstools/jbosstools-jst/pull/248 > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/15/14 2:16 PM: ----------------------------------------------------------- Topic branch: https://github.com/nickboldt/jbdevstudio-product/commits/JBDS-2669_refact... PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/124 (243 changed files including those with line ending changes that git was supposed to ignore, but tracks because of the renamed file) Note that in order to be consistent w/ the new namespace, I also refactored these: {quote} com.jboss.jbds.project.examples => com.jboss.devstudio.core.project.examples com.jboss.jbds.usage.branding => com.jboss.devstudio.core.usage.branding com.jboss.jbds.central => com.jboss.devstudio.core.central com.jboss.jbds.p2.director => com.jboss.devstudio.core.p2.director com.jboss.jbds.installer => com.jboss.devstudio.core.installer etc. {quote} And of course variables in .java and .launch files were updated too to use the new namespace. was (Author: nickboldt): Topic branch: https://github.com/nickboldt/jbdevstudio-product/commits/JBDS-2669_refact... PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/124 (243 changed files including those with line ending changes that git was supposed to ignore, but tracks because of the renamed file) Note that in order to be consistent w/ the new namespace, I also refactored these: {quote} com.jboss.jbds.project.examples => com.jboss.devstudio.core.project.examples com.jboss.jbds.usage.branding => com.jboss.devstudio.core.usage.branding com.jboss.jbds.central => com.jboss.devstudio.core.central com.jboss.jbds.p2.director => com.jboss.devstudio.core.p2.director {quote} And of course variables in .java and .launch files were updated too to use the new namespace. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- Topic branch: https://github.com/nickboldt/jbdevstudio-product/commits/JBDS-2669_refact... PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/124 (243 changed files including those with line ending changes that git was supposed to ignore, but tracks because of the renamed file) Note that in order to be consistent w/ the new namespace, I also refactored these: {quote} com.jboss.jbds.project.examples => com.jboss.devstudio.core.project.examples com.jboss.jbds.usage.branding => com.jboss.devstudio.core.usage.branding com.jboss.jbds.central => com.jboss.devstudio.core.central com.jboss.jbds.p2.director => com.jboss.devstudio.core.p2.director {quote} And of course variables in .java and .launch files were updated too to use the new namespace. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15640) BrowserSim: use JavaFX WebView as a browser engine

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15640?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov 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. - *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 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. - *Coding in progress* # 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. - *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 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16356) OpenShift project wizard does not handle a dirty/modified git project gracefully

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16356 at 1/15/14 1:17 PM: ------------------------------------------------------------------- Without looking into this in details I bet the cause for your failure is that the project that you're importing is not in its individual git repository. It's a project that shares a git repo with other projects (your project is in a subfolder within a git repo that contains several other projects). This layout is what caused troubles in JBIDE-12459. I'll eventually mark one of these duplicate as soon as I could verify it. was (Author: adietish): Without looking into this in details so far I bet the cause for your failure is that the project that you're importing is not in its individual git repository, it's a project that shares a git repo with other projects. This is what caused troubles in JBIDE-12459. I'll eventually mark one of these duplicate as soon as I could verify it. > OpenShift project wizard does not handle a dirty/modified git project gracefully > -------------------------------------------------------------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16356) OpenShift project wizard does not handle a dirty/modified git project gracefully

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16356: ------------------------------------------ Without looking into this in details so far I bet the cause for your failure is that the project that you're importing is not in its individual git repository, it's a project that shares a git repo with other projects. This is what caused troubles in JBIDE-12459. I'll eventually mark one of these duplicate as soon as I could verify it. > OpenShift project wizard does not handle a dirty/modified git project gracefully > -------------------------------------------------------------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2564) JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2564?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2564: ---------------------------------------- [~mmurray] looks like you're right, there's currently nothing that would change in UI. > JBDS70_1214: [Commit] (?) (P?) Fix support for multi-module maven projects > -------------------------------------------------------------------------- > > Key: JBDS-2564 > URL: https://issues.jboss.org/browse/JBDS-2564 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Andre Dietisheim > Fix For: 8.0.0.GA > > > Could be better at detecting proper packaging type for the openshift profile. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2669: ------------------------------------- +1 and I would like to try PR before pushing it > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16365) Tag jbosstools-4.2.0.Alpha1

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16365?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16365. ---------------------------------- Resolution: Done jbosstools-4.2.0.Alpha1 tag added > Tag jbosstools-4.2.0.Alpha1 > --------------------------- > > Key: JBIDE-16365 > URL: https://issues.jboss.org/browse/JBIDE-16365 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Critical > Fix For: 4.2.0.Alpha1 > > > Please tag the commit of your component that was built and aggregated into JBoss Tools 4.2.0.Alpha1. > See parent issue for details. -- 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, 3 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 January 2014