[JBoss JIRA] (JBIDE-23906) NPE when importing empty Git repo from Github using smartimport
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23906?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23906:
----------------------------------
Assignee: Jeff MAURY
> NPE when importing empty Git repo from Github using smartimport
> ---------------------------------------------------------------
>
> Key: JBIDE-23906
> URL: https://issues.jboss.org/browse/JBIDE-23906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: import, jax-rs
> Fix For: 4.4.4.AM2
>
> Attachments: error dialog.png
>
>
> ASSERT: create an empty Git repo on Github
> EXEC: import as project (Import -> Other -> Git -> Projects from Git (with smart import) and fill Git repo URL
> ASSERT: project is imported
> ASSERT: Error dialog is displayed with NPE see !error dialog.png|thumbnail!
> EXPECTED: no error should occurs
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23906) NPE when importing empty Git repo from Github using smartimport
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23906?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23906:
-------------------------------
Sprint: devex #129 March 2017
> NPE when importing empty Git repo from Github using smartimport
> ---------------------------------------------------------------
>
> Key: JBIDE-23906
> URL: https://issues.jboss.org/browse/JBIDE-23906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: import, jax-rs
> Fix For: 4.4.4.AM2
>
> Attachments: error dialog.png
>
>
> ASSERT: create an empty Git repo on Github
> EXEC: import as project (Import -> Other -> Git -> Projects from Git (with smart import) and fill Git repo URL
> ASSERT: project is imported
> ASSERT: Error dialog is displayed with NPE see !error dialog.png|thumbnail!
> EXPECTED: no error should occurs
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24021) Properties file are not reloaded
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24021?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24021:
----------------------------------
Assignee: Jeff MAURY
> Properties file are not reloaded
> --------------------------------
>
> Key: JBIDE-24021
> URL: https://issues.jboss.org/browse/JBIDE-24021
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.4.3.Final
> Reporter: Robert Paasche
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM2
>
>
> After updating an open properties file with "git pull" the file isn't reloaded by the editor.
> This makes the editor useless in multi-developer environments.
> BTW. the egit plugin shows there are something changed (new line for example) on the left border.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24021) Properties file are not reloaded
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24021?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24021:
-------------------------------
Sprint: devex #129 March 2017
> Properties file are not reloaded
> --------------------------------
>
> Key: JBIDE-24021
> URL: https://issues.jboss.org/browse/JBIDE-24021
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.4.3.Final
> Reporter: Robert Paasche
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM2
>
>
> After updating an open properties file with "git pull" the file isn't reloaded by the editor.
> This makes the editor useless in multi-developer environments.
> BTW. the egit plugin shows there are something changed (new line for example) on the left border.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23708:
----------------------------------
Assignee: Jeff MAURY
> Pod Log: unable to get build log if build failed with error
> -----------------------------------------------------------
>
> Key: JBIDE-23708
> URL: https://issues.jboss.org/browse/JBIDE-23708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: logs, properties
> Fix For: 4.4.4.AM2
>
> Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry)
> # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu
> Result:
> You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed:
> !cannot-get-logs-for-erroring-build.png!
> The webconsole allows you to inspect those logs:
> !webconsole-logs-for-erroring-build.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23708:
-------------------------------
Sprint: devex #129 March 2017
> Pod Log: unable to get build log if build failed with error
> -----------------------------------------------------------
>
> Key: JBIDE-23708
> URL: https://issues.jboss.org/browse/JBIDE-23708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Labels: logs, properties
> Fix For: 4.4.4.AM2
>
> Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry)
> # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu
> Result:
> You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed:
> !cannot-get-logs-for-erroring-build.png!
> The webconsole allows you to inspect those logs:
> !webconsole-logs-for-erroring-build.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19391:
-------------------------------
Sprint: devex #129 March 2017
> Properties File editor does not work properly
> ---------------------------------------------
>
> Key: JBIDE-19391
> URL: https://issues.jboss.org/browse/JBIDE-19391
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Reporter: Ali Hopyar
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM2
>
> Attachments: messages_en.properties
>
>
> On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-19391:
----------------------------------
Assignee: Jeff MAURY (was: Viacheslav Kabanovich)
> Properties File editor does not work properly
> ---------------------------------------------
>
> Key: JBIDE-19391
> URL: https://issues.jboss.org/browse/JBIDE-19391
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Reporter: Ali Hopyar
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM2
>
> Attachments: messages_en.properties
>
>
> On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years