You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2012/09/09 05:43:21 UTC
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Jason van Zyl created MNG-5343:
----------------------------------
Summary: Allow the use of JSR330 annotation in Maven extensions and plugins
Key: MNG-5343
URL: https://jira.codehaus.org/browse/MNG-5343
Project: Maven 2 & 3
Issue Type: New Feature
Environment:
Reporter: Jason van Zyl
The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
[1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314361#comment-314361 ]
Herve Boutemy edited comment on MNG-5343 at 11/25/12 3:28 PM:
--------------------------------------------------------------
done in [r1380105|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java?r1=1059233&r2=1380105&pathrev=1380105&diff_format=h]
JSR-330 is available in core since 3.0-beta-3 (see MNG-4749), but since it wasn't exported to plugins or extensions, it couldn't be used outside core.
Notice that Guice API isn't exposed, even in Maven 3.1, so it's still available only inside Maven core, but not in plugins or extensions
was (Author: hboutemy):
done in [r1380105|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java?r1=1059233&r2=1380105&pathrev=1380105&diff_format=h]
JSR-330 is available in core since 3.0-beta-3, but since it wasn't exported to plugins or extensions, it couldn't be used outside core.
Notice that Guice API isn't exposed, even in Maven 3.1, so it's still available only inside Maven core, but not in plugins or extensions
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 3.1.0
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314361#comment-314361 ]
Herve Boutemy edited comment on MNG-5343 at 11/25/12 3:08 PM:
--------------------------------------------------------------
done in [r1380105|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java?r1=1059233&r2=1380105&pathrev=1380105&diff_format=h]
JSR-330 is available in core since 3.0-beta-3, but since it wasn't exported to plugins or extensions, it couldn't be used outside core.
Notice that Guice API isn't exposed, even in Maven 3.1, so it's still available only inside Maven core, but not in plugins or extensions
was (Author: hboutemy):
done in [r1380105|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java?r1=1059233&r2=1380105&pathrev=1380105&diff_format=h]
JSR-330 is available in core since 3.0-beta-3, but since it wasn't exported to plugins or extensions, it couldn't be used outside core
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 3.1.0
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-5343.
------------------------------
Resolution: Fixed
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 3.1.0
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-5343:
-------------------------------
Fix Version/s: 3.0.5
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Fix For: 3.0.5
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-5343:
-------------------------------
Assignee: Jason van Zyl
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 3.1.0
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5343) Allow the use of JSR330 annotation in Maven
extensions and plugins
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314361#comment-314361 ]
Herve Boutemy commented on MNG-5343:
------------------------------------
done in [r1380105|http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java?r1=1059233&r2=1380105&pathrev=1380105&diff_format=h]
JSR-330 is available in core since 3.0-beta-3, but since it wasn't exported to plugins or extensions, it couldn't be used outside core
> Allow the use of JSR330 annotation in Maven extensions and plugins
> ------------------------------------------------------------------
>
> Key: MNG-5343
> URL: https://jira.codehaus.org/browse/MNG-5343
> Project: Maven 2 & 3
> Issue Type: New Feature
> Environment:
> Reporter: Jason van Zyl
> Assignee: Jason van Zyl
> Fix For: 3.1.0
>
>
> The implementation should not require classpath scanning, but work in a similar way to Plexus where the metadata about the components is generated at build time.
> This is realized using features in Sisu/Guice and the sisu-maven-plugin[1] which generates a META-INF/sisu/javax.inject.Named file which Sisu/Guice can pick up without scanning.
> [1]: http://sonatype.github.com/sisu-maven-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira