December 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2837) Investigate adding Gradle tools to Central

by Mickael Istria (JIRA)

Mickael Istria created JBDS-2837: ------------------------------------ Summary: Investigate adding Gradle tools to Central Key: JBDS-2837 URL: https://issues.jboss.org/browse/JBDS-2837 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Security Level: Public (Everyone can see) Components: 3rd-party-certification, central Reporter: Mickael Istria More and more people are talking about Gradle. I'm starting to believe that JBT/JBDS could have interest in providing Eclipse Gradle integration to its users. -- 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-16126) Publish component sites to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16126?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16126. ---------------------------------- Resolution: Duplicate Issue Dup of JBIDE-16128 > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16126 > URL: https://issues.jboss.org/browse/JBIDE-16126 > 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-16161) Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16161?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16161: ---------------------------------------- {quote} I have added the org.eclipse.e4.rcp dependency to the arquillian tests - https://github.com/jbosstools/jbosstools-arquillian/commit/2bb677f3d4e190... Adding the org.eclipse.osgi.compatibility.state fragment isn't enough. {quote} OK. Do you know which other bundle in this feature is necessary? The issue with adding the whole feature is that we don't know exactly what bundles are part of the problem. > Tycho tests require org.eclipse.osgi.compatibility.state fragment on Luna > ------------------------------------------------------------------------- > > Key: JBIDE-16161 > URL: https://issues.jboss.org/browse/JBIDE-16161 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Mickael Istria > > Since Tycho requires the PlatformAdmin service, we have to add the org.eclipse.osgi.compatibility.state fragment to tycho-surefire-plugin. > The easiest way is to add the org.eclipse.e4.rcp feature to the main build. -- 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-16133) No indication that management authentication fails

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-16133: ------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035003|https://bugzilla.redhat.com/show_bug.cgi?id=1035003] from NEW to CLOSED > No indication that management authentication fails > -------------------------------------------------- > > Key: JBIDE-16133 > URL: https://issues.jboss.org/browse/JBIDE-16133 > Project: Tools (JBoss Tools) > Issue Type: Quality Risk > Components: server > Reporter: Steven Hawkins > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.1.1.CR1 > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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-16148) Enable/disable updating pom.xml when adding Arquillian support

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16148?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-16148: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) Max, Could you please review? > 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: Max Rydahl Andersen > -- 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-16148) Enable/disable updating pom.xml when adding Arquillian support

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16148?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16148: --------------------------------------- The PRs: https://github.com/jbosstools/jbosstools-arquillian/pull/39 - master https://github.com/jbosstools/jbosstools-arquillian/pull/40 - jbosstools-4.1.x https://github.com/jbosstools/jbosstools-arquillian/pull/41 - jbosstools-4.1.1.x https://github.com/jbosstools/jbosstools-arquillian/pull/39 has been applied to master. > 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-16134) CordovaSim should start the livereload server

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16134?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16134: -------------------------------------- BrowserSim/CordovaSim has a menu item that says enable livereload and AFAIK that menu item is visible and enabled even if the livereload plugins are not installed. In my opinion, the dependency already exists and BrowserSim/CordovaSim is just dodging it by being an external app. I guess the dependency can be an optional one as long as the menu items are not enabled or visible when the livereload is not possible. I think livereload server is just odd on the servers view but as long as a developer does not have to deal with it on default cases I am OK with it. Would it be too hard if someone enables livereload on BrowserSim the livereload server is created and started automagically so that they never even realise there is a server involved. > 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: Konstantin Marmalyukov > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2013