Re: Sling Feature Launcher: Issue with Content Packages

[Robert Munteanu]

On Wed, 2019-08-21 at 06:27 -0700, Andreas Schaefer wrote:
> BTW the issue with the Content Packages were resolved yesterday by
> adding the Extension Content ahead of the launcher in the list of
> plugin dependencies.

All is good then. Glad to hear you sorted it out.

Thanks,
Robert

Re: Sling Feature Launcher: Issue with Content Packages

[Andreas Schaefer]

Hi Robert

Sorry about this. The CP Converter tool had a change merged in yesterday and I 
forgot to update the test project. Will fix this morning.

BTW the issue with the Content Packages were resolved yesterday by adding the 
Extension Content ahead of the launcher in the list of plugin dependencies.

Cheers - Andy

> On Aug 21, 2019, at 5:40 AM, Robert Munteanu  wrote:
> 
> Hi Andy,
> 
> On Fri, 2019-08-16 at 10:50 -0700, Andreas Schaefer wrote:
>> https://github.com/schaefa/cpconverter-ssue-fm-starter/tree/issue/cp-not-launching
>> > starter/tree/issue/cp-not-launching>
>> 
>> You can launch it with:
>>  mvn clean install -P launch
>> And the open Sling OSGi Installer:
>>  http://localhost:8080/system/console/osgi-installer <
>> http://localhost:8080/system/console/osgi-installer>
> 
> I tried to build that project, but it required sling-feature-converter-
> maven-plugin . I tried to build that plugin, but it failed with a
> compilation error
> 
> [ERROR] 
> /home/robert/sources/apache/sling/feature-converter-maven-plugin/src/main/java/org/apache/sling/cpconverter/maven/mojos/ConvertCPMojo.java:[180,21]
>  no suitable constructor found for 
> DefaultFeaturesManager(boolean,int,java.io.File,java.lang.String,java.util.Map)
>constructor 
> org.apache.sling.feature.cpconverter.features.DefaultFeaturesManager.DefaultFeaturesManager()
>  is not applicable
>  (actual and formal argument lists differ in length)
>constructor 
> org.apache.sling.feature.cpconverter.features.DefaultFeaturesManager.DefaultFeaturesManager(boolean,int,java.io.File,java.lang.String,java.lang.String,java.util.Map)
>  is not applicable
>  (actual and formal argument lists differ in length)
> 
> Does compilation work for you?
> 
> Robert
> 

Re: Sling Feature Launcher: Issue with Content Packages

[Robert Munteanu]

Hi Andy,

On Fri, 2019-08-16 at 10:50 -0700, Andreas Schaefer wrote:
> https://github.com/schaefa/cpconverter-ssue-fm-starter/tree/issue/cp-not-launching
>  starter/tree/issue/cp-not-launching>
> 
> You can launch it with:
>   mvn clean install -P launch
> And the open Sling OSGi Installer:
>   http://localhost:8080/system/console/osgi-installer <
> http://localhost:8080/system/console/osgi-installer>

I tried to build that project, but it required sling-feature-converter-
maven-plugin . I tried to build that plugin, but it failed with a
compilation error

[ERROR] 
/home/robert/sources/apache/sling/feature-converter-maven-plugin/src/main/java/org/apache/sling/cpconverter/maven/mojos/ConvertCPMojo.java:[180,21]
 no suitable constructor found for 
DefaultFeaturesManager(boolean,int,java.io.File,java.lang.String,java.util.Map)
constructor 
org.apache.sling.feature.cpconverter.features.DefaultFeaturesManager.DefaultFeaturesManager()
 is not applicable
  (actual and formal argument lists differ in length)
constructor 
org.apache.sling.feature.cpconverter.features.DefaultFeaturesManager.DefaultFeaturesManager(boolean,int,java.io.File,java.lang.String,java.lang.String,java.util.Map)
 is not applicable
  (actual and formal argument lists differ in length)

Does compilation work for you?

Robert

Re: Sling Feature Launcher: Issue with Content Packages

[Andreas Schaefer]

Hi Robert

I added that bundle to my FM that also contains the packageinit bundle:

{
  
"id":"${project.groupId}:${project.artifactId}:slingfeature:sling_packageinit:${project.version}",
  "variables":{
  },
  "bundles":[
{
  "id":"org.apache.sling:org.apache.sling.jcr.packageinit:0.0.1-SNAPSHOT",
  "start-level":"10"
},
{
  
"id":"org.apache.sling:org.apache.sling.installer.factory.packages:0.1.0-SNAPSHOT",
  "start-level":"10"
}
  ]
}

That said the CPs are still listed as Unresolved Resources.
I updated my test project:

https://github.com/schaefa/cpconverter-ssue-fm-starter/tree/issue/cp-not-launching
 


You can launch it with:
mvn clean install -P launch
And the open Sling OSGi Installer:
http://localhost:8080/system/console/osgi-installer 


Cheers - Andy

> On Aug 16, 2019, at 2:10 AM, Robert Munteanu  wrote:
> 
> Hi Andy,
> 
> On Thu, 2019-08-15 at 16:02 -0700, Andreas Schaefer wrote:
>> Hi
>> 
>> When I convert and Launch the Peregrine CMS then I see that all
>> converted Content Packages remain in ‘Untransformed Resources’ state
>> when I look at the /system/console/osgi-installer page.
>> 
>> Is there a way to figure out why they remain in that state?
>> 
>> I set the launcher to verbose but I do not see anything showing up
>> nor do I see any issues in the error.log.
> 
> IIRC it means that there is no installer that claimed and processed the
> resources. 
> 
> Can you try adding 
> 
>  https://github.com/apache/sling-org-apache-sling-installer-factory-packages
> 
> to your app and see if that fixes the issue?
> 
> Thanks,
> Robert
> 

Re: Sling Feature Launcher: Issue with Content Packages

[Robert Munteanu]

Hi Andy,

On Thu, 2019-08-15 at 16:02 -0700, Andreas Schaefer wrote:
> Hi
> 
> When I convert and Launch the Peregrine CMS then I see that all
> converted Content Packages remain in ‘Untransformed Resources’ state
> when I look at the /system/console/osgi-installer page.
> 
> Is there a way to figure out why they remain in that state?
> 
> I set the launcher to verbose but I do not see anything showing up
> nor do I see any issues in the error.log.

IIRC it means that there is no installer that claimed and processed the
resources. 

Can you try adding 

  https://github.com/apache/sling-org-apache-sling-installer-factory-packages

to your app and see if that fixes the issue?

Thanks,
Robert

Re: Sling Feature Launcher: Issue with Content Packages

[Andreas Schaefer]

Could it be that the issue is with the ‘cloud launcher’ as the ‘jcrinstall’ 
works.

Here is a test project that will showcase the issue:

https://github.com/schaefa/cpconverter-ssue-fm-starter/tree/issue/cp-not-launching
 


- Andy

> On Aug 15, 2019, at 4:02 PM, Andreas Schaefer  
> wrote:
> 
> Hi
> 
> When I convert and Launch the Peregrine CMS then I see that all converted 
> Content Packages remain in ‘Untransformed Resources’ state when I look at the 
> /system/console/osgi-installer page.
> 
> Is there a way to figure out why they remain in that state?
> 
> I set the launcher to verbose but I do not see anything showing up nor do I 
> see any issues in the error.log.
> 
> Cheers - Andy Schaefer

Sling Feature Launcher: Issue with Content Packages

[Andreas Schaefer]

Hi

When I convert and Launch the Peregrine CMS then I see that all converted 
Content Packages remain in ‘Untransformed Resources’ state when I look at the 
/system/console/osgi-installer page.

Is there a way to figure out why they remain in that state?

I set the launcher to verbose but I do not see anything showing up nor do I see 
any issues in the error.log.

Cheers - Andy Schaefer