You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2010/01/23 20:10:18 UTC
[jira] Created: (BUILDR-365) test task should use the test compile
dependencies
test task should use the test compile dependencies
--------------------------------------------------
Key: BUILDR-365
URL: https://issues.apache.org/jira/browse/BUILDR-365
Project: Buildr
Issue Type: Bug
Components: Core features
Affects Versions: 1.3.5
Reporter: Alex Boisvert
Assignee: Alex Boisvert
Priority: Minor
Fix For: 1.4
The current spec,
describe Buildr::TestTask do
...
it 'should not use the test compile dependencies' do
define('foo') { test.compile.using(:javac).with 'group:id:jar:1.0' }
project('foo').test.dependencies.should_not include(artifact('group:id:jar:1.0'))
end
...
end
is invalid. I raised this on the mailing list some time ago http://markmail.org/message/h5i672ko2nup27bw but haven't gotten material responses so I'm fixing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-365) test task should use the test
compile dependencies
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804126#action_12804126 ]
Alex Boisvert commented on BUILDR-365:
--------------------------------------
According to Assaf (in separate conversation), the point of the was to compile tests with one library, but test with a different one. I believe this is a rare need which can be accommodated differently and that using the test compile dependencies is a better default.
> test task should use the test compile dependencies
> --------------------------------------------------
>
> Key: BUILDR-365
> URL: https://issues.apache.org/jira/browse/BUILDR-365
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.5
> Reporter: Alex Boisvert
> Assignee: Alex Boisvert
> Priority: Minor
> Fix For: 1.4
>
>
> The current spec,
> describe Buildr::TestTask do
> ...
> it 'should not use the test compile dependencies' do
> define('foo') { test.compile.using(:javac).with 'group:id:jar:1.0' }
> project('foo').test.dependencies.should_not include(artifact('group:id:jar:1.0'))
> end
> ...
> end
> is invalid. I raised this on the mailing list some time ago http://markmail.org/message/h5i672ko2nup27bw but haven't gotten material responses so I'm fixing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-365) test task should use the test compile
dependencies
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved BUILDR-365.
----------------------------------
Resolution: Fixed
Sending CHANGELOG
Sending spec/core/test_spec.rb
Transmitting file data ..
Committed revision 902464.
> test task should use the test compile dependencies
> --------------------------------------------------
>
> Key: BUILDR-365
> URL: https://issues.apache.org/jira/browse/BUILDR-365
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.5
> Reporter: Alex Boisvert
> Assignee: Alex Boisvert
> Priority: Minor
> Fix For: 1.4
>
>
> The current spec,
> describe Buildr::TestTask do
> ...
> it 'should not use the test compile dependencies' do
> define('foo') { test.compile.using(:javac).with 'group:id:jar:1.0' }
> project('foo').test.dependencies.should_not include(artifact('group:id:jar:1.0'))
> end
> ...
> end
> is invalid. I raised this on the mailing list some time ago http://markmail.org/message/h5i672ko2nup27bw but haven't gotten material responses so I'm fixing it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.