May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-3434: -------------------------------------- Assignee: Andre Dietisheim > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Charles Moulliard > Assignee: Andre Dietisheim > Fix For: 9.0.x > > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-3434: ---------------------------------------- Afaics our primary goal for now is to use STI whereas in kubernetes deployment we'd deploy docker images. In this sense I think that this is something we'll eventually adress in later sprints. [~jcantrill] dare to comment? > Kubernetes editor & wizard > -------------------------- > > Key: JBDS-3434 > URL: https://issues.jboss.org/browse/JBDS-3434 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Reporter: Charles Moulliard > > To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose : > - a kubernetes editor within JBDS to update the YAML or JSON file and > - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3421) Update site lists its files in upper left corner

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3421?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3421. ----------------------------- Closing since it's fixed > Update site lists its files in upper left corner > ------------------------------------------------ > > Key: JBDS-3421 > URL: https://issues.jboss.org/browse/JBDS-3421 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Alpha2 > Reporter: Jan Richter > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > Attachments: updatesite.png > > > Opening the update site here: > https://devstudio.redhat.com/9.0/staging/updates/ > In the attached screenshot is what showed up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19757: ---------------------------------------- The symlinks do not allow to correctly benefit from references to /static/ directory (because they are resolved on server side), whereas composites, which are resolved by clients, correctly hit the static/ urls and allow to benefit from better download speed on this locations. Since we need to use composite for /static/ let's just be consistent and use them everywhere. > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19806) Red Deer archetype project is not imported correctly (not detected as Maven)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19806?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19806: ---------------------------------------- if "archetype" is detected as a Maven project, then it wouldn't recurse in source folder. Need to find out why the Maven configurator is omitted on "archetype" folder. > Red Deer archetype project is not imported correctly (not detected as Maven) > ---------------------------------------------------------------------------- > > Key: JBIDE-19806 > URL: https://issues.jboss.org/browse/JBIDE-19806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Lucia Jelinkova > Attachments: archetype-project.png > > > When I try to import from Red Deer project archetype, I end up with 2 projects instead of one. > The first one, archetype, is the correct one, however, in the report diaog there is not written that it is a maven project, even though it actually has maven nature after the import. > The second one, archetype-resources is actually located in the source folder of the previous one, so I think it should be skipped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19806) Red Deer archetype project is not imported correctly (not detected as Maven)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19806?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19806: ----------------------------------- Summary: Red Deer archetype project is not imported correctly (not detected as Maven) (was: Red Deer archetype project is not imported correctly) > Red Deer archetype project is not imported correctly (not detected as Maven) > ---------------------------------------------------------------------------- > > Key: JBIDE-19806 > URL: https://issues.jboss.org/browse/JBIDE-19806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Lucia Jelinkova > Attachments: archetype-project.png > > > When I try to import from Red Deer project archetype, I end up with 2 projects instead of one. > The first one, archetype, is the correct one, however, in the report diaog there is not written that it is a maven project, even though it actually has maven nature after the import. > The second one, archetype-resources is actually located in the source folder of the previous one, so I think it should be skipped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19769) Check if the project is already present in the workspace

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19769?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19769. ------------------------------------ Resolution: Cannot Reproduce Bug > Check if the project is already present in the workspace > -------------------------------------------------------- > > Key: JBIDE-19769 > URL: https://issues.jboss.org/browse/JBIDE-19769 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: existing-projects.png > > > At the moment the project is attempted to import even if it is already in the workspace. It is OK that it is detected but it should be marked as already imported in the wizard table and it should not be imported again. > At the moment, this is logged into Error log: > {code} > org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /home/ljelinko/workspaces/workspace/RemoteSystemsTempFiles > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:294) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:222) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.searchAndImportChildrenProjectsRecursively(OpenFolderCommand.java:173) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:230) > at org.eclipse.ui.internal.wizards.datatransfer.NestedProjectsWizardPage$10.run(NestedProjectsWizardPage.java:258) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/RemoteSystemsTempFiles' already exists. > at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:313) > at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:300) > at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:51) > at org.eclipse.core.internal.resources.Project.create(Project.java:268) > at org.eclipse.core.internal.resources.Project.create(Project.java:252) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.createOrImportProject(OpenFolderCommand.java:331) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:285) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-640: ------------------------------------ Reiterated request for review on PR, waiting for Xavier's response about an ETA for review. > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-639) JBDS Tech Knowledge: Test all docs to better understand product and use cases by EOM (May)

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-639?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-639: ------------------------------------ Belated comment: nearly done with this, working on OS documentation today and then the 8.1 docs are complete. > JBDS Tech Knowledge: Test all docs to better understand product and use cases by EOM (May) > ------------------------------------------------------------------------------------------ > > Key: TOOLSDOC-639 > URL: https://issues.jboss.org/browse/TOOLSDOC-639 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-638: ------------------------------- Sprint: 11-May -> 24-May 2015-JBDS/JBT (was: 2015/S9 (27-Apr > 10-May)) > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > > We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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