April 2015 - jbosstools-issues - Jboss List Archives

[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: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #3 May 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015) > 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.Alpha2 > > 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.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3004) UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3004?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3004: -------------------------------- Sprint: Sprint 20141112, Sprint to CR1 Release, Sprint #2 April 2015 (was: Sprint 20141112, Sprint to CR1 Release, Sprint #1 April 2015) > UnInstaller should have the same application icon as JBoss Developer Studio and appropriate name > ------------------------------------------------------------------------------------------------ > > Key: JBDS-3004 > URL: https://issues.jboss.org/browse/JBDS-3004 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Minor > Fix For: 8.x > > > See linked Jira about installer icon. I think we should apply the same to Uninstaller icon. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[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: ----------------------------------- Sprint: Sprint #1 April 2015 (was: Sprint #2 April 2015) > 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 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19266) Batch validation problems QuickFixes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19266?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19266: ----------------------------------- Sprint: Sprint #2 April 2015 (was: Sprint #3 May 2015) > Batch validation problems QuickFixes > ------------------------------------ > > Key: JBIDE-19266 > URL: https://issues.jboss.org/browse/JBIDE-19266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18398) Shebang for Node.js is not supported

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18398?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-18398: ----------------------------------------- Shebang will be supported by JSDT since WTP 3.7M7, see: [Bug 462283 - JavaScript Editor complains on Shebang (#!) lines|https://bugs.eclipse.org/bugs/show_bug.cgi?id=462283] > Shebang for Node.js is not supported > ------------------------------------- > > Key: JBIDE-18398 > URL: https://issues.jboss.org/browse/JBIDE-18398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Karel Piwko > Assignee: Victor Rubezhny > Fix For: 4.3.x > > > Shebang in javascript file is reported by IDE as an error. > {code} > #!/usr/bin/env node > /* jshint laxbreak:true */ > var util = require('util'); > var fs = require('fs'); > var prompt = require('prompt'); > {code} > shows marker (x) with following text on line 1: > Multiple markers at this line > - Syntax error on tokens, delete these tokens > - Syntax error on token "Invalid Regular Expression Options", no accurate correction -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19536: ---------------------------------------- [~rawagner] can you reproduce it manually? Maybe your bot test environment is responsible for that loop. > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: cdi_jstack > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19536: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Infinite job loop when creating project > --------------------------------------- > > Key: JBIDE-19536 > URL: https://issues.jboss.org/browse/JBIDE-19536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: cdi_jstack > > > Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974 > I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19446) Completion proposal computers implementations should check content type before doing other computations

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19446: ----------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Completion proposal computers implementations should check content type before doing other computations > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19446 > URL: https://issues.jboss.org/browse/JBIDE-19446 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: batch, cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > BeansXmlCompletionProposalComputer should do computations only for beans.xml. > BatchJobCompletionProposalComputer should do computations only for batch job xml. > These computers are registered for different content types because Eclipse may bind any matching content type to file, including any xml content type. Implementation should start with the check if current xml file is relevant. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18857) Java EE 7 Batch support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18857?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18857. ------------------------------------ Fix Version/s: 4.3.0.Alpha2 (was: 4.3.x) Resolution: Done All main features has been implemented for Alpha2. I converted all remaining subtasks to new feature requests. > Java EE 7 Batch support > ----------------------- > > Key: JBIDE-18857 > URL: https://issues.jboss.org/browse/JBIDE-18857 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19386) Content assist for <* class=""> in Batch Job XML files.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19386?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19386: ----------------------------------- Labels: new_and_noteworthy (was: ) > Content assist for <* class=""> in Batch Job XML files. > ------------------------------------------------------- > > Key: JBIDE-19386 > URL: https://issues.jboss.org/browse/JBIDE-19386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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