[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4687 at 3/14/18 9:30 AM:
-----------------------------------------------------------
To be clear, we're renaming the SERVER/RUNTIME to "Red Hat Fuse", not the TOOLS (which should remain "Red Hat JBoss Fuse Tools")... correct?
So, I would change these:
{code}
"label":"JBoss Fuse Server",
"description":"Fuse Server/ Runtime",
<description>Tools to allow you to create Apache Camel routes in a graphical editor, launch
them locally and deploy them to runtimes like Apache Karaf, Fabric8 and JBoss Fuse.</description>
{code}
but not these:
{code}
"label" :"JBoss Fuse Tooling",
featureName=Red Hat JBoss Fuse Tools
description=This feature contains all the features of JBoss Fuse Tools.
additionalSummaryInfo = additionalSummaryInfo.concat("Red Hat JBoss Fuse Tooling<br>");
<category-def name="FuseTools" label="JBoss Fuse Tools">
{code}
Adding [~mikgue] and [~rkratky] to cc: so they're aware of this upcoming change to marketing / docs.
was (Author: nickboldt):
To be clear, we're renaming the SERVER/RUNTIME to "Red Hat Fuse", not the TOOLS (which should remain "Red Hat JBoss Fuse Tools")... correct?
So, I would change these:
{code}
"label":"JBoss Fuse Server",
"description":"Fuse Server/ Runtime",
<description>Tools to allow you to create Apache Camel routes in a graphical editor, launch them locally and deploy them to runtimes like Apache Karaf, Fabric8 and JBoss Fuse.</description>
{code}
but not these:
{code}
"label" :"JBoss Fuse Tooling",
featureName=Red Hat JBoss Fuse Tools
description=This feature contains all the features of JBoss Fuse Tools.
additionalSummaryInfo = additionalSummaryInfo.concat("Red Hat JBoss Fuse Tooling<br>");
<category-def name="FuseTools" label="JBoss Fuse Tools">
{code}
Adding [~mikgue] and [~rkratky] to cc: so they're aware of this upcoming change to marketing / docs.
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
> ------------------------------------------------------
>
> Key: JBDS-4687
> URL: https://issues.jboss.org/browse/JBDS-4687
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 11.3.0.AM3
>
>
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4687:
----------------------------------
To be clear, we're renaming the SERVER/RUNTIME, not the TOOLS... correct?
So, I would change these:
{code}
"label":"JBoss Fuse Server",
"description":"Fuse Server/ Runtime",
<description>Tools to allow you to create Apache Camel routes in a graphical editor, launch them locally and deploy them to runtimes like Apache Karaf, Fabric8 and JBoss Fuse.</description>
{code}
but not these:
{code}
"label" :"JBoss Fuse Tooling",
featureName=Red Hat JBoss Fuse Tools
description=This feature contains all the features of JBoss Fuse Tools.
additionalSummaryInfo = additionalSummaryInfo.concat("Red Hat JBoss Fuse Tooling<br>");
<category-def name="FuseTools" label="JBoss Fuse Tools">
{code}
Adding [~mikgue] and [~rkratky] to cc: so they're aware of this upcoming change to marketing / docs.
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
> ------------------------------------------------------
>
> Key: JBDS-4687
> URL: https://issues.jboss.org/browse/JBDS-4687
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 11.x
>
>
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4687 at 3/14/18 9:29 AM:
-----------------------------------------------------------
To be clear, we're renaming the SERVER/RUNTIME to "Red Hat Fuse", not the TOOLS (which should remain "Red Hat JBoss Fuse Tools")... correct?
So, I would change these:
{code}
"label":"JBoss Fuse Server",
"description":"Fuse Server/ Runtime",
<description>Tools to allow you to create Apache Camel routes in a graphical editor, launch them locally and deploy them to runtimes like Apache Karaf, Fabric8 and JBoss Fuse.</description>
{code}
but not these:
{code}
"label" :"JBoss Fuse Tooling",
featureName=Red Hat JBoss Fuse Tools
description=This feature contains all the features of JBoss Fuse Tools.
additionalSummaryInfo = additionalSummaryInfo.concat("Red Hat JBoss Fuse Tooling<br>");
<category-def name="FuseTools" label="JBoss Fuse Tools">
{code}
Adding [~mikgue] and [~rkratky] to cc: so they're aware of this upcoming change to marketing / docs.
was (Author: nickboldt):
To be clear, we're renaming the SERVER/RUNTIME, not the TOOLS... correct?
So, I would change these:
{code}
"label":"JBoss Fuse Server",
"description":"Fuse Server/ Runtime",
<description>Tools to allow you to create Apache Camel routes in a graphical editor, launch them locally and deploy them to runtimes like Apache Karaf, Fabric8 and JBoss Fuse.</description>
{code}
but not these:
{code}
"label" :"JBoss Fuse Tooling",
featureName=Red Hat JBoss Fuse Tools
description=This feature contains all the features of JBoss Fuse Tools.
additionalSummaryInfo = additionalSummaryInfo.concat("Red Hat JBoss Fuse Tooling<br>");
<category-def name="FuseTools" label="JBoss Fuse Tools">
{code}
Adding [~mikgue] and [~rkratky] to cc: so they're aware of this upcoming change to marketing / docs.
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x
> ------------------------------------------------------
>
> Key: JBDS-4687
> URL: https://issues.jboss.org/browse/JBDS-4687
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Aurélien Pupier
> Assignee: Nick Boldt
> Fix For: 11.x
>
>
> Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25303 at 3/14/18 6:45 AM:
-------------------------------------------------------------------
[~jkopriva] I finally noticed that the [^fuse-on-openshift.zip] example was missing the devtools dependency and the inclusion of devtools when packaging in it's pom:
{code}
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<optional>true</optional>
</dependency>
{code}
{code}
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludeDevtools>false</excludeDevtools>
</configuration>
</plugin>
{code}
I corrected the zip and re-attached it to this issue. You now should have the springboot application running from an exploded jar.
Can you check this again please?
was (Author: adietish):
[~jkopriva] I finally noticed that the "fuse-on-openshift" example was missing the devtools dependency and the inclusion of devtools when packaging in it's pom:
{code}
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<optional>true</optional>
</dependency>
{code}
{code}
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludeDevtools>false</excludeDevtools>
</configuration>
</plugin>
{code}
I corrected the zip and re-attached it to this issue. You now should have the springboot application running from an exploded jar.
Can you check this again please?
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.3.AM3
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> ** -Dfabric8.generator.from=fabric8/s2i-java
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months