Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Java8 support
You try to let buckminster include two different projects with the same id in the same feature [1]. If such a thing is possible, I think you have to fool around with cquery specs.



On Sat, Apr 5, 2014 at 11:33 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Thanks Markus...your help is much appreciated.

I see that you also added installJRE 1.8 to the Template-Build...again, thanks.

I thought I would give it a try, so I change org.eclipse.ecf.remoteservice.feature to have this contents for asyncproxy bundle:

   <plugin
         id="org.eclipse.ecf.remoteservice.asyncproxy"
         download-size="0"
         install-size="0"
         version="1.0.0"
         unpack="false"/>

   <plugin
         id="org.eclipse.ecf.remoteservice.asyncproxy"
         download-size="0"
         install-size="0"
         version="2.0.0"
         unpack="false"/>


Unfortunately, this failed in build #573 for C-HEAD-sdk.feature. It complains about not being able to find version 2.0.0 of org.eclipse.ecf.remoteservice.asyncproxy.   So I removed the 2.0.0 (and left the 1.0.0) and that failed too...so I tried this:

   <plugin
         id="org.eclipse.ecf.remoteservice.asyncproxy"
         download-size="0"
         install-size="0"
         version="1.0.0.qualifier"
         unpack="false"/>

   <plugin
         id="org.eclipse.ecf.remoteservice.asyncproxy"
         download-size="0"
         install-size="0"
         version="2.0.0.qualifier"
         unpack="false"/>

This doesn't give a warning in PDE (in my workspace) like the 1.0.0 and 2.0.0 above...so I thought I would give it a go.

Unfortunately the sdk build still failed with this as the error message:

org.eclipse.ecf.remoteservice.asyncproxy:osgi.bundle/[2.0.0,2.0.1): Rejecting provider p2({0}?importType=binary[http://download.ecf-project.org/repo/?importType=binary]): No component match was found
org.eclipse.ecf.remoteservice.asyncproxy:osgi.bundle/[2.0.0,2.0.1): No provider was found that could resolve the request
ERROR   [0029] : No suitable provider for component org.eclipse.ecf.remoteservice.asyncproxy:osgi.bundle/[2.0.0,2.0.1) was found in resourceMap file:/opt/hudson/jobs/C-HEAD-sdk.feature/workspace/ecf.rmap
  ERROR   [0029] : No suitable provider for component org.eclipse.ecf.remoteservice.asyncproxy:osgi.bundle/[2.0.0,2.0.1) was found in searchPath org.eclipse.ecf
    ERROR   [0029] : Version 1.0.0.qualifier rejected: Not designated by [2.0.0,2.0.1)
    ERROR   [0029] : Rejecting provider p2({0}?importType=binary[http://download.ecf-project.org/repo/?importType=binary]): No component match was found
INFO:  TAG-ID 0029 = Query for org.eclipse.ecf.sdk:eclipse.feature, path: org.eclipse.ecf.sdk:eclipse.feature$3.8.1.qualifier -> org.eclipse.ecf.remoteservice.sdk.feature:eclipse.feature$3.8.1.qualifier -> org.eclipse.ecf.remoteservice.feature:eclipse.feature$2.1.0.qualifier

Here's the full console output for that build [1].   This sort of surprised me, because if I look in the workspace/projects for HEAD-sdk.feature build job I see both projects:

org.eclipse.ecf.remoteservice.asyncproxy (1.0.0)
org.eclipse.ecf.remoteservice.asyncproxy.j8 (2.0.0)

and the version 2.0.0 version of org.eclipse.ecf.remoteservice.asyncproxy is in the org.eclipse.ecf.remoteservice.asyncproxy project.

Does doing this require some sort of addition/change to the buckminster meta-data (cquery,mspec?) for the SDK project...or perhaps the project name for org.eclipse.ecf.remoteservice.asyncproxy should/needs to be org.eclipse.ecf.remoteservice.asyncproxy.j5?

Please let me know what you think.  We could ask the buckminster guys...if necessary.

Thanks,

Scott

[1] https://build.ecf-project.org/jenkins/job/C-HEAD-sdk.feature/575/consoleText


On 4/4/2014 11:39 PM, Markus Alexander Kuppe wrote:
On 04/04/2014 03:36 AM, Scott Lewis wrote:
I've retrieved Java8...to my home on ecf-build.osuosl.org, but I don't
seem to have permissions in /opt/hudson/tools to make a new directory
for it:

slewis@ecf-builds /opt/hudson/tools $ mkdir Java1.8_b132_x86-64
mkdir: cannot create directory `Java1.8_b132_x86-64': Permission denied
Hi Scott,

you should be able to change to the tomact user which is the user
account under which Jenkins runs.

sudo su - tomcat

It has permissions to extract the java8 archive to /opt/hudson/tools.

I have done this now and extract java8 to /opt/hudson/tools/jdk1.8.0

M.
_______________________________________________
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

Back to the top