Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

[harry.zh...@us.fujitsu.com]

Hi Ecelgp,

I just tried,

sdnnc@sdn-netconf:~/controller/controller$ git fetch --all --tags --prune
Fetching origin
remote: Counting objects: 1294, done.
remote: Compressing objects: 100% (238/238), done.
remote: Total 1294 (delta 491), reused 774 (delta 449), pack-reused 475
Receiving objects: 100% (1294/1294), 234.54 KiB | 0 bytes/s, done.
Resolving deltas: 100% (504/504), completed with 89 local objects.
From https://github.com/opendaylight/controller
   7378db3..34c55b1  stable/oxygen -> origin/stable/oxygen
   e254db5..39f938a  master -> origin/master
* [new tag] release/oxygen-sr2 -> release/oxygen-sr2
sdnnc@sdn-netconf:~/controller/controller$

Could you please correct me. As I understand, from the above I got * [new tag]  
   release/oxygen-sr2 -> release/oxygen-sr2, then I can make up the 
checkout commands as,
“git checkout tags/release/oxygen-sr2” to checkout the release.

The release might not be as stable as stable/oxygen branch, before it is 
finally released, May I ask if it is right?


“I am not sure I full follow the question but you could save the entire git 
repo or just the changes you did. “
I think what you understand is what I mean to ask. May I ask whether my “git 
repo” is fully contained by my local ~/.m2 directory?

Sorry for going too details. I am just trying to avoid making mistakes in such 
areas. It’s kind critical to me.


Thank you very much!

Harry


From: Luis Gomez [mailto:ece...@gmail.com]
Sent: Tuesday, June 19, 2018 4:40 PM
To: Zhang, Harry 
Cc: controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Which Release is the Most Recent in Stable State 
That Compiles




On Jun 19, 2018, at 2:26 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> wrote:

Hi Ecelgp,

Thank you very much! It compiles now.

May I ask whether settings.xml is common to all of the releases? After switched 
to stable/oxygen, it compiles even without changing the settings.xml file.

Thats weird, AFAIK ODL settings.xml is always required.



If I put some of my work under this stable/oxygen branch, someday later the 
branch is no longer supported as what happened to stable/boron, may I ask what 
the best strategy is for me to deal with the situation, in case I am not ready 
to merge my code to a new release?

The trick is to use stable release (never expires) instead of stable branch, 
you can download a given release by using a tag, for example:

git fetch --all --tags —prune
git checkout tags/release/oxygen-sr2



If I need to save my environment to share with a development team, may I ask 
which files and directories that I should save to a local storage so that our 
development efforts would not be effected by Opendaylight release supporting 
plan?

I am not sure I full follow the question but you could save the entire git repo 
or just the changes you did.




Best Regards,

Harry



From: Luis Gomez [mailto:ece...@gmail.com]
Sent: Tuesday, June 19, 2018 3:49 PM
To: Zhang, Harry mailto:harry.zh...@us.fujitsu.com>>
Cc: 
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
Subject: Re: [controller-dev] Which Release is the Most Recent in Stable State 
That Compiles

Hi Harry, stable/oxygen is the latest stable release.



On Jun 19, 2018, at 1:46 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> wrote:

Hi Everybody,

I am trying to find a recent stable branch to compile the controller and 
Netconf projects. I did,

git clone https://git.opendaylight.org/gerrit/p/controller.git
cd controller/
git checkout stable/boron

I saved the file 
https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml 
<https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml%20to%20my%20.m2>
  to my local ~/.m2/

When compiled, I got errors as following. Mr. Tom 
Pantelis<https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tpantelis> 
said “The Boron release is no longer maintained or supported. As such, the 
failed dependencies likely no longer exist on ODL nexus”.

May I ask which stable release that is still supported I should use to continue 
my tests?


Regards,

Harry



ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT 
(/home/hzhang/controller/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT: Failure to find 
org.opendaylight.odlparent:odlparent-lite:pom:1.7.5-SNAPSHOT in 
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/ was 
cached in the local repository,




The Boron release is no longer maintained or supported. As such, the failed 
dependencies likely no longer exist on ODL nexus.

___
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
h

Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

[harry.zh...@us.fujitsu.com]

Hi Ryan,

Thank you for the explanation. By time when I find something to improve, I will 
then need to learn how to contribute a delta back upstream.


Regards,

Harry



From: Ryan Goulding [mailto:ryandgould...@gmail.com]
Sent: Tuesday, June 19, 2018 4:55 PM
To: Luis Gomez 
Cc: Zhang, Harry ; 
controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Which Release is the Most Recent in Stable State 
That Compiles

Thats weird, AFAIK ODL settings.xml is always required.

He still has settings.xml, he is stating he is using the one downloaded from 
stable/oxygen, if I understand correctly.  The fact is, settings.xml hardly 
ever changes, even between releases [0].  It hasn't changed in over a year in 
fact.

The trick is to use stable release (never expires) instead of stable branch, 
you can download a given release by using a tag, for example:

If you are trying to contribute a delta back upstream to the open source code 
base instead of maintaining a "permanent" fork, then you will want to build and 
submit against master.  The stability of master has improved over the years :).

Regards,

Ryan Goulding

[0] https://github.com/opendaylight/odlparent/commits/master/settings.xml

On Tue, Jun 19, 2018 at 5:40 PM, Luis Gomez 
mailto:ece...@gmail.com>> wrote:



On Jun 19, 2018, at 2:26 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> wrote:

Hi Ecelgp,

Thank you very much! It compiles now.

May I ask whether settings.xml is common to all of the releases? After switched 
to stable/oxygen, it compiles even without changing the settings.xml file.

Thats weird, AFAIK ODL settings.xml is always required.



If I put some of my work under this stable/oxygen branch, someday later the 
branch is no longer supported as what happened to stable/boron, may I ask what 
the best strategy is for me to deal with the situation, in case I am not ready 
to merge my code to a new release?

The trick is to use stable release (never expires) instead of stable branch, 
you can download a given release by using a tag, for example:

git fetch --all --tags —prune
git checkout tags/release/oxygen-sr2



If I need to save my environment to share with a development team, may I ask 
which files and directories that I should save to a local storage so that our 
development efforts would not be effected by Opendaylight release supporting 
plan?

I am not sure I full follow the question but you could save the entire git repo 
or just the changes you did.




Best Regards,

Harry



From: Luis Gomez [mailto:ece...@gmail.com]
Sent: Tuesday, June 19, 2018 3:49 PM
To: Zhang, Harry mailto:harry.zh...@us.fujitsu.com>>
Cc: 
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
Subject: Re: [controller-dev] Which Release is the Most Recent in Stable State 
That Compiles

Hi Harry, stable/oxygen is the latest stable release.

On Jun 19, 2018, at 1:46 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> wrote:

Hi Everybody,

I am trying to find a recent stable branch to compile the controller and 
Netconf projects. I did,

git clone https://git.opendaylight.org/gerrit/p/controller.git
cd controller/
git checkout stable/boron

I saved the file 
https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml 
<https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml%20to%20my%20.m2>
  to my local ~/.m2/

When compiled, I got errors as following. Mr. Tom 
Pantelis<https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tpantelis> 
said “The Boron release is no longer maintained or supported. As such, the 
failed dependencies likely no longer exist on ODL nexus”.

May I ask which stable release that is still supported I should use to continue 
my tests?


Regards,

Harry



ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT 
(/home/hzhang/controller/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT: Failure to find 
org.opendaylight.odlparent:odlparent-lite:pom:1.7.5-SNAPSHOT in 
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/ was 
cached in the local repository,




The Boron release is no longer maintained or supported. As such, the failed 
dependencies likely no longer exist on ODL nexus.

___
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/controller-dev


___
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/controller-dev

___
cont

Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

[harry.zh...@us.fujitsu.com]

Hi Ecelgp,

Thank you very much! It compiles now.

May I ask whether settings.xml is common to all of the releases? After switched 
to stable/oxygen, it compiles even without changing the settings.xml file.

If I put some of my work under this stable/oxygen branch, someday later the 
branch is no longer supported as what happened to stable/boron, may I ask what 
the best strategy is for me to deal with the situation, in case I am not ready 
to merge my code to a new release?

If I need to save my environment to share with a development team, may I ask 
which files and directories that I should save to a local storage so that our 
development efforts would not be effected by Opendaylight release supporting 
plan?


Best Regards,

Harry



From: Luis Gomez [mailto:ece...@gmail.com]
Sent: Tuesday, June 19, 2018 3:49 PM
To: Zhang, Harry 
Cc: controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Which Release is the Most Recent in Stable State 
That Compiles

Hi Harry, stable/oxygen is the latest stable release.


On Jun 19, 2018, at 1:46 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> wrote:

Hi Everybody,

I am trying to find a recent stable branch to compile the controller and 
Netconf projects. I did,

git clone https://git.opendaylight.org/gerrit/p/controller.git
cd controller/
git checkout stable/boron

I saved the file 
https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml 
<https://github.com/opendaylight/odlparent/blob/stable/boron/settings.xml%20to%20my%20.m2>
  to my local ~/.m2/

When compiled, I got errors as following. Mr. Tom 
Pantelis<https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tpantelis> 
said “The Boron release is no longer maintained or supported. As such, the 
failed dependencies likely no longer exist on ODL nexus”.

May I ask which stable release that is still supported I should use to continue 
my tests?


Regards,

Harry



ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT 
(/home/hzhang/controller/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
org.opendaylight.controller:releasepom:0.4.5-SNAPSHOT: Failure to find 
org.opendaylight.odlparent:odlparent-lite:pom:1.7.5-SNAPSHOT in 
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/ was 
cached in the local repository,




The Boron release is no longer maintained or supported. As such, the failed 
dependencies likely no longer exist on ODL nexus.

___
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/controller-dev

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

[controller-dev] MD-SAL: Startup Project Archetype Seems Stopped Working Since Release Nitrogen

[harry.zh...@us.fujitsu.com]

Hi Team,

I have been following the procedures, 
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype,
 to create projects. It works with Carbon releases. Recently when I tried it 
with Nitrogen releases, the project creation and compilation were fine, but 
when installed with karaf feature:install, the init method of the Provider was 
not called. I tried all three Nitrogen release and they have the same problem.

The generation command that I used,

mvn archetype:generate -DarchetypeGroupId=org.opendaylight.controller 
-DarchetypeArtifactId=opendaylight-startup-archetype 
-DarchetypeRepository=http://nexus.opendaylight.org/content/repositories/opendaylight.releas/
 -DarchetypeCatalog=remote -DarchetypeVersion=1.4.3

Define value for property 'groupId': : org.opendaylight.example
Define value for property 'artifactId': : example
Define value for property 'package':  org.opendaylight.example: :
Define value for property 'classPrefix':  
${artifactId.substring(0,1).toUpperCase()}${artifactId.substring(1)}
Define value for property 'copyright': : Yoyodyne, Inc.


cd example/

mvn clean install

cd karaf/target/assembly/bin

./karaf

log:display | grep Example
The last command showed nothing. After I did feature:install and installed the 
Example feature without a problem, it still did not show "ExampleProvider 
Session Initiated".

In the karaf.log, there is no "ExampleProvider Session Initiated" either. After 
that, I added a rpc to the service, when browse the rpc from apidoc url, it 
says the api was not implemented.

Could somebody tell me whether some steps changed for bringing up a feature?

I redid the creation with Carbon release with exact the same procedure, there 
were no problems.




Thanks,

Harry







___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] MD-SAL: Startup Project Archetype Seems Stopped Working Since Release Nitrogen

[harry.zh...@us.fujitsu.com]

Hi Tom,

May I ask if you remember how to fix the problem? I could not find the previous 
record.


Thanks,

Harry


From: Tom Pantelis [mailto:tompante...@gmail.com]
Sent: Tuesday, July 24, 2018 11:43 AM
To: Zhang, Harry 
Cc: controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] MD-SAL: Startup Project Archetype Seems Stopped 
Working Since Release Nitrogen



On Tue, Jul 24, 2018 at 12:35 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> 
mailto:harry.zh...@us.fujitsu.com>> wrote:
Hi Team,

I have been following the procedures, 
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opendaylight.org_view_OpenDaylight-5FController-3AMD-2DSAL-3AStartup-5FProject-5FArchetype=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=dfNlHfBik8zrOu8n6LgLAkovupFZzDe3CoTBppdW-F4=UTYenlM54P71KglqRSqCnAcmZoI56uqdIi6ES4qEtlo=>,
 to create projects. It works with Carbon releases. Recently when I tried it 
with Nitrogen releases, the project creation and compilation were fine, but 
when installed with karaf feature:install, the init method of the Provider was 
not called. I tried all three Nitrogen release and they have the same problem.

The generation command that I used,

mvn archetype:generate -DarchetypeGroupId=org.opendaylight.controller 
-DarchetypeArtifactId=opendaylight-startup-archetype 
-DarchetypeRepository=http://nexus.opendaylight.org/content/repositories/opendaylight.releas/<https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.opendaylight.org_content_repositories_opendaylight.releas_=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=dfNlHfBik8zrOu8n6LgLAkovupFZzDe3CoTBppdW-F4=9UQBNL9NRvN5MJlUSbqj7lgl7gAyLTtPRIHqfeLTRWc=>
 -DarchetypeCatalog=remote -DarchetypeVersion=1.4.3

Define value for property 'groupId': : org.opendaylight.example
Define value for property 'artifactId': : example
Define value for property 'package':  org.opendaylight.example: :
Define value for property 'classPrefix':  
${artifactId.substring(0,1).toUpperCase()}${artifactId.substring(1)}
Define value for property 'copyright': : Yoyodyne, Inc.


cd example/

mvn clean install

cd karaf/target/assembly/bin

./karaf

log:display | grep Example
The last command showed nothing. After I did feature:install and installed the 
Example feature without a problem, it still did not show “ExampleProvider 
Session Initiated”.

In the karaf.log, there is no “ExampleProvider Session Initiated” either. After 
that, I added a rpc to the service, when browse the rpc from apidoc url, it 
says the api was not implemented.

Could somebody tell me whether some steps changed for bringing up a feature?

I redid the creation with Carbon release with exact the same procedure, there 
were no problems.



This has come up before in previous mailing list discussions and I don't recall 
the details but FWIC, it's b/c the bundle that contains the ExampleProvider 
isn't installed, either b/c it's not included in a feature or that feature 
isn't installed by the generated local karaf distro.



Thanks,

Harry








___
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/controller-dev<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opendaylight.org_mailman_listinfo_controller-2Ddev=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=dfNlHfBik8zrOu8n6LgLAkovupFZzDe3CoTBppdW-F4=6AWKBlUiFV7bvSAG_2NinQA72-jFco--WFRuqjflivg=>

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] MD-SAL: Startup Project Archetype Seems Stopped Working Since Release Nitrogen

[harry.zh...@us.fujitsu.com]

Hi Tom,

I think that I must get this fixed for Nitrogen release. May I ask whether it 
is possible?


Best Regards,

Harry


From: Michael Vorburger [mailto:vorbur...@redhat.com]
Sent: Tuesday, July 24, 2018 12:01 PM
To: Zhang, Harry 
Cc: Tom Pantelis ; controller-dev 

Subject: Re: [controller-dev] MD-SAL: Startup Project Archetype Seems Stopped 
Working Since Release Nitrogen

Harry,

On Tue, Jul 24, 2018 at 6:57 PM 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> 
mailto:harry.zh...@us.fujitsu.com>> wrote:
Hi Tom,

May I ask if you remember how to fix the problem? I could not find the previous 
record.

if you are willing to work with bleeding edge (master Fluorine, which is about 
to be frozen and released; in August) then please use the new arechetype and 
its documentation, see 
https://docs.opendaylight.org/en/latest/developer-guide/developing-apps-on-the-opendaylight-controller.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_en_latest_developer-2Dguide_developing-2Dapps-2Don-2Dthe-2Dopendaylight-2Dcontroller.html=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=qlUcpe_NM3cC0O1-pyPASj3kDLHD1aUN_3AEMKhH4gM=VIodsdJ7M8zU5osDQGKZl_8P9wHifgt2nHbHWAg3PUw=>

Tx,
M.
--
Michael Vorburger, Red Hat
vorbur...@redhat.com<mailto:vorbur...@redhat.com> | IRC: vorburger @freenode | 
~ = 
http://vorburger.ch<https://urldefense.proofpoint.com/v2/url?u=http-3A__vorburger.ch_=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=qlUcpe_NM3cC0O1-pyPASj3kDLHD1aUN_3AEMKhH4gM=hsDe1ZkE6howrEBxNQXziCIp7nK3fZC0BVZAtf-Se5k=>

Thanks,

Harry


From: Tom Pantelis [mailto:tompante...@gmail.com<mailto:tompante...@gmail.com>]
Sent: Tuesday, July 24, 2018 11:43 AM
To: Zhang, Harry mailto:harry.zh...@us.fujitsu.com>>
Cc: 
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
Subject: Re: [controller-dev] MD-SAL: Startup Project Archetype Seems Stopped 
Working Since Release Nitrogen



On Tue, Jul 24, 2018 at 12:35 PM, 
harry.zh...@us.fujitsu.com<mailto:harry.zh...@us.fujitsu.com> 
mailto:harry.zh...@us.fujitsu.com>> wrote:
Hi Team,

I have been following the procedures, 
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opendaylight.org_view_OpenDaylight-5FController-3AMD-2DSAL-3AStartup-5FProject-5FArchetype=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=dfNlHfBik8zrOu8n6LgLAkovupFZzDe3CoTBppdW-F4=UTYenlM54P71KglqRSqCnAcmZoI56uqdIi6ES4qEtlo=>,
 to create projects. It works with Carbon releases. Recently when I tried it 
with Nitrogen releases, the project creation and compilation were fine, but 
when installed with karaf feature:install, the init method of the Provider was 
not called. I tried all three Nitrogen release and they have the same problem.

The generation command that I used,

mvn archetype:generate -DarchetypeGroupId=org.opendaylight.controller 
-DarchetypeArtifactId=opendaylight-startup-archetype 
-DarchetypeRepository=http://nexus.opendaylight.org/content/repositories/opendaylight.releas/<https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.opendaylight.org_content_repositories_opendaylight.releas_=DwMFaQ=09aR81AqZjK9FqV5BSCPBw=lq6I3u0wiARfxjpvxTgWkgOXHPZRN6twp12sL6yfwoc=dfNlHfBik8zrOu8n6LgLAkovupFZzDe3CoTBppdW-F4=9UQBNL9NRvN5MJlUSbqj7lgl7gAyLTtPRIHqfeLTRWc=>
 -DarchetypeCatalog=remote -DarchetypeVersion=1.4.3

Define value for property 'groupId': : org.opendaylight.example
Define value for property 'artifactId': : example
Define value for property 'package':  org.opendaylight.example: :
Define value for property 'classPrefix':  
${artifactId.substring(0,1).toUpperCase()}${artifactId.substring(1)}
Define value for property 'copyright': : Yoyodyne, Inc.


cd example/

mvn clean install

cd karaf/target/assembly/bin

./karaf

log:display | grep Example
The last command showed nothing. After I did feature:install and installed the 
Example feature without a problem, it still did not show “ExampleProvider 
Session Initiated”.

In the karaf.log, there is no “ExampleProvider Session Initiated” either. After 
that, I added a rpc to the service, when browse the rpc from apidoc url, it 
says the api was not implemented.

Could somebody tell me whether some steps changed for bringing up a feature?

I redid the creation with Carbon release with exact the same procedure, there 
were no problems.



This has come up before in previous mailing list discussions and I don't recall 
the details but FWIC, it's b/c the bundle that contains the ExampleProvider 
isn't installed, either b/c it's not included in a feature or that feature 
isn't installed by the generated local karaf distro.



Thanks,

Harry








___
controller-dev mailing list
controller-dev@li