[JBoss JIRA] (JBIDE-18831) Validator in CDI 1.1 does not validate unused qualifier
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18831?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-18831:
------------------------------------------
I just tried this and it actually works. [~lvalach] can you please take a look ? Maybe we can close it
> Validator in CDI 1.1 does not validate unused qualifier
> -------------------------------------------------------
>
> Key: JBIDE-18831
> URL: https://issues.jboss.org/browse/JBIDE-18831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.x
>
>
> 1. Create a CDI 1.1 project with bean discovery mode "annotated".
> 2. Create a new qualifier type and make an cdi error in it (e.g. member returning array not annotated @Nonbinding)
> Assert: validion error should appear.
> That fails now.
> 3. Create an annotated bean and add qualifier annotation to it.
> Call clean build or modify qualifier file. After that validation includes qualifier.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4495) Missing CDI features
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-4495:
-------------------------------------
+1 on the pull requests. But Pavol just noticed that the README need changing back too - they say that things are deprecated.
> Missing CDI features
> --------------------
>
> Key: JBDS-4495
> URL: https://issues.jboss.org/browse/JBDS-4495
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, cdi
> Affects Versions: 11.0.0.GA
> Reporter: Lukáš Valach
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 11.0.0.GA
>
> Attachments: No_CDI_Plugins.png
>
>
> I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed.
> Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing.
> !No_CDI_Plugins.png|thumbnail!
> JBoss Tools seems to be ok.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4495) Missing CDI features
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4495:
----------------------------------
Just to reiterate how much CDI is actually used, and why we thought it was OK to remove:
{quote}
Some GA data re: seam/ci usage and installation over the last 7mo (Jan 1 - July 31, 2017):
* Seam/CDI feature installs make up about 5.8% of JBT central installs, or 4.8% of devstudio central installs, behind Fuse Tooling, Spring IDE, Aerogear, FindBugs, and Subversion.
* Seam/CDI wizard completions make up 0.07% of wizard completions in JBT, or 0.21% of those in devstudio. So just because it's being installed, doesn't mean it's being USED much.
So... seems like it's safe to deprecate Seam3/CDI as well as Seam2.
Data collected here: https://docs.google.com/spreadsheets/d/1aouMDBbTJbUtV9pFfpAHSHguSoSb0u97J...
> Missing CDI features
> --------------------
>
> Key: JBDS-4495
> URL: https://issues.jboss.org/browse/JBDS-4495
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, cdi
> Affects Versions: 11.0.0.GA
> Reporter: Lukáš Valach
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 11.0.0.GA
>
> Attachments: No_CDI_Plugins.png
>
>
> I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed.
> Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing.
> !No_CDI_Plugins.png|thumbnail!
> JBoss Tools seems to be ok.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24832) Some info on deprecated stuff / move to central missing in N&N
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24832?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24832:
---------------------------------------
I'm not sure which subtask of the N&N superjira should contain this: JBIDE-24706
There is no Seam 3 or Java EE there. Only CDI. But Seam 3 used to be a separate component, no?
> Some info on deprecated stuff / move to central missing in N&N
> --------------------------------------------------------------
>
> Key: JBIDE-24832
> URL: https://issues.jboss.org/browse/JBIDE-24832
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Fix For: 4.5.0.Final
>
>
> The N&N page for 4.5.0.Final currently only has this:
> http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.5.0.Fina...
> Freemarker component deprecation
> The Freemarker component has been marked deprecated as there is no more maintenance on the source code. It is still available in Red Hat Central and may be removed in the future.
> Related JIRA: JBIDE-24484
> Question 1:
> This was only deprecation? This feature was already in central and not included in the coretools feature? Just checking.
> Looks like this was the case - I found this:
> https://github.com/jbosstools/jbosstools-freemarker/pull/79/files
> Question 2:
> Shouldn't we include a N&N note on deprecation / move of Seam 3 stuff? I think we should.
> More details on those changes here:
> JBDS-4495
> JBIDE-24379
> TL;DR: These features are both deprecated and moved to central:
> org.jboss.tools.cdi.seam.feature
> org.jboss.tools.runtime.seam.detector.feature
> We're a bit confused about the seam (2) runtime detector, we thought that was already gone. We can ignore that. What we probably want to say is that Seam 3 feature / tooling has been deprecated and moved to Central.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24832) Some info on deprecated stuff / move to central missing in N&N
by Martin Malina (JIRA)
Martin Malina created JBIDE-24832:
-------------------------------------
Summary: Some info on deprecated stuff / move to central missing in N&N
Key: JBIDE-24832
URL: https://issues.jboss.org/browse/JBIDE-24832
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: website
Affects Versions: 4.5.0.Final
Reporter: Martin Malina
Assignee: Jeff MAURY
Fix For: 4.5.0.Final
The N&N page for 4.5.0.Final currently only has this:
http://tools.stage.jboss.org/documentation/whatsnew/jbosstools/4.5.0.Fina...
Freemarker component deprecation
The Freemarker component has been marked deprecated as there is no more maintenance on the source code. It is still available in Red Hat Central and may be removed in the future.
Related JIRA: JBIDE-24484
Question 1:
This was only deprecation? This feature was already in central and not included in the coretools feature? Just checking.
Looks like this was the case - I found this:
https://github.com/jbosstools/jbosstools-freemarker/pull/79/files
Question 2:
Shouldn't we include a N&N note on deprecation / move of Seam 3 stuff? I think we should.
More details on those changes here:
JBDS-4495
JBIDE-24379
TL;DR: These features are both deprecated and moved to central:
org.jboss.tools.cdi.seam.feature
org.jboss.tools.runtime.seam.detector.feature
We're a bit confused about the seam (2) runtime detector, we thought that was already gone. We can ignore that. What we probably want to say is that Seam 3 feature / tooling has been deprecated and moved to Central.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24831) Race condition between launching minishift and adding debug listener
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24831?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24831:
-------------------------------------
This is most easily replicatable by using 'kvm' when your system doesn't have kvm. Output would quickly result in something like this:
{code}
Starting local OpenShift cluster using 'kvm' hypervisor...
E0808 10:38:15.319627 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
E0808 10:38:15.320522 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
E0808 10:38:15.320598 22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
{code}
Then the process terminates, before the listener has been added, and the server is stuck in 'starting' mode.
> Race condition between launching minishift and adding debug listener
> --------------------------------------------------------------------
>
> Key: JBIDE-24831
> URL: https://issues.jboss.org/browse/JBIDE-24831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> The current code does the following:
> 1) Launch the process
> 2) Then add the debugListener to o.e.debug
> This is problematic. If the process ends very quickly,. our listener will never get alerted that the process terminated, and so the server will be stuck at 'starting'.
> Solution is to add the debugListener BEFORE launching the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24831) Race condition between launching minishift and adding debug listener
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24831?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-24831:
-----------------------------------
Assignee: Rob Stryker
> Race condition between launching minishift and adding debug listener
> --------------------------------------------------------------------
>
> Key: JBIDE-24831
> URL: https://issues.jboss.org/browse/JBIDE-24831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> The current code does the following:
> 1) Launch the process
> 2) Then add the debugListener to o.e.debug
> This is problematic. If the process ends very quickly,. our listener will never get alerted that the process terminated, and so the server will be stuck at 'starting'.
> Solution is to add the debugListener BEFORE launching the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24831) Race condition between launching minishift and adding debug listener
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-24831:
-----------------------------------
Summary: Race condition between launching minishift and adding debug listener
Key: JBIDE-24831
URL: https://issues.jboss.org/browse/JBIDE-24831
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.5.0.Final
Reporter: Rob Stryker
The current code does the following:
1) Launch the process
2) Then add the debugListener to o.e.debug
This is problematic. If the process ends very quickly,. our listener will never get alerted that the process terminated, and so the server will be stuck at 'starting'.
Solution is to add the debugListener BEFORE launching the process.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months