April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18950) New Batch Artifact wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18950?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18950: ----------------------------------- Description: There are about 20 artifacts in Java EE Batch: Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener. We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden). 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods); 2. Reference name should be provided for each artifact. There are 3 options: - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named; - META-INF/batch.xml - by default, when first 2 options failed reference name is tried as the qualified class name. 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact: {code} @Inject @BatchProperty(name="property1") String property; @Inject @BatchProperty String property2; {code} Thus, the wizard will have inputs as follows: - Artifact: [combo] - Source folder: [as in New Java Class wizard] - Package: [as in New Java Class wizard] - Class name: [text] - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled) - Reference name: (block of inputs) | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name | - Name: [text] (for first 2 options filled with default value; for the last option disabled) - Properties: [table editor with 'Property name' and 'Field name' columns] Some more inputs may be inherited from New Java Class wizard, if default values are not enough. !artifact.png! was: There are about 20 artifacts in Java EE Batch: Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener. We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden). 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods); 2. Reference name should be provided for each artifact. There are 3 options: - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named; - META-INF/batch.xml - by default, when first 2 options failed reference name is tried as the qualified class name. 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact: {code} @Inject @BatchProperty(name="property1") String property; @Inject @BatchProperty String property2; {code} Thus, the wizard will have inputs as follows: - Artifact: [combo] - Source folder: [as in New Java Class wizard] - Package: [as in New Java Class wizard] - Class name: [text] - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled) - Reference name: (block of inputs) | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name | - Name: [text] (for first 2 options filled with default value; for the last option disabled) - Properties: [table editor with 'Property name' and 'Field name' columns] Some more inputs may be inherited from New Java Class wizard, if default values are not enough. > New Batch Artifact wizard > ------------------------- > > Key: JBIDE-18950 > URL: https://issues.jboss.org/browse/JBIDE-18950 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > Attachments: artifact.png, BatchArtifact.png, BatchArtifactWizBan.png > > > There are about 20 artifacts in Java EE Batch: > Batchlet; Checkpoint Algorithm; Decider; Item Reader; Item Writer; Item Processor; Partition Analyzer; Partition Reducer; Partition Collector; Partition Mapper; Partition Plan; Chunk Listener; Item Process Listener; Item Reader Listener; Item Writer Listener; Job Listener; Step Listener; Retry Process Listener; Retry Read Listener; Retry Write Listener; Skip Process Listener; Skip Listener; Skip Write Listener. > We may have one wizard for each, or some of this artifacts. However, there is so much common in them that it makes sense also (or instead) to have one wizard with list choice of artifact. When a specific artifact should be created from the context of Batch XML editor, this wizard can be invoked with selection of that artifact (list of artifacts may be disabled or hidden). > 1. Artifact implements a specific Java interface (for interfaces that have more than 1 method, there is optional abstract class to extend that implements rarely overridden methods); > 2. Reference name should be provided for each artifact. There are 3 options: > - An implementation of Batch runtime may define its own way of matching class to name. For example, CDI uses javax.inject.Named; > - META-INF/batch.xml > - by default, when first 2 options failed reference name is tried as the qualified class name. > 3. Artifact class may declare fields, with values to be injected from properties set in job xml element referencing that artifact: > {code} > @Inject @BatchProperty(name="property1") String property; > @Inject @BatchProperty String property2; > {code} > Thus, the wizard will have inputs as follows: > - Artifact: [combo] > - Source folder: [as in New Java Class wizard] > - Package: [as in New Java Class wizard] > - Class name: [text] > - [radio] implement interface [radio] extend abstract class (if class is not available, the option is disabled) > - Reference name: (block of inputs) > | - [radio] Annotation Named [radio] batch.xml [radio] Qualified name > | - Name: [text] (for first 2 options filled with default value; for the last option disabled) > - Properties: [table editor with 'Property name' and 'Field name' columns] > Some more inputs may be inherited from New Java Class wizard, if default values are not enough. > !artifact.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19713) Location for 'runtime-locations.proprty' file hardcode 'studio' segment

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19713?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-19713: ------------------------------------- Assignee: Denis Golovin > Location for 'runtime-locations.proprty' file hardcode 'studio' segment > ----------------------------------------------------------------------- > > Key: JBIDE-19713 > URL: https://issues.jboss.org/browse/JBIDE-19713 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > Latest p2 release introduces new RCP Product layout for Mac where all bits are located inside Product.app package. This leads to runtime detection not being able to find runtime-locations.properties file with default configuration for locations where to search for runtimes. It happens because path to file above has two extra path segments '../studio' which are not required at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19713) Location for 'runtime-locations.proprty' file hardcode 'studio' segment

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19713: ------------------------------------- Summary: Location for 'runtime-locations.proprty' file hardcode 'studio' segment Key: JBIDE-19713 URL: https://issues.jboss.org/browse/JBIDE-19713 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Alpha2 Reporter: Denis Golovin Fix For: 4.3.0.Beta1 Latest p2 release introduces new RCP Product layout for Mac where all bits are located inside Product.app package. This leads to runtime detection not being able to find runtime-locations.properties file with default configuration for locations where to search for runtimes. It happens because path to file above has two extra path segments '../studio' which are not required at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19681) OpenShift New and Noteworthy for 4.3.0.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19681?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19681: ------------------------------------------ content is ready to be merged. > OpenShift New and Noteworthy for 4.3.0.Alpha2 > --------------------------------------------- > > Key: JBIDE-19681 > URL: https://issues.jboss.org/browse/JBIDE-19681 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17686) get TCF and RSE terminals to coexist without bad UX of multiple terminals

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17686?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17686: ------------------------------------- In a fresh m6 install, there's only one view there matching the string 'terminal' and it is in org.eclipse.tcf.te.ui.terminals (1.3.0.201503040858) The RSE "Remote Shell" view is still technically present, and is the default shell to open when browsing from the Remote System Explorer view. This is contributed by org.eclipse.rse.shells.ui (3.0.500.201403271554) > Optimally we could remove the RSE terminal and just use the new one Removing org.eclipse.rse.shells.ui (3.0.500.201403271554) probably won't fix anything. *WE* can just use the new one wherever we're using it, but by removing the RSE one, all we'd be doing is removing the ability to right-click on a connection in the Remote System Explorer and selecting "Launch Shell". It'd also probably break the following plugins, which seem to depend on it: 696 ACTIVE org.eclipse.rse.subsystems.shells.core_3.1.300.201403271554 697 ACTIVE org.eclipse.rse.subsystems.shells.dstore_2.1.400.201403100950 698 ACTIVE org.eclipse.rse.subsystems.shells.local_2.1.400.201403100950 699 ACTIVE org.eclipse.rse.subsystems.shells.ssh_2.1.400.201403100950 700 ACTIVE org.eclipse.rse.subsystems.shells.telnet_1.2.300.201403100950 In order to get "Launch Shell" to open one of the new terminals, instead, we'd probably need to remove all of the above plugins *and* provide replacements for them, that implement the same extension points and fill the same niche. Otherwise we'll be losing that action from the Remote System Explorer view to open a shell. Lars and the Fuse tools seem to be using a deprecated and disappeared terminal view: org.eclipse.tm.terminal.view. Either that or I'm pretty blind. But an 'ss' command in m6 does not show this view present at all. This view (org.eclipse.tm.terminal.view) is definitely present when using a fuseide dev-env and tp, so it seems to have been recently removed. Lars will 100% need to rewrite his terminal integration for any Mars release. It would be very very important for him to review the current proposed terminal to see it meets his API needs. So anyway, can TCF and RSE terminals co-exist without bad UI? Probably not. The RSE terminal is tied to the RSE views, and simply removing them removes functionality. We could rewrite the entire terminal portion of RSE, but since RSE is being deprecated / killed softly, that seems like a big waste of time (unless we planned to continue going with RSE even when it was no longer maintained, or take it over). It seems to me that just leaving them in is hte better short-term fix, but if we had ideas to take over RSE entirely, then it might make sense to get rid of their old crappy terminal and migrate them to the new one. Of course whether this is even technically possible hasn't been investigated by me yet. > get TCF and RSE terminals to coexist without bad UX of multiple terminals > ------------------------------------------------------------------------- > > Key: JBIDE-17686 > URL: https://issues.jboss.org/browse/JBIDE-17686 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta1 > > Attachments: eclipse-can-has-many-consoles.png > > > luna has new Eclipse TCF terminal that brings better Terminal support. > I would assume it is in there but I couldn't find a way to actually open it. Maybe we havent included the full set of plugins. > http://marketplace.eclipse.org/content/tcf-terminals#.U6sJ92Vp7wV > http://eclipsesource.com/blogs/2014/06/17/tcf-terminal-top-eclipse-luna-f... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3408) installer is trying to reach download.jboss.org for content

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3408?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3408: ------------------------------------------- cool thanks. if this happeend before - time to get a test in place to guard against it. > installer is trying to reach download.jboss.org for content > ----------------------------------------------------------- > > Key: JBDS-3408 > URL: https://issues.jboss.org/browse/JBDS-3408 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Running latest devstudio 9 installer I caught it in reaching out to download.jboss.org which it should have *zero* links/dependency on. > My guess is there is an updatesite that have bad reference to download.jboss.org that we need fixing. > See screenshot at https://www.dropbox.com/s/wkr30jlvdc7d8wu/Screenshot%202015-04-15%2013.11... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19668) Freemarker New and Noteworthy for 4.3.0.Alpha2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19668?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-19668. --------------------------------- Resolution: Rejected > Freemarker New and Noteworthy for 4.3.0.Alpha2 > ---------------------------------------------- > > Key: JBIDE-19668 > URL: https://issues.jboss.org/browse/JBIDE-19668 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2635: -------------------------------- Comment: was deleted (was: We'll try to use the same font as in title throughout the installer controls.) > Installation sometimes fail with bundle was not found on Windows > ---------------------------------------------------------------- > > Key: JBDS-2635 > URL: https://issues.jboss.org/browse/JBDS-2635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.Beta1 > Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log > > > For the first time JBDS 7.0.0.Beta1 failed on windows8: > {code} > An error occurred while installing the items > session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found. > Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19256) Autocomplete shows white on white using default RHEL7 theme

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19256?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19256: --------------------------------------- I cannot, because I don't have RHEL7 subscription. > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-19256 > URL: https://issues.jboss.org/browse/JBIDE-19256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Add create from template details pain

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19712: ------------------------------------- Summary: Add create from template details pain Key: JBIDE-19712 URL: https://issues.jboss.org/browse/JBIDE-19712 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Add details pain similiar to v2 where you get template details when you select an individual template -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

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