You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Steve Loughran (JIRA)" <ji...@codehaus.org> on 2005/05/16 16:46:34 UTC
[jira] Created: (MNG-407) Need a way to turn off transient fetching of libraries
Need a way to turn off transient fetching of libraries
------------------------------------------------------
Key: MNG-407
URL: http://jira.codehaus.org/browse/MNG-407
Project: m2
Type: New Feature
Versions: 2.0-alpha-2
Environment: ant1.7alpha on linux, behind a proxied firewall
Reporter: Steve Loughran
We need a way to turn off transient retrieval of stuff in the ant tasks. If, for example, I ask for commons-logging-1.04, the runtime pulls down everything ever used in it
[artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom
[artifact:dependencies] Transferring 7K
[artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar
[artifact:dependencies] Transferring 70K
[artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar
[artifact:dependencies] Transferring 342K
[artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar
[artifact:dependencies] Transferring 114K
[artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar.md5
[artifact:dependencies] Transferring 0K
[artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
[artifact:dependencies] Transferring 62K
[artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar.md5
[artifact:dependencies] Transferring 0K
As a consequence, the classpath is then set up wrong. And if we copy the contents of that path (e.g. into the lib dir of a WAR, we end up with conflicting JAR files).
Another example, if if declare a dependency on jaxen-1.1beta6. That was built against dom4j-1-5.2. That doesnt have an entry in the maven2 repository, so the build fails. Yet all jaxen needs is a JAXP parser, for which xerces works perfectly well.
I've looked at the scope attribute, and it seems that transience is certainly noted as a problem, but I'm not sure that works. What I really need is a transient=on/off attribute, so I can run with transience off when I am being 100% explicit about all my dependencies.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-407) Need a way to turn off transient fetching of libraries
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-407?page=all ]
Brett Porter updated MNG-407:
-----------------------------
Fix Version: 2.0-alpha-3
should be using commons-logging-api in this case, but we will be looking at filtering transitive deps in alpha-3
> Need a way to turn off transient fetching of libraries
> ------------------------------------------------------
>
> Key: MNG-407
> URL: http://jira.codehaus.org/browse/MNG-407
> Project: m2
> Type: New Feature
> Versions: 2.0-alpha-2
> Environment: ant1.7alpha on linux, behind a proxied firewall
> Reporter: Steve Loughran
> Fix For: 2.0-alpha-3
>
>
> We need a way to turn off transient retrieval of stuff in the ant tasks. If, for example, I ask for commons-logging-1.04, the runtime pulls down everything ever used in it
> [artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom
> [artifact:dependencies] Transferring 7K
> [artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar
> [artifact:dependencies] Transferring 70K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar
> [artifact:dependencies] Transferring 342K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar
> [artifact:dependencies] Transferring 114K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
> [artifact:dependencies] Transferring 62K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar.md5
> [artifact:dependencies] Transferring 0K
> As a consequence, the classpath is then set up wrong. And if we copy the contents of that path (e.g. into the lib dir of a WAR, we end up with conflicting JAR files).
> Another example, if if declare a dependency on jaxen-1.1beta6. That was built against dom4j-1-5.2. That doesnt have an entry in the maven2 repository, so the build fails. Yet all jaxen needs is a JAXP parser, for which xerces works perfectly well.
> I've looked at the scope attribute, and it seems that transience is certainly noted as a problem, but I'm not sure that works. What I really need is a transient=on/off attribute, so I can run with transience off when I am being 100% explicit about all my dependencies.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-407) Need a way to turn off transient fetching of libraries
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-407?page=all ]
Brett Porter closed MNG-407:
----------------------------
Resolution: Fixed
implemented as <exclusion groupId=".." artifactId=".." /> within a dependency to selectively filter out unwanted dependendencies.
Please reopen if you believe you need transitive dependencies to be completely turned off - that would be inconsistent with m2's abilities so would require more consideration.
> Need a way to turn off transient fetching of libraries
> ------------------------------------------------------
>
> Key: MNG-407
> URL: http://jira.codehaus.org/browse/MNG-407
> Project: Maven 2
> Type: New Feature
> Versions: 2.0-alpha-2
> Environment: ant1.7alpha on linux, behind a proxied firewall
> Reporter: Steve Loughran
> Assignee: Brett Porter
> Fix For: 2.0-alpha-3
>
>
> We need a way to turn off transient retrieval of stuff in the ant tasks. If, for example, I ask for commons-logging-1.04, the runtime pulls down everything ever used in it
> [artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom
> [artifact:dependencies] Transferring 7K
> [artifact:dependencies] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.pom.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar
> [artifact:dependencies] Transferring 70K
> [artifact:dependencies] Downloading: logkit/logkit/1.0.1/logkit-1.0.1.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar
> [artifact:dependencies] Transferring 342K
> [artifact:dependencies] Downloading: log4j/log4j/1.2.6/log4j-1.2.6.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar
> [artifact:dependencies] Transferring 114K
> [artifact:dependencies] Downloading: junit/junit/3.7/junit-3.7.jar.md5
> [artifact:dependencies] Transferring 0K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar
> [artifact:dependencies] Transferring 62K
> [artifact:dependencies] Downloading: avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar.md5
> [artifact:dependencies] Transferring 0K
> As a consequence, the classpath is then set up wrong. And if we copy the contents of that path (e.g. into the lib dir of a WAR, we end up with conflicting JAR files).
> Another example, if if declare a dependency on jaxen-1.1beta6. That was built against dom4j-1-5.2. That doesnt have an entry in the maven2 repository, so the build fails. Yet all jaxen needs is a JAXP parser, for which xerces works perfectly well.
> I've looked at the scope attribute, and it seems that transience is certainly noted as a problem, but I'm not sure that works. What I really need is a transient=on/off attribute, so I can run with transience off when I am being 100% explicit about all my dependencies.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org