[jbosstools-issues] [JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

[ https://issues.jboss.org/browse/JBIDE-19468?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19468: ---------------------------------------- {code} <akazakov> gastaldi, hey <nickboldt> gastaldi: we'll be renaming next week to make it called "Final" but no new commits should be going into it, unless we find a blocker <akazakov> JBIDE-19468 happens only when you create a new addon, right? If so it doesn't look like a blocker for 4.2.3 and we can ship it with forge 2.15.1 <gastaldi> akazakov, yes, we fixed in Master and we're releasing a new Forge version soon <gastaldi> It would be nice if that could make it to 4.2.3.Final <akazakov> gastaldi, how soon is soon? :) <gastaldi> today? <gastaldi> we can release today, tomorrow tops <gastaldi> akazakov, is that good or is too late? :) <akazakov> gastaldi, nickboldt, we could respin forge only to pick up the latest fixed forge... Still not sure we should do it. But it's not so hard to do if QA have to time to retest forge. Nick, what do you think? <akazakov> gastaldi, how many changes in forge 2.15.2? Just wonder if it tested well enough and we won't have new problems which will require more forge/JBDS updates/respins. <gastaldi> let me see <gastaldi> hm, not much <gastaldi> https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12311820&v... <akazakov> gastaldi, you can go ahead and release 2.15.2 and we will see if it's worth respining JBDS. We should make sure QA and others are OK with that. It doesn't look like a blocker to me so far. But if we can do this respin easily... <gastaldi> awesome, will do {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)