You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Henryk Konsek (JIRA)" <ji...@apache.org> on 2012/10/04 22:41:48 UTC
[jira] [Commented] (CAMEL-5578) Polish our pom's to be as DRY as
possible
[ https://issues.apache.org/jira/browse/CAMEL-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469666#comment-13469666 ]
Henryk Konsek commented on CAMEL-5578:
--------------------------------------
What about adding test scope to test dependencies in parent POM?
For example now we define JUnit in parent POM as:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit-version}</version>
</dependency>
And in particular modules we define this dependency as:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<scope>test</test>
</dependency>
Since we never use JUnit in other scope than "test", then unnecessarily repeat <scope>test</test> in each module. If we want to keep our POMs DRY we should define JUnit in parent POM as follows:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>${junit-version}</version>
<scope>test</scope>
</dependency>
And then in concrete modules:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
</dependency>
The case same is for mockito, easymock, camel-test and so forth.
> Polish our pom's to be as DRY as possible
> -----------------------------------------
>
> Key: CAMEL-5578
> URL: https://issues.apache.org/jira/browse/CAMEL-5578
> Project: Camel
> Issue Type: Improvement
> Components: build system
> Affects Versions: 2.10.1
> Reporter: Christian Müller
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.11.0
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira