[JBoss JIRA] (JBDS-3200) Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-3200?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-3200:
---------------------------------------
[~mmalina] - yep, I can update the docs regarding this. What is the situation on Windows? If the user right-clicks the .jar on Windows, what is the option the user needs to click - is it open or run?
> Provide JBoss Developer studio from Mac App Store or identified developer to prevent warning
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-3200
> URL: https://issues.jboss.org/browse/JBDS-3200
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 8.0.0.GA
> Environment: Mac OS X 10.10, JDK 1.8.0
> Reporter: Manuel Blechschmidt
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: LATER
>
> Attachments: Screen Shot 2014-10-26 at 11.10.30.png, Screen Shot 2014-10-26 at 11.11.53.png
>
>
> Hello,
> I just downloaded the new installer for JBoss Developer Studio 8.0.0.GA from here:
> https://access.cdn.redhat.com/content/origin/files/sha256/9f/9f3fab096014...
> Download was very fast. Afterwards I double clicked on the installer. Unfortunately it showed me a message that I can only install applications from the mac app store.
> {panel}
> "jboss-devstudio-8.0.0.GA-v20141020-1042-B317-installer-eap.jar" can't be opened because it is from an unidentified developer.
> Your security preferences allow installation of only app from the Mac App Store and identified developers.
> {panel}
> Right click on the file and then selecting open gives me the opportunity to ignore this warning.
> Nevertheless it might happen that users don't know this solution.
> Hope that helps
> Manuel
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-17923) Support CDI 1.2
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17923?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-17923:
-----------------------------------------------
A useful link for diff between 1.1 and 1.2 https://docs.jboss.org/cdi/spec/1.2/cdi-spec-diff.html
Diffs that require implementation in JBoss CDI Tools:
1. The set of bean defining annotations for the 'annotated' bean discovery mode is changed. (2.5, 12.4.1)
2. An array type is not a legal bean type if its component type is not a legal bean type. (2.2.1, 3.3, 3.4)
3. Clarification: An observer method will be notified of an event if the event object is assignable to the observed event type, and if the _set of_ observed event qualifiers _is a subset of all_ the event qualifiers of the event. (10 - we have to check if we interpreted specs 1.0 and 1.1 in that way)
4. Section 'Firing events' (10.3) looks totally rewritten, but comparing old 10.3 to new 10.2, I have found only that
previous 'or the @Any qualifier may be used, allowing the application to specify qualifiers dynamically' changed to 'or the application may specify qualifiers dynamically' (both cases imply that there are no other specified qualifiers). Probably, that does not influence what we implemented for resolving event qualifiers, but we have to check it.
> Support CDI 1.2
> ---------------
>
> Key: JBIDE-17923
> URL: https://issues.jboss.org/browse/JBIDE-17923
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdi
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> CDI 1.2 spec was released on april 14th, 2014 : http://www.cdi-spec.org/news/2014/04/14/CDI-1_2-released/
> Apparently, minor things went in, but I assume some validation rules will need to be updated, along adding a CDI 1.2 Facet
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17180:
--------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.x)
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18699) Angular.js is present in both supported and Early Access
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18699?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-18699:
-------------------------------------
Ahh, I haven't noticed these are two different installations. Now looking at the description, it does not same the same thing.
Is there a chance that icon or title could be different to make this less confusing while keeping id the same?
> Angular.js is present in both supported and Early Access
> --------------------------------------------------------
>
> Key: JBIDE-18699
> URL: https://issues.jboss.org/browse/JBIDE-18699
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8.0.0.GA
> Reporter: Karel Piwko
> Assignee: Max Rydahl Andersen
> Attachments: early-access.png, no-early-access.png
>
>
> If I click on enable early access in JBoss Central page Software/Update tab, Angular JS is in Early access.
> However, it is in supported as well. I guess only Arquillian should pop up in early access.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months