[
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)