July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19963: --------------------------------------- Should be updated to 0.10.0.201506172156/ after branch is created. > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19963) Switch Tern.java dependency version range to 0.10.0 release after code freeze

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19963?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19963: ---------------------------------- Summary: Switch Tern.java dependency version range to 0.10.0 release after code freeze (was: Switch Tern.java dependency version range to the only version after code freeze) > Switch Tern.java dependency version range to 0.10.0 release after code freeze > ----------------------------------------------------------------------------- > > Key: JBIDE-19963 > URL: https://issues.jboss.org/browse/JBIDE-19963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20263) Update tern-java and angularjs-eclipse to latest 0.10.0 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20263?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20263: ---------------------------------- Story Points: 1 > Update tern-java and angularjs-eclipse to latest 0.10.0 release > --------------------------------------------------------------- > > Key: JBIDE-20263 > URL: https://issues.jboss.org/browse/JBIDE-20263 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: discovery, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > > Mirrors are available: > http://download.jboss.org/jbosstools/updates/requirements/tern/0.10.0.201... > http://download.jboss.org/jbosstools/updates/requirements/angularjs/0.10.... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20263) Update tern-java and angularjs-eclipse to latest 0.10.0 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20263?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20263: ---------------------------------- Component/s: discovery > Update tern-java and angularjs-eclipse to latest 0.10.0 release > --------------------------------------------------------------- > > Key: JBIDE-20263 > URL: https://issues.jboss.org/browse/JBIDE-20263 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: discovery, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > > Mirrors are available: > http://download.jboss.org/jbosstools/updates/requirements/tern/0.10.0.201... > http://download.jboss.org/jbosstools/updates/requirements/angularjs/0.10.... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20263) Update tern-java and angularjs-eclipse to latest 0.10.0 release

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20263: ------------------------------------- Summary: Update tern-java and angularjs-eclipse to latest 0.10.0 release Key: JBIDE-20263 URL: https://issues.jboss.org/browse/JBIDE-20263 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.3.0.Beta2 Mirrors are available: http://download.jboss.org/jbosstools/updates/requirements/tern/0.10.0.201... http://download.jboss.org/jbosstools/updates/requirements/angularjs/0.10.... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19759: ------------------------------------------ merged and pushed to upstream/master > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. > This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20257) Cannot create any new project via OpenShift Projects dialog

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20257?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20257: --------------------------------------- This error says you do not have the permissions to perform the operation, not that you are unauthorized. You should be able to replicate the behavior from the CLI by making a project JSON and trying to create it like 'oc create -f <file>' {code} { "kind": "Project", "apiVersion": "v1", "metadata": { "name": "test", }, } {code} > Cannot create any new project via OpenShift Projects dialog > ----------------------------------------------------------- > > Key: JBIDE-20257 > URL: https://issues.jboss.org/browse/JBIDE-20257 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > In OpenShift Projects dialog opened via context menu of a v3 application, it is not possible to create a new project. There is a error that project is trying to be created in cluster scope. See full error description below: > {code} > Could not create project "project01dsa": User "demo" cannot create projects at the cluster scope > com.openshift.restclient.authorization.ResourceForbiddenException: User "demo" cannot create projects at the cluster scope > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:393) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:185) > at com.openshift.internal.restclient.DefaultClient.create(DefaultClient.java:169) > at org.jboss.tools.openshift.core.connection.Connection.createResource(Connection.java:316) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizardModel.createProject(NewProjectWizardModel.java:55) > at org.jboss.tools.openshift.internal.ui.wizard.project.NewProjectWizard$1.doRun(NewProjectWizard.java:46) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is happening also on locally running OpenShift v3 and also on staging v3 server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20047) As I user I want to be able to manually trigger builds

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20047?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20047: --------------------------------------- [~adietish] This pull allows you to manually trigger a build from a build config or clone a previous build. After talking to [~maxandersen], opened a new issue to provide additional logic to allow you to right click a connection or project and choose a build config which would follow the pattern we have for other features. > As I user I want to be able to manually trigger builds > ------------------------------------------------------ > > Key: JBIDE-20047 > URL: https://issues.jboss.org/browse/JBIDE-20047 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta2 > > > In STI a build is triggered by a change in the git repository. As a user I can thus triggered a build via a git push given that the git repo has the webhook installed. If I dont have the webhooks installed and I'm maybe not able to install them I'd like to be able to manually trigger the build. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20262) Manually trigger builds from the connection or project level

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20262: ------------------------------------- Summary: Manually trigger builds from the connection or project level Key: JBIDE-20262 URL: https://issues.jboss.org/browse/JBIDE-20262 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Jeff Cantrill Add selection dialog to allow you to choose a build config from which to start a build by right-clicking on a connection or project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19814 at 7/14/15 3:50 PM: ------------------------------------------------------------- PRs applied in master to make JBT and JBDS both use the same mojo for creating source zips. Also allows xulrunner to specify a buildinfo.json file instead of a plugin from which to search MANIFEST.MF for a SHA. https://github.com/jbosstools/jbosstools-maven-plugins/pull/48 https://github.com/jbosstools/jbosstools-build-sites/pull/198 https://github.com/jbdevstudio/jbdevstudio-product/pull/321 and https://github.com/jbdevstudio/jbdevstudio-product/pull/322 was (Author: nickboldt): PRs applied in master to make JBT and JBDS both use the same mojo for creating source zips. Also allows xulrunner to specify a buildinfo.json file instead of a plugin from which to search MANIFEST.MF for a SHA. https://github.com/jbosstools/jbosstools-maven-plugins/pull/48 https://github.com/jbosstools/jbosstools-build-sites/pull/198 https://github.com/jbdevstudio/jbdevstudio-product/pull/321 > sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19814 > URL: https://issues.jboss.org/browse/JBIDE-19814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2, 4.3.0.CR1 > > > If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources. > This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D > Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty: > {code} > git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015