Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-15781

Problem with Ant build Tasks for Ext environment

    Details

    • Branch Version/s:
      6.0.x, 5.2.x
    • Backported to Branch:
      Committed

      Description

      What we're seeing:

      In our Ext Environment, we have classes in both the ext-impl/src and ext-util-java/src locations. As the ext-custom-ext-util-java.jar ends up in the portal class path, we expected we could have classes in ext-impl depend on ext-util-java classes. However, it seems the ant tasks only provide the ext-service/classes to each of the other ext section's classpath when compiling.

      What we would like to know:

      Is this a bug with the Ext Ant build tasks, or is this intentional? If this is intentional, could you provide a bit of information on why ext-impl classes should be prevented from depending on ext-util-java, ext-util-bridges, ext-util-taglib?

      NOTE: Tried Plugins SDK where there's a java class in ext-util-java and a java class in ext-impl. The class in ext-impl tries to call a method in the ext-util-java, when deploying ant on the EXT, there is a build error. (Used Liferay's PwdGenerator.java and created a class in impl to call a method that exists in Liferay first. Ant build works. When an additional method is added to PwdGenerator.java, build error shows up when compiling.)

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  6 years, 27 weeks, 4 days ago

                  Packages

                  Version Package
                  --Sprint - SP
                  6.1.0 CE RC1