[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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18837:
------------------------------------
OK, so at the moment, the master branch for Base's org.j.t.foundation.core plugin relies on parent pom version for its definition of jbosstools.version.
If you want that changed to use Base's root pom version, let me know and I can create a new PR.
Aside: I wasn't suggesting NEW -D flags. I was suggesting that under your new scheme, QE may need to revert to using the OLD flags, since you have no way to differentiate "latest nightly for 4.2.x" from "latest staged for 4.2.x". Since we've discovered that QE sometimes wants to test nightlies before they're staged (JBIDE-18833), we need a workaround for that use case. Being tied to parent pom version HELPS but it's not the silver bullet I'd like.
> 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
> Fix For: 4.3.0.Alpha1
>
>
> 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.8#6338)
11 years, 4 months
[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 reassigned JBIDE-18852:
--------------------------------------
Assignee: Viacheslav Kabanovich
> 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.Alpha1
>
>
> 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.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-17818) Visual Editor: Need to handle external html / htm files
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17818?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17818:
-------------------------------------
QA will be able to test it with 4.2.1.CR1 build
> Visual Editor: Need to handle external html / htm files
> -------------------------------------------------------
>
> Key: JBIDE-17818
> URL: https://issues.jboss.org/browse/JBIDE-17818
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta2
> Reporter: Ilya Buziuk
> Assignee: Konstantin Marmalyukov
> Labels: new_and_noteworthy, respin-a
> Fix For: 4.2.1.CR1
>
>
> Now VPE / HTML Preview can handle only workspace's files. Need to add external files support
> When I open html pages outside eclipse workspace I get an error stating VPE preview cannot open the file.
> That is not ok.
> preview should be able to just fine preview the html no matter where the content is from and if it is because some current limitation about preview then users should at least be able to edit files even if external to the workspace.
> by external to workspace I mean what is opened with File > Open File...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months