July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-20210: ------------------------------------- Assignee: Denis Golovin > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20213) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [LiveReload]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20213?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-20213: ------------------------------------- Assignee: Denis Golovin > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [LiveReload] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20213 > URL: https://issues.jboss.org/browse/JBIDE-20213 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [LiveReload]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20211) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Freemarker]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20211?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-20211: ------------------------------------- Assignee: Denis Golovin > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Freemarker] > -------------------------------------------------------------------------------------- > > Key: JBIDE-20211 > URL: https://issues.jboss.org/browse/JBIDE-20211 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Freemarker]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20206) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JST]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20206?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-20206: ------------------------------------- Assignee: Denis Golovin (was: Alexey Kazakov) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JST] > ------------------------------------------------------------------------------- > > Key: JBIDE-20206 > URL: https://issues.jboss.org/browse/JBIDE-20206 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [JST]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3374) Remove org.eclipse.cvs feature from JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3374?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3374. ---------------------------- Resolution: Rejected Rejected. > Remove org.eclipse.cvs feature from JBDS > ---------------------------------------- > > Key: JBDS-3374 > URL: https://issues.jboss.org/browse/JBDS-3374 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Beta2 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import feature="org.eclipse.cvs"/> > {quote} > I can't see any reason why we'd do that in 2015. > Burr Sutter, Len DiMaggio, Max Rydahl Andersen : is there any client requirement about CVS support? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20249) compile failed in server (jmx)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20249?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20249. ------------------------------ Resolution: Duplicate Issue Fixed in https://issues.jboss.org/browse/JBIDE-20188?focusedCommentId=13088374&pag... > compile failed in server (jmx) > ------------------------------ > > Key: JBIDE-20249 > URL: https://issues.jboss.org/browse/JBIDE-20249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > After this: > https://github.com/jbosstools/jbosstools-server/commit/090b7b3dc20a0aa45a... > You get this: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/808/consoleText} > 09:59:09 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.jmx.ui: Compilation failure: Compilation failure: > 09:59:09 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/views/navigator/MBeanExplorerContentProvider.java:[49] > 09:59:09 [ERROR] import org.jboss.tools.jmx.ui.internal.actions.RefreshActionState; > 09:59:09 [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 09:59:09 [ERROR] The import org.jboss.tools.jmx.ui.internal.actions.RefreshActionState cannot be resolved > 09:59:09 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/views/navigator/MBeanExplorerContentProvider.java:[206] > 09:59:09 [ERROR] TreePath[] treePaths = RefreshActionState.getDefault().getExpansion(w); > 09:59:09 [ERROR] ^^^^^^^^^^^^^^^^^^ > 09:59:09 [ERROR] RefreshActionState cannot be resolved > 09:59:09 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/views/navigator/MBeanExplorerContentProvider.java:[207] > 09:59:09 [ERROR] ISelection sel = RefreshActionState.getDefault().getSelection(w); > 09:59:09 [ERROR] ^^^^^^^^^^^^^^^^^^ > 09:59:09 [ERROR] RefreshActionState cannot be resolved > 09:59:09 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/RefreshAction.java:[102] > 09:59:09 [ERROR] RefreshActionState.getDefault().setSelection(wrapper, sel); > 09:59:09 [ERROR] ^^^^^^^^^^^^^^^^^^ > 09:59:09 [ERROR] RefreshActionState cannot be resolved > 09:59:09 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/jmx/plugins/org.jboss.tools.jmx.ui/src/org/jboss/tools/jmx/ui/internal/actions/RefreshAction.java:[103] > 09:59:09 [ERROR] RefreshActionState.getDefault().setExpansion(wrapper, paths); > 09:59:09 [ERROR] ^^^^^^^^^^^^^^^^^^ > 09:59:09 [ERROR] RefreshActionState cannot be resolved > 09:59:09 [ERROR] 5 problems (5 errors) > {code} > Related: http://memegenerator.net/instance2/662763 > Please fix this and kick a new build to get the job back to blue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20261) Need to create features for JavaScript tools (org.jboss.tools.jst.js)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20261?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20261: ------------------------------------ Note that if you don't plan to include this plugin in JBoss Central or Eclipse Marketplace, you can simply add the <bundle> to your category.xml (update site). No feature is required UNLESS you need this in Central or Marketplace. > Need to create features for JavaScript tools (org.jboss.tools.jst.js) > --------------------------------------------------------------------- > > Key: JBIDE-20261 > URL: https://issues.jboss.org/browse/JBIDE-20261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.Beta1 > Reporter: Ilya Buziuk > Assignee: Denis Golovin > Fix For: 4.3.0.Beta2 > > > There is no proper feature infrastructure for JavaScript Tools (org.jboss.tools.jst.js plugin) in jbosstools-jst -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19795) Bower support

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19795: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-jst/pull/488, https://github.com/jbosstools/jbosstools-jst/pull/489, https://github.com/jbosstools/jbosstools-jst/pull/490, https://github.com/jbosstools/jbosstools-jst/pull/493, https://github.com/jbosstools/jbosstools-jst/pull/499, https://github.com/jbosstools/jbosstools-jst/pull/502 (was: https://github.com/jbosstools/jbosstools-jst/pull/488, https://github.com/jbosstools/jbosstools-jst/pull/489, https://github.com/jbosstools/jbosstools-jst/pull/490, https://github.com/jbosstools/jbosstools-jst/pull/493, https://github.com/jbosstools/jbosstools-jst/pull/499) > Bower support > ------------- > > Key: JBIDE-19795 > URL: https://issues.jboss.org/browse/JBIDE-19795 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta2 > > > Need to have initial [Bower|http://bower.io/] tools support: > *The gist* > Bower tooling should initially support several bower API commands : > |Command||Description| > | *bower init* |creates a *bower.json* file| > |*bower install <package>*|installs packages to *bower_components* folder| > |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory| > |*bower update* |updates installed packages to their newest version according to *bower.json*| > Basically, the main idea of the implementation is the following: > Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration* > Native bower tools must be preinstalled > *The main questions & proposals:* > 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.) > 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature? > 3. Implementation details: > - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) > - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20147) Batch Property mapping issue with reference

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20147?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20147 at 7/15/15 11:17 AM: ------------------------------------------------------------------------- Well, now I see that I fixed something else instead - same issue with @Named. was (Author: scabanovich): It works for me, and there is an automatic test that passes. Please attach your project. > Batch Property mapping issue with reference > ------------------------------------------- > > Key: JBIDE-20147 > URL: https://issues.jboss.org/browse/JBIDE-20147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Environment: Mars > Tools 4.3.0 Beta1 > Reporter: Cody Lerum > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > After upgrading to Mars and JBT I started getting a validation warning on my batch configuration > If I have the following I get an error {{Property "INVOICE_JOB_ID" is not found in artifact "invoiceCreateBatchlet" and is not used in other properties.}} > {code} > @Inject > @BatchProperty(name = InvoiceCreatePartitionMapper.INVOICE_JOB_ID_KEY) > private String invoiceJobId; > {code} > In a different class > {code} > public static final String INVOICE_JOB_ID_KEY = "INVOICE_JOB_ID"; > {code} > However if have the following there is no warning. > {code} > @Inject > @BatchProperty(name = "INVOICE_JOB_ID") > private String invoiceJobId; > {code} > It appears that the validation logic cannot follow the reference -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20147) Batch Property mapping issue with reference

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20147?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20147: ----------------------------------------------- It works for me, and there is an automatic test that passes. Please attach your project. > Batch Property mapping issue with reference > ------------------------------------------- > > Key: JBIDE-20147 > URL: https://issues.jboss.org/browse/JBIDE-20147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Environment: Mars > Tools 4.3.0 Beta1 > Reporter: Cody Lerum > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > After upgrading to Mars and JBT I started getting a validation warning on my batch configuration > If I have the following I get an error {{Property "INVOICE_JOB_ID" is not found in artifact "invoiceCreateBatchlet" and is not used in other properties.}} > {code} > @Inject > @BatchProperty(name = InvoiceCreatePartitionMapper.INVOICE_JOB_ID_KEY) > private String invoiceJobId; > {code} > In a different class > {code} > public static final String INVOICE_JOB_ID_KEY = "INVOICE_JOB_ID"; > {code} > However if have the following there is no warning. > {code} > @Inject > @BatchProperty(name = "INVOICE_JOB_ID") > private String invoiceJobId; > {code} > It appears that the validation logic cannot follow the reference -- 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 July 2015