Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-288

Document how to integrate Arquillian into non-Maven builds (build integration chapter)

    Details

    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Estimated Difficulty:
      Medium

      Description

      There is a misconception spreading that Arquillian can only be used from a Maven. We need a build integration chapter to clarify the message that Arquillian is build-independent. The chapter should describe in general how Arquillian is hooked into a build system, then provide tutorials for Ant and Gradle.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            dan.j.allen Dan Allen added a comment - - edited
            Show
            dan.j.allen Dan Allen added a comment - - edited Tracking branch: http://github.com/mojavelinux/arquillian/tree/ARQ-288_build_int
            Hide
            aslak Aslak Knutsen added a comment -

            moved to https://docs.jboss.org/author/display/ARQ/Build+system+integration

            Dan, this still considered work in progress?

            Show
            aslak Aslak Knutsen added a comment - moved to https://docs.jboss.org/author/display/ARQ/Build+system+integration Dan, this still considered work in progress?
            Hide
            dan.j.allen Dan Allen added a comment -

            I believe so, at least in the sense that we have accomplished the task of introducing the documentation. From this point forward, we can deal with the content through issue reports.

            We should have QA verify the instructions.

            The only thing missing is that we still don't have a well-documented way of listing which dependencies are required if you didn't want to use a dependency management system. My vision for this is a script which will pull down the dependencies you need for a given container and stick them in a folder somewhere. Obviously, you limit your ability to use different containers, which I don't think needs to be our concern. In fact, the best way to resolve it is to simply be able to produce a report of which JARs are used, with links to download them.

            Show
            dan.j.allen Dan Allen added a comment - I believe so, at least in the sense that we have accomplished the task of introducing the documentation. From this point forward, we can deal with the content through issue reports. We should have QA verify the instructions. The only thing missing is that we still don't have a well-documented way of listing which dependencies are required if you didn't want to use a dependency management system. My vision for this is a script which will pull down the dependencies you need for a given container and stick them in a folder somewhere. Obviously, you limit your ability to use different containers, which I don't think needs to be our concern. In fact, the best way to resolve it is to simply be able to produce a report of which JARs are used, with links to download them.
            Hide
            aslak Aslak Knutsen added a comment -

            Jar documentation spawn of to separate issue, ARQ-463

            Show
            aslak Aslak Knutsen added a comment - Jar documentation spawn of to separate issue, ARQ-463
            Hide
            aslak Aslak Knutsen added a comment -

            1.0.0.CR1 Released, Closing

            Show
            aslak Aslak Knutsen added a comment - 1.0.0.CR1 Released, Closing

              People

              • Assignee:
                dan.j.allen Dan Allen
                Reporter:
                dan.j.allen Dan Allen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development