March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3285 at 3/25/15 9:17 AM: ------------------------------------------------------------- Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? What we want is to be able to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.) This will be a big deal for 9.0 - and a major change requiring extensive testing - and user docs. was (Author: ldimaggio): Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? What we want is to be able to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.) > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3285 at 3/25/15 9:16 AM: ------------------------------------------------------------- Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? What we want is to be able to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.) was (Author: ldimaggio): Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? Can we get a tool to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.) > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Len DiMaggio edited comment on JBDS-3285 at 3/25/15 9:13 AM: ------------------------------------------------------------- Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? Can we get a tool to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.) was (Author: ldimaggio): Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Git: Easy Import

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3285: ------------------------------------ Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse? > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work with remote server docs missing

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Mustafa Musaji updated TOOLSDOC-620: ------------------------------------ Summary: How to work with remote server docs missing (was: How to work remote server docs missing) > How to work with remote server docs missing > ------------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work remote server docs missing

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Mustafa Musaji commented on TOOLSDOC-620: ----------------------------------------- https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > How to work remote server docs missing > -------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work remote server docs missing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TOOLSDOC-620: ---------------------------------------------- do you have a link to the 7.x docs you refer to ? > How to work remote server docs missing > -------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19497: -------------------------------- Description: *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles *Project page/sources:* https://www.eclipse.org/jetty/ *Version:* 9.2.5.v20141112 *License and owner:* Eclipse.org *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ *JBoss mirror:* TODO *Include Sources:* Yes *Affected projects:* Livereload, Cordovasim, BrowserSim *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO: suggested diff on the .target files/p2diff {code} was: *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles *Project page/sources:* https://www.eclipse.org/jetty/ *Version:* 9.2.5.v20141112 *License and owner:* Eclipse.org *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ *JBoss mirror:* TODO *Include Sources:* Yes *Affected projects:* Livereload, Cordovasim *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO: suggested diff on the .target files/p2diff {code} > Use Jetty 9 in TP > ----------------- > > Key: JBIDE-19497 > URL: https://issues.jboss.org/browse/JBIDE-19497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Ilya Buziuk > > *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles > *Project page/sources:* https://www.eclipse.org/jetty/ > *Version:* 9.2.5.v20141112 > *License and owner:* Eclipse.org > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ > *JBoss mirror:* TODO > *Include Sources:* Yes > *Affected projects:* Livereload, Cordovasim, BrowserSim > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO: suggested diff on the .target files/p2diff > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19497: -------------------------------- Description: *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles *Project page/sources:* https://www.eclipse.org/jetty/ *Version:* 9.2.5.v20141112 *License and owner:* Eclipse.org *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ *JBoss mirror:* TODO *Include Sources:* Yes *Affected projects:* Livereload, Cordovasim *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO: suggested diff on the .target files/p2diff {code} was: *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles *Project page/sources:* https://www.eclipse.org/jetty/ *Version:* 9.2.5.v20141112 *License and owner:* Eclipse.org *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.9.v20150224 *JBoss mirror:* TODO *Include Sources:* Yes *Affected projects:* Livereload, Cordovasim *Include in JBDS:* Yes *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO: suggested diff on the .target files/p2diff {code} > Use Jetty 9 in TP > ----------------- > > Key: JBIDE-19497 > URL: https://issues.jboss.org/browse/JBIDE-19497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Ilya Buziuk > > *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles > *Project page/sources:* https://www.eclipse.org/jetty/ > *Version:* 9.2.5.v20141112 > *License and owner:* Eclipse.org > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ > *JBoss mirror:* TODO > *Include Sources:* Yes > *Affected projects:* Livereload, Cordovasim > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO: suggested diff on the .target files/p2diff > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work remote server docs missing

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Mustafa Musaji updated TOOLSDOC-620: ------------------------------------ Project: Documentation for JBoss Tools and Developer Studio (was: Developer Studio (JBoss Developer Studio)) Key: TOOLSDOC-620 (was: JBDS-3388) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: 4.1.2 (was: 8.0.2.GA) Component/s: General documentation issues (was: documentation) Docs QE Status: (was: NEW) > How to work remote server docs missing > -------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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