Discussion:
Tycho build fails when Babel repo is included in the target platform
(too old to reply)
Rizzo, Eric
2013-01-22 22:17:43 UTC
Permalink
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.

Here is some of what Tycho spits out:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent

I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.

Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.

Any ideas?

Thanks,
Eric
Jeff MAURY
2013-01-23 08:36:39 UTC
Permalink
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.

Jeff
Post by Rizzo, Eric
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is
indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused about
how including Babel bundles could trigger compile errors referring to SWT.
I'm not even referencing any of the Babel bundles from any features or
plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem or
something in PDE that ignores a real problem, or what. At this point I'm
just (desperately) looking for ideas about where to look and what to try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Rizzo, Eric
2013-01-23 15:35:19 UTC
Permalink
Great, at least it's comforting to know I don't have something strangely wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there any workaround? Forgive my ignorance, but if there is no workaround how can I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how to use a patch since it seems that Tycho plugins are being downloaded from Maven's central repo, no?

Thanks,
Eric

On 1/23/13 3:36 AM, "Jeff MAURY" wrote:

I've got the same problem and submitted a patch (see https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.

Jeff



On Tue, Jan 22, 2013 at 11:17 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.

Here is some of what Tycho spits out:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent

I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.

Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.

Any ideas?

Thanks,
Eric


_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user




--
Jeff MAURY

[Loading Image...
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Jeff MAURY
2013-01-23 17:45:10 UTC
Permalink
The best way is to download the version from Eclipse Gerrit, do a Mvn
install or deploy and use 0.17.0-SNAPSHOT in your poms.

Regards
Jeff MAURY
Post by Rizzo, Eric
Great, at least it's comforting to know I don't have something strangely
wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there
any workaround? Forgive my ignorance, but if there is no workaround how can
I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how
to use a patch since it seems that Tycho plugins are being downloaded from
Maven's central repo, no?
Thanks,
Eric
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
Post by Rizzo, Eric
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It
is indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused about
how including Babel bundles could trigger compile errors referring to SWT.
I'm not even referencing any of the Babel bundles from any features or
plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem or
something in PDE that ignores a real problem, or what. At this point I'm
just (desperately) looking for ideas about where to look and what to try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Rizzo, Eric
2013-01-30 22:53:53 UTC
Permalink
So I noticed that the tycho bug was marked FIXED today (and there was much celebration). When will it be in a build? Just for fun I tried updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to resolve:


[ERROR] Unresolveable build extension: Plugin org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]


So my first question is how can I consume 0.17 snapshot builds (or, are they even available)? Follow-up question is, is this fix in the build yet?

Thanks for forgiving my relative Tycho/Maven ignorance,
Eric


On 1/23/13 12:45 PM, "Jeff MAURY" wrote:

The best way is to download the version from Eclipse Gerrit, do a Mvn install or deploy and use 0.17.0-SNAPSHOT in your poms.

Regards
Jeff MAURY


On Wed, Jan 23, 2013 at 4:35 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
Great, at least it's comforting to know I don't have something strangely wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there any workaround? Forgive my ignorance, but if there is no workaround how can I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how to use a patch since it seems that Tycho plugins are being downloaded from Maven's central repo, no?

Thanks,
Eric

On 1/23/13 3:36 AM, "Jeff MAURY" wrote:

I've got the same problem and submitted a patch (see https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.

Jeff



On Tue, Jan 22, 2013 at 11:17 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.

Here is some of what Tycho spits out:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent

I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.

Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.

Any ideas?

Thanks,
Eric


_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user




--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury



_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user




--
Jeff MAURY

[http://devoxx.fr/download/attachments/5342010/465x60_anime.gif?version=2&modificationDate=1323625564000]
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Oberlies, Tobias
2013-01-31 07:55:03 UTC
Permalink
No worries. Here is the answer to your question: http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds

Regards
Tobias

From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform

So I noticed that the tycho bug was marked FIXED today (and there was much celebration). When will it be in a build? Just for fun I tried updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to resolve:


[ERROR] Unresolveable build extension: Plugin org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]


So my first question is how can I consume 0.17 snapshot builds (or, are they even available)? Follow-up question is, is this fix in the build yet?

Thanks for forgiving my relative Tycho/Maven ignorance,
Eric


On 1/23/13 12:45 PM, "Jeff MAURY" wrote:

The best way is to download the version from Eclipse Gerrit, do a Mvn install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY

On Wed, Jan 23, 2013 at 4:35 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
Great, at least it's comforting to know I don't have something strangely wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there any workaround? Forgive my ignorance, but if there is no workaround how can I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how to use a patch since it seems that Tycho plugins are being downloaded from Maven's central repo, no?

Thanks,
Eric

On 1/23/13 3:36 AM, "Jeff MAURY" wrote:

I've got the same problem and submitted a patch (see https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff

On Tue, Jan 22, 2013 at 11:17 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.

Here is some of what Tycho spits out:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent

I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.

Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.

Any ideas?

Thanks,
Eric


_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY

Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury



_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY

[Image removed by sender.]
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Rizzo, Eric
2013-02-01 00:26:57 UTC
Permalink
On 1/31/13 2:55 AM, "Oberlies, Tobias" wrote:

No worries. Here is the answer to your question: http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds

Regards
Tobias

Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build the features that we use to iclude Babel bundles. Tycho is complaining that it can't resolve dependencies to org.eclipse.* host bundles that are definitely in the target platform (see build output excerpt below). The only build failures being reported are on these nl features, none of our actual code plugins or features.

It's almost like the nl features are not inheriting the target platform from the patent pom, but I've double-checked to make sure they declare it properly. Since the bug fix was in the area of the compile classpath, I wonder if something is amiss with the bug fix…

Any ideas or pointers are welcomed.
Eric



[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0' but it could not be found


[org.eclipse.compare.core is definitely in the target platform, similarly so are the bundles that can't be resolved below.]



[ERROR] Cannot satisfy dependency: com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier depends on: com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
[ERROR] Cannot satisfy dependency: com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency from


[and LOTS more like this…]



From: tycho-user-***@eclipse.org<mailto:tycho-user-***@eclipse.org> [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform

So I noticed that the tycho bug was marked FIXED today (and there was much celebration). When will it be in a build? Just for fun I tried updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to resolve:


[ERROR] Unresolveable build extension: Plugin org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]


So my first question is how can I consume 0.17 snapshot builds (or, are they even available)? Follow-up question is, is this fix in the build yet?

Thanks for forgiving my relative Tycho/Maven ignorance,
Eric


On 1/23/13 12:45 PM, "Jeff MAURY" wrote:

The best way is to download the version from Eclipse Gerrit, do a Mvn install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY

On Wed, Jan 23, 2013 at 4:35 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
Great, at least it's comforting to know I don't have something strangely wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there any workaround? Forgive my ignorance, but if there is no workaround how can I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how to use a patch since it seems that Tycho plugins are being downloaded from Maven's central repo, no?

Thanks,
Eric

On 1/23/13 3:36 AM, "Jeff MAURY" wrote:

I've got the same problem and submitted a patch (see https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff

On Tue, Jan 22, 2013 at 11:17 PM, Rizzo, Eric <***@emc.com<mailto:***@emc.com>> wrote:
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.

Here is some of what Tycho spits out:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent

I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.

Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.

Any ideas?

Thanks,
Eric


_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY

Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury



_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org<mailto:tycho-***@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Jeff MAURY

[cid:~WRD000.jpg]
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
Sievers, Jan
2013-02-01 13:00:32 UTC
Permalink
I don't think it's related to the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391011
unless you have seen the same build succeed before the fix was applied.

looks to me like you have only babel in the target platform and all the hosts for the NL fragments (typically provided by the release train p2 repo) are missing.
If you can provide links to a sample project, full debug log (-X -e) and steps to reproduce, open a bug so we can analyse this one.

Regards,
Jan


From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Freitag, 1. Februar 2013 01:27
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform

On 1/31/13 2:55 AM, "Oberlies, Tobias" wrote:

No worries. Here is the answer to your question: http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds
 
Regards
Tobias

Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build the features that we use to iclude Babel bundles. Tycho is complaining that it can't resolve dependencies to org.eclipse.* host bundles that are definitely in the target platform (see build output excerpt below). The only build failures being reported are on these nl features, none of our actual code plugins or features.

It's almost like the nl features are not inheriting the target platform from the patent pom, but I've double-checked to make sure they declare it properly. Since the bug fix was in the area of the compile classpath, I wonder if something is amiss with the bug fix.

Any ideas or pointers are welcomed.
Eric


[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0' but it could not be found

[org.eclipse.compare.core is definitely in the target platform, similarly so are the bundles that can't be resolved below.]


[ERROR] Cannot satisfy dependency: com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier depends on: com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
[ERROR] Cannot satisfy dependency: com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency from

[and LOTS more like this.]


 
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform
 
So I noticed that the tycho bug was marked FIXED today (and there was much celebration). When will it be in a build? Just for fun I tried updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to resolve:
 
[ERROR]     Unresolveable build extension: Plugin org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]
 
So my first question is how can I consume 0.17 snapshot builds (or, are they even available)? Follow-up question is, is this fix in the build yet?
 
Thanks for forgiving my relative Tycho/Maven ignorance,
Eric
 
 
On 1/23/13 12:45 PM, "Jeff MAURY" wrote:
 
The best way is to download the version from Eclipse Gerrit, do a Mvn install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY
 
On Wed, Jan 23, 2013 at 4:35 PM, Rizzo, Eric <***@emc.com> wrote:
Great, at least it's comforting to know I don't have something strangely wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there any workaround? Forgive my ignorance, but if there is no workaround how can I apply the patch locally? I'm somewhat Maven-ignorant so I don't know how to use a patch since it seems that Tycho plugins are being downloaded from Maven's central repo, no?
 
Thanks,
Eric
 
On 1/23/13 3:36 AM, "Jeff MAURY" wrote:
 
I've got the same problem and submitted a patch (see https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
 
On Tue, Jan 22, 2013 at 11:17 PM, Rizzo, Eric <***@emc.com> wrote:
I'm building a product based on Eclipse 3.8. The product compiles fine in Eclipse IDEs and with our newly-constructed Tycho build. However, when I add the Babel repository () to our target platform, Tycho complains with strange compilation errors realting to not finding SWT classes. The exact same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in the IDE) produces no compilation errors.
 
Here is some of what Tycho spits out:
 
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project com.emc.xcp.common.ui: Compilation failure: Compilation failure:
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It is indirectly referenced from required .class files
[ERROR] F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
 
I have confirmed (twice) that simply removing the Babel bundles from the target platform restores the build to success, so I'm pretty confused about how including Babel bundles could trigger compile errors referring to SWT. I'm not even referencing any of the Babel bundles from any features or plugins.
 
Before you ask, no I haven't been able to construct a simple test project that demonstrates the problem. I'm not even sure if it's a Tycho problem or something in PDE that ignores a real problem, or what. At this point I'm just (desperately) looking for ideas about where to look and what to try.
 
Any ideas?
 
Thanks,
Eric
 

_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY

Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
 
 

_______________________________________________
tycho-user mailing list
tycho-***@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
 
 
Rizzo, Eric
2013-02-01 15:41:38 UTC
Permalink
Jan,
As I said, the target platform most definitely includes all the host
bundles (I've triple-checked). This is a large RCP app that builds using
the same target platform and Tycho 0.16 (without the Babel fragments)
which uses many of those same bundles that host the NL fragments.

It will take a bit of work to produce a sample that demonstrates just this
problem, and I'm not sure it is even a bug in Tycho or reproducible via a
simple setup. It very well could be something strange in how our app build
is set up. I'll work on that, but in the meantime I was hoping for some
ideas to look at, since the only differences between this failed build and
the one that succeeds are:
* Added features that are shells just to include various Babel fragments.
* Added the latest Babel p2 repo to my target platform
* Updated my parent pom to use Tycho 0.17.0-SNAPSHOT and include <modules>
for the new Babel container features I added.

That's it, nothing was removed from the target platform and all that is
new is the babel plugins (included via a feature).

Eric
Post by Sievers, Jan
I don't think it's related to the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391011
unless you have seen the same build succeed before the fix was applied.
looks to me like you have only babel in the target platform and all the
hosts for the NL fragments (typically provided by the release train p2
repo) are missing.
If you can provide links to a sample project, full debug log (-X -e) and
steps to reproduce, open a bug so we can analyse this one.
Regards,
Jan
Sent: Freitag, 1. Februar 2013 01:27
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds
Regards
Tobias
Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build
the features that we use to iclude Babel bundles. Tycho is complaining
that it can't resolve dependencies to org.eclipse.* host bundles that are
definitely in the target platform (see build output excerpt below). The
only build failures being reported are on these nl features, none of our
actual code plugins or features.
It's almost like the nl features are not inheriting the target platform
from the patent pom, but I've double-checked to make sure they declare it
properly. Since the bug fix was in the area of the compile classpath, I
wonder if something is amiss with the bug fix.
Any ideas or pointers are welcomed.
Eric
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0'
but it could not be found
[org.eclipse.compare.core is definitely in the target platform, similarly
so are the bundles that can't be resolved below.]
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group
1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found
because the problem is unsatisfiable.": ["Unable to satisfy dependency
from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency
from
[and LOTS more like this.]
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
So I noticed that the tycho bug was marked FIXED today (and there was
much celebration). When will it be in a build? Just for fun I tried
updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to
[ERROR] Unresolveable build extension: Plugin
org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]
So my first question is how can I consume 0.17 snapshot builds (or, are
they even available)? Follow-up question is, is this fix in the build yet?
Thanks for forgiving my relative Tycho/Maven ignorance,
Eric
The best way is to download the version from Eclipse Gerrit, do a Mvn
install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY
Great, at least it's comforting to know I don't have something strangely
wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there
any workaround? Forgive my ignorance, but if there is no workaround how
can I apply the patch locally? I'm somewhat Maven-ignorant so I don't
know how to use a patch since it seems that Tycho plugins are being
downloaded from Maven's central repo, no?
Thanks,
Eric
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile)
on project com.emc.xcp.common.ui: Compilation failure: Compilation
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.
java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It
is indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.
java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused
about how including Babel bundles could trigger compile errors referring
to SWT. I'm not even referencing any of the Babel bundles from any
features or plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem
or something in PDE that ignores a real problem, or what. At this point
I'm just (desperately) looking for ideas about where to look and what to
try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Sievers, Jan
2013-02-01 16:23:00 UTC
Permalink
I can only recommend to go back to the working version and then go step by step.
other than that,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=392357
may be related but this is a wild guess without a sample project.

Regards
Jan

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Freitag, 1. Februar 2013 16:42
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform

Jan,
As I said, the target platform most definitely includes all the host
bundles (I've triple-checked). This is a large RCP app that builds using
the same target platform and Tycho 0.16 (without the Babel fragments)
which uses many of those same bundles that host the NL fragments.

It will take a bit of work to produce a sample that demonstrates just this
problem, and I'm not sure it is even a bug in Tycho or reproducible via a
simple setup. It very well could be something strange in how our app build
is set up. I'll work on that, but in the meantime I was hoping for some
ideas to look at, since the only differences between this failed build and
the one that succeeds are:
* Added features that are shells just to include various Babel fragments.
* Added the latest Babel p2 repo to my target platform
* Updated my parent pom to use Tycho 0.17.0-SNAPSHOT and include <modules>
for the new Babel container features I added.

That's it, nothing was removed from the target platform and all that is
new is the babel plugins (included via a feature).

Eric
Post by Sievers, Jan
I don't think it's related to the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391011
unless you have seen the same build succeed before the fix was applied.
looks to me like you have only babel in the target platform and all the
hosts for the NL fragments (typically provided by the release train p2
repo) are missing.
If you can provide links to a sample project, full debug log (-X -e) and
steps to reproduce, open a bug so we can analyse this one.
Regards,
Jan
Sent: Freitag, 1. Februar 2013 01:27
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds
Regards
Tobias
Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build
the features that we use to iclude Babel bundles. Tycho is complaining
that it can't resolve dependencies to org.eclipse.* host bundles that are
definitely in the target platform (see build output excerpt below). The
only build failures being reported are on these nl features, none of our
actual code plugins or features.
It's almost like the nl features are not inheriting the target platform
from the patent pom, but I've double-checked to make sure they declare it
properly. Since the bug fix was in the area of the compile classpath, I
wonder if something is amiss with the bug fix.
Any ideas or pointers are welcomed.
Eric
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0'
but it could not be found
[org.eclipse.compare.core is definitely in the target platform, similarly
so are the bundles that can't be resolved below.]
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group
1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found
because the problem is unsatisfiable.": ["Unable to satisfy dependency
from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency
from
[and LOTS more like this.]
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
So I noticed that the tycho bug was marked FIXED today (and there was
much celebration). When will it be in a build? Just for fun I tried
updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to
[ERROR] Unresolveable build extension: Plugin
org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]
So my first question is how can I consume 0.17 snapshot builds (or, are
they even available)? Follow-up question is, is this fix in the build yet?
Thanks for forgiving my relative Tycho/Maven ignorance,
Eric
The best way is to download the version from Eclipse Gerrit, do a Mvn
install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY
Great, at least it's comforting to know I don't have something strangely
wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there
any workaround? Forgive my ignorance, but if there is no workaround how
can I apply the patch locally? I'm somewhat Maven-ignorant so I don't
know how to use a patch since it seems that Tycho plugins are being
downloaded from Maven's central repo, no?
Thanks,
Eric
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile)
on project com.emc.xcp.common.ui: Compilation failure: Compilation
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.
java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It
is indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundles
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette.
java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused
about how including Babel bundles could trigger compile errors referring
to SWT. I'm not even referencing any of the Babel bundles from any
features or plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem
or something in PDE that ignores a real problem, or what. At this point
I'm just (desperately) looking for ideas about where to look and what to
try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Rizzo, Eric
2013-02-04 21:50:10 UTC
Permalink
I've attached a small "project" that demonstrates the problem I'm having.
It consists of a "master" pom and 4 sub-modules: a target-platform, a
container feature, and 2 nls features that include various .nl bundle
fragments from Babel.

The Tycho output is included, but the gist is that it fails with this:

[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed:
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.core.commands.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.core.commands 0.0.0'
but it could not be found

Looking at the .target file you can see that org.eclipse.core.commands is
included (not to mention the fact that I can see that plugin in my IDE
with the same target platform loaded).


I'm don't know if this is a bug in Tycho or a mistake in usage. Any advice
is appreciated.

Eric
Post by Rizzo, Eric
Jan,
As I said, the target platform most definitely includes all the host
bundles (I've triple-checked). This is a large RCP app that builds using
the same target platform and Tycho 0.16 (without the Babel fragments)
which uses many of those same bundles that host the NL fragments.
It will take a bit of work to produce a sample that demonstrates just this
problem, and I'm not sure it is even a bug in Tycho or reproducible via a
simple setup. It very well could be something strange in how our app build
is set up. I'll work on that, but in the meantime I was hoping for some
ideas to look at, since the only differences between this failed build and
* Added features that are shells just to include various Babel fragments.
* Added the latest Babel p2 repo to my target platform
* Updated my parent pom to use Tycho 0.17.0-SNAPSHOT and include <modules>
for the new Babel container features I added.
That's it, nothing was removed from the target platform and all that is
new is the babel plugins (included via a feature).
Eric
Post by Sievers, Jan
I don't think it's related to the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391011
unless you have seen the same build succeed before the fix was applied.
looks to me like you have only babel in the target platform and all the
hosts for the NL fragments (typically provided by the release train p2
repo) are missing.
If you can provide links to a sample project, full debug log (-X -e) and
steps to reproduce, open a bug so we can analyse this one.
Regards,
Jan
Sent: Freitag, 1. Februar 2013 01:27
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds
Regards
Tobias
Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build
the features that we use to iclude Babel bundles. Tycho is complaining
that it can't resolve dependencies to org.eclipse.* host bundles that are
definitely in the target platform (see build output excerpt below). The
only build failures being reported are on these nl features, none of our
actual code plugins or features.
It's almost like the nl features are not inheriting the target platform
from the patent pom, but I've double-checked to make sure they declare it
properly. Since the bug fix was in the area of the compile classpath, I
wonder if something is amiss with the bug fix.
Any ideas or pointers are welcomed.
Eric
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0'
but it could not be found
[org.eclipse.compare.core is definitely in the target platform, similarly
so are the bundles that can't be resolved below.]
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group
1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found
because the problem is unsatisfiable.": ["Unable to satisfy dependency
from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency
from
[and LOTS more like this.]
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
So I noticed that the tycho bug was marked FIXED today (and there was
much celebration). When will it be in a build? Just for fun I tried
updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to
[ERROR] Unresolveable build extension: Plugin
org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]
So my first question is how can I consume 0.17 snapshot builds (or, are
they even available)? Follow-up question is, is this fix in the build
yet?
Thanks for forgiving my relative Tycho/Maven ignorance,
Eric
The best way is to download the version from Eclipse Gerrit, do a Mvn
install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY
Great, at least it's comforting to know I don't have something strangely
wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there
any workaround? Forgive my ignorance, but if there is no workaround how
can I apply the patch locally? I'm somewhat Maven-ignorant so I don't
know how to use a patch since it seems that Tycho plugins are being
downloaded from Maven's central repo, no?
Thanks,
Eric
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile)
on project com.emc.xcp.common.ui: Compilation failure: Compilation
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundle
s
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette
.
java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It
is indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundle
s
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette
.
java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused
about how including Babel bundles could trigger compile errors referring
to SWT. I'm not even referencing any of the Babel bundles from any
features or plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem
or something in PDE that ignores a real problem, or what. At this point
I'm just (desperately) looking for ideas about where to look and what to
try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Sievers, Jan
2013-02-05 12:30:32 UTC
Permalink
thanks for the sample project, I was able to strip it down further.
this is a bug for both 0.16.0 and 0.17.0
https://bugs.eclipse.org/bugs/show_bug.cgi?id=399966

as a workaround, including the NL features from babel instead of single NL fragments seems to work.

Jan

-----Original Message-----
From: tycho-user-***@eclipse.org [mailto:tycho-user-***@eclipse.org] On Behalf Of Rizzo, Eric
Sent: Montag, 4. Februar 2013 22:50
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included in the target platform

I've attached a small "project" that demonstrates the problem I'm having.
It consists of a "master" pom and 4 sub-modules: a target-platform, a
container feature, and 2 nls features that include various .nl bundle
fragments from Babel.

The Tycho output is included, but the gist is that it fails with this:

[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed:
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group 1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.core.commands.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.core.commands 0.0.0'
but it could not be found

Looking at the .target file you can see that org.eclipse.core.commands is
included (not to mention the fact that I can see that plugin in my IDE
with the same target platform loaded).


I'm don't know if this is a bug in Tycho or a mistake in usage. Any advice
is appreciated.

Eric
Post by Rizzo, Eric
Jan,
As I said, the target platform most definitely includes all the host
bundles (I've triple-checked). This is a large RCP app that builds using
the same target platform and Tycho 0.16 (without the Babel fragments)
which uses many of those same bundles that host the NL fragments.
It will take a bit of work to produce a sample that demonstrates just this
problem, and I'm not sure it is even a bug in Tycho or reproducible via a
simple setup. It very well could be something strange in how our app build
is set up. I'll work on that, but in the meantime I was hoping for some
ideas to look at, since the only differences between this failed build and
* Added features that are shells just to include various Babel fragments.
* Added the latest Babel p2 repo to my target platform
* Updated my parent pom to use Tycho 0.17.0-SNAPSHOT and include <modules>
for the new Babel container features I added.
That's it, nothing was removed from the target platform and all that is
new is the babel plugins (included via a feature).
Eric
Post by Sievers, Jan
I don't think it's related to the fix for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=391011
unless you have seen the same build succeed before the fix was applied.
looks to me like you have only babel in the target platform and all the
hosts for the NL fragments (typically provided by the release train p2
repo) are missing.
If you can provide links to a sample project, full debug log (-X -e) and
steps to reproduce, open a bug so we can analyse this one.
Regards,
Jan
Sent: Freitag, 1. Februar 2013 01:27
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
http://wiki.eclipse.org/Tycho/Release_Notes/0.17#SNAPSHOT_builds
Regards
Tobias
Thanks, including the snapshots repository worked.
Now, however, I'm getting strange resolution errors when trying to build
the features that we use to iclude Babel bundles. Tycho is complaining
that it can't resolve dependencies to org.eclipse.* host bundles that are
definitely in the target platform (see build output excerpt below). The
only build failures being reported are on these nl features, none of our
actual code plugins or features.
It's almost like the nl features are not inheriting the target platform
from the patent pom, but I've double-checked to make sure they declare it
properly. Since the bug fix was in the area of the compile classpath, I
wonder if something is amiss with the bug fix.
Any ideas or pointers are welcomed.
Eric
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
1.0.0.qualifier
[ERROR] Missing requirement: org.eclipse.compare.core.nl_de
4.2.0.v20121120043402 requires 'bundle org.eclipse.compare.core 0.0.0'
but it could not be found
[org.eclipse.compare.core is definitely in the target platform, similarly
so are the bundles that can't be resolved below.]
com.emc.xcp.eclipse.infrastructure.nl.feature.feature.group
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group 0.0.0
com.emc.xcp.eclipse.infrastructure.nl_de.feature.feature.group
1.0.0.qualifier depends on: org.eclipse.compare.core.nl_de 0.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found
because the problem is unsatisfiable.": ["Unable to satisfy dependency
from org.eclipse.compare.core.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.core.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare.core 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.compare.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.compare 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.boot.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.boot 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.commands.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.commands 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_es 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_fr 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_it 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_ja 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.contenttype.nl_zh 4.2.0.v20121120043402 to bundle
org.eclipse.core.contenttype 0.0.0.", "Unable to satisfy dependency from
org.eclipse.core.databinding.beans.nl_de 4.2.0.v20121120043402 to bundle
org.eclipse.core.databinding.beans 0.0.0.", "Unable to satisfy dependency
from
[and LOTS more like this.]
Sent: Mittwoch, 30. Januar 2013 23:54
To: Tycho user list
Subject: Re: [tycho-user] Tycho build fails when Babel repo is included
in the target platform
So I noticed that the tycho bug was marked FIXED today (and there was
much celebration). When will it be in a build? Just for fun I tried
updating my pom to specify 0.17.0-SNAPSHOT but that doesn't seem to
[ERROR] Unresolveable build extension: Plugin
org.eclipse.tycho:tycho-maven-plugin:0.17.0-SNAPSHOT or one of its
dependencies could not be resolved: Could not find artifact
org.eclipse.tycho:tycho-maven-plugin:jar:0.17.0-SNAPSHOT -> [Help 2]
So my first question is how can I consume 0.17 snapshot builds (or, are
they even available)? Follow-up question is, is this fix in the build yet?
Thanks for forgiving my relative Tycho/Maven ignorance,
Eric
The best way is to download the version from Eclipse Gerrit, do a Mvn
install or deploy and use 0.17.0-SNAPSHOT in your poms.
Regards
Jeff MAURY
Great, at least it's comforting to know I don't have something strangely
wrong in my poms or plugin manifests.
Until the patch is accepted and available (in 0.17, presumably), is there
any workaround? Forgive my ignorance, but if there is no workaround how
can I apply the patch locally? I'm somewhat Maven-ignorant so I don't
know how to use a patch since it seems that Tycho plugins are being
downloaded from Maven's central repo, no?
Thanks,
Eric
I've got the same problem and submitted a patch (see
https://git.eclipse.org/r/#/c/8163/). It is only for Babel 4.2.
Jeff
I'm building a product based on Eclipse 3.8. The product compiles fine in
Eclipse IDEs and with our newly-constructed Tycho build. However, when I
add the Babel repository () to our target platform, Tycho complains with
strange compilation errors realting to not finding SWT classes. The exact
same target platform applied in Eclipse 3.8 or 3.7 SDK workspaces (ie, in
the IDE) produces no compilation errors.
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile)
on project com.emc.xcp.common.ui: Compilation failure: Compilation
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundle
s
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette
.
java:[0,0]
[ERROR] package com.emc.xcp.common.ui.function;
[ERROR] ^
[ERROR] The type org.eclipse.swt.events.KeyEvent cannot be resolved. It
is indirectly referenced from required .class files
[ERROR]
F:\P4_Int\depot\Platform\XCPBuilder\Int\int_XCPBLD_2.0\staging\app\bundle
s
\com.emc.xcp.common.ui\src\com\emc\xcp\common\ui\function\FunctionPalette
.
java:[20,0]
[ERROR] public class FunctionPalette extends AbstractTreePalette {
[ERROR] ^^^^^^^^^^^^^^^
[ERROR] The hierarchy of the type FunctionPalette is inconsistent
I have confirmed (twice) that simply removing the Babel bundles from the
target platform restores the build to success, so I'm pretty confused
about how including Babel bundles could trigger compile errors referring
to SWT. I'm not even referencing any of the Babel bundles from any
features or plugins.
Before you ask, no I haven't been able to construct a simple test project
that demonstrates the problem. I'm not even sure if it's a Tycho problem
or something in PDE that ignores a real problem, or what. At this point
I'm just (desperately) looking for ideas about where to look and what to
try.
Any ideas?
Thanks,
Eric
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
Error! Filename not specified.
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Jeff MAURY
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
- Bjarne Stroustrup
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
https://dev.eclipse.org/mailman/listinfo/tycho-user
Continue reading on narkive:
Loading...