[
https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22673:
------------------------------------
Curiously, when I apply the above PR for discovery and try to use verifyTarget.sh to
verify the target platform, I get this:
{code}
[ERROR] Internal error: java.lang.ClassCastException:
org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to
org.eclipse.tycho.ReactorProject -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.ClassCastException:
org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to
org.eclipse.tycho.ReactorProject
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:164)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: java.lang.ClassCastException:
org.eclipse.tycho.core.osgitools.DefaultReactorProject cannot be cast to
org.eclipse.tycho.ReactorProject
at
org.eclipse.tycho.core.osgitools.DefaultReactorProject.adapt(DefaultReactorProject.java:44)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:90)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:271)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
... 11 more
{code}
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
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)