January 2014 - jbosstools-issues - Jboss List Archives

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2669: -------------------------------------- I prefer com.jboss.devstudio over com.redhat.jbdevstudio because it is IMO a more explicit name. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16323) Cordovasim: Need to make some UI enhancements

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16323?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-16323: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-vpe/pull/203 (was: https://github.com/jbosstools/jbosstools-vpe/pull/202) > Cordovasim: Need to make some UI enhancements > --------------------------------------------- > > Key: JBIDE-16323 > URL: https://issues.jboss.org/browse/JBIDE-16323 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha2 > > Attachments: barcode.png, proposal.png > > > There were several UI proposals for CordovaSim design: > - cordovasim takes up *Alot* of real estate. Need to make just one row for all panels - http://snag.gy/2gb2B.jpg. > - need to add icon to all "select" tags to make it more user-friendly -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16128: --------------------------------------------- if tycho would run integrations tests in a repository project you could do the assert against the previous released version to notice differences. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16334) GWT WAR directory is not set properly in Eclipse Google (GWT) plug-in

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16334?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16334: ------------------------------------- >From what I see in the current com.google.gdt.eclipse.maven.e37_3.4.2.v201310081834-rel-r43.jar, src/main/webapp is hardcoded when calling WebAppProjectProperties.setWarSrcDir. In their latest code (not currently public), they compute the directory from the <warSourceDirectory> value from org.codehaus.mojo:gwt-maven-plugin configuration. I don't know if/when current GPE dev builds will be available. Worst case scenario, we backport their fix to our own gwt configurator. > 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: maven > 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, 2 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: ---------------------------------------- A first drawback of Nexus compared to current publishing mechanism is that current plain "mvn deploy" don't take into account whether it's necessary to re-publish stuff (changes in code). However, as some changes can happen independently of commits (for example build config changing some build options), checking only commits to decide whether to publish or not seems somehow limited. Ideally what would be cool would be to re-use Tycho mechanism for replacement, but without enforcing commit-based timestamps. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16317?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16317: ------------------------------------ Portlet, GWT, and Freemarker have not changed in 4.2.x stream so no need to tag until they actually change / start development. > Tag projects for jbosstools-4.2.0.Alpha1 > ---------------------------------------- > > Key: JBIDE-16317 > URL: https://issues.jboss.org/browse/JBIDE-16317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.2.0.Alpha1 > > > Project leads, please tag your projects! > {code} > co jbosstools-4.2.0.Alpha1x > git tag jbosstools-4.2.0.Alpha1 > git push origin jbosstools-4.2.0.Alpha1 > {code} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16317?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16317: ------------------------------------- Central done > Tag projects for jbosstools-4.2.0.Alpha1 > ---------------------------------------- > > Key: JBIDE-16317 > URL: https://issues.jboss.org/browse/JBIDE-16317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Fix For: 4.2.0.Alpha1 > > > Project leads, please tag your projects! > {code} > co jbosstools-4.2.0.Alpha1x > git tag jbosstools-4.2.0.Alpha1 > git push origin jbosstools-4.2.0.Alpha1 > {code} -- 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 Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16334?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16334: -------------------------------- Component/s: maven (was: gwt) > 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: maven > 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] (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'm working on replacing the Ant script by something smarter that reads configuration of test runtime to find the right jars (instead of assuming it's using the locally built ones). That should solve our report mechanism. For EclEmma, here is a related feature request https://github.com/jacoco/eclemma/issues/74 > 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-16323) Cordovasim: Need to make some UI enhancements

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16323?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-16323: ------------------------------------- [~maxandersen], I understand now that the idea of making just one row of panels is not really neat. CordovaSim has several pop-up windows (Camera, Barcode etc). So, one row of panels brakes the layout !barcode.png|thumbnail! What do you think about living two rows of panels and making the CordovaSim window smaller by the default? !proposal.png|thumbnail! > Cordovasim: Need to make some UI enhancements > --------------------------------------------- > > Key: JBIDE-16323 > URL: https://issues.jboss.org/browse/JBIDE-16323 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.2.0.Alpha2 > > Attachments: barcode.png, proposal.png > > > There were several UI proposals for CordovaSim design: > - cordovasim takes up *Alot* of real estate. Need to make just one row for all panels - http://snag.gy/2gb2B.jpg. > - need to add icon to all "select" tags to make it more user-friendly -- 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