You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/06/03 03:25:21 UTC
[jira] Created: (MNG-442) devide way to pass artifacts to tests
devide way to pass artifacts to tests
-------------------------------------
Key: MNG-442
URL: http://jira.codehaus.org/browse/MNG-442
Project: Maven 2
Type: Improvement
Components: maven-plugins
Reporter: Brett Porter
Fix For: 2.0-beta-1
currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
It would be good to hand the test dependencies to the surefire tests directly.
--
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-442) devise way to pass artifacts to tests
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-442?page=all ]
Jason van Zyl updated MNG-442:
------------------------------
Description:
currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
It would be good to hand the test dependencies to the surefire tests directly.
was:
currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
It would be good to hand the test dependencies to the surefire tests directly.
Environment:
Summary: devise way to pass artifacts to tests (was: devide way to pass artifacts to tests)
> devise way to pass artifacts to tests
> -------------------------------------
>
> Key: MNG-442
> URL: http://jira.codehaus.org/browse/MNG-442
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Reporter: Brett Porter
> Fix For: 2.0-beta-1
>
>
> currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
> It would be good to hand the test dependencies to the surefire tests directly.
--
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-442) devise way to pass artifacts to tests
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-442?page=all ]
Brett Porter updated MNG-442:
-----------------------------
Priority: Critical (was: Major)
Description:
currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
It would be good to hand the test dependencies to the surefire tests directly.
was:
currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
It would be good to hand the test dependencies to the surefire tests directly.
Environment:
> devise way to pass artifacts to tests
> -------------------------------------
>
> Key: MNG-442
> URL: http://jira.codehaus.org/browse/MNG-442
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Reporter: Brett Porter
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
> It would be good to hand the test dependencies to the surefire tests directly.
--
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-442) devise way to pass artifacts to tests
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-442?page=all ]
Brett Porter updated MNG-442:
-----------------------------
Fix Version: (was: 2.0-beta-1)
its the first one, but your suggestion isn't workable if it makes a dep on m2, or even requires not forking.
I see your point - I think we will just put this one off for now. This isn't really necessary - you could just parse the pom in the first place :)
> devise way to pass artifacts to tests
> -------------------------------------
>
> Key: MNG-442
> URL: http://jira.codehaus.org/browse/MNG-442
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Reporter: Brett Porter
> Assignee: John Casey
> Priority: Critical
>
>
> currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
> It would be good to hand the test dependencies to the surefire tests directly.
--
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-442) devise way to pass artifacts to tests
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-442?page=all ]
Brett Porter closed MNG-442:
----------------------------
Assign To: Brett Porter (was: John Casey)
Resolution: Duplicate
> devise way to pass artifacts to tests
> -------------------------------------
>
> Key: MNG-442
> URL: http://jira.codehaus.org/browse/MNG-442
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
>
>
> currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
> It would be good to hand the test dependencies to the surefire tests directly.
--
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] Commented: (MNG-442) devise way to pass artifacts to tests
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-442?page=comments#action_44327 ]
John Casey commented on MNG-442:
--------------------------------
Are we talking about allowing the unit test methods, etc. actually get access to the testClasspathElements file list? If so, can we could create a utility class to register this file list in either a static variable or a ThreadLocal, but this will require the tests to depend on m2 to register these elements in the first place.
One alternative might be to supply a utility to parse a POM and retrieve the testClasspathElements from that...which is a little heavy to say the least. This would also require that the utility somehow knows where to get hold of the required artifacts to parse the POM and resolve it's dependencies.
> devise way to pass artifacts to tests
> -------------------------------------
>
> Key: MNG-442
> URL: http://jira.codehaus.org/browse/MNG-442
> Project: Maven 2
> Type: Improvement
> Components: maven-plugins
> Reporter: Brett Porter
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> currently, tests look for the maven.repo.local system property and guess at the path layout to be able to create a classpath with some jars that were test dependencies.
> It would be good to hand the test dependencies to the surefire tests directly.
--
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