[JBoss JIRA] (JBIDE-25582) Add Spring Boot M2 configurator
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25582?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25582:
-------------------------------
Description: In order to support Spring Boot apps in OpenShift server adapter, we need an M2 configurator that assign the jar utility facet to JAR packaged Spring Boot apps (was: In order to support SpringBoot apps in OpenShift server adapter, we need an M2 configurator that assign the jar utility facet to JAR packaged SpringBoot apps)
> Add Spring Boot M2 configurator
> -------------------------------
>
> Key: JBIDE-25582
> URL: https://issues.jboss.org/browse/JBIDE-25582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Fix For: 4.5.2.Final
>
>
> In order to support Spring Boot apps in OpenShift server adapter, we need an M2 configurator that assign the jar utility facet to JAR packaged Spring Boot apps
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25309) [Central] Can't install stuff from RH Central into JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-25309.
--------------------------------
Resolution: Done
Going to mark this as resolved for 4.5.2.Final. Once we GA, we can confirm if it's in fact fixed or not, and reopen if not.
> [Central] Can't install stuff from RH Central into JBoss Tools
> --------------------------------------------------------------
>
> Key: JBIDE-25309
> URL: https://issues.jboss.org/browse/JBIDE-25309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.5.1.Final
> Environment: RHEL7, OpenJDK 1.8
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.2.Final
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> I can't install stuff from RH Central into JBoss Tools because of unavailable connectors.
> There is dialog I got:
> !JBT_unavailable_connectors.png|thumbnail!
> After click "No" the error dialog with this message was displayed:
> [^JBT_unavailable_connectors.txt]
> Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\].
> \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/
> This problem appears only in JBoss Tools, JBDS works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25309) [Central] Can't install stuff from RH Central into JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25309:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.2.Final)
> [Central] Can't install stuff from RH Central into JBoss Tools
> --------------------------------------------------------------
>
> Key: JBIDE-25309
> URL: https://issues.jboss.org/browse/JBIDE-25309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.5.1.Final
> Environment: RHEL7, OpenJDK 1.8
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.2.Final
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> I can't install stuff from RH Central into JBoss Tools because of unavailable connectors.
> There is dialog I got:
> !JBT_unavailable_connectors.png|thumbnail!
> After click "No" the error dialog with this message was displayed:
> [^JBT_unavailable_connectors.txt]
> Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\].
> \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/
> This problem appears only in JBoss Tools, JBDS works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25309) [Central] Can't install stuff from RH Central into JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25309:
-------------------------------
Fix Version/s: 4.5.2.Final
(was: 4.5.x)
> [Central] Can't install stuff from RH Central into JBoss Tools
> --------------------------------------------------------------
>
> Key: JBIDE-25309
> URL: https://issues.jboss.org/browse/JBIDE-25309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.5.1.Final
> Environment: RHEL7, OpenJDK 1.8
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.2.Final
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> I can't install stuff from RH Central into JBoss Tools because of unavailable connectors.
> There is dialog I got:
> !JBT_unavailable_connectors.png|thumbnail!
> After click "No" the error dialog with this message was displayed:
> [^JBT_unavailable_connectors.txt]
> Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\].
> \[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/
> This problem appears only in JBoss Tools, JBDS works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4665) Enable m2e logging
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4665?page=com.atlassian.jira.plugin.... ]
Vsevolod Golovanov commented on JBDS-4665:
------------------------------------------
In the end I'm asking that m2e logging works out of the box. That means if I open a Maven project a log should appear in workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/0.log.
This is what happens with vanilla Eclipse for Java EE.
Including "m2e - slf4j over logback logging" is a part that's required towards that goal, but there may be something else needed. I don't know why installing "m2e - slf4j over logback logging" doesn't achieve logging with JBDS 11.1.
> Enable m2e logging
> ------------------
>
> Key: JBDS-4665
> URL: https://issues.jboss.org/browse/JBDS-4665
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Affects Versions: 11.1.0.GA
> Reporter: Vsevolod Golovanov
> Assignee: Nick Boldt
> Fix For: 11.x
>
>
> I used to enable it manually, by installing m2e - slf4j over logback logging (Optional). (For some reason, this doesn't work with JBDS 11.1: https://stackoverflow.com/questions/48276549/enable-m2e-logging-in-jboss-... )
> It would be much more convenient if m2e logging came bundled with JBDS. It does with Eclipse for Java EE.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4618) remove dupe/older versions of glassfish and jersey so devstudio and docker-tools use the same versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4618?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-4618.
------------------------------
Resolution: Done
Fixed with these commits:
https://github.com/jbdevstudio/jbdevstudio-product/commit/a5ea98b89d9d654...
https://github.com/jbdevstudio/jbdevstudio-product/commit/bf59dab0704da80...
> remove dupe/older versions of glassfish and jersey so devstudio and docker-tools use the same versions
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4618
> URL: https://issues.jboss.org/browse/JBDS-4618
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: rpm, target-platform
> Affects Versions: 11.1.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.2.0.GA
>
>
> Some bundles that appear in both docker tools and devstudio:
> {code}
> org.glassfish.hk2.osgi-resource-locator_2.4.0.jar -> ../../../../../java/glassfish-hk2/osgi-resource-locator.jar linuxtools-docker
> org.glassfish.hk2.osgi-resource-locator_2.5.0.v20161103-1916 devstudio
> org.glassfish.jersey.core.jersey-common_2.22.1.v20161103-1916 devstudio
> org.glassfish.jersey.core.jersey-common_2.23.2.jar -> ../../../../../java/jersey/jersey-common.jar linuxtools-docker
> org.glassfish.jersey.core.jersey-server_2.22.1.v20161103-1916 devstudio
> org.glassfish.jersey.core.jersey-server_2.23.2.jar -> ../../../../../java/jersey/jersey-server.jar linuxtools-docker
> {code}
> Symlinks are to paths here (installed via rpm):
> * /opt/rh/rh-eclipse47/root/usr/share/java/glassfish-hk2 --> rh-eclipse47-glassfish-hk2-osgi-resource-locator.noarch
> * /opt/rh/rh-eclipse47/root/usr/share/java/jersey --> rh-eclipse47-jersey.noarch
> Complete list via this script:
> {code}
> sudo su
> cd /opt/rh/rh-eclipse47/root/usr/share/eclipse/
> rm -f /tmp/list.txt
> for d in $(find . -mindepth 3 -name \*glassfish\* | egrep -v "META-INF|org/glas"); do ls -lad $d | sed -e "s#.\+droplets/\([^/]\+\)/eclipse/plugins/\(.\+\)#\2 \1#" >> /tmp/list.txt; done
> cat /tmp/list.txt | sort | egrep "jersey|glassfish"
> rm -f /tmp/list.txt
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months