Jetspeed 2
  1. Jetspeed 2
  2. JS2-445

Unable to build J2 - Failed to download, Missing version numbers

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL
    • Fix Version/s: 2.1-dev, 2.1
    • Component/s: Project Build
    • Labels:
      None
    • Environment:
      maven 1.0.2
      jdk 1.5.0_06

      Description

      When performing maven:war, releases of dependent libraries are not found.

      Output:
      maven war:install
      __ __

      \/ __ Apache_ ___
        \/ / ` \ V / -) ' \ ~ intelligent projects ~
      _   _,_ _/___ _ _ v. 1.0.2

      Attempting to download portals-bridges-common-.jar.
      WARNING: Failed to download portals-bridges-common-.jar.
      Attempting to download portals-bridges-velocity-.jar.
      WARNING: Failed to download portals-bridges-velocity-.jar.
      Attempting to download derby-.jar.
      WARNING: Failed to download derby-.jar.
      The build cannot continue because of the following unsatisfied dependencies:

      portals-bridges-common-.jar
      portals-bridges-velocity-.jar
      derby-.jar

        Activity

        Hide
        Andre Michel Gauthier added a comment -

        I have had this problem when attempting to build a custom portal with the maven plugin.
        It is possible to work around this issue by creating a project.properties based on the plugin.properties in the maven/plugin directory.
        Just the section on version dependencies should be sufficient.
        e.g.

        1. ---------------------------------------------------------------------------
        2. Dependencies versions
        3. ---------------------------------------------------------------------------
          jetspeed.version=2.0
          pluto.version=1.0.1
          portlet.api.version=1.0
          servlet.api.version=2.3
          myfaces.version=1.1.0
          spring.version=1.1.5
          portals.bridges.common.version=1.0
          portals.bridges.frameworks.version=1.0
          portals.bridges.jsf.version=1.0
          portals.bridges.perl.version=1.0
          portals.bridges.php.version=1.0
          portals.bridges.struts.version=1.2.7-1.0
          portals.bridges.velocity.version=1.0
          commons.logging.version=1.0.3
          log4j.version=1.2.8
          derby.version=10.1.1.0
        Show
        Andre Michel Gauthier added a comment - I have had this problem when attempting to build a custom portal with the maven plugin. It is possible to work around this issue by creating a project.properties based on the plugin.properties in the maven/plugin directory. Just the section on version dependencies should be sufficient. e.g. --------------------------------------------------------------------------- Dependencies versions --------------------------------------------------------------------------- jetspeed.version=2.0 pluto.version=1.0.1 portlet.api.version=1.0 servlet.api.version=2.3 myfaces.version=1.1.0 spring.version=1.1.5 portals.bridges.common.version=1.0 portals.bridges.frameworks.version=1.0 portals.bridges.jsf.version=1.0 portals.bridges.perl.version=1.0 portals.bridges.php.version=1.0 portals.bridges.struts.version=1.2.7-1.0 portals.bridges.velocity.version=1.0 commons.logging.version=1.0.3 log4j.version=1.2.8 derby.version=10.1.1.0
        Hide
        David Sean Taylor added a comment -

        The maven plugin should generate the following files:

        full-portal.xml
        core-build.xml
        jetspeed-components.xml

        All dependencies should be in these files including version numbers

        I've seen where it fails to generate the version numbers when you are building from a different directory than where your setting is in build.properties:

        #org.apache.jetspeed.portal.home = /eclipse/workspace/myproject

        Show
        David Sean Taylor added a comment - The maven plugin should generate the following files: full-portal.xml core-build.xml jetspeed-components.xml All dependencies should be in these files including version numbers I've seen where it fails to generate the version numbers when you are building from a different directory than where your setting is in build.properties: #org.apache.jetspeed.portal.home = /eclipse/workspace/myproject
        Hide
        Ate Douma added a comment -

        I fixed this earlier on the current trunk (version 2.1-dev) on March 9 and 10.
        After updating your plugin these problems will be gone.

        Show
        Ate Douma added a comment - I fixed this earlier on the current trunk (version 2.1-dev) on March 9 and 10. After updating your plugin these problems will be gone.

          People

          • Assignee:
            Ate Douma
            Reporter:
            Greg Buchanan
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development