[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25664?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-25664 at 2/26/18 5:48 AM:
----------------------------------------------------------------
Rob sent me the email thread. It seems that at first Rob tried to add logic to handle the situation when the jboss.org credentials stop working in the future. But eventually he ended up removing the jboss.org domain from the gui rightway.
I verified this in devstudio-11.3.0.AM2-v20180226-0716-B2118-installer-standalone.jar . Downloads using developers.redhat.com credentials continue to work.
was (Author: mmalina):
Rob sent me the email thread. It seems that at first Rob tried to add logic to handle the situation when the jboss.org credentials stop working in the future. But eventually he ended up removing the jboss.org domain from the gui rightway.
I verified this in devstudio-11.3.0.AM2-v20180226-0716-B2118-installer-standalone.jar . Unfortunately it seems logging in at developers.redhat.com is currently down and I wanted to verify that continues to work. So I will not close this JIRA until it works again.
> Sunsetting download manager jboss.org accounts
> ----------------------------------------------
>
> Key: JBIDE-25664
> URL: https://issues.jboss.org/browse/JBIDE-25664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.5.3.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
>
> jboss.org accounts will be deprecated for downloadmanager.
> See email thread for more information, or, add more information here as it becomes available.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25664) Sunsetting download manager jboss.org accounts
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25664?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25664:
---------------------------------------
Rob sent me the email thread. It seems that at first Rob tried to add logic to handle the situation when the jboss.org credentials stop working in the future. But eventually he ended up removing the jboss.org domain from the gui rightway.
I verified this in devstudio-11.3.0.AM2-v20180226-0716-B2118-installer-standalone.jar . Unfortunately it seems logging in at developers.redhat.com is currently down and I wanted to verify that continues to work. So I will not close this JIRA until it works again.
> Sunsetting download manager jboss.org accounts
> ----------------------------------------------
>
> Key: JBIDE-25664
> URL: https://issues.jboss.org/browse/JBIDE-25664
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.5.3.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.3.AM2
>
>
> jboss.org accounts will be deprecated for downloadmanager.
> See email thread for more information, or, add more information here as it becomes available.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBDS-4679) Installation Guide - spelling of dependencies incorrect in section 7.2
by Deborah Rieden (JIRA)
Deborah Rieden created JBDS-4679:
------------------------------------
Summary: Installation Guide - spelling of dependencies incorrect in section 7.2
Key: JBDS-4679
URL: https://issues.jboss.org/browse/JBDS-4679
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: documentation
Affects Versions: 11.1.0.GA
Reporter: Deborah Rieden
In the Installation Guide:
The word "dependencies" is mispelled in the following section:
# 7.2. Installing JBoss Developer Studio and its Dependencies
# To install JBoss Developer Studio and all the debendencies, run the following command:
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25748) Discovery of "foreign" bean types for JSF auto-complete
by Thies . (JIRA)
Thies . created JBIDE-25748:
-------------------------------
Summary: Discovery of "foreign" bean types for JSF auto-complete
Key: JBIDE-25748
URL: https://issues.jboss.org/browse/JBIDE-25748
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdi, jsf
Affects Versions: 4.5.2.Final
Environment: Eclipse Oxygen, but every version should be affected.
Also every version of JBoss Tools since 2012 (last change date of the modified files below).
Reporter: Thies .
Auto-complete in JSF supports {{@ManagedBean}} and {{@Named}}, fine.
But it is also possible to use "foreign" beans, concretely Spring via {{@Controller}}.
I manually implemented a "hack" (see also https://stackoverflow.com/questions/48933757/el-autocomplete-code-assist-...) by simply extending a single classes method.
For JSF only extend class {{org.jboss.tools.jsf.jsf2.bean.model.impl.AbstractMemberDefinition}} methods {{getManagedBeanAnnotation()}} and {{isAnnotationPresent()}}:
{code:java}
public boolean isAnnotationPresent(String annotationTypeName) {
//TW: added Spring annotations
boolean b = (getAnnotation(annotationTypeName) != null);
if (!b && JSF2Constants.MANAGED_BEAN_ANNOTATION_TYPE_NAME.equals(annotationTypeName)) {
b = (getAnnotation("org.springframework.stereotype.Controller") != null);
/* with support for all Spring annotations:
b = (getAnnotation("org.springframework.stereotype.Controller") != null
|| getAnnotation("org.springframework.stereotype.Service") != null
|| getAnnotation("org.springframework.stereotype.Repository") != null
|| getAnnotation("org.springframework.stereotype.Component") != null);
*/
}
return b;
}
public AnnotationDeclaration getManagedBeanAnnotation() {
AnnotationDeclaration ad = annotationsByType.get(JSF2Constants.MANAGED_BEAN_ANNOTATION_TYPE_NAME);
//TW: added Spring annotations
if (ad != null) return ad;
ad = annotationsByType.get("org.springframework.stereotype.Controller");
/* with support for all Spring annotations:
if (ad == null) ad = annotationsByType.get("org.springframework.stereotype.Service");
if (ad == null) ad = annotationsByType.get("org.springframework.stereotype.Repository");
if (ad == null) ad = annotationsByType.get("org.springframework.stereotype.Component");
*/
if (ad != null) {
// create wrapper to map "value" (used by Spring) to "name" (which is used by @ManageBean)
ad = new AnnotationDeclaration() {
private AnnotationDeclaration wrapped;
AnnotationDeclaration init(AnnotationDeclaration wrappedAD) {
this.wrapped = wrappedAD;
return this;
}
@Override
public Object getMemberValue(String name) {
Object val = wrapped.getMemberValue(name);
if (val == null && "name".equals(name)) {
val = wrapped.getMemberValue(null);
}
return val;
}
@Override
public Object getMemberValue(String name, boolean resolve) {
Object result = null;
if (resolve) {
result = this.getMemberConstantValue(name);
}
if (result == null) {
result = this.getMemberValue(name);
}
return result;
}
@Override
public void setDeclaration(IJavaAnnotation annotation) {
wrapped.setDeclaration(annotation);
}
@Override
public IJavaAnnotation getDeclaration() {
return wrapped.getDeclaration();
}
@Override
public IResource getResource() {
return wrapped.getResource();
}
@Override
public IMemberValuePair[] getMemberValuePairs() {
return wrapped.getMemberValuePairs();
}
@Override
public Object getMemberConstantValue(String name) {
return wrapped.getMemberConstantValue(name);
}
@Override
public Object getMemberDefaultValue(String name) {
return wrapped.getMemberDefaultValue(name);
}
@Override
public IMember getParentMember() {
return wrapped.getParentMember();
}
@Override
public String getTypeName() {
return wrapped.getTypeName();
}
@Override
public IType getType() {
return wrapped.getType();
}
@Override
public int getLength() {
return wrapped.getLength();
}
@Override
public int getStartPosition() {
return wrapped.getStartPosition();
}
@Override
public IAnnotationType getAnnotation() {
return wrapped.getAnnotation();
}
@Override
public IAnnotation getJavaAnnotation() {
return wrapped.getJavaAnnotation();
}
@Override
public IMember getSourceMember() {
return wrapped.getSourceMember();
}
@Override
public IJavaElement getSourceElement() {
return wrapped.getSourceElement();
}
}.init(ad); // class
}
return ad;
}
{code}
For CDI extend class {{org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition}} method {{getNamedAnnotation()}}:
{code:java}
public AnnotationDeclaration getNamedAnnotation() {
AnnotationDeclaration ad = getAnnotation(CDIConstants.NAMED_QUALIFIER_TYPE_NAME);
//TW: added Spring annotations
if (ad != null) return ad;
ad = getAnnotation("org.springframework.stereotype.Controller");
/* add additional Spring annotations, if desired:
if (ad != null) return ad;
ad = getAnnotation("org.springframework.stereotype.Service");
if (ad != null) return ad;
ad = getAnnotation("org.springframework.stereotype.Repository");
if (ad != null) return ad;
ad = getAnnotation("org.springframework.stereotype.Component");
*/
return ad;
}
{code}
Best would be to offer a preferences String, that allows to add arbitrary annotations - maybe even a project specific setting.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25737) Openshif IO login window triggers error dialog when closed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25737?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25737:
------------------------------------
There is no way with OSIO to get login error. Either your OAuth callback gets called positively either the browser stays on the login page.
So as the OSIO component is about getting a token or throwing an error, if the user closes the dialog before login is complete, then error is thrown. Maybe throwing an InterruptedException would be better in this case.
> Openshif IO login window triggers error dialog when closed
> ----------------------------------------------------------
>
> Key: JBIDE-25737
> URL: https://issues.jboss.org/browse/JBIDE-25737
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM1
> Environment: Windows 10 Pro
> Reporter: Denis Golovin
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
> Attachments: OSIOLoginError.mp4
>
>
> The error dialog reads: "Error login to cluster OpenShift.io".
> !OSIOLoginError.mp4|id=media!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25736:
-------------------------------
Description:
This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
* jbosstools-portlet
* jbosstools-aerogear
* jbosstools-browsersim
* jbosstools-livereload
* {color:red}-jbosstools-webservices-{color}
* {color:red}-jbosstools-javaee-{color}
* {color:red}-jbosstools-forge-{color}
These projects could be *removed*, since they were deprecated some time ago:
* jbosstools-freemarker
* jbosstools-arquillian
For supporting arguments, see this doc (RH only, sorry):
https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
was:
This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
* jbosstools-portlet
* jbosstools-aerogear
* jbosstools-browsersim
* jbosstools-livereload
* jbosstools-webservices
* jbosstools-javaee
* -jbosstools-forge-
These projects could be *removed*, since they were deprecated some time ago:
* jbosstools-freemarker
* jbosstools-arquillian
For supporting arguments, see this doc (RH only, sorry):
https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider *deprecating* the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * {color:red}-jbosstools-webservices-{color}
> * {color:red}-jbosstools-javaee-{color}
> * {color:red}-jbosstools-forge-{color}
> These projects could be *removed*, since they were deprecated some time ago:
> * jbosstools-freemarker
> * jbosstools-arquillian
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month