Developing JSPS in eclipse cannot resolve some dependencies | Community
Skip to main content
C
clives5916718
Level 2
October 16, 2015
Solved

Developing JSPS in eclipse cannot resolve some dependencies

  • October 16, 2015
  • 8 replies
  • 3590 views

I am trying to move all JSP dev from using CRXDE lite to using Eclipse

I do not seem able to get the following instance variables to be able to point to the correct classes in my maven.

resourceResolver

currentPage e.g.String navstart = currentPage.getPath();

properties e.g. properties.get("pageItems", "1");

resource e.g. resource.getPath()

xssAPI e.g. xssAPI.encodeForHTML(cls)

sling.getService(example.class)

 

I have used the following mavendependencies plugins for my content module in my Maven Project. I am not sure what plugin or dependencies I am missing.

I have been working off of the following dev articles

https://docs.adobe.com/docs/en/cq/5-3/developing/developmenttools/developing_with_eclipse.html

http://docs.adobe.com/docs/en/aem/6-0/develop/dev-tools/ht-projects-maven.html#How-To%20Work%20with%20JSPs

 

 

    <!-- ====================================================================== -->
    <!-- D E P E N D E N C I E S -->
    <!-- ====================================================================== -->
    <dependencies>
        <dependency>
            <groupId>za.co.checkers</groupId>
            <artifactId>Checkers.core</artifactId>
            <version>0.0.1-SNAPSHOT</version>
        </dependency>

        <dependency>
            <groupId>com.adobe.aem</groupId>
            <artifactId>aem-api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.jcr.jcr-wrapper</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.api</artifactId>
        </dependency>

        <dependency>
            <groupId>com.day.cq</groupId>
            <artifactId>cq-commons</artifactId>
            <!-- com.day.cq.commons -->
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-commons</artifactId>
            <!-- com.day.cq.wcm.commons -->
        </dependency>
        <dependency>
            <groupId>com.day.commons</groupId>
            <artifactId>day-commons-jstl</artifactId>
            <!-- javax.servlet.jsp.jstl.core -->
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-taglib</artifactId>
            <!-- com.day.cq.wcm.tags -->
        </dependency>
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.scripting.jsp.taglib</artifactId>
            <!-- org.apache.sling.scripting.jsp.taglib -->
        </dependency>
        <dependency>
            <groupId>com.adobe.granite</groupId>
            <artifactId>com.adobe.granite.xssprotection</artifactId>
            <!-- com.adobe.granite.xss -->
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-core</artifactId>
            <!-- com.day.cq.wcm.core.components -->
        </dependency>
        <dependency>
            <groupId>org.apache.commons</groupId>
            <artifactId>commons-lang3</artifactId>
            <!-- org.apache.commons.lang3 -->
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
        </dependency>

        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-api</artifactId>
            <!-- com.day.cq.wcm.api -->
        </dependency>
        <dependency>
            <groupId>com.day.cq.wcm</groupId>
            <artifactId>cq-wcm-foundation</artifactId>
        </dependency>
    </dependencies>
</project>

and the following plugins

<plugins>
                        <plugin>
                            <groupId>org.eclipse.m2e</groupId>
                            <artifactId>lifecycle-mapping</artifactId>
                            <version>1.0.0</version>
                            <configuration>
                                <lifecycleMappingMetadata>
                                    <pluginExecutions>
                                        <pluginExecution>
                                            <pluginExecutionFilter>
                                                <groupId>org.apache.sling</groupId>
                                                <artifactId>maven-jspc-plugin</artifactId>
                                                <versionRange>[2.0.6,)</versionRange>
                                                <goals>
                                                    <goal>jspc</goal>
                                                </goals>
                                            </pluginExecutionFilter>
                                            <action>
                                                <ignore />
                                            </action>
                                        </pluginExecution>
                                        <pluginExecution>
                                            <pluginExecutionFilter>
                                                <groupId>org.apache.maven.plugins</groupId>
                                                <artifactId>maven-clean-plugin</artifactId>
                                                <versionRange>[2.4.1,)</versionRange>
                                                <goals>
                                                    <goal>clean</goal>
                                                </goals>
                                            </pluginExecutionFilter>
                                            <action>
                                                <ignore />
                                            </action>
                                        </pluginExecution>
                                    </pluginExecutions>
                                </lifecycleMappingMetadata>
                            </configuration>
                        </plugin>
                    </plugins>
                </pluginManagement>
                <plugins>
                    <plugin>
                        <artifactId>maven-resources-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>copy-resources</id>
                                <phase>generate-sources</phase>
                                <goals>
                                    <goal>copy-resources</goal>
                                </goals>
                                <configuration>
                                    <outputDirectory>${project.build.directory}/jsps-to-compile</outputDirectory>
                                    <resources>
                                        <resource>
                                            <directory>src/main/content/jcr_root</directory>
                                            <includes>
                                                <include>apps/**</include>
                                                <include>libs/foundation/global.jsp</include>
                                            </includes>
                                        </resource>
                                    </resources>
                                </configuration>
                            </execution>
                        </executions>
                    </plugin>
                    <plugin>
                        <groupId>org.apache.sling</groupId>
                        <artifactId>maven-jspc-plugin</artifactId>
                        <version>2.0.6</version>
                        <executions>
                            <execution>
                                <id>compile-jsp</id>
                                <goals>
                                    <goal>jspc</goal>
                                </goals>
                                <configuration>
                                    <jasperClassDebugInfo>false</jasperClassDebugInfo>
                                    <sourceDirectory>${project.build.directory}/jsps-to-compile</sourceDirectory>
                                    <outputDirectory>${project.build.directory}/ignoredjspc</outputDirectory>
                                </configuration>
                            </execution>
                        </executions>
                    </plugin>
               
     
                </plugins>

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by edubey

    Hi, 

    It is recommended to develop in eclipse with AEM and Sling plugin installed.It will help to resolve all your dependency.

    Please follow steps given here : http://adobeaemclub.com/aem-eclipse-plugin-setup-tutorial/

    8 replies

    O
    Adobe Employee
    ogillAdobe Employee
    Adobe Employee
    October 16, 2015

    Hi Clive,

    it seems you are using AEM6, in which case you can use the uber jar rather than the individual dependencies[1]

    If you feel you want to use the individual dependencies, then you can use the following URL

    http://localhost:4502/system/console/depfinder

    In the above page, you can enter the actual class that can't be resolved in Eclipse, and AEM will tell you the internal version of the bundle. You can then set the version in your master pom and mark it as provided.

    Regards,

    Opkar

    [1]http://blogs.adobe.com/experiencedelivers/experience-management/aem6-maven-dependencies-simplicity/

      C
      clives5916718Author
      Level 2
      October 16, 2015

      I am using these plugins. The difficulty I have is that I have not been able to find much information on them besides using them to connect to an aem instance for debugging. I would greatly appreciate it if anyone could help me with finding a detailed explanation of the full features of the plugins.

      C
      clives5916718Author
      Level 2
      October 16, 2015

      Thank you for the article.

       

      I have gone through it steps, it helped a lot.

      But I still cannot find some classes. None of the maven dependencies resolve

      String selectorPath = currentPage.adaptTo(Resource.class).getResourceMetadata().getResolutionPathInfo();

      currentPage throws error class not found, so does Resource, and ResourceReslover.

       

      My content project and my AEM are in sync from using the file vault.

       

      Another dificulty is that the development article shows to add the following dependencies into the content pom. Bit these have no version numbers or example of Dependencies with version numbers to place dependencies inside the parent pom

       

       

              <dependency>
                  <groupId>org.apache.sling</groupId>
                  <artifactId>org.apache.sling.jcr.jcr-wrapper</artifactId>
                  <!-- javax.jcr -->
              </dependency>
              <dependency>
                  <groupId>org.apache.sling</groupId>
                  <artifactId>org.apache.sling.api</artifactId>
              </dependency>
              <dependency>
                  <groupId>com.day.cq</groupId>
                  <artifactId>cq-commons</artifactId>
                  <!-- com.day.cq.commons -->
              </dependency>
              <dependency>
                  <groupId>com.day.cq.wcm</groupId>
                  <artifactId>cq-wcm-commons</artifactId>
                  <!-- com.day.cq.wcm.commons -->
              </dependency>
              <dependency>
                  <groupId>com.day.cq.wcm</groupId>
                  <artifactId>cq-wcm-api</artifactId>
                  <!-- com.day.cq.wcm.api -->
              </dependency>
              <dependency>
                  <groupId>com.day.commons</groupId>
                  <artifactId>day-commons-jstl</artifactId>
                  <!-- javax.servlet.jsp.jstl.core -->
              </dependency>
              <dependency>
                  <groupId>com.day.cq.wcm</groupId>
                  <artifactId>cq-wcm-taglib</artifactId>
                  <!-- com.day.cq.wcm.tags -->
              </dependency>
              <dependency>
                  <groupId>org.apache.sling</groupId>
                  <artifactId>org.apache.sling.scripting.jsp.taglib</artifactId>
                  <!-- org.apache.sling.scripting.jsp.taglib -->
              </dependency>
              <dependency>
                  <groupId>com.adobe.granite</groupId>
                  <artifactId>com.adobe.granite.xssprotection</artifactId>
                  <!-- com.adobe.granite.xss -->
              </dependency>
              <dependency>
                  <groupId>com.day.cq.wcm</groupId>
                  <artifactId>cq-wcm-core</artifactId>
                  <!-- com.day.cq.wcm.core.components -->
              </dependency>
              <dependency>
                  <groupId>org.apache.commons</groupId>
                  <artifactId>commons-lang3</artifactId>
                  <!-- org.apache.commons.lang3 -->
              </dependency>
              <dependency>
                  <groupId>org.slf4j</groupId>
                  <artifactId>slf4j-api</artifactId>
              </dependency>

      smacdonald2008
      smacdonald2008
      Level 10
      October 16, 2015

      You can sync JSP (and other nodes/files) from the AEM JCR (CRXDE lite) to Eclipse using vault. See this community article - it shows you how to sync between these tools and setup Eclipse to use these JSPs. (see Prepare for JSP support in Eclipse): 

      https://helpx.adobe.com/experience-manager/using/creating-aem-project-using-eclipse.html

        edubey
        edubeyAccepted solution
        Level 10
        October 16, 2015

        Hi, 

        It is recommended to develop in eclipse with AEM and Sling plugin installed.It will help to resolve all your dependency.

        Please follow steps given here : http://adobeaemclub.com/aem-eclipse-plugin-setup-tutorial/

          jorgefdez205
          jorgefdez205
          Level 2
          January 4, 2016

          Hi Clive,

          I had the same issue and I just included the uber-jar as external jar in my project and all solved ...

          I don't know if this is helpful but better late than never..

          Thanks

          C
          Clive_Stewart
          Level 6
          January 5, 2016

          Thank you Jorge, I will try the uber.jar

           

          regards

          Clive

          C
          Clive_Stewart
          Level 6
          January 5, 2016

          Hi Jorge,

          I tried the uber.jar.

          My problem is resolved.

          Thank you

          Clive Stewart

          Terms & ConditionsAccessibility statement

          Loading footer...