February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19263) Add sslcertcallback for v2 since its null

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19263?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19263. ------------------------------------ > Add sslcertcallback for v2 since its null > ----------------------------------------- > > Key: JBIDE-19263 > URL: https://issues.jboss.org/browse/JBIDE-19263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18742) Use p2diff to determine whether to publish new aggregate

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18742?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18742: ------------------------------------ Please note that the above code fails if there's no pre-existing update site in http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ Needs a better bootstrap check -- eg., if site can't be hit with wget (returns 404) then set publish=true and skip trying to p2diff. Also needs to be rolled out to the rest of the 4.3.mars and master jobs. > Use p2diff to determine whether to publish new aggregate > -------------------------------------------------------- > > Key: JBIDE-18742 > URL: https://issues.jboss.org/browse/JBIDE-18742 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > Instead of the composite-install test to decide whether we aggregate or not, it would be simpler to build aggregation in any case and then use p2diff (or other smart mechanism) to decide whether we want to publish the new composite or not. > It's more or less just a matter of scripting > {code:none} > p2diff file:${WORKSPACE}/results/${JOB_NAME}/all/repo/ http://download.jboss.org/jbosstools/builds/staging/${JOB_NAME}/all/repo/ | grep -e ^\< -e ^\> > p2diff_snapshot > if [[ -s p2diff_snapshot ]]; then > ./publish.sh > fi > {code} > Another benefit is that it allows us to get rid of the composite (1 less couple of files to maintain) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19263) Add sslcertcallback for v2 since its null

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19263: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 > Add sslcertcallback for v2 since its null > ----------------------------------------- > > Key: JBIDE-19263 > URL: https://issues.jboss.org/browse/JBIDE-19263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-593) Reference to Developer Studio "dependencies" may cause some confusion

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-593: ------------------------------------- Summary: Reference to Developer Studio "dependencies" may cause some confusion Key: TOOLSDOC-593 URL: https://issues.jboss.org/browse/TOOLSDOC-593 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: Integration Stack Guide Affects Versions: 4.2.0.Final Environment: Build Name: 23023, Integration Stack Guide-8.0 Build Date: 13-02-2015 00:21:18 Topic ID: 42756-742863 [Latest] Reporter: Len DiMaggio Assignee: Michelle Murray Priority: Blocker Title: Install JBoss Developer Studio Integration Stack in Eclipse when Offline Describe the issue: The reference to Developer Studio "dependencies" may cause some confusion for readers. Can we simply refer to "Developer Studio?" Thx! ===================================== 4. Install JBoss Developer Studio Integration Stack in Eclipse when Offline permlink Two .zip files are provided for installing JBoss Developer Studio Integration Stack in Eclipse in offline mode, one containing JBoss Developer Studio Integration Stack and one containing required JBoss Developer Studio dependencies. Both archives are available from the Red Hat Customer Portal. The JBoss Developer Studio .zip file is also available from https://devstudio.jboss.com/updates/8.0/and the JBoss Developer Studio Integration Stack .zip file also from https://devstudio.jboss.com/updates/8.0/integration-stack. ===================================== Suggestions for improvement: Additional information: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19263) Add sslcertcallback for v2 since its null

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19263: ------------------------------------- Summary: Add sslcertcallback for v2 since its null Key: JBIDE-19263 URL: https://issues.jboss.org/browse/JBIDE-19263 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19261) User is not prompted for password when connecting to OpenShift v2

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19261?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19261: --------------------------------------- [~adietish] fix password prompt issue and resolve deferred loading with a lazy loader > User is not prompted for password when connecting to OpenShift v2 > ----------------------------------------------------------------- > > Key: JBIDE-19261 > URL: https://issues.jboss.org/browse/JBIDE-19261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19237) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19237?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19237: ------------------------------------ Building... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.... >=4 > For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt] > --------------------------------------------------- > > Key: JBIDE-19237 > URL: https://issues.jboss.org/browse/JBIDE-19237 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: task > Fix For: 4.3.0.Alpha1 > > > For JBIDE 4.3.0.Alpha1 [Birt]: Please perform the following tasks: > 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100. > *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Alpha1x > git push origin jbosstools-4.3.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3345: ------------------------------------------- Do you have the full log from the server ? not from eclipse. ? The logs you show still shows Java 8 jars being present in your server. Can you provide me a link to the exact server you are running with ? Also can you (when the server is launched) go to Debug perspective, right click the node in the process view and click properties to get the exact used command line arguments for your launch ? > Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8 > ----------------------------------------------------------------- > > Key: JBDS-3345 > URL: https://issues.jboss.org/browse/JBDS-3345 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: runtime > Affects Versions: 8.0.2.GA > Environment: Fedora 21 x86_64 > JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71 > Reporter: Andrej Podhradsky > Priority: Critical > Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, runtime_jre.png > > > FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file. > Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually. > Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19112) Create Luna SR2 target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19112?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-19112 at 2/13/15 9:51 AM: ----------------------------------------------------------------- Added pull request to use Luna SR2 RC3 bundles: https://github.com/jbosstools/jbosstools-target-platforms/pull/130 p2diff report no change (when ignoring version). Most remarkable change is the TM moved to 3.7.0 (was 3.6.0 in SR1) Please try it locally with {code} $ cd jbosstools-target-platforms $ git fetch jbosstools pull/130/head $ cd jbosstools/multiple $ mvn install $ cd jbosstools-component-to-test $ mvn clean verify -Pmutliple.target -Dtpc.version=4.42.0.Beta1-SNAPSHOT {code} was (Author: mickael_istria): Added pull request to use Luna SR2 RC3 bundles: https://github.com/jbosstools/jbosstools-target-platforms/pull/130 p2diff report no change (when ignoring version). Most remarkable change is the TM moved to 3.7.0 (was 3.6.0 in SR1) Please try it locally with {code} $ cd jbosstools-target-platforms $ git fetch jbosstools pull/130/head $ cd jbosstools/multiple $ mvn install $ cd jbosstools-component-to-test $ mvn clean verify -Pmutliple.target -Dtpc.version=4.42.0.Beta1-SNAPSHOT > Create Luna SR2 target platform > -------------------------------- > > Key: JBIDE-19112 > URL: https://issues.jboss.org/browse/JBIDE-19112 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.3.Beta1 > > > Need a target platform from 4.42.x branch based on Luna SR2. > Schedule of RC1 - RC4 milestones is here (GA bits available as of 02/20): > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19112) Create Luna SR2 target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19112?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19112: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/120, https://github.com/jbosstools/jbosstools-target-platforms/pull/130 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/120) Added pull request to use Luna SR2 RC3 bundles: https://github.com/jbosstools/jbosstools-target-platforms/pull/130 p2diff report no change (when ignoring version). Most remarkable change is the TM moved to 3.7.0 (was 3.6.0 in SR1) Please try it locally with {code} $ cd jbosstools-target-platforms $ git fetch jbosstools pull/130/head $ cd jbosstools/multiple $ mvn install $ cd jbosstools-component-to-test $ mvn clean verify -Pmutliple.target -Dtpc.version=4.42.0.Beta1-SNAPSHOT > Create Luna SR2 target platform > -------------------------------- > > Key: JBIDE-19112 > URL: https://issues.jboss.org/browse/JBIDE-19112 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.3.Beta1 > > > Need a target platform from 4.42.x branch based on Luna SR2. > Schedule of RC1 - RC4 milestones is here (GA bits available as of 02/20): > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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