[jira] (MNG-5387) Add ability to replace an artifact in mid-build
[ https://jira.codehaus.org/browse/MNG-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314338#comment-314338 ] Stephen Connolly commented on MNG-5387: --- I agree with last wins. The only gotcha-cconcern I have is the forked life cycles. Specifically a cobertura or clover forked life cycle. If the forked life cycle doesn't splat over then it's fine Add ability to replace an artifact in mid-build --- Key: MNG-5387 URL: https://jira.codehaus.org/browse/MNG-5387 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.1.0 Reporter: Benson Margulies Assignee: Benson Margulies To clean up how the shade plugin works, we need an API to allow it to say, 'please replace the jar file that the jar plugin has given you with this other one here.' It turns out we already more or less have this method, due to a collection of historical conflict. At some point in time, http://jira.codehaus.org/browse/MNG-3119 called for Maven to reject more than one call to attach the same artifact to the build. However, this proved an unacceptable incompatibility at the time. Instead, under http://jira.codehaus.org/browse/MNG-4013, Maven was changed to log but otherwise ignore all calls to 'addArtifact' on MavenProject after the first for a G/A/V/C/T coordinate. This decision to take 'first wins' instead of 'last wins' doesn't help much of anyone. It prevents something like shade from intentionally displacing an earlier execution's results, and while it doesn't produce backtraces, ever, it can still be entirely confusing. Under this JIRA, I'm switching to 'last one wins'. This could still be confusing, and someone might argue that there should be some way to distinguish casual and incorrect user config that results in two plugins trying to deliver the same thing from something intentional. On the other hand, if two plugins are configured to attach the same G/A/V/C, having the last one win makes more sense, and has the effect of enabling the desired behavior in shade. -- 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] (MPDF-10) Support menu sub-items in table of contents
[ https://jira.codehaus.org/browse/MPDF-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314346#comment-314346 ] Data Nucleus commented on MPDF-10: -- I've updated the way of reproducing this flaw :- svn co https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform-maven-skin/trunk dn-maven-skin cd dn-maven-skin mvn clean install cd .. svn co https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform/trunk dn-project cd dn-project mvn clean pdf:pdf This creates a PDF like http://www.datanucleus.org/products/accessplatform_3_2/datanucleus-accessplatform-docs.pdf which has section numbers correct in TOC, but not in the doc. Alternatively if anyone can provide tips on where the problem lies in Doxia/PDF code then please add them here so someone could look at it if time. Support menu sub-items in table of contents --- Key: MPDF-10 URL: https://jira.codehaus.org/browse/MPDF-10 Project: Maven 2.x PDF Plugin Issue Type: New Feature Reporter: Lukas Theussl Currently, every source document starts a new chapter. -- 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-5387) Add ability to replace an artifact in mid-build
[ https://jira.codehaus.org/browse/MNG-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MNG-5387. - Resolution: Fixed Fix Version/s: 3.1.0 Integration test in 1413359. Add ability to replace an artifact in mid-build --- Key: MNG-5387 URL: https://jira.codehaus.org/browse/MNG-5387 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 3.1.0 Reporter: Benson Margulies Assignee: Benson Margulies Fix For: 3.1.0 To clean up how the shade plugin works, we need an API to allow it to say, 'please replace the jar file that the jar plugin has given you with this other one here.' It turns out we already more or less have this method, due to a collection of historical conflict. At some point in time, http://jira.codehaus.org/browse/MNG-3119 called for Maven to reject more than one call to attach the same artifact to the build. However, this proved an unacceptable incompatibility at the time. Instead, under http://jira.codehaus.org/browse/MNG-4013, Maven was changed to log but otherwise ignore all calls to 'addArtifact' on MavenProject after the first for a G/A/V/C/T coordinate. This decision to take 'first wins' instead of 'last wins' doesn't help much of anyone. It prevents something like shade from intentionally displacing an earlier execution's results, and while it doesn't produce backtraces, ever, it can still be entirely confusing. Under this JIRA, I'm switching to 'last one wins'. This could still be confusing, and someone might argue that there should be some way to distinguish casual and incorrect user config that results in two plugins trying to deliver the same thing from something intentional. On the other hand, if two plugins are configured to attach the same G/A/V/C, having the last one win makes more sense, and has the effect of enabling the desired behavior in shade. -- 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] (MSHADE-135) Add PluginTransformer
[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MSHADE-135: - Assignee: Robert Scholte Add PluginTransformer - Key: MSHADE-135 URL: https://jira.codehaus.org/browse/MSHADE-135 Project: Maven 2.x Shade Plugin Issue Type: New Feature Affects Versions: 2.0 Reporter: Robert Scholte Assignee: Robert Scholte Priority: Critical When using doclet-tags for the Maven plugin we had to specify the shaded class as the role, since this String couldn't be recognized as a class. But now we have annotations as well, and here the role is a real class, so the trick above doesn't work anymore. Hence, we need a transformer for it. -- 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-5388) Restore embedded integration tests
[ https://jira.codehaus.org/browse/MNG-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5388: --- Fix Version/s: 3.1.1 Restore embedded integration tests -- Key: MNG-5388 URL: https://jira.codehaus.org/browse/MNG-5388 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Fix For: 3.1.1 The embedded integration tests through not being run for a long time, and changes made in the verifier make it impossible for them to pass currently. They test long-lived processes using Maven and makes sure things are cleaned up correctly and they run an order of magnitude faster than the forked tests. -- 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-5388) Restore embedded integration tests
Jason van Zyl created MNG-5388: -- Summary: Restore embedded integration tests Key: MNG-5388 URL: https://jira.codehaus.org/browse/MNG-5388 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl The embedded integration tests through not being run for a long time, and changes made in the verifier make it impossible for them to pass currently. They test long-lived processes using Maven and makes sure things are cleaned up correctly and they run an order of magnitude faster than the forked tests. -- 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-5381) Restore MavenSession.getRepositoryCache()
[ https://jira.codehaus.org/browse/MNG-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anders Hammar reopened MNG-5381: Re-opening as this is not fixed. I get this error trying the staged Maven v3.1.0 with Tycho 0.15.0. Restore MavenSession.getRepositoryCache() - Key: MNG-5381 URL: https://jira.codehaus.org/browse/MNG-5381 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 Error when running stock Tycho 0.16.0 Exception in thread main java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositoryCache()Lorg/apache/maven/artifact/repository/RepositoryCache; This method was deprecated but it can be bridged to Aether code as this screws up Tycho users unecessarily. Tycho can migrate off this method but currently this breaks all Tycho users which is an unacceptable break. -- 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] (MSHADE-135) Add PluginXmlTransformer
[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHADE-135: -- Summary: Add PluginXmlTransformer (was: Add PluginTransformer) Add PluginXmlTransformer Key: MSHADE-135 URL: https://jira.codehaus.org/browse/MSHADE-135 Project: Maven 2.x Shade Plugin Issue Type: New Feature Affects Versions: 2.0 Reporter: Robert Scholte Assignee: Robert Scholte Priority: Critical When using doclet-tags for the Maven plugin we had to specify the shaded class as the role, since this String couldn't be recognized as a class. But now we have annotations as well, and here the role is a real class, so the trick above doesn't work anymore. Hence, we need a transformer for it. -- 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] (MSHADE-135) Add PluginXmlTransformer
[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSHADE-135. - Resolution: Fixed Fix Version/s: 3.0 Fixed in [r1413392|https://svn.apache.org/r1413392] Add PluginXmlTransformer Key: MSHADE-135 URL: https://jira.codehaus.org/browse/MSHADE-135 Project: Maven 2.x Shade Plugin Issue Type: New Feature Affects Versions: 2.0 Reporter: Robert Scholte Assignee: Robert Scholte Priority: Critical Fix For: 3.0 When using doclet-tags for the Maven plugin we had to specify the shaded class as the role, since this String couldn't be recognized as a class. But now we have annotations as well, and here the role is a real class, so the trick above doesn't work anymore. Hence, we need a transformer for it. -- 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-5381) Restore MavenSession.getRepositoryCache()
[ https://jira.codehaus.org/browse/MNG-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314354#comment-314354 ] Jason van Zyl commented on MNG-5381: Code now on trunk Restore MavenSession.getRepositoryCache() - Key: MNG-5381 URL: https://jira.codehaus.org/browse/MNG-5381 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 Error when running stock Tycho 0.16.0 Exception in thread main java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositoryCache()Lorg/apache/maven/artifact/repository/RepositoryCache; This method was deprecated but it can be bridged to Aether code as this screws up Tycho users unecessarily. Tycho can migrate off this method but currently this breaks all Tycho users which is an unacceptable break. -- 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-5381) Restore MavenSession.getRepositoryCache()
[ https://jira.codehaus.org/browse/MNG-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-5381. -- Resolution: Fixed Restore MavenSession.getRepositoryCache() - Key: MNG-5381 URL: https://jira.codehaus.org/browse/MNG-5381 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 Error when running stock Tycho 0.16.0 Exception in thread main java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositoryCache()Lorg/apache/maven/artifact/repository/RepositoryCache; This method was deprecated but it can be bridged to Aether code as this screws up Tycho users unecessarily. Tycho can migrate off this method but currently this breaks all Tycho users which is an unacceptable break. -- 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-5356) Make encrypt/decrypt logic pluggable
[ https://jira.codehaus.org/browse/MNG-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314355#comment-314355 ] Jason van Zyl commented on MNG-5356: Have you taken a look at the SettingsDecrypter in maven-settings-builder? I'll pull your branch in and take a closer look now that 3.1.0 is almost wrapped up. Make encrypt/decrypt logic pluggable Key: MNG-5356 URL: https://jira.codehaus.org/browse/MNG-5356 Project: Maven 2 3 Issue Type: Improvement Environment: n/a Reporter: Anders Hammar Assignee: Anders Hammar Fix For: 3.1.1 It would be good if Maven Core facilitated the encryption (and decryption) logic to be replaceable. Today's solution is very much hard-coded to the plexus logic. This would make it possible for enterprise environments to re-use existing solutions, like for eg smart cards, for this. The default should be the current implementation though. -- 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-5381) Restore MavenSession.getRepositoryCache()
[ https://jira.codehaus.org/browse/MNG-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314356#comment-314356 ] Robert Scholte commented on MNG-5381: - Fixed in [r1413391|http://svn.apache.org/viewvc?rev=1413391view=rev] Restore MavenSession.getRepositoryCache() - Key: MNG-5381 URL: https://jira.codehaus.org/browse/MNG-5381 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 Error when running stock Tycho 0.16.0 Exception in thread main java.lang.NoSuchMethodError: org.apache.maven.execution.MavenSession.getRepositoryCache()Lorg/apache/maven/artifact/repository/RepositoryCache; This method was deprecated but it can be bridged to Aether code as this screws up Tycho users unecessarily. Tycho can migrate off this method but currently this breaks all Tycho users which is an unacceptable break. -- 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-5388) Restore embedded integration tests
[ https://jira.codehaus.org/browse/MNG-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5388: --- Assignee: Jason van Zyl Restore embedded integration tests -- Key: MNG-5388 URL: https://jira.codehaus.org/browse/MNG-5388 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.1 The embedded integration tests through not being run for a long time, and changes made in the verifier make it impossible for them to pass currently. They test long-lived processes using Maven and makes sure things are cleaned up correctly and they run an order of magnitude faster than the forked tests. -- 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-5382) Add an IT for @Inject used in plugins
[ https://jira.codehaus.org/browse/MNG-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314357#comment-314357 ] Herve Boutemy commented on MNG-5382: IT added in [r1413023|http://svn.apache.org/viewvc?rev=1413023view=rev] Add an IT for @Inject used in plugins - Key: MNG-5382 URL: https://jira.codehaus.org/browse/MNG-5382 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 -- 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-5356) Make encrypt/decrypt logic pluggable
[ https://jira.codehaus.org/browse/MNG-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314358#comment-314358 ] Anders Hammar commented on MNG-5356: Yes, DefaultSettingsDecrypter uses the new Crypto component. Make encrypt/decrypt logic pluggable Key: MNG-5356 URL: https://jira.codehaus.org/browse/MNG-5356 Project: Maven 2 3 Issue Type: Improvement Environment: n/a Reporter: Anders Hammar Assignee: Anders Hammar Fix For: 3.1.1 It would be good if Maven Core facilitated the encryption (and decryption) logic to be replaceable. Today's solution is very much hard-coded to the plexus logic. This would make it possible for enterprise environments to re-use existing solutions, like for eg smart cards, for this. The default should be the current implementation though. -- 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-5375) Document use of SLF4J
[ https://jira.codehaus.org/browse/MNG-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314360#comment-314360 ] Herve Boutemy commented on MNG-5375: http://maven.apache.org/maven-logging.html Document use of SLF4J -- Key: MNG-5375 URL: https://jira.codehaus.org/browse/MNG-5375 Project: Maven 2 3 Issue Type: Task Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 -- 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-5373) Document the usage and benefits of JSR330
[ https://jira.codehaus.org/browse/MNG-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314359#comment-314359 ] Herve Boutemy commented on MNG-5373: http://maven.apache.org/maven-jsr330.html Document the usage and benefits of JSR330 - Key: MNG-5373 URL: https://jira.codehaus.org/browse/MNG-5373 Project: Maven 2 3 Issue Type: Task Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 -- 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
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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=1059233r2=1380105pathrev=1380105diff_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-5376) Account for changes between the Apple and Oracle JDKs on OSX
[
https://jira.codehaus.org/browse/MNG-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314362#comment-314362
]
Stuart McCulloch commented on MNG-5376:
---
FYI, this change results in some oddities on OSX 10.6.8 because
/System/Library/Java/JavaVirtualMachines/CurrentJDK (used in the new script)
does not exist whereas
/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK (used in the
old script) does:
{code}
readlink: illegal option -- f
usage: readlink [-n] [file ...]
Warning: JAVA_HOME environment variable is not set.
[INFO] Scanning for projects...
...etc...
{code}
Suggest both locations should be checked for the sake of backwards
compatibility.
Account for changes between the Apple and Oracle JDKs on OSX
Key: MNG-5376
URL: https://jira.codehaus.org/browse/MNG-5376
Project: Maven 2 3
Issue Type: Task
Reporter: Jason van Zyl
Assignee: Jason van Zyl
Fix For: 3.1.0
With the arrival of Java 7 on OSX the directory locations and naming has
changed. Some changes need to be made in the launch scripts to account for
the changes.
--
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
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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=1059233r2=1380105pathrev=1380105diff_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=1059233r2=1380105pathrev=1380105diff_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-5344) Allow the SLF4J loggers to be @Injected
[ https://jira.codehaus.org/browse/MNG-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314363#comment-314363 ] Herve Boutemy commented on MNG-5344: done in [r1380105|http://svn.apache.org/viewvc?view=revisionrevision=1380105] Allow the SLF4J loggers to be @Injected --- Key: MNG-5344 URL: https://jira.codehaus.org/browse/MNG-5344 Project: Maven 2 3 Issue Type: New Feature Environment: Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 SLF4J is being used by 15 Apache projects and counting[1] is a good API for logging, has many implementations and Sisu/Guice has support for @Injecting them which makes it convenient in extensions and plugins. The MavenCLI needs to be cleaned up and when a default implementation is picked the logging mechanism can be simplified and all Plexus logger and SLF4J logger instsances can all be routed through the same mechanism. [1]: http://slf4j.org -- 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
[ https://jira.codehaus.org/browse/MNG-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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=1059233r2=1380105pathrev=1380105diff_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=1059233r2=1380105pathrev=1380105diff_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-5376) Account for changes between the Apple and Oracle JDKs on OSX
[ https://jira.codehaus.org/browse/MNG-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314366#comment-314366 ] Jason van Zyl commented on MNG-5376: Makes sense, I'll try to add that in. Account for changes between the Apple and Oracle JDKs on OSX Key: MNG-5376 URL: https://jira.codehaus.org/browse/MNG-5376 Project: Maven 2 3 Issue Type: Task Reporter: Jason van Zyl Assignee: Jason van Zyl Fix For: 3.1.0 With the arrival of Java 7 on OSX the directory locations and naming has changed. Some changes need to be made in the launch scripts to account for the changes. -- 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
