Re: Resolving MDEP-98, 187, 194 and 354
Thanks Hervé! I'm on Pacific time, 9 hours behind you. I'll do my best to be available for e-mail from 6PM your time. I'll also be in the #maven IRC channel on irc.codehaus.org as ianbrandt if that's easier. Regards, Ian On Jul 31, 2012, at 10:30 PM, Hervé BOUTEMY wrote: I will take a look at it tonight, after work (Paris time :) ) I don't know if I will need more explanations or not, but if you can be online at this time to reply to mails, it can spped up our eventual discussions Regards, Hervé Le mardi 31 juillet 2012 19:28:25 Ian Brandt a écrit : Greetings, I'm working on an m2e connector for the Maven Dependency Plugin: https://github.com/ianbrandt/m2e-maven-dependency-plugin The very first bug report filed against it appears to actually just be a manifestation of the long outstanding MDEP-98/187/194/354: http://jira.codehaus.org/browse/MDEP-98 http://jira.codehaus.org/browse/MDEP-187 http://jira.codehaus.org/browse/MDEP-194 http://jira.codehaus.org/browse/MDEP-354 There have been patches attached to these JIRA's over the years, the latest of which I believe is on MDEP-194. Correct me if I'm wrong, but I notice no recent committer activity. Is there anything I could do to help expedite the resolution of this bug? Would it help if I wrangled the patches into a pull request on the GitHub mirror? Are more test cases needed? Thanks, Ian P.S. If anyone knows the answer to my last Maven Dependency Plugin related question that would be great too: http://mail-archives.apache.org/mod_mbox/maven-dev/201206.mbox/%3CD6E6D74A- 7454-4043-B2D2-E3232025CF47%40ianbrandt.com%3E - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Does maven have pluggable available build extensions?
Hi Tony, Tony Lâmpada wrote: We all know maven has a lot of available pluginshttp://maven.apache.org/plugins/index.htmlthat do a lot of useful stuff. I recently learned about a different kind of extension point for maven builds: build extensionshttp://maven.apache.org/examples/maven-3-lifecycle- extensions.html . Is there a similar list of useful build extensions that one can use? And more specifically, one that can maybe help with thishttp://stackoverflow.com/questions/11749375/import-maven-plugin- configuration-by-composition-rather-than-inheritance-can-it ? Well, with M3 you can use profiles ... hehehe Seriously, I'd not meddle with the execution order at runtime. You will not have much fun with a parallel build later. First you have to understand, why your profile example cannot work (and never will). Maven *has to* resolve the parent POM completely first (i.e. all profiles are evaluated and merged into the effective POM). Then the same happens for the current POM. Obviously no property will have now any effect on profile activation in the parent ... this is simply too late. You must also know, that the output of help:active-profiles is not complete. It does not show you the profiles that have been activated in a parent POM. The best you can do in your use case is to define a profile in the parent and activate it based on the existence on a file. We have a profile in our global POM that automatically activates the verifier plugin, if the project contains a verifications file: % profile idauto-verification/id activation file !-- cannot use variables here -- existssrc/test/verifier/verifications.xml/exists /file /activation build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-verifier-plugin/artifactId /plugin /plugins /build /profile % However, this will only work in a multi-project build with M3, but not with M2, because M3 uses the current POM root as reference for file resolution, while M2 uses the current working directory. For your problem you might simply create in your projects a profile folder that contains empty files with proper names % / + boy + profiles - kid - boy + girl + profiles - kid - girl + kid + profiles - kid % and the profile activation is based on existence of those files, e.g. existsprofile/kid/exists Hope this helps, Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: issues in maven
On Wed, Aug 1, 2012 at 4:38 PM, bshibin shibi...@nestgroup.net wrote: Hi, I am new to maven... I created java spring hibernate project.. and i kept all .java files in this path Myapplication\src\main\java\com\mycompany and create resources, webapp folders in Myapplication\src\main and inside resources i created 3 folders hibernate, properties and spring. in hibernate i kept all .hbm.xml files, in properties all properties files, and in spring again i created 3 folders beans, config and database. in beans i kept dispatch-servlet.xml and in database i kept hibernate.cfg.xml. in webapp i created WebINF\pages inside WebINF i kept web.xml and inside the pages folder i kept all jsp pages... After this using the command mvn clean install -U -U and it shows BUILD SUCCESS. then using this command mvn war : war. for creating the war. then i deployed the war file in localhost 8080. then I got the index page of my application.. then after clicking any link on the index page it shows 500 error.. Im attaching my pom.xml and the error log from the tomcat also :) Please post this to the Users list at us...@maven.apache.org This list is for developing Maven rather than using it. You might also benefit from reading the freely available books at http://maven.apache.org/articles.html Paying particular attention to the sections on Maven builds one artifact per project and how war projects can be setup - you shouldn't need to run mvn war:war. You should also try building your war by hand and make sure that works. Then you can compare what maven is building with what you know is working and determine how to fix that. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Release plan for maven-installer-plugin
Hi @all, I hope I'm in the correct list for this question. When is the release of the maven installer plugin version 2.4 planned? I would need at least the fix for MINSTALL-73. Kind regards, Felix - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.12.1
+1 binding. I don't see that issue as a blocker. On Wed, Aug 1, 2012 at 1:47 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: I have updated the doc pages in question; http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/featurematrix.html http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/examples/single-test.html I also created https://jira.codehaus.org/browse/SUREFIRE-893, which I'll try to get fiexd for the next release. The vote will complete in less than 24 hours. @Milos; you're still registered with a -1 (onlist-dialogue (+ some offlist) has this release proceeding anyway) Kristian 2012/7/31 Milos Kleint mkle...@gmail.com: then update this page as well: http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/examples/single-test.html On Mon, Jul 30, 2012 at 10:04 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: There is an integration test (TestMultipleMethodsIT) that runs the project located at SVN in https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/junit48-multiple-methods https://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-integration-tests/src/test/resources/junit44-multiple-methods This test passed using this command: mvn -Dtest=junit4.BasicTest#testSuccessOne+testFailOne,junit4.TestThree#testSuccessTwo -Dsurefire.version=2.12.1 test Is this a documentation problem or is there some other issue ? Please try to reproduce in terms of the existing IT projects if you can. As for TestNG, I do not believe this is supported (neither JUnit3). I will update the official feature matrix (http://maven.apache.org/plugins/maven-surefire-plugin-2.12.1/plugins/maven-surefire-plugin/featurematrix.html) and mark this as not supported for TestNG/JUnit3. I will redeploy the site sometime tomorrow. Since we traditionally do not cancel votes due to documentation changes, I'm not cancelling this vote until there's a clear proof of a bug. If necessary I'll extend the vote period so we're sure. Kristian mvn -Dsurefire.version=2.12.1 -Dtest=test.mavenproject2.AppNGTest#testMain,test.mavenproject2.AppNGTest#testMain2 test 2012/7/30 Milos Kleint mkle...@gmail.com: -1 surefire 1.12.1 + testng 6.5.2 or 6.7: mvn -Dtest=test.mavenproject2.AppNGTest#testMain,test.mavenproject2.AppNGTest#testMain2 test doesn't work (no tests run), even though running just 1 test method will succeed. surefire 1.12.1 + junit 4.10: mvn -Dtest=test.mavenproject1.AppTest#testMain2,test.mavenproject1.AppTest#testMain test doesn't work either, will run just one test, ignore the other. If I have 2 test classes each with 2 failing tests and attempt to execute all of them, then only one per class file is executed. the variants with 1 test method being executed work fine. variant with multiple test classes (not methods) does work in both testng and junit4. Milos On Sun, Jul 29, 2012 at 10:45 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Hi, This is a bugfix release. We solved a few issues: Bug [SUREFIRE-659] - Maven PDF plugin:showSuccess=false creates empty table causing error [SUREFIRE-825] - NPE in JUnit4TestChecker if org.junit.runner.RunWith class can't be loaded by testClassloader [SUREFIRE-827] - Surefire 2.12 cannot run a single test, regression from 2.11 [SUREFIRE-828] - testng test need a excludedGroups element to not fail [SUREFIRE-832] - JUnit categories only work when junit47 provider is explicitly set [SUREFIRE-836] - regression with surefire 2.12 plugin and SecurityManager [SUREFIRE-844] - test parameter no longer working with JUnit in 2.12 (worked in 2.9 - 2.11) [SUREFIRE-847] - surefire cannot run single testng test [SUREFIRE-858] - Running a single unit test in Windows [SUREFIRE-865] - surefire 2.12 with parallel=methods does not execute junit 4.7+ tests in parallel [SUREFIRE-869] - Parallel test execution on class level runs not all tests but some twice [SUREFIRE-871] - Output of forked tests with non-zero exit code not retained [SUREFIRE-877] - Surefire doesn't support mixed TestNG 6.5.x config parameter [SUREFIRE-879] - maven-surefire-report-plugin fails some times with ConcurrentModificationException when running parallel TestNG [SUREFIRE-880] - ObjectFactory no longer works with TestNG 6.5.2 [SUREFIRE-883] - Cannot run tests in parallel Improvement [SUREFIRE-745] - -Dtest supports multiple test classes but not multiple test methods [SUREFIRE-876] - surefire-junit47 does not work in an OSGi classloader environment [SUREFIRE-881] - use plugins annotations [SUREFIRE-889] - JUnit | supprot inheritance of test's categories/groups We unresolved 1 issue; which had to be reverted because it was the root cause of several of
Re: Does maven have pluggable available build extensions?
if that works it will be beautifull. I'll test it. Thanks!! On 1 August 2012 04:01, Jörg Schaible joerg.schai...@scalaris.com wrote: Hi Tony, Tony Lâmpada wrote: We all know maven has a lot of available pluginshttp://maven.apache.org/plugins/index.htmlthat do a lot of useful stuff. I recently learned about a different kind of extension point for maven builds: build extensionshttp://maven.apache.org/examples/maven-3-lifecycle- extensions.html . Is there a similar list of useful build extensions that one can use? And more specifically, one that can maybe help with thishttp://stackoverflow.com/questions/11749375/import-maven-plugin- configuration-by-composition-rather-than-inheritance-can-it ? Well, with M3 you can use profiles ... hehehe Seriously, I'd not meddle with the execution order at runtime. You will not have much fun with a parallel build later. First you have to understand, why your profile example cannot work (and never will). Maven *has to* resolve the parent POM completely first (i.e. all profiles are evaluated and merged into the effective POM). Then the same happens for the current POM. Obviously no property will have now any effect on profile activation in the parent ... this is simply too late. You must also know, that the output of help:active-profiles is not complete. It does not show you the profiles that have been activated in a parent POM. The best you can do in your use case is to define a profile in the parent and activate it based on the existence on a file. We have a profile in our global POM that automatically activates the verifier plugin, if the project contains a verifications file: % profile idauto-verification/id activation file !-- cannot use variables here -- existssrc/test/verifier/verifications.xml/exists /file /activation build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-verifier-plugin/artifactId /plugin /plugins /build /profile % However, this will only work in a multi-project build with M3, but not with M2, because M3 uses the current POM root as reference for file resolution, while M2 uses the current working directory. For your problem you might simply create in your projects a profile folder that contains empty files with proper names % / + boy + profiles - kid - boy + girl + profiles - kid - girl + kid + profiles - kid % and the profile activation is based on existence of those files, e.g. existsprofile/kid/exists Hope this helps, Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Does maven have pluggable available build extensions?
Wow thanks a lot! It works just as you said. THANK YOU! :-) Cheers Tony On 1 August 2012 09:25, Tony Lâmpada t...@freedomsponsors.com wrote: if that works it will be beautifull. I'll test it. Thanks!! On 1 August 2012 04:01, Jörg Schaible joerg.schai...@scalaris.com wrote: Hi Tony, Tony Lâmpada wrote: We all know maven has a lot of available pluginshttp://maven.apache.org/plugins/index.htmlthat do a lot of useful stuff. I recently learned about a different kind of extension point for maven builds: build extensionshttp://maven.apache.org/examples/maven-3-lifecycle- extensions.html . Is there a similar list of useful build extensions that one can use? And more specifically, one that can maybe help with thishttp://stackoverflow.com/questions/11749375/import-maven-plugin- configuration-by-composition-rather-than-inheritance-can-ithttp://stackoverflow.com/questions/11749375/import-maven-plugin-configuration-by-composition-rather-than-inheritance-can-it ? Well, with M3 you can use profiles ... hehehe Seriously, I'd not meddle with the execution order at runtime. You will not have much fun with a parallel build later. First you have to understand, why your profile example cannot work (and never will). Maven *has to* resolve the parent POM completely first (i.e. all profiles are evaluated and merged into the effective POM). Then the same happens for the current POM. Obviously no property will have now any effect on profile activation in the parent ... this is simply too late. You must also know, that the output of help:active-profiles is not complete. It does not show you the profiles that have been activated in a parent POM. The best you can do in your use case is to define a profile in the parent and activate it based on the existence on a file. We have a profile in our global POM that automatically activates the verifier plugin, if the project contains a verifications file: % profile idauto-verification/id activation file !-- cannot use variables here -- existssrc/test/verifier/verifications.xml/exists /file /activation build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-verifier-plugin/artifactId /plugin /plugins /build /profile % However, this will only work in a multi-project build with M3, but not with M2, because M3 uses the current POM root as reference for file resolution, while M2 uses the current working directory. For your problem you might simply create in your projects a profile folder that contains empty files with proper names % / + boy + profiles - kid - boy + girl + profiles - kid - girl + kid + profiles - kid % and the profile activation is based on existence of those files, e.g. existsprofile/kid/exists Hope this helps, Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
build extensions
Greetings,
After being inspired by another thread, I decided to create a build
extension. All it does right now is cut a message to the log:
@Component(role = AbstractMavenLifecycleParticipant.class)
public final class BannerExtension extends AbstractMavenLifecycleParticipant
{
@Requirement private RuntimeInformation runtime;
@Requirement private Logger logger;
@Override
public void afterProjectsRead(final MavenSession session) {
if (logger.isInfoEnabled())
{ logger.info(RUNTIME: + runtime.getApplicationVersion()); }
}
}
Most of the time it works just fine, however sometimes after I have
mvn clean previously, I will take an exception in the log on the next
mvn invocation:
[WARNING] Failed to retrieve plugin descriptor for
com.acme.maven.extensions:banner-maven-extension:0.1: Failed to parse
plugin descriptor for
com.acme.maven.extensions:banner-maven-extension:0.1
($HOME/.m2/repository/com/acme/maven/extensions/banner-maven-extension/0.1/banner-maven-extension-0.1.jar):
No plugin descriptor found at META-INF/maven/plugin.xml
However, I have followed the documentation
http://maven.apache.org/examples/maven-3-lifecycle-extensions.html and
the extension pom generates both the metadata and test-metadata
(though no META-INF/maven/plugin.xml is created), and I find
META-INF/plugins/components.xml with:
?xml version=1.0 encoding=UTF-8?
component-set
components
component
roleorg.apache.maven.AbstractMavenLifecycleParticipant/role
role-hintdefault/role-hint
implementationcom.acme.maven.extensions.BannerExtension/implementation
description /
isolated-realmfalse/isolated-realm
requirements
requirement
roleorg.codehaus.plexus.logging.Logger/role
role-hint /
field-namelogger/field-name
/requirement
requirement
roleorg.apache.maven.execution.RuntimeInformation/role
role-hint /
field-nameruntime/field-name
/requirement
/requirements
/component
/components
/component-set
This isn't a fatal issue, the build continues just fine. But it is
very annoying to sometimes have that WARNING put into the build logs.
Any hints for me?
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Indexer 4.1.3
Here my +1 2012/7/30 Olivier Lamy ol...@apache.org: Hi, I'd like to release Maven Indexer 4.1.3. We fixed 7 issues: https://jira.codehaus.org/browse/MINDEXER/fixforversion/17843 Staging repository: https://repository.apache.org/content/repositories/maven-097/ Staging site: http://maven.apache.org/maven-indexer-4.1.3/ (wait sync) Vote open for 72H. [+1] [0] [-1] Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1367470 - /maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
On 07/31/2012 02:43 PM, Hervé BOUTEMY wrote: compile is the default scope, isn't it? Or do I miss something? Perhaps scopeprovided/scope was meant? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1367470 - /maven/plugin-tools/trunk/maven-plugin-plugin/src/site/apt/examples/using-annotations.apt.vm
2012/8/1 Jesse Glick jgl...@cloudbees.com: On 07/31/2012 02:43 PM, Hervé BOUTEMY wrote: compile is the default scope, isn't it? Or do I miss something? Perhaps scopeprovided/scope was meant? Yup. Just saying this is not needed at runtime level. I have changed and remove the scope. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: New plugin archetype (was: New annotation system)
Yup. I will work on that. 2012/7/23 Jesse Glick jgl...@cloudbees.com: On a related note, I think we need a new archetype for plugins; the existing maven-archetype-mojo 1.0 is out of date and not ready for annotations. Specifically needed: 1. Need a dep on maven-plugin-annotations. 2. Need to specify skipErrorNoDescriptorsFound. 3. Have to explicitly call descriptor goal - not part of default lifecycle (!). 4. Apparently need to tell maven-site-plugin to run maven-plugin-plugin. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: build extensions
Greetings, On Wed, Aug 1, 2012 at 9:57 AM, Jesse Farinacci jie...@gmail.com wrote: Most of the time it works just fine, however sometimes after I have mvn clean previously, I will take an exception in the log on the next mvn invocation: [WARNING] Failed to retrieve plugin descriptor for com.acme.maven.extensions:banner-maven-extension:0.1: Failed to parse plugin descriptor for com.acme.maven.extensions:banner-maven-extension:0.1 ($HOME/.m2/repository/com/acme/maven/extensions/banner-maven-extension/0.1/banner-maven-extension-0.1.jar): No plugin descriptor found at META-INF/maven/plugin.xml So, I have narrowed down the failure a bit. When I invoke it via: extensionsextension groupIdcom.acme.maven.extensions/groupId artifactIdbanner-maven-extension/artifactId version0.1/version /extension/extensions it works! However, when I invoke it via: buildpluginsplugin groupIdcom.acme.maven.extensions/groupId artifactIdbanner-maven-extension/artifactId version0.1/version extensionstrue/extensions /plugin/plugins/build It fails with the aforementioned error. Is this a bug? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: build extensions
This probably just means that you are building the extension as a JAR, not a maven-plugin, so there's no descriptor. Of if it is as a Maven plugin, it might be a lack of mojos in there. ISTR a fix in a recent plugin tools to avoid a related warning if there are only extensions in the plugin. - Brett On 02/08/2012, at 12:24 AM, Jesse Farinacci jie...@gmail.com wrote: Greetings, On Wed, Aug 1, 2012 at 9:57 AM, Jesse Farinacci jie...@gmail.com wrote: Most of the time it works just fine, however sometimes after I have mvn clean previously, I will take an exception in the log on the next mvn invocation: [WARNING] Failed to retrieve plugin descriptor for com.acme.maven.extensions:banner-maven-extension:0.1: Failed to parse plugin descriptor for com.acme.maven.extensions:banner-maven-extension:0.1 ($HOME/.m2/repository/com/acme/maven/extensions/banner-maven-extension/0.1/banner-maven-extension-0.1.jar): No plugin descriptor found at META-INF/maven/plugin.xml So, I have narrowed down the failure a bit. When I invoke it via: extensionsextension groupIdcom.acme.maven.extensions/groupId artifactIdbanner-maven-extension/artifactId version0.1/version /extension/extensions it works! However, when I invoke it via: buildpluginsplugin groupIdcom.acme.maven.extensions/groupId artifactIdbanner-maven-extension/artifactId version0.1/version extensionstrue/extensions /plugin/plugins/build It fails with the aforementioned error. Is this a bug? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: build extensions
On 08/01/2012 09:57 AM, Jesse Farinacci wrote: http://maven.apache.org/examples/maven-3-lifecycle-extensions.html Side note: this page fails to mention -Dmaven.ext.class.path=... as an alternative to adding to lib/ext/*.jar, which I guess would work (based on its recommendation from EventSpy). - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Indexer 4.1.3
+1 Hervé Le lundi 30 juillet 2012 19:04:21 Olivier Lamy a écrit : Hi, I'd like to release Maven Indexer 4.1.3. We fixed 7 issues: https://jira.codehaus.org/browse/MINDEXER/fixforversion/17843 Staging repository: https://repository.apache.org/content/repositories/maven-097/ Staging site: http://maven.apache.org/maven-indexer-4.1.3/ (wait sync) Vote open for 72H. [+1] [0] [-1] Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT][VOTE] Release Maven Surefire Plugin version 2.12.1
Hi, The vote has passed with the following result : +1 (binding): Olivier Lamy, Mark Struberg, Hervé Boutemy,Benson Margulies, Kristian Rosenvold +1 (non binding): abhijith tn -1 (Non binding): Milos Kleint (see vote thread for resolution). I will promote the artifacts to the central repo. Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Dependency Tree 2.0 + Maven Project Info Reports Plugin 2.5 + Maven Dependency Plugin 2.5 (take 2)
Hi, We solved 3 + 7 + 8 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761styleName=Htmlversion=14540 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142styleName=Htmlversion=17369 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11214styleName=Htmlversion=18077 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11761status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11142status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11214status=1 Staging repo: https://repository.apache.org/content/repositories/maven-110/ https://repository.apache.org/content/repositories/maven-110/org/apache/maven/shared/maven- dependency-tree/2.0/maven-dependency-tree-2.0-source-release.zip https://repository.apache.org/content/repositories/maven-110/org/apache/maven/plugins/maven- project-info-reports-plugin/2.5/maven-project-info-reports-plugin-2.5-source- release.zip https://repository.apache.org/content/repositories/maven-110/org/apache/maven/plugins/maven- dependency-plugin/2.5/maven-dependency-plugin-2.5-source-release.zip Staging sites: http://maven.apache.org/shared/maven-dependency-tree-2.0/ http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.5/ http://maven.apache.org/plugins/maven-dependency-plugin-2.5/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1
Re: Release Request: maven-rar-plugin
Hi All. Just a reminder. :-) -Chris On Sat, Jul 28, 2012 at 12:52 AM, Olivier Lamy ol...@apache.org wrote: Hi I will take care of that next week. -- Olivier Le 27 juil. 2012 12:26, Chris Graham chrisgw...@gmail.com a écrit : Hi All. I'm starting to do some serious work with Maven 3 and parallel builds. In doing so, I've discovered that the maven-rar-plugin has not been recently released. There have been 15 issues closed, with 12 still outstanding. So I'd really like to see the current code released, as it addresses my MRAR-27 - Add @threadSafe support. The last time the 2.2 package was released was back in 2006 (!) Also (and I know that this is not the right place to ask, but it is worth while, as there is lots of knowledge here, but...) The codehaus cobertura plugin (2.5.1) is not marked as @threadSafe. The underlying cobertura release is listed as threadsafe (but no locking support [whatever that really means]). Are there any technical reasons as to why we can also not mark the cobertura-maven-plugin as threadsafe? -Chris
