[
https://issues.jboss.org/browse/ARQ-288?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on ARQ-288:
-------------------------------
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.
Document how to integrate Arquillian into non-Maven builds (build
integration chapter)
--------------------------------------------------------------------------------------
Key: ARQ-288
URL:
https://issues.jboss.org/browse/ARQ-288
Project: Arquillian
Issue Type: Task
Components: Documentation
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.0.CR1
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira