Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ice-dev] Adding ECF modules - Building ICE
Hello ICE-Dev,

I made some local changes to Core and ran the Core tests which are passing. No changes were necessary on the Client.java side. These are small changes to try and enable Remote OSGi first and ensure that ICE can startup.

I am now trying to build the ICE package with my changes, but I am facing a build error here. I have looked up the Tycho Dependency Resolution link that is usually printed out, but I am still not able to resolve the build error which is:

[INFO] Resolving dependencies of MavenProject: org.eclipse.ice:org.eclipse.ice.client:2.1.8-SNAPSHOT @ /home/(user)/github/ice/org.eclipse.ice.client/pom.xml
[INFO] {osgi.os=linux, osgi.ws=gtk, org.eclipse.update.install.features=true, osgi.arch=x86}
[ERROR] Cannot resolve project dependencies:
[ERROR]   Software being installed: org.eclipse.ice.client 2.1.8.qualifier
[ERROR]   Missing requirement: org.eclipse.ice.client 2.1.8.qualifier requires 'bundle org.eclipse.ecf.osgi.services.distribution 2.1.0' but it could not be found
[ERROR] 

With Debug messages enabled, it looks like ice.client depends on ice.core (through iCore) and so the real issue comes from ice.core package. I have tried adding ecf.osgi.services.distribution as a bundle and package for both the ice.client and ice.core Manifests but it doesn't resolve the issue.

I guess I have to modify the pom.xml file of either core or client, or should it be the parent POM file? If so, it is not clear where I should add the support for the ecf.osgi.services package.

Please take a look at my changes which are stored at
https://github.com/knram06/ice/tree/remoteosgi2

To reproduce the issue:
1) The target platform should be set using org.eclipse.ice.target.neon/modified_ecf.target which has the entries for the ECF Modules. 
2) Using Build ICE.launch, the error is thrown when ice.client is being built.

Hope this helps in reproducing the issue. Any directions on resolving this would be great.

Thanks,
Ram



On Fri, Sep 9, 2016 at 9:36 AM Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx> wrote:
Thanks a lot Robert and Jay. The Manifest file edit was very useful and I don't have the import error right now. I will revert if I face any issue with the connector installation.

Thanks,
Ram

On Fri, Sep 9, 2016 at 8:28 AM Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:

Ram,

The manifest that Robert mentions is in the META-INF directory of every bundle.

For the Connectors, if you open up any pom.xml file, you should see a red error at the top that gives you the option to install more connectors if you hover over it. Just click on it and follow the on screen instructions. See step 1 here. Once you install the connector, this error should go away. Let me know if you have trouble getting them installed.

I'm on travel so I will be slow to respond, but Robert and Greg will help you.

Jay


On Sep 8, 2016 3:54 PM, "Smith, Robert W." <smithrw@xxxxxxxx> wrote:

Ram,


Eclipse's automatic detection for whether it can find the package you want to import can be hit and miss. You can go into the MANIFEST.MF file in org.eclipse.ice.core, open the Dependencies tab, and click "Add..." in the Imported Packages section to add a package (in this case org.eclipse.ecf.core and org.eclipse.ecf.remoteservice) explicitly. Alternatively, I seem to have better luck with Eclipse finding the package itself when I create a variable of the type I want (eg IContainer test = null;) and hover over the resulting error. 


Robert

From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx>
Sent: Thursday, September 08, 2016 4:59 PM
To: ice developer discussions
Subject: Re: [ice-dev] Adding ECF modules - Building ICE
 
Hello all,

I took the neon.target file from the jay/rap branch and modified it to remove extra repositories. So I now have a Target Platform that includes ECF Modules. When I proceed from here, I am facing an issue.

I tried to introduce relevant imports in Core.java but they don't get picked up (Unable to resolve imports). I then choose the option to search the repository for org.eclipse.ecf.core (search_artifact.png).

It finds a module and when I select it (ecf_core_artifact.png), I now get even more import errors in other modules (errors_after_add.png), which I am not able to understand. Can anyone explain how to resolve this?

My changes are in

Thanks,
Ram


On Wed, Sep 7, 2016 at 5:43 PM Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx> wrote:
Hi Robert,

Ah ok. I thought I was keeping my fork synchronized with the upstream repository, using the controls from within ICE, but I guess it didn't pull the changes.

Once I updated my local repository with the upstream repo (from the terminal), I get no errors and it seems fine. Thanks for pointing that out. I am yet to try the jay/rap branch for the ECF modules.

Thanks,
Ram


On Wed, Sep 7, 2016 at 4:52 PM Smith, Robert W. <smithrw@xxxxxxxx> wrote:

​Ram,


Your repo has references to an old class that's been recently taken out of EAVP. You'll need to merge with the latest version of next from our repo to get the update that removes these references. (This is separate from the "plugin execution not covered by lifecycle..." problem.)


Robert

From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx>
Sent: Wednesday, September 07, 2016 3:49 PM

To: ice developer discussions
Subject: Re: [ice-dev] Adding ECF modules - Building ICE
Hello Jay,

Thanks for offering to take a look. What I did before was to change the Target Platform in Window->Preferences. Upon rebuilding the workspace is when I get the version error.

I created a new target file from the existing neon target file and added the ECF modules in it. I don't get the version error, but I still get new errors now. My changes are in:


The main change is a new file ram_neon2.target under o.e.ice.target.neon. I had added a new Software Site for the ECF modules. Please take a look when possible.

I will checkout the jay/rap branch and the neon target file as well.

Thanks,
Ram


On Wed, Sep 7, 2016 at 2:05 PM Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Ram,


Will you commit your target with the new ECF pieces added to your fork? One of us will take a look at it and see if we can fix it.


Also, I have a new ICE Neon target that might work better for you if you are brave enough to try it. ;-) It is in the jay/rap branch and already contains some parts of ECF. It resolves fine for me on my laptop, but the version of ICE in the branch will not build correctly with Maven because of dependency issues.


FYI - the goal of that branch is to see how well Eclipse RAP will work with ICE, which might interest you given what you are working on.


Jay


Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx>
Sent: Wednesday, September 07, 2016 11:45 AM

To: ice developer discussions
Subject: Re: [ice-dev] Adding ECF modules - Building ICE
Hi Jay,

When I use the Developer->ICE->Clone option, it directly takes the code from the eclipse/ice GitHub repo and sets it up, which doesn't have issues and I use the Neon target. If I manually add my forked repo, then the connectors and other options are not setup and I also don't see the option to install them, but I will double check that. In the previous case, I had added my forked repo and didn't use the Developer menu.

Whether I use my forked repo or the original eclipse/ice repo, I get the same error when I try to add ECF modules though, i.e. the version error. When adding ECF, I make a copy of the Neon target platform and then specify the ECF Plugins. When the workspace is rebuilt, I get the error.

Hope this helps.

Regards,
Ram



On Wed, Sep 7, 2016 at 11:19 AM Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Ram,


You should use the Neon target. Unfortunately, those errors that you see are caused by a Maven lifecycle bug. If you open up any pom.xml file, you should see a red error at the top that gives you the option to install more connectors. Once you install those, this error should go away. Let me know if you have trouble getting them installed.


We have it setup so that it would automatically install those connectors if you used the Developer->ICE menu. Did you use that to check out your project or create your fork?


Jay


Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx>
Sent: Wednesday, September 07, 2016 11:11 AM
To: ice developer discussions
Subject: Re: [ice-dev] Adding ECF modules - Building ICE
 
Hi Jay,

If I select the org.eclipse.target.neon and click on "Set as Target Platform", I get a few errors overall (neon_target.png). These were present earlier too, but they didn't seem like "compile" errors and I didn't report it.

Project->Clean or Restarting ICE didn't resolve those errors too.

I have no changes in my fork since I was trying to update my Target Platform to include ECF modules. I can try recloning my fork again, but I think I will have the same issues.

Thanks,
Ram


On Wed, Sep 7, 2016 at 10:46 AM Billings, Jay Jay <billingsjj@xxxxxxxx> wrote:

Ram,


That's weird. The 20160906 build should be on the latest build of Eclipse Neon. Can you check to see if you have loaded the org.eclipse.target.mars target or the org.eclipse.target.neon target? This could be the problem.


Is this checked into your fork?


Jay


Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
From: ice-dev-bounces@xxxxxxxxxxx <ice-dev-bounces@xxxxxxxxxxx> on behalf of Ramachandran K. Narayanan <knarayanan@xxxxxxxxxxxxx>
Sent: Wednesday, September 07, 2016 10:26 AM
To: ice developer discussions
Subject: [ice-dev] Adding ECF modules - Building ICE
 
Hello ICE-Dev,

I am trying to import org.eclipse.ecf modules and I am having trouble setting up the relevant Target Platform in ICE (using ICE to build ICE).

I follow the instructions in adding ECF to the Target Platform from

But, when the workspace is rebuilt, I get the following error (ecf_sdk_error.png). I am using the ICE install from the stable nightly build. The screenshot is from 6th September zip file.

It looks like

a) I should use an older version of ECF so that the conflict does not occur. If someone has set this up before in ICE, could you explain how?

b) Maybe I should just work on ICE code using Eclipse Neon? Is the Plugin Environment detecting an "older" version of Eclipse in ICE somehow? I don't entirely understand the error.

Thanks for any inputs on this.

Regards,
Ram
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248

_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248
--
Ramachandran K. Narayanan
Software Engineer
RNET Technologies Inc.
240 W.Elmwood Drive, Suite 2010
Dayton, OH 45459-4248

Back to the top