January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-18692 at 1/15/15 8:03 AM: -------------------------------------------------------------- [~mickael_istria] in terms of building ripple on windows. It seems to build everything but wasn't able to deploy http://snag.gy/HSfnF.jpg was (Author: ibuziuk): [~misria] in terms of building ripple on windows. It seems to build everything but wasn't able to deploy http://snag.gy/HSfnF.jpg > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18692: ------------------------------------- [~misria] in terms of building ripple on windows. It seems to build everything but wasn't able to deploy http://snag.gy/HSfnF.jpg > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18861: --------------------------------------- [~rob.stryker], when I followed the steps, I noticed that when I stopped the module, it was undeployed and then the server said: {code} 13:46:20,300 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found earproj.ear in deployment directory. To trigger deployment create a file called earproj.ear.dodeploy {code} I know it's kind of expected - we would need to remove the contents of the ear from the folder to avoid this. Do you think it's ok? But then, when I carried on, after I stopped and started Wildfly, the module was shown as [Synchronized] in the server view and it was not running. Shouldn't it say [Stopped, Synchronized]? I was then able to start it and it worked, so in this regard it's ok. > module start action does not delete *.undeployed file > ----------------------------------------------------- > > Key: JBIDE-18861 > URL: https://issues.jboss.org/browse/JBIDE-18861 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > If you start Wildfly with all modules enabled and started. > Now use STOP action on an EAR module. > Now stop Wildfly. > Now start Wildfly (debug or run). > It will start up without the EAR module running, this is correct behavior at this point. > Now use START on EAR module. It fails to start at all. > This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up. > If you perform a "full publish" on the module that appears to cause it to start up as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18861?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-18861 at 1/15/15 7:49 AM: ---------------------------------------------------------------- [~rob.stryker], when I followed the steps, I noticed that when I stopped the module, it was undeployed and then the server said: {code} 13:46:20,300 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found earproj.ear in deployment directory. To trigger deployment create a file called earproj.ear.dodeploy {code} I know it's kind of expected - we would need to remove the contents of the ear from the folder to avoid this. Do you think it's ok? But then, when I carried on, after I stopped and started Wildfly, the module was shown as [Synchronized] in the server view and it was not running. Shouldn't it say [Stopped, Synchronized]? I was then able to start it and it worked, so in this regard it's ok. (I tried this on master from a few days ago.) was (Author: mmalina): [~rob.stryker], when I followed the steps, I noticed that when I stopped the module, it was undeployed and then the server said: {code} 13:46:20,300 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found earproj.ear in deployment directory. To trigger deployment create a file called earproj.ear.dodeploy {code} I know it's kind of expected - we would need to remove the contents of the ear from the folder to avoid this. Do you think it's ok? But then, when I carried on, after I stopped and started Wildfly, the module was shown as [Synchronized] in the server view and it was not running. Shouldn't it say [Stopped, Synchronized]? I was then able to start it and it worked, so in this regard it's ok. > module start action does not delete *.undeployed file > ----------------------------------------------------- > > Key: JBIDE-18861 > URL: https://issues.jboss.org/browse/JBIDE-18861 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windows7 64bit, JDK 8u25 > Reporter: Darryl Miles > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.3.Final, 4.3.0.Alpha1 > > > If you start Wildfly with all modules enabled and started. > Now use STOP action on an EAR module. > Now stop Wildfly. > Now start Wildfly (debug or run). > It will start up without the EAR module running, this is correct behavior at this point. > Now use START on EAR module. It fails to start at all. > This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up. > If you perform a "full publish" on the module that appears to cause it to start up as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12532) Open command doesn't open URLs in JBoss Tools

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12532?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-12532: ------------------------------------ I can confirm that this error does not happen when the external browser is selected. > Open command doesn't open URLs in JBoss Tools > --------------------------------------------- > > Key: JBIDE-12532 > URL: https://issues.jboss.org/browse/JBIDE-12532 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 3.3.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.2.2.Final, 4.2.3.Final > > > As of FORGE-611, now it's possible for the OpenPlugin to open URLs. This works when running Forge in console mode, but does not on JBoss Tools. > To reproduce, type the following in the Forge console: > {code} > open http://forge.jboss.org > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- "the extra stuff" would be the integration stack plugins + their needed dependencies. And on question on whether users need todo a software update or not depends on timing. We've done software updatesite only releases in the past - whether you want to do that or not for IS is up to you. I'm just suggesting we at least make it so *if* IS have done their GA release that they respin the installers when we do JBDS core installer updates too. If we don't, then yes IS users would need to do or at least be asked/told there are updates available to install. > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3314) Include JGit security patch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3314?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3314: ------------------------------------- [~ljelinko], can you close this JIRA once you verify some basic functionality of egit in JBDS 8.0.2 B382? Thanks! > Include JGit security patch > --------------------------- > > Key: JBDS-3314 > URL: https://issues.jboss.org/browse/JBDS-3314 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 8.0.1.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 8.0.2.GA > > Attachments: jbds-git-update.png > > > A vulnerability was announced in most Git clients (including JGit). > JGit has provided a new version that fixes this vulnerability, and this has been included in a rebuild of Luna SR1. We should include it. > https://mmilinkov.wordpress.com/2015/01/12/eclipse-ships-luna-sr1a-git-se... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3314) Include JGit security patch

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3314?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3314: -------------------------------- Attachment: jbds-git-update.png With JBDS, the update is pretty straightforward. After I added the staging 8.0 repo to my JBDS 8.0.1 install and then clicked Check for updates, I was shown the 8.0.2 update including this jgit/egit update: !jbds-git-update.png! With JBoss Tools it's a bit tricky. First, the git security update is already included in the standard eclipse update site that everybody has set up by default, so chances are the user will have the update before we release JBoss Tools 4.2.2. Second, when I tried to verify this, I installed 4.2.1 from the stable url first, but it turns out that this already contains the new TP including the git security fix [1], so I couldn't really check if the update will work - when I installed JBT 4.2.1 on top of vanilla Eclipse Java EE, the git fix was already there. [1] http://download.jboss.org/jbosstools/updates/stable/luna/ points to http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ which already contains the just released TP. > Include JGit security patch > --------------------------- > > Key: JBDS-3314 > URL: https://issues.jboss.org/browse/JBDS-3314 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 8.0.1.GA > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 8.0.2.GA > > Attachments: jbds-git-update.png > > > A vulnerability was announced in most Git clients (including JGit). > JGit has provided a new version that fixes this vulnerability, and this has been included in a rebuild of Luna SR1. We should include it. > https://mmilinkov.wordpress.com/2015/01/12/eclipse-ships-luna-sr1a-git-se... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19041) Build failure on Jenkins

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19041: ------------------------------------- Summary: Build failure on Jenkins Key: JBIDE-19041 URL: https://issues.jboss.org/browse/JBIDE-19041 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Blocker Fix For: 4.3.0.Alpha1 See http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-webservice... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14783) Licence for JBoss AS Downloads looks like HTML source

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14783?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-14783. --------------------------------- I checked that the license is rendered as text now in JBDS 8.0 via Preferences Runtime Detection -> Download. I tried different older versions of JBoss AS. Closing. > Licence for JBoss AS Downloads looks like HTML source > ----------------------------------------------------- > > Key: JBIDE-14783 > URL: https://issues.jboss.org/browse/JBIDE-14783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: license-3.2.8.SP1.png > > > When JBoss AS 3.2.8.SP1 download is requested from new Runtime Dialog it shows license that looke like this: > !license-3.2.8.SP1.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015