AWS package cannot be resolved by Felix Console

Include  "bom" and "aws-java-sdk-cloudfront"  in Embed-Dependency

example:

<plugin>

<groupId>org.apache.felix</groupId>

<artifactId>maven-bundle-plugin</artifactId>

<extensions>true</extensions>

<configuration>

<instructions>

<Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>

<Bundle-Name>${project.name}</Bundle-Name>

<Embed-Dependency>bom,aws-java-sdk-cloudfront,*;scope=compile</Embed-Dependency>

<Import-Package>*</Import-Package>

</instructions>

</configuration>

</plugin>

If that doesn't work, please share your pom.xml's  maven-bundle-plugin configuration

Thank you so much for the prompt answer. Unfortunately it did not work. My Core Pom is as follows:

<?xml version="1.0" encoding="UTF-8"?>

<!-- | Copyright 2014 Adobe Systems Incorporated | | Licensed under the Apache

License, Version 2.0 (the "License"); | you may not use this file except

in compliance with the License. | You may obtain a copy of the License at

| | http://www.apache.org/licenses/LICENSE-2.0 | | Unless required by applicable

law or agreed to in writing, software | distributed under the License is

distributed on an "AS IS" BASIS, | WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND, either express or implied. | See the License for the specific language

governing permissions and | limitations under the License. -->

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

    <modelVersion>4.0.0</modelVersion>

    <parent>

        <groupId>com.company</groupId>

        <artifactId>CC-aem</artifactId>

        <version>${companyCurrent}</version>

        <relativePath>../pom.xml</relativePath>

    </parent>

    <artifactId>CC-aem.core</artifactId>

    <packaging>bundle</packaging>

    <name>Comapny CMS (AEM6) - Core</name>

    <description>Core bundle for Company CMS (AEM6)</description>

    <build>

        <plugins>

            <plugin>

                <groupId>org.apache.felix</groupId>

                <artifactId>maven-scr-plugin</artifactId>

            </plugin>

            <plugin>

                <groupId>org.apache.felix</groupId>

                <artifactId>maven-bundle-plugin</artifactId>

                <extensions>true</extensions>

                <configuration>

                    <instructions>

                        <!-- <Embed-Dependency> artifactId1, artifactId2;inline=true </Embed-Dependency> -->

                    </instructions>

                </configuration>

            </plugin>

        </plugins>

    </build>

    <profiles>

        <!-- Development profile: install only the bundle -->

        <profile>

            <id>autoInstallBundle</id>

            <activation>

                <activeByDefault>false</activeByDefault>

            </activation>

            <build>

                <plugins>

                    <plugin>

                        <groupId>org.apache.sling</groupId>

                        <artifactId>maven-sling-plugin</artifactId>

                        <configuration>

                            <slingUrlSuffix>/apps/company/install/</slingUrlSuffix>

                            <failOnError>true</failOnError>

                        </configuration>

                    </plugin>

                </plugins>

            </build>

        </profile>

    </profiles>

    <dependencies>

        <!--AWS Dependency -->

        <dependency>

            <groupId>com.amazonaws</groupId>

            <artifactId>aws-java-sdk-cloudfront</artifactId>

        </dependency>

        <!-- OSGi Dependencies -->

        <dependency>

            <groupId>org.apache.felix</groupId>

            <artifactId>org.apache.felix.scr</artifactId>

        </dependency>

        <dependency>

            <groupId>org.apache.felix</groupId>

            <artifactId>org.apache.felix.scr.annotations</artifactId>

        </dependency>

        <dependency>

            <groupId>biz.aQute</groupId>

            <artifactId>bndlib</artifactId>

        </dependency>

        <dependency>

            <groupId>org.osgi</groupId>

            <artifactId>org.osgi.core</artifactId>

        </dependency>

        <dependency>

            <groupId>org.osgi</groupId>

            <artifactId>org.osgi.compendium</artifactId>

        </dependency>

        <!-- Other Dependencies -->

        <dependency>

            <groupId>org.slf4j</groupId>

            <artifactId>slf4j-api</artifactId>

        </dependency>

        <dependency>

            <groupId>javax.jcr</groupId>

            <artifactId>jcr</artifactId>

        </dependency>

        <dependency>

            <groupId>javax.servlet</groupId>

            <artifactId>servlet-api</artifactId>

        </dependency>

        <dependency>

            <groupId>com.adobe.aem</groupId>

            <artifactId>aem-api</artifactId>

        </dependency>

        <dependency>

            <groupId>junit</groupId>

            <artifactId>junit</artifactId>

        </dependency>

        <dependency>

            <groupId>org.mockito</groupId>

            <artifactId>mockito-all</artifactId>

        </dependency>

        <dependency>

            <groupId>junit-addons</groupId>

            <artifactId>junit-addons</artifactId>

        </dependency>

        <dependency>

            <groupId>org.slf4j</groupId>

            <artifactId>slf4j-log4j12</artifactId>

            <!-- the binding version needs to match the slf4j api -->

            <version>1.5.11</version>

            <scope>test</scope>

        </dependency>

        <dependency>

            <groupId>org.projectlombok</groupId>

            <artifactId>lombok</artifactId>

            <version>1.18.6</version>

            <scope>provided</scope>

        </dependency>

    </dependencies>

</project>

Try getting the JARs that expose these packages and wrap them into an OSGi bundle and deploy to AEM. That way - you know for sure these Java Packages are in the OSGi service container.

Thank you Macdonald! How do I do that with my Core bundle?

Thanks

The nice thing about AEM is you can build an OSGi bundle that contains dependent JARS separate from your project. Any OSGi bundle that contains AWS JARs will resolve these Java packages for any OSGi bundle that requires them.

One way to build an OSGi bundle that contains other JARS is documented here - notice how we wrap the SIMPLE JSON JAR into a bundle.

Adobe Experience Manager Help | Submitting Adobe Experience Manager form data to Java Sling Servlets

Thanks Macdonald. I have done that and now I can see the dependency in the depfinder:

The problem is my project still can't find those dependencies:

My POM currently looks like this:

<build>

   <plugins>

   <plugin>

   <groupId>org.apache.felix</groupId>

   <artifactId>maven-scr-plugin</artifactId>

   </plugin>

   <plugin>

   <groupId>org.apache.felix</groupId>

   <artifactId>maven-bundle-plugin</artifactId>

   <extensions>true</extensions>

   <configuration>

   <instructions>

   </instructions>

   </configuration>

   </plugin>

   </plugins>

</build>

If I add the following to the POM instructions in the POM

<build>

   <plugins>

   <plugin>

   <groupId>org.apache.felix</groupId>

   <artifactId>maven-scr-plugin</artifactId>

   </plugin>

   <plugin>

   <groupId>org.apache.felix</groupId>

   <artifactId>maven-bundle-plugin</artifactId>

   <extensions>true</extensions>

   <configuration>

   <instructions>

   <Embed-Dependency>aws-java-sdk-osgi,*;scope=compile</Embed-Dependency>

   <Import-Package>com.amazonaws.*,*</Import-Package>

   </instructions>

   </configuration>

   </plugin>

   </plugins>

</build>

I get even more errors... Does this mean I need to wrap those extra dependencies to my project bundle I created separately? Kinda feels like I am going down a rabbit hole haha

Or are the instructions to the pom not the correct one? Help....

For com.fasterxml.* packages, install OSGIfied bundles from Maven Repository: Search/Browse/Explore ​

for org.springframework.*, aspectj.*, joda.* use Spring DM bundles and install in OSGI

for org.apache.http.*, update maven-bundle-plugin to import it dynamically from AEM-OOB -- use org.apache.httpcomponents.httpcore

for netty, use OSGIfied bundle

for amazon.*, either use OSGIfied bundles or package them into your code bundle  using Embed-Dependency as mentioned above

What do you mean by OSGified bundles?

I meant OSGI bundles and not that jar files (you'd find both versions on web in mvnrepository and other sites)

Mate the bundles are already there... I don't have to install them again. I can find them through the depfinder

Problem is they cannot be resolved... Same happens to the AWS packages. I followed Macdonalds advice and created a bundle that exports them, but for some reason they are not picked up.