[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22128:
-------------------------------------
I'm using the CDK v2Beta5, but I can't create the imagestream
{noformat}
oc create -n helloworld-msa -f https://raw.githubusercontent.com/jboss-openshift/application-templates/m...
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
Error from server: User "openshift-dev" cannot create imagestreams in project "helloworld-msa"
{noformat}
[~hardy.ferentschik] how do we escalate the problem to the CDK?
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Rafael Benevides commented on JBIDE-22128:
------------------------------------------
The steps and projects that I used to create the EAP project are here: https://htmlpreview.github.io/?https://github.com/redhat-helloworld-msa/h...
After that, I selected the project in the openshift plugin and clicked on "Server Adapter". On the Servers tab, the "hello" project is presented and the console shows hello.war and not ROOT.war. The name was also verified by logging in the pod.
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20387:
----------------------------------------
[~ddekany] sorry for the delay. We have limited resources to verify the PRs. Hope we can find time to review them for the next JBoss Tools release targeted Eclipse Neon.
> Use column number when navigating to errors, and more
> -----------------------------------------------------
>
> Key: JBIDE-20387
> URL: https://issues.jboss.org/browse/JBIDE-20387
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}):
> * {{getColumnNumber()}}, {{getEndColumnNumber()}}
> * {{getEndLineNumber()}}
> * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20491) "incompatibleImprovements" setting should be set
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20491:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.x)
(was: 4.4.x)
> "incompatibleImprovements" setting should be set
> ------------------------------------------------
>
> Key: JBIDE-20491
> URL: https://issues.jboss.org/browse/JBIDE-20491
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> Where the {{freemarker.template.Configuration}} is created, the {{incompatibleImprovements}} setting shouldn't be left on its default, 2.3.0. It should be set to {{Configuration.getVersion()}} (like {{new Configuration(Configuration.getVersion())}}, or with {{config.setIncompatibleImprovements(Configuration.getVersion())}}).
> Why: The plugin doesn't execute the templates, just parses them. As of 2.3.24, all the "incompatible" fixes that affect the parser (not the execution) just makes it stricter by eliminating legacy parser glitches that let through things that are pretty much always just user oversights. Also when 2.3.24 is out, the new {{ftlh}} and {{ftlx}} file extensions, which affect parsing, will only have effect with {{incompatibleImprovements}} 2.3.24.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20387:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.x)
> Use column number when navigating to errors, and more
> -----------------------------------------------------
>
> Key: JBIDE-20387
> URL: https://issues.jboss.org/browse/JBIDE-20387
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}):
> * {{getColumnNumber()}}, {{getEndColumnNumber()}}
> * {{getEndLineNumber()}}
> * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-22128 at 4/6/16 6:16 PM:
-------------------------------------------------------------
Ok but how did you setup the *OpenShift* project (as an OpenShift resource)? Please provide the *exact* steps you followed to create the OpenShift application.
was (Author: fbricon):
Ok but how did you setup the *OpenShift* project? Please provide the *exact* steps you followed to create the OpenShift application.
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22128) Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22128?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22128:
-------------------------------------
Ok but how did you setup the *OpenShift* project? Please provide the *exact* steps you followed to create the OpenShift application.
> Openshift 3 plugin "Server Adapter" doesn't respect openshift maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-22128
> URL: https://issues.jboss.org/browse/JBIDE-22128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
>
> I have a Java project with an "openshift" maven profile that creates a ROOT.war
> When I create a "Server Adapter", the openshift plugins deploys the name of the project.war
> The plugin should be integrated with M2E in a way that if I select/enable the "openshift" profile on M2E, the Openshift plugin should deploy ROOT.war through "Server Adapter".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22130) Update FreeMarker to 2.3.24
by Daniel Dekany (JIRA)
Daniel Dekany created JBIDE-22130:
-------------------------------------
Summary: Update FreeMarker to 2.3.24
Key: JBIDE-22130
URL: https://issues.jboss.org/browse/JBIDE-22130
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: freemarker
Reporter: Daniel Dekany
The {{freemarker}} dependency should be updated so that it doesn't show error for the new core directives/built-ins.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years