April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19700) Support @BatchProperty qualifiers for injected beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19700?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19700: ----------------------------------- Labels: new_and_noteworthy (was: ) > Support @BatchProperty qualifiers for injected beans > ---------------------------------------------------- > > Key: JBIDE-19700 > URL: https://issues.jboss.org/browse/JBIDE-19700 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch, cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > You can find an example of such beans here: > https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... > 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project > 2. Open batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/RecordsReader.java > 3. There should not be warning messages about no eligible beans for *separatorRegex* and *fileName* properties. > 4. OpenOns for these properties should open import-file.xml and select the corresponding properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ [~mickael_istria] I see you've updated these jobs. Please update the _4.3.mars ones, too. {code} DevStudio_Master/job/jbosstools-aerogear_master/config.xml DevStudio_Master/job/jbosstools-arquillian_master/config.xml DevStudio_Master/job/jbosstools-base_master/config.xml DevStudio_Master/job/jbosstools-birt_master/config.xml DevStudio_Master/job/jbosstools-browsersim_master/config.xml DevStudio_Master/job/jbosstools-central_master/config.xml DevStudio_Master/job/jbosstools-forge_master/config.xml DevStudio_Master/job/jbosstools-freemarker_master/config.xml DevStudio_Master/job/jbosstools-hibernate_master/config.xml DevStudio_Master/job/jbosstools-javaee_master/config.xml DevStudio_Master/job/jbosstools-jst_master/config.xml DevStudio_Master/job/jbosstools-livereload_master/config.xml DevStudio_Master/job/jbosstools-openshift_master/config.xml DevStudio_Master/job/jbosstools-playground_master/config.xml DevStudio_Master/job/jbosstools-portlet_master/config.xml DevStudio_Master/job/jbosstools-server_master/config.xml DevStudio_Master/job/jbosstools-TEMPLATE_master/config.xml DevStudio_Master/job/jbosstools-TEMPLATE.NESTED_master/config.xml DevStudio_Master/job/jbosstools-vpe_master/config.xml DevStudio_Master/job/jbosstools-webservices_master/config.xml {code} Also, I see you've removed some configuration... was that intentional? https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19701) Support javax.batch.runtime.context.JobContext injections

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19701: -------------------------------------- Summary: Support javax.batch.runtime.context.JobContext injections Key: JBIDE-19701 URL: https://issues.jboss.org/browse/JBIDE-19701 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: batch, cdi-extensions Affects Versions: 4.3.0.Alpha2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 You can find an example of such injections here: https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project 2. Open /batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/listener/JobListener.java 3. There should not be a warning message about no eligible beans for: {code:java} @Inject private JobContext jobContext; {code} 4. I guess this is a built-in CDI bean ([~scabanovich] please double check it). If so, the Ctrl+Click on this injection should open javax.batch.runtime.context.JobContext interface. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19449) p2.director install script is finding non-IU IUs to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19449?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-19449. -------------------------------- Resolution: Done This seems to be working fine. I believe the fix that did it was done last June. https://github.com/jbosstools/jbosstools-build-ci/commit/054223e6b6b15c2a... > p2.director install script is finding non-IU IUs to install > ----------------------------------------------------------- > > Key: JBIDE-19449 > URL: https://issues.jboss.org/browse/JBIDE-19449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > p2.director install script is finding non-IU IUs to install such as: > {code}eclipse.buildId > java.version{code} > {code} > list.ius: > [echo] Searching for IUs in http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... with -list 'Q:everything.select(y | everything.select(x | x.properties ~= filter("(org.eclipse.equinox.p2.bundle.localization='plugin')")).collect(x | x.requirements).flatten().exists(r | y ~= r))' ... > [echo] Result: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > [echo] IU list written to /qa/hudson_workspace/workspace/jbosstools-composite-install_master/data/plugin.list.properties > {code} > Full list here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > Reason: here's what's in the plugin.list.properties file: > {code} > !SESSION 2015-03-13 18:06:15.934 ----------------------------------------------- > eclipse.buildId=4.5.0.I20150203-1300 > java.version=1.8.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > !ENTRY org.eclipse.osgi 4 0 2015-03-13 18:06:17.233 > !MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: /qa/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/org.eclipse.osgi > org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. > ch.qos.logback.classic=1.0.7.v20121108-1250 > ch.qos.logback.core=1.0.7.v20121108-1250 > ... > tern.server.nodejs=0.9.0.201502141213 > ternjs=0.9.0.201502141213 > Operation completed in 183432 ms. > {code} > So we need to filter out the header garbage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19700) Support @BatchProperty qualifiers for injected beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19700?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19700: ----------------------------------- Sprint: Sprint #3 May 2015 > Support @BatchProperty qualifiers for injected beans > ---------------------------------------------------- > > Key: JBIDE-19700 > URL: https://issues.jboss.org/browse/JBIDE-19700 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: batch, cdi-extensions > Affects Versions: 4.3.0.Alpha2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > > You can find an example of such beans here: > https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... > 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project > 2. Open batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/RecordsReader.java > 3. There should not be warning messages about no eligible beans for *separatorRegex* and *fileName* properties. > 4. OpenOns for these properties should open import-file.xml and select the corresponding properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19700) Support @BatchProperty qualifiers for injected beans

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19700: -------------------------------------- Summary: Support @BatchProperty qualifiers for injected beans Key: JBIDE-19700 URL: https://issues.jboss.org/browse/JBIDE-19700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: batch, cdi-extensions Affects Versions: 4.3.0.Alpha2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 You can find an example of such beans here: https://github.com/jboss-developer/jboss-sandbox-quickstarts/blob/master/... 1. Import https://github.com/jboss-developer/jboss-sandbox-quickstarts/ as an exisitng maven project 2. Open batch-processing/src/main/java/org/jboss/as/quickstarts/batch/job/RecordsReader.java 3. There should not be warning messages about no eligible beans for *separatorRegex* and *fileName* properties. 4. OpenOns for these properties should open import-file.xml and select the corresponding properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19676) Visual Editor New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19676?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19676. ---------------------------------- Resolution: Rejected > Visual Editor New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------------- > > Key: JBIDE-19676 > URL: https://issues.jboss.org/browse/JBIDE-19676 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > 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 Visual Editor is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Visual Editor 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19664) Live Reload New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19664?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19664. ---------------------------------- > Live Reload New and Noteworthy for 4.3.0.Alpha2 > ----------------------------------------------- > > Key: JBIDE-19664 > URL: https://issues.jboss.org/browse/JBIDE-19664 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > 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 Live Reload is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Live Reload 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)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- [~snjeza], ok, but that still doesn't explain why my eap 6.3 directory is in the newly initialized config file, right? How does it know to add that exact directory? Note that it specifies /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0, but nothing else in the runtimes/ directory (I have plenty of servers there) - I use this one often. So it must have taken it from another instance of Eclipse or something. But how? > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19693) Exception when invoking code assist for external HTML file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19693?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19693: ---------------------------------------- Error message is not longer added to the log but content assist for external files remains limited. > Exception when invoking code assist for external HTML file > ---------------------------------------------------------- > > Key: JBIDE-19693 > URL: https://issues.jboss.org/browse/JBIDE-19693 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64 bit, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > 1. Open external html file in VPE > 2. Invoke code assist > ERROR (appears 3 times): > {noformat} > !ENTRY org.jboss.tools.jst.web.ui 4 0 2015-04-23 08:57:43.421 > !MESSAGE Cannot find existing file by its document. > !STACK 0 > java.lang.IllegalStateException: Cannot find existing file by its document. > at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.createContext(AbstractXmlCompletionProposalComputer.java:125) > at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.FaceletsELCompletionProposalComputer.createContext(FaceletsELCompletionProposalComputer.java:127) > at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:83) > at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.FaceletsELCompletionProposalComputer.computeCompletionProposals(FaceletsELCompletionProposalComputer.java:74) > at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) > at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290) > at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484) > at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255) > at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127) > at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:384) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3790) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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