You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2005/09/13 17:02:02 UTC
[jira] Created: (MNG-872) Allow defined dependencies to be related to certain types (attachments)
Allow defined dependencies to be related to certain types (attachments)
-----------------------------------------------------------------------
Key: MNG-872
URL: http://jira.codehaus.org/browse/MNG-872
Project: Maven 2
Type: Bug
Reporter: Kenney Westerhof
Currently, if you have attachments on a pom, both the main artifact and the attachments have the
same dependencies.
Use case 1:
packaging ejb: there's an ejb jar and an ejb-client jar. The ejb-client jar only
contains interfaces (actually, everything except the beans themselves), but no
business logic. The business logic in the ejb beans themselves however can have
a dependency that is not required for the ejb-client.
Use case 2:
POMS producing .jar, .dll and .so suffer from the same problem. If there are dependencies
needed for just one or two types (either the jar or both .dll and .so), depending on
the other type also includes those dependencies.
Proposal: add a tag <forTypes> (better name!) to <dependency>; when absent, all types
will have this dependency; when present, only the specified types will have these dependencies.
Implications:
- add 'getXXClasspath( type ); methods to MavenProject and let the plugins use those.
- dependency resolution should pick foreign dependencies parameterized by the <type>
or get them all and just group them by type (the first is preferred since the latter will cause
unused dependencies to be resolved).
--
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-872) Allow defined dependencies to be related to certain types (attachments)
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-872?page=all ]
Brett Porter updated MNG-872:
-----------------------------
Component: maven-artifact
> Allow defined dependencies to be related to certain types (attachments)
> -----------------------------------------------------------------------
>
> Key: MNG-872
> URL: http://jira.codehaus.org/browse/MNG-872
> Project: Maven 2
> Type: Bug
> Components: maven-artifact
> Reporter: Kenney Westerhof
> Fix For: 2.1
>
>
> Currently, if you have attachments on a pom, both the main artifact and the attachments have the
> same dependencies.
> Use case 1:
> packaging ejb: there's an ejb jar and an ejb-client jar. The ejb-client jar only
> contains interfaces (actually, everything except the beans themselves), but no
> business logic. The business logic in the ejb beans themselves however can have
> a dependency that is not required for the ejb-client.
> Use case 2:
> POMS producing .jar, .dll and .so suffer from the same problem. If there are dependencies
> needed for just one or two types (either the jar or both .dll and .so), depending on
> the other type also includes those dependencies.
> Proposal: add a tag <forTypes> (better name!) to <dependency>; when absent, all types
> will have this dependency; when present, only the specified types will have these dependencies.
> Implications:
> - add 'getXXClasspath( type ); methods to MavenProject and let the plugins use those.
> - dependency resolution should pick foreign dependencies parameterized by the <type>
> or get them all and just group them by type (the first is preferred since the latter will cause
> unused dependencies to be resolved).
--
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-872) Allow defined dependencies to be related to certain types (attachments)
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-872?page=all ]
Brett Porter updated MNG-872:
-----------------------------
Fix Version: 2.1
> Allow defined dependencies to be related to certain types (attachments)
> -----------------------------------------------------------------------
>
> Key: MNG-872
> URL: http://jira.codehaus.org/browse/MNG-872
> Project: Maven 2
> Type: Bug
> Reporter: Kenney Westerhof
> Fix For: 2.1
>
>
> Currently, if you have attachments on a pom, both the main artifact and the attachments have the
> same dependencies.
> Use case 1:
> packaging ejb: there's an ejb jar and an ejb-client jar. The ejb-client jar only
> contains interfaces (actually, everything except the beans themselves), but no
> business logic. The business logic in the ejb beans themselves however can have
> a dependency that is not required for the ejb-client.
> Use case 2:
> POMS producing .jar, .dll and .so suffer from the same problem. If there are dependencies
> needed for just one or two types (either the jar or both .dll and .so), depending on
> the other type also includes those dependencies.
> Proposal: add a tag <forTypes> (better name!) to <dependency>; when absent, all types
> will have this dependency; when present, only the specified types will have these dependencies.
> Implications:
> - add 'getXXClasspath( type ); methods to MavenProject and let the plugins use those.
> - dependency resolution should pick foreign dependencies parameterized by the <type>
> or get them all and just group them by type (the first is preferred since the latter will cause
> unused dependencies to be resolved).
--
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