[JBoss JIRA] (JBIDE-13161) Server adapter: Port forwarding should not display error message after removing connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13161?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13161:
-------------------------------------
Steps to Reproduce:
# ASSERT: have a server adapter who's application does not exist any more
# EXEC: pick *OpenShift->Port forwarding* from it's context menu
Resullt:
!error-getting-application.png!
> Server adapter: Port forwarding should not display error message after removing connection
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-13161
> URL: https://issues.jboss.org/browse/JBIDE-13161
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: error-getting-application.png
>
>
> The error message dialog should:
> * not appear to achieve consistent behaviour as in JBIDE-13146 (it's the same situation) - as a temporary solution, until it gets fixed properly as stated in JBIDE-13145
> *or*
> * add to the error message also that the associated connection cannot be found.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16170?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-16170:
-----------------------------------
Assignee: Fred Bricon (was: Max Rydahl Andersen)
> Latest HTML5 archetype doesn't show unavailable maven repo in wizard
> --------------------------------------------------------------------
>
> Key: JBIDE-16170
> URL: https://issues.jboss.org/browse/JBIDE-16170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.1.Final
>
>
> The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore)
> Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes.
> So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (TOOLSDOC-390) Update book versions for 7.1.0/4.1.1
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-390?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-390:
------------------------------------------
Made PRs based on 4.1.1.x branches thinking they could be applied to 4.1.1.x and 4.1.x. Alexy found conflicts with applying to 4.1.x (no surprising since I built off 4.1.1.x! lesson learnt). Lead to this discussion:
{quote}
(07:41:01 PM) maxandersen: akazakov: whats the question ? :)
(07:41:57 PM) akazakov: maxandersen, https://github.com/jbosstools/jbosstools-javaee/pull/177
(07:41:57 PM) jbossbot: git pull req [jbosstools-javaee] (open) michellemurray TOOLSDOC-390: Doc versions updated for 4.1 and 7.1 https://github.com/jbosstools/jbosstools-javaee/pull/177
(07:41:58 PM) jbossbot: jira [TOOLSDOC-390] Update book versions for 7.1.0/4.1.1 [Open (Unresolved) Task, Major, Michelle Murray] https://issues.jboss.org/browse/TOOLSDOC-390
(07:42:06 PM) akazakov: is it ok to push to 4.1.1.x?
(07:42:25 PM) maxandersen: akazakov: doc changes into 4.1.1.x ? hmm…. murraym remind me if did we do that in past ? I *thought* it was just built from master…..in any case, probably simpler if go into 4.1.x instead imo.
(07:44:03 PM) murraym: 4.1.1.x will have wrong version numbers in docs
(07:44:50 PM) murraym: maxandersen: I don't think we did anything before, hence why the doc version numbers are so outdated
(07:45:16 PM) murraym: master will be for 4.2 and 8.0 - right?
(07:45:51 PM) murraym: i was making PRs to update version numbers in docs in 4.1.1.x and 4.1.x branches
(07:48:18 PM) jbossbot: git [jbosstools-base] push master 4e09f7e.. Fred Bricon JBIDE-16176 : use proper stacks archetype id during lookup...
(07:48:18 PM) jbossbot: jira [JBIDE-16176] Wrong archetype id used to lookup stacks archetypes [Resolved (Done) Bug, Critical, Rob Stryker] https://issues.jboss.org/browse/JBIDE-16176
(07:48:18 PM) jbossbot: git [jbosstools-base] push master URL: http://github.com/jbosstools/jbosstools-base/commit/4e09f7e85
(07:50:13 PM) murraym: maxandersen: if you want me to make changes in 4.1.x only then say so, I think I can cherry-pick the commits i have onto 4.1.x branch and make new PRs for 4.1.x branches
(07:50:29 PM) murraym: would like to get this done tonight
(07:55:33 PM) maxandersen: murraym: just do it for 4.1.x. 4.1.1 train has left the building for noncritical fixes ;)
(07:56:06 PM) murraym: maxandersen: ok, will do - will go close my existing PRs for 4.1.1.x so please disregard
{quote}
So original PRs requesting merging with 4.1.1.x and 4.1.x closed with being applied by me. Made the following new PRs just for 4.1.x branch:
https://github.com/jbosstools/jbosstools-birt/pull/16
https://github.com/jbosstools/jbosstools-bpel/pull/20
https://github.com/jbosstools/jbosstools-central/pull/192
https://github.com/jbosstools/jbosstools-esb/pull/46
https://github.com/jbosstools/jbosstools-hibernate/pull/34
https://github.com/jbosstools/jbosstools-javaee/pull/178
https://github.com/jbosstools/jbosstools-portlet/pull/23
https://github.com/jbosstools/jbosstools-server/pull/182
https://github.com/jbosstools/jbosstools-webservices/pull/102
These set the JBDS doc version to 7.1 and JBT doc version to 4.1.x. Going with 4.1.x rather than 4.1.1 so won't need to be updated if there is a 4.1.blah. This brings the docs numbering in line with JBDS - so new set of docs for each minor version only (x.y) and not maintenance (x.y.z).
Need to update Jenkins job to reflect this.
> Update book versions for 7.1.0/4.1.1
> ------------------------------------
>
> Key: TOOLSDOC-390
> URL: https://issues.jboss.org/browse/TOOLSDOC-390
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: General documentation issues
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
>
> Update Book_Info.xml & Revision History with 7.1.
> Update pom.xml with 4.2.0
> Also incorporate TOOLSDOC-313 (moving doc version out of master.xml and into pom.xml).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16170) Latest HTML5 archetype doesn't show unavailable maven repo in wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16170?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16170:
---------------------------------------------
+1
> Latest HTML5 archetype doesn't show unavailable maven repo in wizard
> --------------------------------------------------------------------
>
> Key: JBIDE-16170
> URL: https://issues.jboss.org/browse/JBIDE-16170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.1.Final
>
>
> The latest HTML 5 archetype now depends on WFK dependencies by default (there used to be a community/enterprise distinction before, not anymore)
> Problem is, the missing enterprise dependencies warning (JBIDE-14909) only shows up if an enterprise runtime is selected. In this case, it should also be displayed for all runtimes.
> So all JBoss Central users not selecting an enterprise runtime will create a broken project if the maven redhat repo is missing from their settings.xml. Which is bad :/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-13145) Server Adapter: Should show connection wizard if "Tail files" and connection was removed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13145?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13145:
------------------------------------------
setting fixVersion to LATER since it's very unlikely that we'll have time for this in the near future.
> Server Adapter: Should show connection wizard if "Tail files" and connection was removed
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-13145
> URL: https://issues.jboss.org/browse/JBIDE-13145
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> # ASSERT: make sure that you have an application on OpenShift that you imported to your workspace (and got a project for it)
> # ASSERT: make sure that you have a server adapter for this project
> # EXEC: in *OpenShift Explorer*: select the connection that you used when importing and pick *Remove from View*
> # EXEC: go to your server adapter and pick *OpenShift->Tail files*
> Result:
> Nothing happens. In the log you'll spot:
> {quote}
> !ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-11-23 22:49:23.742
> !MESSAGE Failed to retrieve Application from the selected Server.
> Please verify that the associated OpenShift Application still exists.
> {quote}
> Expected:
> The connection wizard pops up with the server, username filled in from the settings in your project (<project>/.settings/org.jboss.tools.openshift.express.ui.prefs)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-13299) openshift server adapter editor: should notice if project is removed/recreated
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13299?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13299:
-------------------------------------
Fix Version/s: LATER
(was: 4.2.x)
> openshift server adapter editor: should notice if project is removed/recreated
> ------------------------------------------------------------------------------
>
> Key: JBIDE-13299
> URL: https://issues.jboss.org/browse/JBIDE-13299
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: LATER
>
>
> The server adapter editor should notice if it's deploy project is removed/recreated
> How to reproduce:
> # EXEC: launch *OpenShift Application* wizard and create some application
> # ASSERT: the applicaiton is imported into a project in your workspace and the server adapter for it is created
> # EXEC: open the server adapter editor
> # ASSERT: *Deploy Project* combo is enabled and shows the workspace project
> # EXEC: delete the project from your workspace
> Result:
> *Deploy project* is still selected even though the project was deleted. It should live react to this removal, remove the project from the combo.
> Workaround:
> Close and reopen the server adapter editor.
> (btw. the server adapter will inform you when you try to use it to publish. It'll tell you that the project it is bound to is not existing any more)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months