[
https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-22673:
-------------------------------
Attachment: verify-log.txt
When I run this:
{code}export JAVA_HOME=/opt/sun-java2-8.0/
echo $JAVA_HOME;
cd ~/tru/jbosstools-discovery
~/tru/jbosstools-build-ci/util/verifyTarget.sh -x -b `pwd` -p jbtcentral -u
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
I get this error log for the first & second maven steps - it's the second one that
craps out [1]:
[^verify-log.txt]
[1]
https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/u...
I've tried applying this in parent pom and building locally but it doesn't help:
{code}
diff --git a/parent/pom.xml b/parent/pom.xml
index 6a56183..3536b29 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -26,9 +26,9 @@
- <tychoVersion>0.25.0</tychoVersion>
+ <tychoVersion>0.26.0-SNAPSHOT</tychoVersion>
<tychoExtrasVersion>${tychoVersion}</tychoExtrasVersion>
- <jbossTychoPluginsVersion>0.25.0-SNAPSHOT</jbossTychoPluginsVersion>
+ <jbossTychoPluginsVersion>0.25.1-SNAPSHOT</jbossTychoPluginsVersion>
<jbosstoolsRelengPublishVersion>4.4.0.Final-SNAPSHOT</jbosstoolsRelengPublishVersion>
{code}
[~mickael_istria] Can you suggest what is going wrong or what to fix?
Need better duplicate IU detection when validating target platforms
-------------------------------------------------------------------
Key: JBIDE-22673
URL:
https://issues.jboss.org/browse/JBIDE-22673
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build, target-platform, upstream
Affects Versions: 4.4.0.Final
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.4.1.AM2
Attachments: verify-log.txt
As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD
contain duplicate IUs, and when it should not.
{quote}Problem is there's no way to identify easily which dupes are OK and which are
not. I suppose I could crack open all the jars and see which are singletons...?
Or add a whitelist?{quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)