[JBoss JIRA] (JBIDE-21352) OpenShift Server Adapter: New server adapter could use preselected project from project explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21352?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21352:
------------------------------------------
hmm, good point indeed.
The problem is actually that you can select some project is package-/project-explorer/navigator and get over to the servers view. In this case there's none of the project listing views that is active (the servers view is active) and afaics there's no way for me to find out which one of the 3 is visible.
I could use a mix: try the active view (to see if I can get a project from it) and if I cannot, fallback to the fixed precedence?
> OpenShift Server Adapter: New server adapter could use preselected project from project explorer
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21352
> URL: https://issues.jboss.org/browse/JBIDE-21352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.Beta2
>
>
> It would be nice if wizard to create a new OpenShift 3 server adapter would use preselected project from Project explorer, if it is opened and selected. Currently it uses first eclipse project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21323) EL Knowledge Base Problem with enums
by Andrei Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21323?page=com.atlassian.jira.plugi... ]
Andrei Ivanov updated JBIDE-21323:
----------------------------------
Description:
Enum properties and method are not recognized:
In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
{code:xml}
<p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
...
</p:dataTable>
{code}
{code:java}
public enum SignOffStatus {
VALID("Valid"),
ALMOST_EXPIRED("Almost expired"),
EXPIRED("Expired");
private final String label;
private SignOffStatus(String label) {
this.label = label;
}
public String getLabel() {
return label;
}
}
{code}
In a different page:
{code:xml}
<p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
<f:selectItem itemLabel="--select--" itemValue="#{null}" />
<f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
</p:selectOneMenu>
{code}
The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"label" cannot be resolved}}).
was:
Enum properties and method are not recognized:
In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
{code:xml}
<p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
...
</p:dataTable>
{code}
{code:java}
public enum SignOffStatus {
VALID("Valid"),
ALMOST_EXPIRED("Almost expired"),
EXPIRED("Expired");
private final String label;
private SignOffStatus(String label) {
this.label = label;
}
public String getLabel() {
return label;
}
}
{code}
In a different page:
{code:xml}
<p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
<f:selectItem itemLabel="--select--" itemValue="#{null}" />
<f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
</p:selectOneMenu>
{code}
The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"name" cannot be resolved}}).
> EL Knowledge Base Problem with enums
> ------------------------------------
>
> Key: JBIDE-21323
> URL: https://issues.jboss.org/browse/JBIDE-21323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> Enum properties and method are not recognized:
> In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
> {code:xml}
> <p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
> rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
> ...
> </p:dataTable>
> {code}
> {code:java}
> public enum SignOffStatus {
> VALID("Valid"),
> ALMOST_EXPIRED("Almost expired"),
> EXPIRED("Expired");
> private final String label;
> private SignOffStatus(String label) {
> this.label = label;
> }
> public String getLabel() {
> return label;
> }
> }
> {code}
> In a different page:
> {code:xml}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"label" cannot be resolved}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21335) CDK stuck on Starting state when you forget to enter credentials
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21335?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21335.
---------------------------------
Verified in jboss-devstudio-9.1.0.Beta1-v20151216-2040-B197-installer-standalone.jar. I checked that the commit is also present in other branches.
> CDK stuck on Starting state when you forget to enter credentials
> ----------------------------------------------------------------
>
> Key: JBIDE-21335
> URL: https://issues.jboss.org/browse/JBIDE-21335
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> I added CDK using runtime detection. Then I tried to start it. First attempt failed on missing path to vagrant. I provided that and then tried to start it again. This time it complained I didn't enter the credentials. But unfortunately after this the server adapter is stuck on Starting... There is no way to press start or stop and there is no console output. I guess I either have to wait for it to time out or just restart Eclipse.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21233:
---------------------------------------------
a) sorry, but did not follow that answer at all. Did not answer my question on whether this would be affecting only the final public updatessites or also the internal ones used for builds. If it affects the latter then I don't see how we can build reliably.
b) You are now showing me something that should *not* happen. This TP should not be listed in the list of available updatesites. That is a bug and something that should never have happened. This is why we moved to use the p2 associate sites(not sure if right term) since it avoided it to be shown in here, and we didn't use composite sites in the past since it caused problems with content showing up in uncategorized. Is that fixed ? Are you saying that at some point we moved back from the lower level p2 concept (that does not show up in p2 update ui) to use associate sites and this jira is about undoing that mistake ?
c) If you refute this statement then I don't know what to say. That is and has been a goal for years to avoid building larger and larger releases.
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt-creeping-update-sites.png
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19178:
---------------------------------------------
If properties view gets enriched like this we should make sure Properties view in the JBoss Perspective is in a visible by default location.
btw. I like this since it makes it much less noisy.
looking forward to try play with it.
> Explorer, Servers view: Add logical view to OpenShift v3 explorer
> -----------------------------------------------------------------
>
> Key: JBIDE-19178
> URL: https://issues.jboss.org/browse/JBIDE-19178
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_v3
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png
>
>
> Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16970 at 12/17/15 10:54 PM:
---------------------------------------------------------------
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... shows SHA check kicked the deployment, because no significant change in the build input (just a README change in the jbosstools-build-sites project). THEREFORE *working*!
Still trying to perfect the devstudio.product check as we don't want any IUs that change w/ every build (eg., com.jboss.devstudio.* and tooling*).
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=4406
was (Author: nickboldt):
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... shows SHA check kicked the deployment, because no significant change in the build input (just a README change in the jbosstools-build-sites project)
Still trying to perfect the devstudio.product check as we don't want any IUs that change w/ every build (eg., com.jboss.devstudio.* and tooling*).
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=4406
> create mechanism to verify that nightly build is different from previous milestone
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-16970
> URL: https://issues.jboss.org/browse/JBIDE-16970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.x
>
>
> After the discovery site build job is done, we should:
> * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case)
> * for respins, use *job param* label = "respin-a" or "respin-b" in jira query
> * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6
> * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet...
> * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder)
> * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/
> * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal...
> * run p2diff on the two repos - see https://github.com/irbull/p2diff
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21357) Missing dialog messages for publishing via server adapter on OpenShift 2 applications
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21357?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21357 at 12/17/15 9:44 PM:
-------------------------------------------------------------------------
ExpressServerMessages.BUNDLE_NAME is incorrect. It helps to avoid strings in such cases, when possible:
{code}
BUNDLE_NAME = ExpressServerMessages.class.getName();
{code}
It will work because the name of property file the same - ExpressServerMessages (and it might survive rename-move).
was (Author: scabanovich):
ExpressServerMessages.BUNDLE_NAME is incorrect. It helps to avoid strings in such cases, when possible:
{code}
BUNDLE_NAME = ExpressServerMessages.class.getName();
{code}
It will work because the name of property file the same - ExpressServerMessages.
> Missing dialog messages for publishing via server adapter on OpenShift 2 applications
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21357
> URL: https://issues.jboss.org/browse/JBIDE-21357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
> Attachments: publish_msg.png, publish_msg_no_changes.png
>
>
> When I am trying to publish code to OpenShift 2 application via server adapter, there are dialogs which contains missing msg info instead of message. First one is in case of publishing no changes, another one is when I create a new OpenShift 2 application from local eclipse project via deploying to OpenShift in context menu of the eclipse project and then select Publish in context menu of server adapter. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21357) Missing dialog messages for publishing via server adapter on OpenShift 2 applications
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21357?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21357:
-----------------------------------------------
ExpressServerMessages.BUNDLE_NAME is incorrect. It helps to avoid strings in such cases, when possible:
{code}
BUNDLE_NAME = ExpressServerMessages.class.getName();
{code}
It will work because the name of property file the same - ExpressServerMessages.
> Missing dialog messages for publishing via server adapter on OpenShift 2 applications
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21357
> URL: https://issues.jboss.org/browse/JBIDE-21357
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
> Attachments: publish_msg.png, publish_msg_no_changes.png
>
>
> When I am trying to publish code to OpenShift 2 application via server adapter, there are dialogs which contains missing msg info instead of message. First one is in case of publishing no changes, another one is when I create a new OpenShift 2 application from local eclipse project via deploying to OpenShift in context menu of the eclipse project and then select Publish in context menu of server adapter. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21352) OpenShift Server Adapter: New server adapter could use preselected project from project explorer
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21352?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21352:
-----------------------------------------------
Could it be good to change precedence in favour of the one of the three that is currently active?
Suppose all three are open in the left 'navigator' side of workbench and Project Explorer is active and shown while Package Explorer is presented with its tab only (but it has selection, other than selection in Project Explorer). Probably, not many users actively use several navigators, and if Project Explorer is active, the odds are high that there is no selection in the inactive Package Explorer; then selection in wizard is correct. But possibility remains that a user switched to Package Explorer to do something for which it is more handy, and then returned into his favourite Project Explorer. Then the selection in the wizard will be confusing.
> OpenShift Server Adapter: New server adapter could use preselected project from project explorer
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21352
> URL: https://issues.jboss.org/browse/JBIDE-21352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.Beta2
>
>
> It would be nice if wizard to create a new OpenShift 3 server adapter would use preselected project from Project explorer, if it is opened and selected. Currently it uses first eclipse project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months