[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 updated JBIDE-22128:
--------------------------------
Labels: respin-b (was: )
> 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
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> 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 reassigned JBIDE-22128:
-----------------------------------
Assignee: Fred Bricon
> 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
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> 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 updated JBIDE-22128:
--------------------------------
Fix Version/s: 4.3.1.CR1
> 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
> Fix For: 4.3.1.CR1
>
>
> 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:
-------------------------------------
So we actually have 2 problems here:
- the openshift app was not created from a template, and we don't detect it's an EAP kind of server. The current detection mechanism is very brittle, we can make it a tiny bit better by checking if the name of the image contains eap or wildfly. That will fix the immediate issue (EAP server profile automatically tries to create a ROOT.war) but that won't be a long term solution I guess. I have a PR coming for this.
- the maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> 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] (JBTIS-648) Improve the tracking of BPMN2 issues
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.... ]
Robert (Bob) Brodt commented on JBTIS-648:
------------------------------------------
Hey [~maxandersen] can you give us some guidance here, based on your previous experiences with Eclipse projects & JBDS?
> Improve the tracking of BPMN2 issues
> ------------------------------------
>
> Key: JBTIS-648
> URL: https://issues.jboss.org/browse/JBTIS-648
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: BPMN2
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Priority: Critical
>
> Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/).
> Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles.
> In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla).
> Other solutions could be
> * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ)
> * or move the whole project to the Jira JBoss Tools
> What do you think? Do you have any ideas how to improve the process?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-21351.
------------------------------------
Resolution: Done
+1 to include it to respin-b. Resolving. [~nickboldt] please make sure it's included in CR1 this time.
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22136) IllegalArgumentException thrown when starting debug mode with services missing env vars
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22136?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22136:
-------------------------------------
{noformat}
java.lang.IllegalArgumentException
at org.jboss.dmr.ModelValue.asList(ModelValue.java:140)
at org.jboss.dmr.ModelNode.asList(ModelNode.java:1384)
at com.openshift.internal.restclient.model.ReplicationController.setEnvironmentVariable(ReplicationController.java:78)
at com.openshift.internal.restclient.model.ReplicationController.setEnvironmentVariable(ReplicationController.java:61)
{noformat}
> IllegalArgumentException thrown when starting debug mode with services missing env vars
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22136
> URL: https://issues.jboss.org/browse/JBIDE-22136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Critical
> Labels: respin-b
> Fix For: 4.3.1.CR1
>
>
> Create an openshift app following the steps from https://htmlpreview.github.io/?https://github.com/redhat-helloworld-msa/h...
> After importing the maven project in eclipse and creating a server adapter, if you try to start in debug mode, an exception will be thrown because we're trying to update the env var list in the deployment config, but it doesn't already exists
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years