Re: [cbi-dev] Eclipse SDK Build fails with org.eclipse.jdt.compiler.apt.

["Sievers, Jan" <jan.sievers@xxxxxxx>]

this is probably unrelated to your first error.
the bundle org.eclipse.equinox.servletbridge.extensionbundle was removed in Kepler M7 [1].
This is a wild guess but it could be that the platform build only works because it uses an outdated local cache copy of that bundle.

Jan

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=348045


From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Lars Vogel
Sent: Dienstag, 22. Oktober 2013 15:43
To: Common-build Developers discussion
Subject: Re: [cbi-dev] Eclipse SDK Build fails with org.eclipse.jdt.compiler.apt.tests: Working tree is dirty.

Thanks Jan and Matthias. I agree that it would be very nice if the CBI Build could run twice without the git clean and reset command. 


I try to test the build with the jgit.dirtyWorkingTree=ignore flag. Currently I see another error [see below] before this error. 


[ERROR] The following artifacts could not be downloaded: 
[ERROR]   osgi.bundle,org.eclipse.equinox.servletbridge.extensionbundle,1.2.100.v20120522-2049
[ERROR] Internal error: java.lang.RuntimeException: Some required artifacts could not be downloaded. See log output for details. -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Some required artifacts could not be downloaded. See log output for details.
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: Some required artifacts could not be downloaded. See log output for details.
	at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.failIfArtifactsMissing(P2ResolverImpl.java:190)
	at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.toResolutionResult(P2ResolverImpl.java:176)
	at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:140)
	at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)
	at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)
	at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)
	at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)
	at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
	... 11 more
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException

2013/10/22 Sievers, Jan <jan.sievers@xxxxxxx>
there is a lengthy discussion on

https://bugs.eclipse.org/bugs/show_bug.cgi?id=419030

Basically, the build currently produces a non-clean 'git status' and this is validated now with tycho 0.19.0 if you use reproducible build qualifiers based on last git commit timestamps [1].

As long as the build produces 'dirt', your options are one of

* make sure the build is really clean before each build (from your error message below, it looks like there is some leftover dirt from a previous build)
* use jgit.dirtyWorkingTree=warning, which will give you a warning and will use current build timestamp qualifiers for 'dirty' modules
* use jgit.dirtyWorkingTree=ignore, which will ignore dirty modules and always use last commit timestamp (this is the previous behaviour but buggy IMHO as it potentially produces same timestamp for completely different binaries leading to late p2 update surprises)
* change the build configuration to use git commit-based qualifiers for central builds only with a specific build profile, by default local builds would always produce current build-time timestamps

Regards,
Jan

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19


From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Lars Vogel
Sent: Dienstag, 22. Oktober 2013 14:59
To: Eclipse CBI
Subject: [cbi-dev] Eclipse SDK Build fails with org.eclipse.jdt.compiler.apt.tests: Working tree is dirty.

Hello,

our Eclipse SDK build is currently failing with the error message from below.

We are using the following commands for the build:

git submodule foreach git clean -f -d -x
git submodule foreach git reset --hard HEAD
git clean -f -d -x
git reset --hard HEAD
git checkout master
git pull --recurse-submodules
git submodule update
mvn clean install

Any advice how to fix that? Are is this a setup issue with org.eclipse.jdt.compiler.apt.tests?

Best regards, Lars




[ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.19.0-SNAPSHOT:build-qualifier (default-build-qualifier) on project org.eclipse.jdt.compiler.apt.tests: Working tree is dirty.
[ERROR] git status org.eclipse.jdt.compiler.apt.tests:
[ERROR]
[ERROR] Changes not staged for commit:
[ERROR] deleted:     org.eclipse.jdt.compiler.apt.tests/lib/apttestprocessors.jar
[ERROR] deleted:     org.eclipse.jdt.compiler.apt.tests/lib/.cvsignore
[ERROR]
[ERROR] You are trying to use tycho-buildtimestamp-jgit on a directory that has uncommitted changes (see details above).
[ERROR] Either commit all changes/add files to .gitignore, or enable fallback to default timestamp provider by configuring
[ERROR] jgit.dirtyWorkingTree=warning for tycho-packaging-plugin
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :org.eclipse.jdt.compiler.apt.tests

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev