May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19505: ---------------------------------------- Priority: Blocker (was: Major) > Angular Code Assist doesn't work for jboss-kitchensink-angularjs app > -------------------------------------------------------------------- > > Key: JBIDE-19505 > URL: https://issues.jboss.org/browse/JBIDE-19505 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > 1. Import jboss-kitchensink-angularjs from JBoss Central > 2. Open partials/home.html page > 3. Open Angular Explorer and lind modules > MemberService > MembersCtrl to controler > 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m > ERROR: Code Assist doesn't contain proposal for message variable -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19505: --------------------------------------------- according to Victors comment this affects all angularjs completion. so marking as blocker. > Angular Code Assist doesn't work for jboss-kitchensink-angularjs app > -------------------------------------------------------------------- > > Key: JBIDE-19505 > URL: https://issues.jboss.org/browse/JBIDE-19505 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.3.0.Alpha1 > Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > 1. Import jboss-kitchensink-angularjs from JBoss Central > 2. Open partials/home.html page > 3. Open Angular Explorer and lind modules > MemberService > MembersCtrl to controler > 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m > ERROR: Code Assist doesn't contain proposal for message variable -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ JBT pre-Beta1 core: http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/ JBT pre-Beta1 tests: http://download.jboss.org/jbosstools/mars/snapshots/updates/coretests/mas... Need links for Central too? http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... > Create and use Mars RC2 target-platform > --------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. > However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Paul Leacu updated JBIDE-19776: ------------------------------- Hey Nick - Okay - my error is this: [ERROR] Software being installed: org.jboss.tools.as.test.core 3.1.0.Alpha2-v20150417-0145-B13 [ERROR] Missing requirement: org.jboss.ide.eclipse.as.rse.ui 3.1.0.Alpha2-v20150417-0145-B13 requires 'bundle org.eclipse.tm.terminal 3.1.0' but it could not be found Which makes sense since I'm referencing the 4.50.0.Beta1-SNAPSHOT. I'm pulling in org.jboss.tools.as.test.core from: http://download.jboss.org/jbosstools/static/mars/development/updates/core... Where should I get coretests from?? Thkx, --paull ----- Original Message ----- > Create and use Mars RC2 target-platform > --------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. > However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ 3.1 was removed here [1] and build here [2] with results here [3]. [1] https://github.com/jbosstools/jbosstools-target-platforms/commit/da4aeb27... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... ref: [~pleacu] [~lhein] > Create and use Mars RC2 target-platform > --------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. > However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ Still to do (could be in a second JIRA if people prefer): The following job configs need to be changed to use this new deployment approach in Jenkins: {code} // NOTE: this check varies for each job if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then cd ${WORKSPACE}/sources/aggregate/${projectName}-site # or similar path for your project M2_HOME=/qa/tools/opt/apache-maven-3.2.5/ $M2_HOME/bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=$WORKSPACE/.repository ${MAVEN_FLAGS} else echo "Publish cancelled (nothing to do). Skip this check with skipRevisionCheckWhenPublishing=true" BUILD_DESCRIPTION="NOT PUBLISHED: UNCHANGED" fi{code} Jobs to fix (in _master and _4.3.mars): {code}devstudio.product jbosstools-browsersim-standalone jbosstools-discovery jbosstools-integration-stack-tests.aggregate jbosstools-integration-tests.aggregate jbosstools-locus.site RedDeer_master {code} > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ What you're asking is currently possible, and is being done today. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -> invokes the pom [1] to perform the deployment to devstudio.redhat.com by passing in different parameters to the rsync.sh script. You can also disable deploying to JBoss Nexus [2] at the same time and only push to an rsync location. Not sure if you can enable publishing to a DIFFERENT Nexus. Perhaps using an override in your settings.xml? [1] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... [2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19776) Create and use Mars RC2 target-platform

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-19776: ------------------------------------ I need the org.eclipse.tm.terminal 3.1 removal in order to build a complete JBTIS Mars TP. I believe its involved in this somewhere. Please announce in this Jira when a staging URL is available - Fuse Tooling and other components need it. ref [~lhein] > Create and use Mars RC2 target-platform > --------------------------------------- > > Key: JBIDE-19776 > URL: https://issues.jboss.org/browse/JBIDE-19776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt > > > Mars M7 was released and contains interesting changes. > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. > However, moving to RC1 or RC2 might be ever better as RC1 includes a fix for JBIDE-19773. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- The old and new are there because org.eclipse.tm.terminal/plugins/org.eclipse.tm.terminal.view.ui/plugin.xml contains the following xml: {code} <view allowMultiple="true" category="org.eclipse.tm.terminal.view.ui.views.category" class="org.eclipse.tm.terminal.view.ui.view.TerminalsView" icon="icons/eview16/terminal_view.gif" id="org.eclipse.tm.terminal.view.ui.TerminalsView" name="%TerminalsView.name"> </view>  <view allowMultiple="true" class="org.eclipse.tm.terminal.view.ui.view.OldTerminalsViewHandler" icon="icons/eview16/terminal_view.gif" id="org.eclipse.tcf.te.ui.terminals.TerminalsView" name="%TerminalsView.name.old"> </view> {code} ie, the single plugin declaring the new view has (for now) left the old view in as well. I would suspect they have plans to remove it before GA, and I can look into that for you I guess. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png, org.jboss.tools.as.management.itests.AS7IntegrationTestSuite.txt > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19335: ------------------------------------- [~dgolovin] Would you mind sharing your projected fix idea? Maybe I can implement it quickly for you ;) > org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19335 > URL: https://issues.jboss.org/browse/JBIDE-19335 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, runtime-detection > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Environment: Linux > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015