[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20110:
----------------------------------------
Sprint: Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #5 Jun 2015)
> Batch Diagram silently closes Palette view
> ------------------------------------------
>
> Key: JBIDE-20110
> URL: https://issues.jboss.org/browse/JBIDE-20110
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Beta1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
>
> Case 1:
> 1. Open Studio.
> 2. Open Palette.
> 3. Open some batch job xml file.
> FAIL: Palette is silently closed.
> The code that does it, is commented with
> {code}
> /**
> * This is a workaround that ensures that the flyout pallete (inner
> * composite inside the diagram editor) is used instead of a separate
> * pallete view. The separate pallete view does not work with the diagram
> * editor currently.
> */
> {code}
> This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace.
> There is another case when this silent close does not work.
> Case 2:
> 1. Open some batch job xml file.
> 2. Open Palette view.
> 3. Test work with the separate palette.
> 4. Close/Restart Eclipse.
> 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it)
> 6. Test work with the separate palette.
> [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it.
> Separate Palette view does not work with Batch diagram in this usecase:
> 1. Open batch job editor.
> 2. Open separate palette. Make sure that it works.
> 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'.
> 4. Make sure that Palette does not work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20139) Labels at property editors with 'Browse' button are missing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20139?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20139:
----------------------------------------
Sprint: Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #5 Jun 2015)
> Labels at property editors with 'Browse' button are missing
> -----------------------------------------------------------
>
> Key: JBIDE-20139
> URL: https://issues.jboss.org/browse/JBIDE-20139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Beta1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Beta2
>
> Attachments: LabelsNotRendered.png
>
>
> Open faces config xml file in JBoss Tools XML editor. Select Application or Factory node. The form has several property editors with Browse button for selecting class. The label for these editors is not rendered.
> I see it in Mars-M7, Linux Ubuntu 14.04. [~ljelinko], could you please check it on available OS?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19706) Refactor the hibernate service provider implementations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19706?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19706:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> Refactor the hibernate service provider implementations
> --------------------------------------------------------
>
> Key: JBIDE-19706
> URL: https://issues.jboss.org/browse/JBIDE-19706
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate
> Affects Versions: 4.3.0.Alpha2
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta2
>
>
> The SPI implementation "proxy" classes need a common superclass that can implement most of the functionality using introspection. In this way probably 70% of the code can be eliminated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19759:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> Application wizard: cannot launch v3 application wizard via File->New->OpenShift
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19759
> URL: https://issues.jboss.org/browse/JBIDE-19759
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: empty-v2-wizard-page.png, no-application-wizard.png
>
>
> If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional.
> This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19741:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19741
> URL: https://issues.jboss.org/browse/JBIDE-19741
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi, jsp/jsf/xml/html source editing, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Beta2
>
> Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt
>
>
> There are 141M of binaries in the jbosstools-javaee source tree.
> See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19729) Version Auditing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19729?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19729:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> Version Auditing
> ----------------
>
> Key: JBIDE-19729
> URL: https://issues.jboss.org/browse/JBIDE-19729
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Epic to track issues related to auditing and quality control.
> This may include tools & workflows to ensure we're not building the wrong stuff, including too much (or incompatible versions) in target platforms, forgetting to upversion components, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19814:
----------------------------------------
Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015)
> sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19814
> URL: https://issues.jboss.org/browse/JBIDE-19814
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources.
> This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D
> Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty:
> {code}
> git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months