[dna-issues] [JBoss JIRA] Commented: (DNA-493) Integration tests should not be run via Maven by default
[
https://jira.jboss.org/jira/browse/DNA-493?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-493:
-----------------------------------
I'm thinking that the following projects would be included by default:
dna-common
dna-graph
dna-repository
dna-cnd
dna-jcr
extensions/*
Then, the "tck" profile (e.g., "mvn -P tck") would add to the main
list the following:
dna-jcr-tck
dna-integration-tests
The "integration" profile (e.g., "mvn -P integration") would add to
the main list the following:
dna-jcr-tck
dna-integration-tests
docs/examples/gettingstarted
And of course there is the "release" profile, which runs all projects (basically
the above plus the 'docs' project).
Integration tests should not be run via Maven by default
--------------------------------------------------------
Key: DNA-493
URL: https://jira.jboss.org/jira/browse/DNA-493
Project: DNA
Issue Type: Task
Components: Development Environment
Affects Versions: 0.5
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.6
The dna-integration-tests project is currently included by default whenever 'mvn
clean install' is executed. Now that they are taking considerable amount of time to
execute (>1min), we should change the parent POM so that they are included only when
specified via the command line.
The benefit is that the developers don't have to wait for these integration tests to
execute (unless they want to). But, to ensure no regressions, the continuous integration
tests and the nightly Hudson jobs should be run with the integration tests enabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira