January 2014 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------- Good catch, fixed feature id. There is no reason mark it as *.branding, because it is not only branding. Usage is a different story, usage.branding contains service implementation which provides labels for usage UI in JBDS. > 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-2669 at 1/7/14 2:42 PM: ------------------------------------------------------------- *Option D* Plug-ins usually don't use suffix ".plugin" and it is not plug-in anymore, but bundle; *.core.* to be consistent with JBossTools Core {code}com.jboss.jbds.product => com.jboss.jbds.core{code} Features usually named after branding plugins w/ or w/o suffix ".feature" all our features have suffix {code}com.jboss.jbds.product.feature => com.jboss.jbds.core.feature {code} This is meta IU ID generated for .product file and I agree that "package" would look better here than "all" and core for consistency {code}com.jboss.jbds.all => com.jboss.jbds.core.package{code} This id I believe should match product id defined through extension point in branding plugin and it forms as <plug-in-id>.<extension-point-id> {code}com.jboss.jbds.product.product => com.jboss.jbds.core.product{code} was (Author: dgolovin): *Option D* Plug-ins usually don't use suffix ".plugin" and it is not plug-in anymore, but bundle; *.core.* to be consistent with JBossTools Core {code}com.jboss.jbds.product => com.jboss.jbds.core{code} Features usually named after branding plugins w/ or w/o suffix ".feature" all our features have suffix {code}com.jboss.jbds.product.feature => com.jboss.devstudio.core.feature {code} This is meta IU ID generated for .product file and I agree that "package" would look better here than "all" and core for consistency {code}com.jboss.jbds.all => com.jboss.jbds.core.package{code} This id I believe should match product id defined through extension point in branding plugin and it forms as <plug-in-id>.<extension-point-id> {code}com.jboss.jbds.product.product => com.jboss.jbds.core.product{code} > 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-2866) CordovaSim Debugger

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-2866: ----------------------------------- {quote} Do you have a HD version of this video? {quote} [~burrsutter], you should choose 720p HD quality on the YouTube. {quote} For instance, it would appear that you are not using the JS editors in Eclipse but some 3rd party window for JS editing. {quote} Yes, I have set Sublime Text editor as a default in the eclipse. Eclipse js editor was absolutely unusable when I worked with ripple source code (3mb of js). Since then I got used to the Sublime :-) > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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-16128) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16128: ---------------------------------------- Changes pushed to job configurations. Let's wait for time to do his work and give us ideas on what's to improve (if there's stuff to improve). Example of site created: https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/op... Note that nothing says it's part of the "master" nor "4.2.luna" stream. If we go for releases the project will have to announce new available versions and all consumers (components, aggregation, product) would have to adapt, similarly to what happens for JBT-IS. > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- 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-16336) Firebug Lite copy & paste

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-16336: ----------------------------------- Summary: Firebug Lite copy & paste Key: JBIDE-16336 URL: https://issues.jboss.org/browse/JBIDE-16336 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Reporter: Burr Sutter Copy & Paste issue - i only tested on Mac http://screencast.com/t/uDFcCHgnoN -- 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] (JBTIS-232) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-232?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-232. ---------------------------- Fix Version/s: 4.1.3.Final 7.0.0.Final-JBDSIS Resolution: Done Updated teiid designer to 8.3.1.Final https://github.com/jbosstools/jbosstools-integration-stack/pull/166 > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-232 > URL: https://issues.jboss.org/browse/JBTIS-232 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: teiid > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Barry LaFond > Fix For: 4.1.3.Final, 7.0.0.Final-JBDSIS > > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible if the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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-16214) Code Coverage jobs needs to have locally available measured plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16214: ---------------------------------------- Note that if you build and test everything at once for a given component (both plugins/ and tests/) then you get good coverage reports. However, it will test the output of the reactor, not the jar coming from repositories or external application. > Code Coverage jobs needs to have locally available measured plugins > ------------------------------------------------------------------- > > Key: JBIDE-16214 > URL: https://issues.jboss.org/browse/JBIDE-16214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Vlado Pakan > Assignee: Mickael Istria > Fix For: 4.1.x > > > Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site. > When these are built locally prior to build calculating code coverage it returns correct results. > Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build. > We need to find way how to fix this. > It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560 -- 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-16334) GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16334?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-16334: ------------------------------------- Assignee: Denis Golovin > GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in > --------------------------------------------------------------------- > > Key: JBIDE-16334 > URL: https://issues.jboss.org/browse/JBIDE-16334 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: gwt > Affects Versions: 4.1.0.Final > Environment: Eclipse Kepler > m2e 1.2 > m2e-wtp 1.0.1 > Google Plugin for Eclipse 3.4.2 > JBoss Maven GWT Configurator 1.5.4 > Reporter: Slawa Giterman > Assignee: Denis Golovin > > Hello, > I use Eclipse Kepler, m2e 1.2, m2e-wtp 1.0.1, Google Plugin for Eclipse 3.4.2 and JBoss Maven GWT Configurator 1.5.4. > My project uses not default warSourceDirectory in Maven pom.xml (<warSourceDirectory>$\{basedir\}/WebContent</warSourceDirectory>). > The problem is that after each Maven -> Update Project action, GWT WAR directory in Eclipse (Project -> context menu -> Google -> Web Toolkit Settings -> Web Application -> WAR directory) is set to default Maven value "src/main/webapp" and not to the value of warSourceDirectory from pom.xml. > It seems that WAR Directory value is read from file <ECLIPSE_PROJECT>/.settings/com.google.gdt.eclipse.core.prefs, property *warSrcDir*. This file has also another property, *lastWarOutDir* which tells Google GWT Plugin where to compile the GWT code (this issue was solved in JBIDE-11224) > Current content of com.google.gdt.eclipse.core.prefs after Maven -> Update Project: > {code}lastWarOutDir=/applicationserver/WebContent > warSrcDir=src/main/webapp{code} > So, the question is, is it possible to set value of warSrcDir to the same value as lastWarOutDir so that Eclipse does not show error "WAR source directory /applicationserver/src/main/webapp is missing" after each update? -- 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-2864) Support faster turnarounds (with possibly hot deploy)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2864: ---------------------------------------- new priorities as discussed with OpenShift team: {quote} 1.) Downloadable Cartridges + predefined quickstarts 2.) Binary Deployment 3.) xPaaS (Fuse/BPM/Aero) 4.) Intergrating Jenkins/Nexus Completion {quote} > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- 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-16214) Code Coverage jobs needs to have locally available measured plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16214: ---------------------------------------- I believe it's an occurence of https://github.com/jacoco/eclemma/issues/49 . pack200 modifies class files and make JaCoCo unable to read classes after that. A fix was provided so that Jacoco could use the pack200 jars to generate good reports, but it seems like nothing can be done in EclEmma for now... > Code Coverage jobs needs to have locally available measured plugins > ------------------------------------------------------------------- > > Key: JBIDE-16214 > URL: https://issues.jboss.org/browse/JBIDE-16214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Vlado Pakan > Assignee: Mickael Istria > Fix For: 4.1.x > > > Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site. > When these are built locally prior to build calculating code coverage it returns correct results. > Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build. > We need to find way how to fix this. > It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560 -- 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