[JBoss JIRA] (JBIDE-19512) version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19512:
----------------------------------
Summary: version of RSE/TM plugins in JBDS decreased between JBDS 8.1 and 9.0.Alpha2
Key: JBIDE-19512
URL: https://issues.jboss.org/browse/JBIDE-19512
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, qa, target-platform, updatesite
Affects Versions: 4.3.0.Alpha1
Reporter: Nick Boldt
These plugins versions dropped from these versions in JBDS 8.1.0...
{code}
org.eclipse.rse.dstore_3.7.0.201502160819
org.eclipse.tm.terminal_3.7.0.201502160819
org.eclipse.rse_3.7.0.201502160819
org.eclipse.rse.ssh_3.7.0.201502160819
org.eclipse.rse.telnet_3.7.0.201502160819
org.eclipse.rse.ftp_3.7.0.201502160819
org.eclipse.rse.terminals_3.7.0.201502160819
org.eclipse.rse.local_3.7.0.201502160819
org.eclipse.rse.core_3.7.0.201502160819
org.eclipse.rse.terminals.ui_1.2.200.201412161015
org.eclipse.tm.terminal_3.3.0.201501281007 {code}
to older versions in JBDS 9.0.
This could be an upstream problem (plugins not correctly upversioned at Eclipse) or it could be something that's been fixed in the latest Mars M6. Something we definitely need to investigate and report upstream if not fixed there already.
See detailed reports here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3387.
----------------------------
Assignee: Nick Boldt
Resolution: Done
com.jcraft.jsch is now ignored from the reports, so closing. Will open separate issues to examine the rse/tm version decreases and multiple versions of jetty and servlet.
> JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51
> ---------------------------------------------------------------------------
>
> Key: JBDS-3387
> URL: https://issues.jboss.org/browse/JBDS-3387
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-dependencies, installer, updatesite
> Affects Versions: 8.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.1.0.GA, 9.0.0.Alpha2
>
>
> This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem?
> If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions.
> cc: [~jpeterka] [~akazakov]
> Who depends on these?
> {code}com.jcraft.jsch_0.1.51.v201410302000.jar
> com.jcraft.jsch_0.1.50.v201403120620.jar{code}
> Note that the update site only contains ONE of these IUs:
> {code}
> com.jcraft.jsch_0.1.50.v201403120620.jar{code}
> But when you install from the installer, you get both on disk:
> {code}
> find . -name com.jcraft.jsch\*
> ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar
> ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3387:
----------------------------------
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is blue!
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... is back to yellow (version decreases and more multiple version issues)
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio.versionwatch_master/1899/artifact/sources/vwatch/report_detailed_all.html}
VW product report: jbds-9.0.0.Alpha2
Version decreased issue
org.eclipse.rse.dstore_3.7.0.201502160819
org.eclipse.tm.terminal_3.7.0.201502160819
org.eclipse.rse_3.7.0.201502160819
org.eclipse.rse.ssh_3.7.0.201502160819
org.eclipse.rse.telnet_3.7.0.201502160819
org.eclipse.rse.ftp_3.7.0.201502160819
org.eclipse.rse.terminals_3.7.0.201502160819
org.eclipse.rse.local_3.7.0.201502160819
org.eclipse.rse.core_3.7.0.201502160819
org.eclipse.rse.terminals.ui_1.2.200.201412161015
org.eclipse.tm.terminal_3.3.0.201501281007
Multiple Version issue
org.eclipse.jetty.http_8.1.14.v20131031
org.eclipse.jetty.servlet_8.1.14.v20131031
org.eclipse.jetty.server_8.1.14.v20131031
org.eclipse.jetty.security_8.1.14.v20131031
org.eclipse.jetty.continuation_8.1.14.v20131031
javax.servlet_3.1.0.v201410161800
org.eclipse.jetty.util_8.1.14.v20131031
org.eclipse.jetty.io_8.1.14.v20131031
{code}
> JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51
> ---------------------------------------------------------------------------
>
> Key: JBDS-3387
> URL: https://issues.jboss.org/browse/JBDS-3387
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-dependencies, installer, updatesite
> Affects Versions: 8.1.0.CR1
> Reporter: Nick Boldt
> Fix For: 8.1.0.GA, 9.0.0.Alpha2
>
>
> This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem?
> If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions.
> cc: [~jpeterka] [~akazakov]
> Who depends on these?
> {code}com.jcraft.jsch_0.1.51.v201410302000.jar
> com.jcraft.jsch_0.1.50.v201403120620.jar{code}
> Note that the update site only contains ONE of these IUs:
> {code}
> com.jcraft.jsch_0.1.50.v201403120620.jar{code}
> But when you install from the installer, you get both on disk:
> {code}
> find . -name com.jcraft.jsch\*
> ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar
> ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19509) JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19509?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-19509:
----------------------------------
Assignee: Nick Boldt (was: Denis Golovin)
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
Turns out the problem was this:
{code}
00:00:12.866 [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Alpha2 (2/3) ]
00:00:12.867 -jar "/home/hudson/static_build_env/jbds/versionwatch/installations/jbds-9.0.0.Alpha2/studio/p2/director/plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar" -roaming -vm "/qa/tools/opt/x86_64/jdk1.8.0_40/jre" -r 'jar:file:///qa/services/http/binaries/RHDS/builds/staging/devstudio.product_master/installer/jboss-devstudio-9.0.0.Alpha2-v20150325-1051-B2894-installer-standalone.jar!/' -d "/home/hudson/static_build_env/jbds/versionwatch/installations/jbds-9.0.0.Alpha2/studio" -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group -profileProperties org.eclipse.update.install.features=true
00:00:15.970 Installer
00:00:15.970
00:00:16.475 Installing com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150325-1051-B2894.
00:00:16.475
00:00:16.475 Installing org.testng.eclipse.feature.group 6.8.6.20130914_0724.
00:00:16.475
00:00:17.722 Cannot complete the install because one or more required items could not be found.
00:00:17.722
00:00:17.722 Software being installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150325-1051-B2894 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150325-1051-B2894)
00:00:17.722
00:00:17.723 Missing requirement: JBoss Central 2.0.0.Alpha2-v20150313-1539-B660 (org.jboss.tools.central 2.0.0.Alpha2-v20150313-1539-B660) requires 'bundle org.jboss.tools.foundation.help.ui 1.2.0' but it could not be found{code}
Thanks to Denis for the suggestion to enable tracing!
https://github.com/jbdevstudio/jbdevstudio-qa/commits/master [added support for -DTRACE=true ]
https://github.com/jbdevstudio/jbdevstudio-product/commit/dd4cb0752b78ce9... [fixed missing IU]
> JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19509
> URL: https://issues.jboss.org/browse/JBIDE-19509
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha2
>
>
> JBDS headless install no longer works in Jenkins, so versionwatch is unable to diff 9.0.0.Alpha2 master builds w/ previous Alpha1 and 8.1.x builds.
> I've repeated exactly what the versionwatch script does locally and it's fine w/ JDK 7 and 8, so it's not a config problem.
> But in Jenkins, with VNC enabled (and when not) the headless install process repeatedly stalls out at step 2:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio.versionwatch_master/1892/console}
> [ Starting automated installation ]
> [ Starting to unpack ]
> [ Processing package: P2 Director Application (1/3) ]
> [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Alpha2 (2/3) ]
> [ Unpacking finished ] ...
> {code}
> But in the 8.1.luna branch, the job is fine:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatch_8.0.luna/363/console}
> +++ /qa/tools/opt/jdk1.6.0_last/bin/java -jar /qa/services/http/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/jboss-devstudio-8.1.0.GA-v20150324-2058-B454-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-8.1.0.GA.install.xml
> [ Starting automated installation ]
> [ Starting to unpack ]
> [ Processing package: P2 Director Application (1/3) ]
> [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA (2/3) ]
> [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA Metadata Generation (3/3) ]
> [ Unpacking finished ]
> [ Creating shortcuts done. ]
> [ Add shortcuts to uninstaller done. ]
> [ Writing the uninstaller data ... ]
> [ Automated installation done ]{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19511) RuntimeException in error log when choosing decorated interface by double click
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-19511:
----------------------------------------
Summary: RuntimeException in error log when choosing decorated interface by double click
Key: JBIDE-19511
URL: https://issues.jboss.org/browse/JBIDE-19511
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi, upstream
Affects Versions: 4.3.0.Alpha1
Reporter: Rastislav Wagner
Priority: Minor
{code}
java.lang.RuntimeException
at org.eclipse.jface.viewers.ColumnViewer.checkBusy(ColumnViewer.java:760)
at org.eclipse.jface.viewers.AbstractTableViewer.replace(AbstractTableViewer.java:1016)
at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ContentProvider.updateElement(FilteredItemsSelectionDialog.java:2800)
at org.eclipse.jface.viewers.AbstractTableViewer$VirtualManager$1.handleEvent(AbstractTableViewer.java:83)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1437)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1422)
at org.eclipse.swt.widgets.Table.checkData(Table.java:284)
at org.eclipse.swt.widgets.Table.cellDataProc(Table.java:223)
at org.eclipse.swt.widgets.Display.cellDataProc(Display.java:761)
at org.eclipse.swt.internal.gtk.OS._gtk_list_store_set(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_list_store_set(OS.java:9042)
at org.eclipse.swt.widgets.TableItem.setText(TableItem.java:1164)
at org.eclipse.jface.viewers.TableViewerRow.setText(TableViewerRow.java:114)
at org.eclipse.jface.viewers.ViewerCell.setText(ViewerCell.java:159)
at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ItemsListLabelProvider.update(FilteredItemsSelectionDialog.java:1674)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:154)
at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:385)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:473)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.refreshItem(StructuredViewer.java:1573)
at org.eclipse.jface.viewers.AbstractTableViewer.replace(AbstractTableViewer.java:1019)
at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$ContentProvider.updateElement(FilteredItemsSelectionDialog.java:2800)
at org.eclipse.jface.viewers.AbstractTableViewer.getVirtualSelection(AbstractTableViewer.java:489)
at org.eclipse.jface.viewers.AbstractTableViewer.getSelectionFromWidget(AbstractTableViewer.java:460)
at org.eclipse.jface.viewers.StructuredViewer.getSelection(StructuredViewer.java:1040)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1732)
at org.eclipse.jface.viewers.TableViewer.setSelection(TableViewer.java:162)
at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:388)
at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog.refresh(FilteredItemsSelectionDialog.java:961)
at org.eclipse.ui.dialogs.FilteredItemsSelectionDialog$RefreshJob.runInUIThread(FilteredItemsSelectionDialog.java:1391)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.jdt.internal.ui.dialogs.FilteredTypesSelectionDialog.open(FilteredTypesSelectionDialog.java:512)
at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.chooseSuperInterfaces(NewTypeWizardPage.java:2046)
at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.typePageCustomButtonPressed(NewTypeWizardPage.java:1093)
at org.eclipse.jdt.ui.wizards.NewTypeWizardPage.access$1(NewTypeWizardPage.java:1091)
at org.eclipse.jdt.ui.wizards.NewTypeWizardPage$TypeFieldsAdapter.customButtonPressed(NewTypeWizardPage.java:1037)
at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.buttonPressed(ListDialogField.java:209)
at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.doButtonSelected(ListDialogField.java:478)
at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField.access$0(ListDialogField.java:474)
at org.eclipse.jdt.internal.ui.wizards.dialogfields.ListDialogField$2.widgetSelected(ListDialogField.java:440)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4480)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1413)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3818)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3285:
-------------------------------------------
I've renamed the title to make it clear this is not specific to Git and that the issue is about *non-eclipse* projects since if the projects are eclipse based this would "just work"
> Easy Import of non-eclipse projects
> -----------------------------------
>
> 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)
10 years, 11 months
[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3285:
--------------------------------------
Summary: Easy Import of non-eclipse projects (was: Git: Easy Import)
> Easy Import of non-eclipse projects
> -----------------------------------
>
> 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)
10 years, 11 months
[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:24 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.
Testing approach - Create every type of project supported in Central, delete the eclipse metadata, then import and verify that the projects can be reconstructed.
JIRA title is misleading - this is not limited to git projects - svn, cvs should also be supported after 9.0
For JBDS 9.0 there will be 2 git import wizards - one for the default eclipse git import and one for easy import - when importing a git project, user will be given the option of the generic git import (this may include user manual steps) or the easy import.
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.)
This will be a big deal for 9.0 - and a major change requiring extensive testing - and user docs.
Testing approach - Create every type of project supported in Central, delete the eclipse metadata, then import and verify that the projects can be reconstructed.
> 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)
10 years, 11 months
[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:20 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.
Testing approach - Create every type of project supported in Central, delete the eclipse metadata, then import and verify that the projects can be reconstructed.
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.)
This will be a big deal for 9.0 - and a major change requiring extensive testing - and user docs.
> 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)
10 years, 11 months
[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)
10 years, 11 months