| Re: [ecf-dev] Java8 support |
'JavaSE-1.8' is not a valid Execution Environment
Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8: Unbound classpath container: 'JRE System Library [JavaSE-1.8]' in project 'org.eclipse.ecf.remoteservice.asyncproxy.j8' Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8: The project cannot be built until build path errors are resolved Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/META-INF/MANIFEST.MF, line 11: 'JavaSE-1.8' is not a valid Execution Environment Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacSource' build entry and the project has Java compliance preferences set Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacTarget' build entry and the project has Java compliance preferences set Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacErrors..' build entry and the project has Java compliance preferences set Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice: The project was not built since it depends on org.eclipse.ecf.remoteservice.asyncproxy.j8, which has build path errors Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice: API analysis aborted for 'org.eclipse.ecf.remoteservice' since its build path is incomplete
I've changed the SDK from default to J8 and started a build.Cheers,
Wim
On Thu, Apr 10, 2014 at 1:19 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Ok, I've made additions/changes to the ecf.rmap file and now the buckminster materialization is happening properly.
However, when buckminster runs the PDE build, the compile fails because the J2SE-1.8 BREE is not recognized. See below for the output for the C-HEAD-org.eclipse.ecf.remoteservice build.
This doesn't happen when I locally (my workspace) invoke the feature export for org.eclipse.ecf.remoteservice.feature. But in that case 1.8 is being used as the vm running Eclipse/PDE, and the target platform is 4.4.I20140408.
Is it obvious to Markus, Wim, or others...what needs to change in the Jenkins build to allow the 1.8 BREE (in 2.0.0 version of asyncproxy) to be available?
Thanks,
Scott
--output from https://build.ecf-project.org/jenkins/job/C-HEAD-remoteservice.feature/115/consoleText
...
WARN: Server returned lastModified <= 0 for http://download.ecf-project.org/repo/compositeArtifacts.xml
Processing changes in target platform locations...
INFO: Resetting target platform Directory /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/targetPlatformPath
Done processing changes in target platform locations
Unable to determine readerType for project org.eclipse.ecf.remoteservice.asyncproxy.j8. Assuming "local"
Unable to determine readerType for project org.eclipse.ecf.remoteservice.asyncproxy. Assuming "local"
Unable to determine readerType for project org.eclipse.ecf.remoteservice. Assuming "local"
Unable to determine readerType for project org.eclipse.ecf.remoteservice.feature. Assuming "local"
Project org.eclipse.ecf.remoteservice.feature now has dynamic dependencies to org.eclipse.ecf.remoteservice org.eclipse.ecf.remoteservice.asyncproxy org.eclipse.ecf.remoteservice.asyncproxy.j8
INFO: Import complete.
Doing full workspace refresh
Cancel jobs that are known to run indefinitely...
Waiting for jobs to end
importtargetdefinition 'http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/plain/releng/org.eclipse.ecf.releng.bm/ECF3-6Baseline.target'
Downloading http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/plain/releng/org.eclipse.ecf.releng.bm/ECF3-6Baseline.target
Doing full workspace refresh
Cancel jobs that are known to run indefinitely...
Waiting for jobs to end
lstargets
Using workspace at file:/opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/ ...
* Directory /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/targetPlatformPath : linux,gtk,x86_64/en_US
Target Platform : linux,gtk,x86_64/en_US
ECF3-6Baseline : linux,gtk,x86_64/en_US
Running Platform : linux,gtk,x86_64/en_US
Doing full workspace refresh
Cancel jobs that are known to run indefinitely...
Waiting for jobs to end
addbaseline '-A' 'ECF3-6Baseline'
Doing full workspace refresh
Cancel jobs that are known to run indefinitely...
Waiting for jobs to end
Joining JOB: (org.eclipse.buckminster.core.metadata.MetadataSynchronizer$MetadataRefreshJob) Metadata refresh(2789)
build
Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8: Unbound classpath container: 'JRE System Library [JavaSE-1.8]' in project 'org.eclipse.ecf.remoteservice.asyncproxy.j8'
Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8: The project cannot be built until build path errors are resolved
Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/META-INF/MANIFEST.MF, line 11: 'JavaSE-1.8' is not a valid Execution Environment
Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacSource' build entry and the project has Java compliance preferences set
Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacTarget' build entry and the project has Java compliance preferences set
Warning: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice.asyncproxy.j8/build.properties, line 1: There is no 'javacErrors..' build entry and the project has Java compliance preferences set
Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice: The project was not built since it depends on org.eclipse.ecf.remoteservice.asyncproxy.j8, which has build path errors
Error: file /opt/hudson/jobs/C-HEAD-remoteservice.feature/workspace/projects/org.eclipse.ecf.remoteservice: API analysis aborted for 'org.eclipse.ecf.remoteservice' since its build path is incomplete
Errors: 4
Warnings: 4
Infos: 0
Build failed after 0 seconds.
Doing full workspace refresh
Cancel jobs that are known to run indefinitely...
Waiting for jobs to end
Build step 'Use builders from another project' marked build as failure
Archiving artifacts
Sending e-mails to: slewis@xxxxxxxxxxxxx
Finished: FAILURE
On 4/8/2014 11:35 AM, Scott Lewis wrote:
On 4/8/2014 11:12 AM, Wim Jongman wrote:
I don't think it is possible. Did you manage to get it working without buckminster, i.e. try to export the feature by hand?
Yes...just locally via (j8 enabled) Eclipse 4.4 PDE feature export...but that worked fine (i.e. both versions of asyncproxy bundle are built).
I think it must be possible with Bucky to support the build of multiple versions of a single bundle...as I would expect that someone in the group of simultaneous release projects is doing something with building multiple versions of a bundle.
I've already posted a question about this use case to buckminster-dev mailing list (couple of days ago)...but no response from the buckminster guys yet.
Thanks,
Scott
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev