June 2018 - jbosstools-issues - Jboss List Archives

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1233: --------------------------------- Summary: Resync IS TP Key: JBTIS-1233 URL: https://issues.jboss.org/browse/JBTIS-1233 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 12.0.0.AM1-TP Reporter: Paul Leacu Reason: Update to latest 4.6.0 JBT TP Project page/sources: Version: 12.0.0.CR1 License and owner: EPL Original p2 repo: JBoss mirror: Include Sources: Yes Affected JBoss Tools components: Integration Stack Include in JBDS: Yes (DevtsudioIS) Type of dependency: distribution List of bundles added/removed: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26146: ------------------------------------ I believe part of the reason for this change [1] from m2e 1.8.3 to 1.9.0 was that egit 5 requires m2e 1.9. [1] https://github.com/jbosstools/jbosstools-target-platforms/commit/f7beebb7... So... unless [~fbricon] can help us get a fix to 1.9.x, I don't think going back to 1.8.x is feasible for this release. > Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.6.0.Final > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26147: ---------------------------------- Summary: Incremental publish not working with WF13, WF12 and WF11 Key: JBIDE-26147 URL: https://issues.jboss.org/browse/JBIDE-26147 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.6.0.AM3 Reporter: Jeff MAURY Assignee: Rob Stryker Fix For: 4.9.0.AM1 Attachments: helloworld-rs.zip Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26147) Incremental publish not working with WF13, WF12 and WF11

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26147: ------------------------------- Attachment: helloworld-rs.zip > Incremental publish not working with WF13, WF12 and WF11 > -------------------------------------------------------- > > Key: JBIDE-26147 > URL: https://issues.jboss.org/browse/JBIDE-26147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Fix For: 4.9.0.AM1 > > Attachments: helloworld-rs.zip > > > Deployed a JAX-RS application to WF11, WF12 and WF13. This application is using JAX-RS 2.1 server side event Sse injected into method parameter through @Context. > This application is deployed but when an endpoint is used, an error is raised probably because WF is still on JAX-RS 2.0. > Then this code is commented out, the application is incrementally published but the error persists -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-643) Embedded Maven is not behaving the same as standalone Maven causing ClassNotFoundException [EBZ#536402]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-643: --------------------------------------- Summary: Embedded Maven is not behaving the same as standalone Maven causing ClassNotFoundException [EBZ#536402] Key: ERT-643 URL: https://issues.jboss.org/browse/ERT-643 Project: Eclipse Release Train Issue Type: Task Components: m2e Reporter: Friendly Jira Robot the Maven Emebedded 3.5.3 is not behaving the same than a standalone Maven. Only when using the embedded version I have a build error when using fabric8-maven-plugin: [ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.5.33.fuse-000067-redhat-1:resource (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.5.33.fuse-000067-redhat-1:resource failed: A required class was missing while executing io.fabric8:fabric8-maven-plugin:3.5.33.fuse-000067-redhat-1:resource: org/fusesource/jansi/Ansi$Color you can find the some investigation details on this issue: https://issues.jboss.org/browse/FUSETOOLS-3026 to reproduce the issue: - import as Maven project https://github.com/fabric8-quickstarts/spring-boot-camel-xml - create a launch configuration with clean package goals --> notice the error please note that it is working fine when: - using a Maven 3.5.3 as an external Maven Runtime with a launch configuration - using command-line -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-26146: --------------------------------------- Assignee: Fred Bricon (was: Nick Boldt) > Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.6.0.Final > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-26146: --------------------------------------- Assignee: Nick Boldt > Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.6.0.Final > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-26146: ----------------------------------------- interesting chat in dev suite room adietish 10:43 AM @apupier I see an update to m2e here: https://github.com/jbosstools/jbosstools-target-platforms/commit/f7beebb7... @apupier version="1.9.0.20180606-2036" is this the culprit? apupier 10:45 AM our first failing tests fo rthat are from the 21st June https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... so it seems to be related the commit you pointed is 9 days old so th e19th June between 19 and 21 we had a single build but maybe the TP was not fully built yet? or as it is a pr it was based on a previous TP > Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Priority: Critical > Fix For: 4.6.0.Final > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-26146: --------------------------------------- Summary: Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform Key: JBIDE-26146 URL: https://issues.jboss.org/browse/JBIDE-26146 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.6.0.Final Reporter: Aurélien Pupier Priority: Critical either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26146) Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26146?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-26146: ------------------------------------ Fix Version/s: 4.6.0.Final > Have a version of m2e without bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=536402 in the target Platform > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26146 > URL: https://issues.jboss.org/browse/JBIDE-26146 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.6.0.Final > Reporter: Aurélien Pupier > Priority: Critical > Fix For: 4.6.0.Final > > > either we have a workaround in the code (not a workaround to ask to users), or a fix and use a newer version in TP or maybe revert to previous version if possible in TP > the current impact is that the most visible templates of Fuse are not working out of the box. it exists a workaround for users which is to configure to use an external Maven Runtime (but it is not very convenient) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2018