Cargo
  1. Cargo
  2. CARGO-871

Add tests for the Maven2 archetypes

    Details

    • Type: Test Test
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: Maven2
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      We shall add automated testing of the Add Maven2 archetypes. This way, the Codehaus CI can even test these on Maven 2.x and 3.x at each change.

        Issue Links

          Activity

          Hide
          Savas Ali Tokmen added a comment -

          I would tend to think that if the samples pass on all containers + the archetypes pass on any container (for example, Jetty); the archetypes should be OK on the other containers as well.

          EXCEPT ... when we break things like ZipUrlInstaller or others, which are tested elsewhere.

          Anders, do you know if we could set the configuration properties via Java system properties?

          Show
          Savas Ali Tokmen added a comment - I would tend to think that if the samples pass on all containers + the archetypes pass on any container (for example, Jetty); the archetypes should be OK on the other containers as well. EXCEPT ... when we break things like ZipUrlInstaller or others, which are tested elsewhere. Anders, do you know if we could set the configuration properties via Java system properties?
          Hide
          Savas Ali Tokmen added a comment -

          Any ideas on this one?

          What I'm wondering if we could, for example, the same way as we define -Dcargo.maven.wait, define things like

          -Dcargo.maven.configuration.cargo.jboss.classloading.webservice.port=xxx -Dcargo.maven.configuration.cargo.jboss.transaction.recoveryManager.port=yyy
          

          ... then we could set all ports randomly without touching the archetypes.

          Show
          Savas Ali Tokmen added a comment - Any ideas on this one? What I'm wondering if we could, for example, the same way as we define -Dcargo.maven.wait, define things like -Dcargo.maven.configuration.cargo.jboss.classloading.webservice.port=xxx -Dcargo.maven.configuration.cargo.jboss.transaction.recoveryManager.port=yyy ... then we could set all ports randomly without touching the archetypes.
          Hide
          Anders Hammar added a comment -

          I'm thinking that we'll just leave it with a test on the embedded jetty container for now.
          I really think that we is needed is a better overall test suite, and that could take care of all this. What we do here in the archetype projects should be more of some type of sanity check.

          ok?

          Show
          Anders Hammar added a comment - I'm thinking that we'll just leave it with a test on the embedded jetty container for now. I really think that we is needed is a better overall test suite, and that could take care of all this. What we do here in the archetype projects should be more of some type of sanity check. ok?
          Hide
          Savas Ali Tokmen added a comment -

          Fair enough, we should then perhaps close the issue, then

          Show
          Savas Ali Tokmen added a comment - Fair enough, we should then perhaps close the issue, then
          Hide
          Anders Hammar added a comment -

          Did some cleaning up in r2856. Closing as fixed.

          Show
          Anders Hammar added a comment - Did some cleaning up in r2856. Closing as fixed.

            People

            • Assignee:
              Anders Hammar
              Reporter:
              Savas Ali Tokmen
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: