July 2015 - jbosstools-issues - Jboss List Archives

[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.CR1 (was: 4.3.0.Beta2) > 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.CR1 > > Attachments: cdi_jstack, jstack.out > > > 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.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19824) HTML5 Palette: Add JS/CSS libs to project via Bower

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19824?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19824: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > HTML5 Palette: Add JS/CSS libs to project via Bower > --------------------------------------------------- > > Key: JBIDE-19824 > URL: https://issues.jboss.org/browse/JBIDE-19824 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.x > > > If you insert an html5 component (html5 core, ionic, jQueryMobile) from our HTML5 Palette then the corresponding JS/CSS links are inserted (if needed) to the page too. But currently we insert direct links to remote JSs/CSSs. > As soon as JBIDE-19795 is done we can use the Bower tooling to install the needed libs. > It may be a checkbox in the wizard which will tell us to use Bower when inserting the JS/CSS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20147?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20147: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20135) Add validation for integer and enumerated attributes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20135?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20135: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > Add validation for integer and enumerated attributes > ----------------------------------------------------- > > Key: JBIDE-20135 > URL: https://issues.jboss.org/browse/JBIDE-20135 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.x > > > There are many attributes that are restricted only to some enumerated value or integer value and that are not validated at all. Is there a reason why there is no validation for them? > Example: > {code} > <chunk checkpoint-policy="{item|custom}" > item-count="{value}" > time-limit="{value}" > skip-limit="{value}" > retry-limit="{value}" > /> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20127) Add validation for step element's attributes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20127?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20127: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > Add validation for step element's attributes > -------------------------------------------- > > Key: JBIDE-20127 > URL: https://issues.jboss.org/browse/JBIDE-20127 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.x > > > The step element could have two attributes that seem not to have any validation on them: > - start-limit - this should be an integer > - allow-start-if-complete - only true/false -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19332) batch editor seems slow even on small file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19332?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19332: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > batch editor seems slow even on small file > ------------------------------------------ > > Key: JBIDE-19332 > URL: https://issues.jboss.org/browse/JBIDE-19332 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > I created a file and named it job.xml with the following content: > {code} > <job id="loadRealmAuctionFileJob" xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="1.0"> > <step id="loadRealmAuctionFileStep"> > <batchlet ref="loadAuctionFilesBatchlet"> > <properties> > <property name="region" value="#{partitionPlan['region']}"/> > <property name="target" value="#{partitionPlan['target']}"/> > </properties> > </batchlet> > <partition> > <plan partitions="2"> > <properties partition="0"> > <property name="region" value="US"/> > <property name="target" value="http://us.battle.net/api/wow/auction/data/"/> > </properties> > <properties partition="1"> > <property name="region" value="EU"/> > <property name="target" value="http://eu.battle.net/api/wow/auction/data/"/> > </properties> > </plan> > </partition> > </step> > </job> > {code} > Small file, shouldn't be slow but when I click and/or scroll up/down in the UI it seem to be doing "something" and it feels sluggish. > Here is a recording of me scrolling up and down with keyboard. https://v.usetapes.com/PoUrCOUNty -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19997) Add possibility to select interface and abstract class in New Batch Artifact wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19997?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19997: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > Add possibility to select interface and abstract class in New Batch Artifact wizard > ----------------------------------------------------------------------------------- > > Key: JBIDE-19997 > URL: https://issues.jboss.org/browse/JBIDE-19997 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.x > > > I think that in every bigger enterprise project you would have your own implementation of batch interfaces and abstract classes. So the possibility to select them in the New Batch Artifact wizard would be very useful. > Maybe you could just put there interface and abstract class selection section from New Java Class wizard and pre-define the right batch classes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19573) Improve test coverage for CDI 1.1/1.2 Annotated beans

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19573?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19573: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Improve test coverage for CDI 1.1/1.2 Annotated beans > ----------------------------------------------------- > > Key: JBIDE-19573 > URL: https://issues.jboss.org/browse/JBIDE-19573 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > Currently we test CDI 1.1/1.2 annotated beans only for CDI as-you-type model. (CDI model snapshots for files which are being edited). We should test it for regular CDI projects/models which are built by CDI builder. > I see it in CDI11AnnotatedTest. Maybe more tests effected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19940) Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19940?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19940: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Detector of non-compatilbe JVMs may miss UnsupportedClassVersionError(s) > ------------------------------------------------------------------------ > > Key: JBIDE-19940 > URL: https://issues.jboss.org/browse/JBIDE-19940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > When testing JBIDE-19500 (warn/inform users running on non-compatilbe JVMs they are loosing out on features) on some old workspaces I got a situation when Eclipse didn't report a usual error saying "Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))" but I got UnsupportedClassVersionErrors like: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/jboss/tools/usage/event/UsageEventType : Unsupported major.minor version 52.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:272) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:588) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:540) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:527) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.initializeUsageReporting(ForgeCorePlugin.java:48) > at org.jboss.tools.forge.core.internal.ForgeCorePlugin.start(ForgeCorePlugin.java:44) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764) > {code} > Maybe it's because I was running JBT from my dev eclipse environment and Eclipse used some cashed Require-Capability's of load plugins and we won't have such problems in real world when problematic plugins are installed/updated but not modified in dev environment. > But anyway, this is worth investigation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19941) Create a JUnit integration test for o.j.t.foundation.checkup plugin to cover the case if Eclipse log message about unsupported JVM is changed

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19941?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19941: ----------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Create a JUnit integration test for o.j.t.foundation.checkup plugin to cover the case if Eclipse log message about unsupported JVM is changed > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19941 > URL: https://issues.jboss.org/browse/JBIDE-19941 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > Currently we don't test any real eclipse errors. It would be useful to have an integration test which will help us to be aware if Eclipse change the format of such errors in log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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