[jira] Updated: (MNG-634) Scope needs to be taken into account when providing dependencies by ant tasks
[ http://jira.codehaus.org/browse/MNG-634?page=all ] Brett Porter updated MNG-634: - Priority: Critical (was: Major) Scope needs to be taken into account when providing dependencies by ant tasks - Key: MNG-634 URL: http://jira.codehaus.org/browse/MNG-634 Project: Maven 2 Type: Improvement Components: maven-artifact-ant Versions: 2.0-alpha-3 Environment: any Reporter: Matthias Unverzagt Assignee: Brett Porter Priority: Critical Fix For: 2.0-beta-1 Best practise would be to have all depency info inside pom.xml files, none within build.xml files. One of this info is the 'scope' information. Suppose you declare a dependency that is needed for compiling but not in your runtime environment because it is provided by e.g. the container then you - would like to have the dependency on your compile classpath (e.g. to be independend of the container) - would like to have a fileset representing the runtime requirement - omitting the provided dependency Therefore there needs to be some kind of scope filter insided the dependencies task. Example: artifact:dependencies pathId=dependency.compile.classpath scope=compile pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies artifact:dependencies filesetId=dependency.runtime.fileset scope=runtime pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies CONCERNING PRIORITY: Without such a scope attribute you need to duplicate the scope information that is in the pom.xml in some sense inside the build.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-634) Scope needs to be taken into account when providing dependencies by ant tasks
[ http://jira.codehaus.org/browse/MNG-634?page=all ] Brett Porter updated MNG-634: - Remaining Estimate: 2 hours Original Estimate: 7200 Scope needs to be taken into account when providing dependencies by ant tasks - Key: MNG-634 URL: http://jira.codehaus.org/browse/MNG-634 Project: Maven 2 Type: Improvement Components: maven-artifact-ant Versions: 2.0-alpha-3 Environment: any Reporter: Matthias Unverzagt Assignee: Brett Porter Priority: Critical Fix For: 2.0-beta-1 Original Estimate: 2 hours Remaining: 2 hours Best practise would be to have all depency info inside pom.xml files, none within build.xml files. One of this info is the 'scope' information. Suppose you declare a dependency that is needed for compiling but not in your runtime environment because it is provided by e.g. the container then you - would like to have the dependency on your compile classpath (e.g. to be independend of the container) - would like to have a fileset representing the runtime requirement - omitting the provided dependency Therefore there needs to be some kind of scope filter insided the dependencies task. Example: artifact:dependencies pathId=dependency.compile.classpath scope=compile pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies artifact:dependencies filesetId=dependency.runtime.fileset scope=runtime pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies CONCERNING PRIORITY: Without such a scope attribute you need to duplicate the scope information that is in the pom.xml in some sense inside the build.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-634) Scope needs to be taken into account when providing dependencies by ant tasks
[ http://jira.codehaus.org/browse/MNG-634?page=all ] Brett Porter updated MNG-634: - Fix Version: 2.0-beta-1 Scope needs to be taken into account when providing dependencies by ant tasks - Key: MNG-634 URL: http://jira.codehaus.org/browse/MNG-634 Project: Maven 2 Type: Improvement Components: maven-artifact-ant Versions: 2.0-alpha-3 Environment: any Reporter: Matthias Unverzagt Fix For: 2.0-beta-1 Best practise would be to have all depency info inside pom.xml files, none within build.xml files. One of this info is the 'scope' information. Suppose you declare a dependency that is needed for compiling but not in your runtime environment because it is provided by e.g. the container then you - would like to have the dependency on your compile classpath (e.g. to be independend of the container) - would like to have a fileset representing the runtime requirement - omitting the provided dependency Therefore there needs to be some kind of scope filter insided the dependencies task. Example: artifact:dependencies pathId=dependency.compile.classpath scope=compile pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies artifact:dependencies filesetId=dependency.runtime.fileset scope=runtime pom refid=maven.project/ localRepository refid=repo.localrepo/ /artifact:dependencies CONCERNING PRIORITY: Without such a scope attribute you need to duplicate the scope information that is in the pom.xml in some sense inside the build.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
