[TAV-149] Avoiding cyclic loops in test targets in Maven Created: 2006-09-06 Updated: 2006-11-09 Resolved: 2006-11-08 |
|
Status: |
Closed |
Project: |
|
Component/s: |
None |
Affects Version/s: |
|
Fix Version/s: |
None |
Type: |
Bug |
Priority: |
Minor |
Reporter: |
Assignee: |
||
Resolution: |
Not A Bug |
Votes: |
0 |
None |
|||
Remaining Estimate: |
Not Specified |
||
Time Spent: |
Not Specified |
||
Original Estimate: |
Not Specified |
Description |
|
Comments |
|
Comment by Stuart Owen [ 2006-09-14 ] |
This isn't a bug but is normal. Maven can't build taverna-java-processor until its built scufl-model, and can't build scufl-model until its built taverna-java-processor - its stuck and hence the complaint about cyclic references. Tests like this that rely on more than the module being tested are not really appropriate as a unit test, and would be better be placed within an integrated testing phase. Maven includes this phase, but the exact mechanism for building this into the build is unclear to me. |
Comment by David Withers (Inactive) [ 2006-11-08 ] |
I agree with Stuart that this is the expected behaviour and not a bug. |
Generated at Fri Nov 05 13:57:10 GMT 2021 using JIRA 6.1.2#6157-sha1:98c729218aad6de1537eb8e98889ee5562c90d96.
Tags: avoiding cyclic, [tav149], avoiding, targets, maven, cyclic, loops