November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16148) Enable/disable updating pom.xml when adding Arquillian support

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-16148: ------------------------------------- Summary: Enable/disable updating pom.xml when adding Arquillian support Key: JBIDE-16148 URL: https://issues.jboss.org/browse/JBIDE-16148 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing-tools Affects Versions: 4.1.1.Beta1 Reporter: Snjezana Peco Assignee: Snjezana Peco -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16140) Investigate usage of Jenkins folder plugin

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16140: ---------------------------------------- > They are statically defined, tied to how views are organized, how machines are labeled and requires multiple search and replace to actually work. Views are actually not a problem as it's just following the layout of cache folder. However, I forgot the issue with the slave names, which indeed makes that jobs are indeed not much portable. > Investigate usage of Jenkins folder plugin > ------------------------------------------ > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- 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, 4 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: --------------------------------------------- We don't need to mirror nexus content for stuff that is just for building imo. We can just have a composite referencing the nexus locations. We should test what performance difference there is if any before starting to force mirror. And Nick, *every* other jboss developer uses nexus to release - we don't because our current setup that you describe is not easy to understand and is very different and mixes various concerns. That is just where we ended up by growing it organically and with focus on release engineering immediate needs, missing a more overall view. We are trying to clean that up. Experimenting with nexus to make it as easy to do mvn deploy is part of that. I'm not saying using nexus solves everything but it removes alot of complexity and it becomes clearer which parts does what. With respect to next steps - [~mickael_istria] are you just suggesting we enabled mvn deploy towards snapshot repo in jenkins build to see what happens ? Not really sure what that will give us that a basic manual mvn deploy would not do ? I would imagine next step is to fork a few of the components and try see how parent pom and their pom could be setup to consume these nexus urls (or derived composite urls) ? > 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.Alpha1 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16093: --------------------------------------------- None of the wtp validators, jbt validators runs on all projects without something being enabled (i.e. by maven configurator). That is the big difference. With the former arquillian behavior users had zero control. Yes, I think a *separate* jira should be made to make it possible to enable arquillian without changing nor requiring a pom.xml to be present. > NPEs when compiling wildfly codebase > ------------------------------------ > > Key: JBIDE-16093 > URL: https://issues.jboss.org/browse/JBIDE-16093 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: respin-b > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png > > > When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian. > !npes-building-wildfly.png! > !npes-building-wildfly-2.png! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16140) Investigate usage of Jenkins folder plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16140: --------------------------------------------- I have not found any way to publish jbdevstudio-ci config anywhere else than jboss.org. They are statically defined, tied to how views are organized, how machines are labeled and requires multiple search and replace to actually work. With buildchow I can experiement and try without affecting main jenkins and I can setup different profiles to have it adjusted to other servers. Thats where the power of buildchow comes in. I actually think Folder can be combined with buildchow - just have buildchow generate folder styled jobs. I haven't tried this though. I don't think they are mutually exclusive. > Investigate usage of Jenkins folder plugin > ------------------------------------------ > > Key: JBIDE-16140 > URL: https://issues.jboss.org/browse/JBIDE-16140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Mickael Istria > > Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc... > We should investigate on whether it would help to use to manage JBT/JBDS jobs. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15980) NullPointerException in RuntimeMatcher.RuntimeMatcher.findExistingRuntimes()

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15980?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15980. --------------------------------- Verified in JBDS 7.1.0.CR1a B560. The Google App Engine is still there, but no pop up or NPE. > NullPointerException in RuntimeMatcher.RuntimeMatcher.findExistingRuntimes() > ---------------------------------------------------------------------------- > > Key: JBIDE-15980 > URL: https://issues.jboss.org/browse/JBIDE-15980 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Victor Rubezhny > Assignee: Rob Stryker > Fix For: 4.1.1.CR1 > > Attachments: BrokenGoogleRuntime.png, central-npe.png, ServerRuntimeEnvironments.png > > > What I did to Reproduce (Used JBDS 7.1.Beta1: jbdevstudio-product-eap-universal-7.1.0.Beta1-v20131102-1529-B493): > EXECUTE: Start jbdevstudio, proceed to continue with the Central > EXECUTE: Open "Help->Install New Software..." dialog > EXECUTE: Add new Software Site and make it to point to Central TP (http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/4.3...) > EXECUTE: Choose the Software Site just created, uncheck "Group items by Category", then find and install "Google Plugin for Eclipse 4.3", restart when requested > EXECUTE: Open "Help->Install New Software..." dialog > EXECUTE: Click on "What's already installed" link due to open "JBoss Developer Studio Installation Details" dialog. > EXECUTE: Select "Google Plugin for Eclipse" and press "Uninstall..." button, proceed with all the uninstallation steps and restart when requested > FAILED: See NPE dialog poping up after restart and error message is logged: > {code} > !ENTRY org.eclipse.core.jobs 4 2 2013-11-15 17:07:31.748 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:249) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16147) Run findbugs on LiveReload and shoot all the scary bugs

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-16147: ------------------------------------- Summary: Run findbugs on LiveReload and shoot all the scary bugs Key: JBIDE-16147 URL: https://issues.jboss.org/browse/JBIDE-16147 Project: Tools (JBoss Tools) Issue Type: Task Components: livereload Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.x [~fbricon] reported to me that Findbugs spotted a few scary bugs on some (unused pieces of code). Let's kill those bugs ! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16134) CordovaSim should start the livereload server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16134: --------------------------------------------- I think it makes sense to have livereload info dialog show up during launch in case it is not running. [~xcoulon] and I talked about doing that too when simply opening a html file - then it would be enabled for all other cases too ("normal" browser livereload) what do you think about that option ? > CordovaSim should start the livereload server > --------------------------------------------- > > Key: JBIDE-16134 > URL: https://issues.jboss.org/browse/JBIDE-16134 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.CR1 > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > > CordovaSim should configure and start the livereload server when the livereload is enabled. > If starting the server from CordovaSim menu is a big problem, alternately, the server can always be configured and started before a CordovaSim launch. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Vlado Pakan commented on JBDS-2709: ----------------------------------- Tested with JBDS7.1.0.CR1 CR1-v20131124-0717-B560 everything works fine installing from http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... . But org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar feature was installed and it's the same as was already tested when rc1 SVN Kit build was available. Is it ok? On http://eclipse.svnkit.com/1.8.x are these two versions of SVN Kit feature: - org.tmatesoft.svnkit_1.8.0.r10086_v20131126_1344.r10086_v20131126_1344.jar - org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar The second one is older but unfortunately becaus of name is installed as newer. I think we should use the first one? > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.1.0.GA > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ] Vlado Pakan edited comment on JBDS-2709 at 11/28/13 5:13 AM: ------------------------------------------------------------- Tested with JBDS7.1.0.CR1 CR1-v20131124-0717-B560 everything works fine installing from http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... . But org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar feature was installed and it's the same as was already tested when rc1 SVN Kit build was available. Is it ok? On http://eclipse.svnkit.com/1.8.x are these two versions of SVN Kit feature: - org.tmatesoft.svnkit_1.8.0.r10086_v20131126_1344.r10086_v20131126_1344.jar - org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar The second one is older but unfortunately because of name is installed as newer. I think we should use the first one? was (Author: vpakan): Tested with JBDS7.1.0.CR1 CR1-v20131124-0717-B560 everything works fine installing from http://download.jboss.org/jbosstools/updates/requirements/subclipse/1.10.... . But org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar feature was installed and it's the same as was already tested when rc1 SVN Kit build was available. Is it ok? On http://eclipse.svnkit.com/1.8.x are these two versions of SVN Kit feature: - org.tmatesoft.svnkit_1.8.0.r10086_v20131126_1344.r10086_v20131126_1344.jar - org.tmatesoft.svnkit_1.8.0.rc1_r10069_v20131105_1500.jar The second one is older but unfortunately becaus of name is installed as newer. I think we should use the first one? > Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central > ---------------------------------------------------------- > > Key: JBDS-2709 > URL: https://issues.jboss.org/browse/JBDS-2709 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Vlado Pakan > Fix For: 7.1.0.GA > > > As reported here: > https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=... > {quote} > Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN. > http://subclipse.tigris.org/update_1.10.x > Local repository compatibility between these tools and JBDS is very nice to have. > Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question. > {quote} > http://www.svnkit.com/download.php > Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version. -- 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, 4 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 November 2013