[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 updated JBIDE-25303:
-------------------------------------
Fix Version/s: 4.5.3.AM3
(was: 4.5.2.Final)
> 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, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 2/28/18 10:18 AM:
--------------------------------------------------------------------
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/deployments/BOOT-INF/classes*) that *SHOULD* exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
ps. you can ssh to the pod via
{code}
oc rsh <pod-id>
{code}
was (Author: adietish):
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/BOOT-INF/classes) that *SHOULD* exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
> 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.2.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 2/28/18 10:18 AM:
--------------------------------------------------------------------
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/deployments/BOOT-INF/classes*) that *SHOULD* exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
ps. you can ssh to the pod via
{code}
oc rsh <pod-id>
{code}
was (Author: adietish):
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/deployments/BOOT-INF/classes*) that *SHOULD* exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
ps. you can ssh to the pod via
{code}
oc rsh <pod-id>
{code}
> 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.2.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 commented on JBIDE-25303:
------------------------------------------
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/BOOT-INF/classes) that **SHOULD** exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
> 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.2.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 2/28/18 10:17 AM:
--------------------------------------------------------------------
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/BOOT-INF/classes) that *SHOULD* exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
was (Author: adietish):
[~jkopriva] your error is different from mine. In your case it tries to copy files to a directory (/BOOT-INF/classes) that **SHOULD** exist. The only way I see this not being present is if the springboot application (fat) jar is not unpacked.
This could either happen if you're using the wrong docker image (fis image instead of fabric8/s2i-java) or the environment variables dont contain the JAVA_DEBUG variable that tells the docker image to unpack the jar. Can you please verify this?
> 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.2.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 commented on JBIDE-25303:
------------------------------------------
I can and then cannot reproduce the permissions issue that I faced in https://issues.jboss.org/browse/JBIDE-25303?focusedCommentId=13519836&pag... in CDK 3.3. I cannot determine yet what the reason might be. The anyuid addons is always enabled for me and doesnt seem involved.
When the permission issue occurrs the error looks very similar to what we see in OpenShift Online JBIDE-25700
> 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.2.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, fuse-on-openshift.zip, project-deployment-assembly.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)
8 years
[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 edited comment on JBIDE-25736 at 2/28/18 9:50 AM:
-------------------------------------------------------------
*REMOVALS*
Freemarker and Arquillian jobs have been disabled and their builds have been removed from the composite and aggregate sites. Their connectors have been removed from Central. As a result, the Early Access site [1] is now empty. Their repos have been tagged with "deprecated" and "deprecated-repo" tags, and their README.md files have been updated to note that these projects were removed from JBoss Tools as of 4.5.3.
[1] https://github.com/jbosstools/jbosstools-build-sites/commit/c348034dbc71b...
*DEPRECATIONS*
Portlet, Aerogear, Browsersim, and Livereload have been marked deprecated, and I've added deprecated tags to their github repos too:
https://github.com/jbosstools/jbosstools-portlet/blob/master/README.md (not currently being built so just marked the README.md file)
https://github.com/jbosstools/jbosstools-aerogear/commit/f1cbb77b02e69ce0...
https://github.com/jbosstools/jbosstools-browsersim/commit/c9154552caf1fc...
https://github.com/jbosstools/jbosstools-livereload/commit/cba8d71ef2e823...
https://github.com/jbosstools/jbosstools-central/commit/49444d205799c4059...
They all exist already in Central, but those connectors are now deprecated too.
https://github.com/jbosstools/jbosstools-discovery/commit/acf86dcb6f5e01d...
Note that the connector called "JBoss Hybrid Mobile Tools + CordovaSim" includes Aerogear, Browsersim, and Livereload. There's also a connector for LiveReload by itself, another for Portlet, and a 4th for Maven support for Portlets. I've marked all 4 deprecated.
I have *NOT* created new connectors solely for *Aerogear* and *Browsersim*. I can do so if requested but figure what we have already is good enough.
Would you agree [~rpdavis] [~jeffmaury] [~gercan] [~ibuziuk] ?
was (Author: nickboldt):
Freemarker and Arquillian jobs have been disabled and their builds have been removed from the composite and aggregate sites. Their connectors have been removed from Central. As a result, the Early Access site [1] is now empty. Their repos have been tagged with "deprecated" and "deprecated-repo" tags, and their README.md files have been updated to note that these projects were removed from JBoss Tools as of 4.5.3.
[1] https://github.com/jbosstools/jbosstools-build-sites/commit/c348034dbc71b...
Portlet, Aerogear, Browsersim, and Livereload have been marked deprecated, and I've added deprecated tags to their github repos too:
https://github.com/jbosstools/jbosstools-portlet/blob/master/README.md (not currently being built so just marked the README.md file)
https://github.com/jbosstools/jbosstools-aerogear/commit/f1cbb77b02e69ce0...
https://github.com/jbosstools/jbosstools-browsersim/commit/c9154552caf1fc...
https://github.com/jbosstools/jbosstools-livereload/commit/cba8d71ef2e823...
https://github.com/jbosstools/jbosstools-central/commit/49444d205799c4059...
They all exist already in Central, but those connectors are now deprecated too.
https://github.com/jbosstools/jbosstools-discovery/commit/acf86dcb6f5e01d...
Note that the connector called "JBoss Hybrid Mobile Tools + CordovaSim" includes Aerogear, Browsersim, and Livereload. There's also a connector for LiveReload by itself, another for Portlet, and a 4th for Maven support for Portlets. I've marked all 4 deprecated.
I have *NOT* created new connectors solely for *Aerogear* and *Browsersim*. I can do so if requested but figure what we have already is good enough.
Would you agree [~rpdavis] [~jeffmaury] [~gercan] [~ibuziuk] ?
> 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
[JBoss JIRA] (JBIDE-25738) arquillian build with tycho 1.1.0 fails on test package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25738?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-25738.
------------------------------
Resolution: Won't Fix
Won't fix. Arquillian has been removed from JBoss Tools.
> arquillian build with tycho 1.1.0 fails on test package
> -------------------------------------------------------
>
> Key: JBIDE-25738
> URL: https://issues.jboss.org/browse/JBIDE-25738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build
> Affects Versions: 4.5.3.AM1
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> Running command "mvn clean install -DtychoVersion=1.1.0" on master branch of repository jbosstools-arquillian fails:
> {code:java}
> [INFO] --- tycho-surefire-plugin:1.1.0:test (default-test) @ org.jboss.tools.arquillian.test ---
> [INFO] Expected eclipse log file: /home/jkopriva/git/jbosstools-arquillian/tests/org.jboss.tools.arquillian.test/target/work/data/.metadata/.log
> [INFO] Command line:
> [/usr/lib/jvm/java-9-openjdk-9.0.4.11-4.fc27.x86_64/bin/java, -Dosgi.noShutdown=false, -Dosgi.os=linux, -Dosgi.ws=gtk, -Dosgi.arch=x86_64, -javaagent:/home/jkopriva/.m2/repository/org/jacoco/org.jacoco.agent/0.7.1.201405082137/org.jacoco.agent-0.7.1.201405082137-runtime.jar=destfile=/home/jkopriva/git/jbosstools-arquillian/target/jacoco.exec,append=true,includes=org.jboss.tools.*, -Xms512m, -Xmx1024m, -XX:MetaspaceSize=256m, -Dusage_reporting_enabled=false, -Dorg.jboss.tools.tests.skipPrivateRequirements=true, -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true, -Dosgi.clean=true, -jar, /home/jkopriva/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.4.0.v20161219-1356/org.eclipse.equinox.launcher-1.4.0.v20161219-1356.jar, -data, /home/jkopriva/git/jbosstools-arquillian/tests/org.jboss.tools.arquillian.test/target/work/data, -install, /home/jkopriva/git/jbosstools-arquillian/tests/org.jboss.tools.arquillian.test/target/work, -configuration, /home/jkopriva/git/jbosstools-arquillian/tests/org.jboss.tools.arquillian.test/target/work/configuration, -application, org.eclipse.tycho.surefire.osgibooter.uitest, -testproperties, /home/jkopriva/git/jbosstools-arquillian/tests/org.jboss.tools.arquillian.test/target/surefire.properties]
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:500)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:512)
> Caused by: java.lang.RuntimeException: Class java/util/UUID could not be instrumented.
> at org.jacoco.agent.rt.internal_932a715.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:139)
> at org.jacoco.agent.rt.internal_932a715.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:100)
> at org.jacoco.agent.rt.internal_932a715.PreMain.createRuntime(PreMain.java:55)
> at org.jacoco.agent.rt.internal_932a715.PreMain.premain(PreMain.java:47)
> ... 6 more
> Caused by: java.lang.NoSuchFieldException: $jacocoAccess
> at java.base/java.lang.Class.getField(Class.java:1956)
> at org.jacoco.agent.rt.internal_932a715.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:137)
> ... 9 more
> FATAL ERROR in native method: processing of -javaagent failed
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] jbosstools-arquillian .............................. SUCCESS [ 6.441 s]
> [INFO] arquillian.features ................................ SUCCESS [ 0.034 s]
> [INFO] arquillian.plugins ................................. SUCCESS [ 0.023 s]
> [INFO] org.jboss.tools.arquillian.core .................... SUCCESS [ 29.414 s]
> [INFO] org.jboss.tools.arquillian.ui ...................... SUCCESS [ 6.807 s]
> [INFO] org.jboss.tools.arquillian.maven.configurator ...... SUCCESS [ 3.055 s]
> [INFO] org.jboss.tools.arquillian.feature ................. SUCCESS [ 2.116 s]
> [INFO] arquillian.tests ................................... SUCCESS [ 0.024 s]
> [INFO] org.jboss.tools.arquillian.test .................... FAILURE [ 3.627 s]
> [INFO] org.jboss.tools.arquillian.test.feature ............ SKIPPED
> [INFO] arquillian.site .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 01:26 min
> [INFO] Finished at: 2018-02-20T07:13:56+01:00
> [INFO] Final Memory: 112M/374M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.1.0:test (default-test) on project org.jboss.tools.arquillian.test: An unexpected error occured while launching the test runtime (return code 134). See log for details. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :org.jboss.tools.arquillian.test
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years