Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Migrating to 4.10 solutions

Hi

Rebuilding on 4.10 is not as easy as it could be. I outline below solutions to the problems I encountered. Hopefully you can avoid them.

32 bit Windows support removed : https://bugs.eclipse.org/bugs/show_bug.cgi?id=536766

If you build with Tycho (1.2.0) on a Windows 64 platform, you will hit https://bugs.eclipse.org/bugs/show_bug.cgi?id=539656

The classpath issue is opaque. The solution is trivial. Remove the obsolete/wrong

            <environment>
              <os>win32</os>
              <ws>win32</ws>
              <arch>x86</arch>
            </environment>

from your (root) pom.xml.

?? Is there a central location where the correct environment definitions are to be found. The current change on breakage is very fragile. What about Linux 32 ??

org.eclipse.equinox.ds removed : https://bugs.eclipse.org/bugs/show_bug.cgi?id=538737

This problem wills probably be resolved by Tycho 1.3.0, but today using 1.2.0 ...

Once upon a time org.eclipse.equinox.ds was started automatically, and it started org.apache.flex.scr. org.eclipse.equinox.ds does nothing so the platform has moved to just starting just org.apache.flex.scr. Unfortunately Tycho has not yet caught up.

Workaround 1: add an optional Require-Bundle for org.eclipse.equinox.ds to the MANIFEST.MF of every bundle that contains tests executed by Tycho.

Unfortunately the hidden packaging of org.eclipse.equinox.ds changes in 4.10 and so the above workaround gives a Tycho provisioning failure.

Additional Workaround 2: add

	<unit id="org.eclipse.equinox.ds" version="0.0.0"/>

to your platform target definition.

    Regards

        Ed Willink




Virus-free. www.avast.com

Back to the top