Labs
  1. Labs
  2. LABS-333

[maven] Compatibility with war enabled plugins

    Details

    • Type: Improvement Improvement
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: Current
    • Fix Version/s: Next
    • Component/s: Magma
    • Labels:
      None

      Description

      Tomcat mojo, plugin mojo and many others work only if the project is packaged as war, but unfortunately we need a custom packaging to build magma artifacts. When magma:war is called, then that artifact could be considered as a war from that point on, at least for compatibility with those mojos.

        Activity

        Hide
        Simone Gianni added a comment -

        Still missing :

        • When using tomcat:deploy, a strange internal maven error occurrs, related to the forked lifecycle executing the tests. This could be not important, cause we mainly want to use tomcat:deploy-only
        • The generated war file and exploded war directory does not follow the war maven plugin standards, Magma generates $ {artifactId}.war, while it sould be ${artifactId}

          -$

          {version}

          .war

        Show
        Simone Gianni added a comment - Still missing : When using tomcat:deploy, a strange internal maven error occurrs, related to the forked lifecycle executing the tests. This could be not important, cause we mainly want to use tomcat:deploy-only The generated war file and exploded war directory does not follow the war maven plugin standards, Magma generates $ {artifactId}.war, while it sould be ${artifactId} -$ {version} .war
        Hide
        Simone Gianni added a comment -

        Probably it would be better to have a packaging for wars, this would not only solve this bug, but also a number of other ambiguities in the build process, like the possibility to mvn clean install a project that should be a war instead, or the possibility to check on a war that proper packages are included which is not possible right now.

        Show
        Simone Gianni added a comment - Probably it would be better to have a packaging for wars, this would not only solve this bug, but also a number of other ambiguities in the build process, like the possibility to mvn clean install a project that should be a war instead, or the possibility to check on a war that proper packages are included which is not possible right now.
        Hide
        Simone Gianni added a comment -

        Created the new packagin type, but unfortunately the tomcat plugin looks at the packaging instead of the type. This is a bug, but it is coherent with how things works in maven 2, I commented a bug already existing on MTOMCAT ( http://jira.codehaus.org/browse/MTOMCAT-23 ), both solutions would make Magma mojo to work properly.

        Show
        Simone Gianni added a comment - Created the new packagin type, but unfortunately the tomcat plugin looks at the packaging instead of the type. This is a bug, but it is coherent with how things works in maven 2, I commented a bug already existing on MTOMCAT ( http://jira.codehaus.org/browse/MTOMCAT-23 ), both solutions would make Magma mojo to work properly.

          People

          • Assignee:
            Simone Gianni
            Reporter:
            Simone Gianni
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development