February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19168) Exception thrown when external HTML opened in VPE

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19168: -------------------------------------- Summary: Exception thrown when external HTML opened in VPE Key: JBIDE-19168 URL: https://issues.jboss.org/browse/JBIDE-19168 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing, upstream Affects Versions: 4.2.1.CR1 Environment: JBDS 8.0.1.CR1-v20141124-0632-B333 Linux 64bit Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 4.2.3.Beta1 1. Install AngulaJS for Eclipse from JBoss Central 2. Open external HTML file in VPE ERROR: {noformat} IFile parameter can not be null org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1272) at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:126) at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:118) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19167) JBT 4.2.luna nightly site has left the building

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19167: ---------------------------------- Summary: JBT 4.2.luna nightly site has left the building Key: JBIDE-19167 URL: https://issues.jboss.org/browse/JBIDE-19167 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.3.Beta1 Reporter: Nick Boldt For some reason, the nightly core 4.2.luna site [1] has vanished. [1] http://download.jboss.org/jbosstools/updates/nightly/core/4.2.luna/ Need to know what happened. Problem is that downstream builds are of course failing: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-build-sites.aggregate.hibernatetools-site_4.2.luna/223/console} [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'jbosstools-base' from location http://download.jboss.org/jbosstools/updates/nightly/core/4.2.luna/: No repository found at http://download.jboss.org/jbosstools/updates/nightly/core/4.2.luna. -> [Help 1] {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19168) Exception thrown when external HTML opened in VPE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19168?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19168: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.2.3.Beta1) > Exception thrown when external HTML opened in VPE > ------------------------------------------------- > > Key: JBIDE-19168 > URL: https://issues.jboss.org/browse/JBIDE-19168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.1.CR1 > Environment: JBDS 8.0.1.CR1-v20141124-0632-B333 Linux 64bit > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Fix For: 4.3.0.Alpha1 > > > 1. Install AngulaJS for Eclipse from JBoss Central > 2. Open external HTML file in VPE > ERROR: > {noformat} > IFile parameter can not be null > org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1272) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:126) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:118) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18834) Exception thrown when external HTML opened in VPE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18834?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18834: ----------------------------------- Fix Version/s: (was: 4.3.0.Alpha1) > Exception thrown when external HTML opened in VPE > ------------------------------------------------- > > Key: JBIDE-18834 > URL: https://issues.jboss.org/browse/JBIDE-18834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.1.CR1 > Environment: JBDS 8.0.1.CR1-v20141124-0632-B333 Linux 64bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.3.Beta1 > > > 1. Install AngulaJS for Eclipse from JBoss Central > 2. Open external HTML file in VPE > ERROR: > {noformat} > IFile parameter can not be null > org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1272) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:126) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:118) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18834) Exception thrown when external HTML opened in VPE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18834?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18834: ----------------------------------- Fix Version/s: 4.2.3.Beta1 > Exception thrown when external HTML opened in VPE > ------------------------------------------------- > > Key: JBIDE-18834 > URL: https://issues.jboss.org/browse/JBIDE-18834 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Affects Versions: 4.2.1.CR1 > Environment: JBDS 8.0.1.CR1-v20141124-0632-B333 Linux 64bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.2.3.Beta1, 4.3.0.Alpha1 > > > 1. Install AngulaJS for Eclipse from JBoss Central > 2. Open external HTML file in VPE > ERROR: > {noformat} > IFile parameter can not be null > org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: IFile parameter can not be null > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1272) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:126) > at org.eclipse.angularjs.internal.ui.validation.AbstractValidator.validate(AbstractValidator.java:118) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18852) No warning about missing invocation handler for interface

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18852?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18852: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > No warning about missing invocation handler for interface > --------------------------------------------------------- > > Key: JBIDE-18852 > URL: https://issues.jboss.org/browse/JBIDE-18852 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Affects Versions: 4.2.1.CR1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > > 1. Create CDI 1.1 project and add deltaspike libs > 2. create partial bean binding > {code} > @PartialBeanBinding > @Target(ElementType.TYPE) > @Retention(RetentionPolicy.RUNTIME) > public @interface ExamplePartialBeanBinding { > } > {code} > 3.create interface > {code} > import javax.enterprise.context.ApplicationScoped; > @ApplicationScoped > @ExamplePartialBeanBinding > public interface Interf { > String sayHello(String hello); > } > {code} > FAIL: There's no warning saying that class should have an invocation handler > 4. create abstract class > {code} > import javax.enterprise.context.ApplicationScoped; > @ApplicationScoped > @ExamplePartialBeanBinding > public abstract class Abs { > public abstract String sayHello(String hello); > public String otherHey (String hello) { > return "Other: " + hello; > } > } > {code} > ASSERT: warning about missing invocation handler is displayed for abstract class > 5. Check interface class again -> no warning, edit file & save -> warning is displayed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18837: -------------------------------------- Assignee: Fred Bricon > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha1 > > Attachments: generated-vs-soource-zip.png > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

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: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > New Batch Artifact wizard > ------------------------- > > Key: JBIDE-18950 > URL: https://issues.jboss.org/browse/JBIDE-18950 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19023) CDI validation cannot find beans in src/test to be used for injection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19023?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19023: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Alpha1) > CDI validation cannot find beans in src/test to be used for injection > --------------------------------------------------------------------- > > Key: JBIDE-19023 > URL: https://issues.jboss.org/browse/JBIDE-19023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Reporter: Jason Porter > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > While trying to fix BZ1178874 I discovered that classes in src/test are not picked up as being valid beans to satisfy injection points. In the example in the Bugzilla issue (https://github.com/jboss-developer/jboss-eap-quickstarts/commit/7aa69072e...) it's a public static class being used, but even if that class is split off into its own public class it still isn't found as a valid bean. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18768) Document use cases where JST Tern integration is taking place

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18768?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18768: ----------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Alpha1) > Document use cases where JST Tern integration is taking place > ------------------------------------------------------------- > > Key: JBIDE-18768 > URL: https://issues.jboss.org/browse/JBIDE-18768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Final > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.x > > > We need to keep list of use cases where jst tern integration bundle is doing tern/angularjs configuration behind the scene. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015