Re: [VOTE] Release Apache Maven Ear Plugin version 2.9
+1, thanks! S. On Tue, Nov 26, 2013 at 9:45 PM, Robert Scholte wrote: > Hi, > > We solved 11 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa? > projectId=11132&version=18770&styleName=Html > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa? > reset=true&pid=11132&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-004/ > https://repository.apache.org/content/repositories/maven- > 004/org/apache/maven/plugins/maven-ear-plugin/2.9/maven- > ear-plugin-2.9-source-release.zip > > Source release checksum(s): > maven-ear-plugin-2.9-source-release.zip sha1: > 4dcbfdc637050eaad2f55c951c36bd17d4205572 > > Staging site: > http://maven.apache.org/plugins-archives/maven-ear-plugin-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[ANN] Apache Maven Shade Plugin 2.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shade Plugin, version 2.2 This plugin provides the capability to package the artifact in an uber-jar, including its dependencies and to shade - i.e. rename - the packages of some of the dependencies. http://maven.apache.org/plugins/maven-shade-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-shade-plugin 2.2 Release Notes - Apache Maven Shade Plugin - Version 2.2 ** Improvement * [MSHADE-158] - Allow shading of test jar Have fun -- The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Ear Plugin version 2.9
+1 On 27 November 2013 07:45, Robert Scholte wrote: > Hi, > > We solved 11 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=18770&styleName=Html > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11132&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-004/ > https://repository.apache.org/content/repositories/maven-004/org/apache/maven/plugins/maven-ear-plugin/2.9/maven-ear-plugin-2.9-source-release.zip > > Source release checksum(s): > maven-ear-plugin-2.9-source-release.zip sha1: > 4dcbfdc637050eaad2f55c951c36bd17d4205572 > > Staging site: > http://maven.apache.org/plugins-archives/maven-ear-plugin-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Olivier Lamy Ecetera: http://ecetera.com.au 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: More hard problems...
> To: dev@maven.apache.org > Subject: Re: More hard problems... > Date: Tue, 26 Nov 2013 22:57:45 +0100 > From: e...@zusammenkunft.net > > Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte : > > In addition to this story: There's an open issue called MDEPLOY-118 > > which describes a related issue: how to release the same version for > > different platforms? > > Related there is also the need for "features". Larger projects typically > have a lot of optional dependencies but dont help to requesat a specific > subset. For example a Scheduler like Quartz offers a core engine but also MG>Here are the Quartz configuration properties i have org.quartz.scheduler.instanceName = JBossQuartzScheduler org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool org.quartz.threadPool.threadCount = 10 org.quartz.threadPool.threadPriority = 5 org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true MG>would you know of a plugin that will update my quartz.properties MG>in org\jboss\resource\adapter\quartz\inflow > EJB APIs or a Servlet manager implementation. In an ideal world the > project would be split into multiple artifacts, but even then there can be > a complexity explosion. Depending on the "core scheduler" feature of > "quartz" would then skip all optional dependencies (like servlet and EJB > API). MG>How best to configure quartz core scheduler feature? MG>What would this look like? > > (This is similiar to the testing scope, which could be implemented as a > well known "feature"). And this also goes in line with > platforms/implementations: the "jdk1.4" feature can depend on a > concurrent-backport wherees the java7 does not. > > Gruss > Bernd MG>Beste Grüße MG>Martin > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org >
Re: Property namespaces Was: Changing JDK version without specifying maven-compiler-plugin version
On Wed, Nov 27, 2013 at 5:49 PM, Mirko Friedenhagen wrote: > Hello Laird, > > the only pity with using properties is that they are not namespaced most of > the time (the maven.compiler.* ones being an exception here), "output" is > claimed at least by three mojos IIRC. And skipTests is almost a general one > but you may not easily specify that you do not want to run surefire but > e.g. invoker tests nonetheless :-) > > I would have liked conventions like always "prefix with plugin name". > > +1000 to that!
[RESULT][VOTE] Apache Maven Shade Plugin 2.2
Hi The vote has passed with the following result: +1 (binding): Stephen, Hervé, Olivier I will continue the release process. Cheers, -- Olivier Lamy Ecetera: http://ecetera.com.au 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: [VOTE] Apache Maven Shade Plugin 2.2
My +1 On 25 November 2013 10:19, Olivier Lamy wrote: > Hi, > I'd like to release Apache Maven Shade plugin 2.2 > > We fixed 1 issue: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540&version=18768 > > Staging repository: > https://repository.apache.org/content/repositories/maven-002/ > > Source release: > https://repository.apache.org/content/repositories/maven-002/org/apache/maven/plugins/maven-shade-plugin/2.2/maven-shade-plugin-2.2-source-release.zip > > Staging site: > http://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ > > Vote open for 72H. > > [+1] > [0] > [-1] > > Thanks > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Ecetera: http://ecetera.com.au 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
Maven 2.2.1: How to convert an enum in a complex configuration element?
Hello, the jacoco-maven-plugin 0.6.3 introduced a complex type with an enum field as configuration element[0] This works fine with Maven 3.X however with Maven 2.2.1 this fails badly[1]. Using an implementation hint did help for the uppermost configuration element itself, however the field "element" which is an enum may not be converted. As we want to maintain 2.2.1 compatibility urging the users to Maven 3.X is not really an option :-) The used plexus-container-default-1.0* does not include an EnumConverter so we see the stack trace below. - Is there any way to enforce a newer plexus-container-default during the build/parsing of the pom/DOM generation? - Does anyone know of a workaround? --- snip --- [INFO] Failed to configure plugin parameters for: org.jacoco:jacoco-maven-plugin:0.6.4-SNAPSHOT (found static expression: 'CLASS' which may act as a default value). Cause: Cannot assign configuration entry 'element' to 'class org.jacoco.core.analysis.ICoverageNode$ElementType' from 'CLASS', which is of type class java.lang.String [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.jacoco:jacoco-maven-plugin. Reason: Unable to parse the created DOM for plugin configuration at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginConfigurationException: Error configuring: org.jacoco:jacoco-maven-plugin. Reason: Unable to parse the created DOM for plugin configuratio n at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot assign configuration entry 'element' to 'class org.jacoco.core.analysis.ICoverageNode $ElementType' from 'CLASS', which is of type class java.lang.String at org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.fromExpression(AbstractConfigurationConverter.java:149) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:80) at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:207) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90) at org.codehaus.plexus.component.configurator.converters.composite.CollectionConverter.fromConfiguration(CollectionConverter.java:177) at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
Re: [VOTE] Apache Maven SCM 1.9
On Nov 26, 2013 8:41 AM, "Robert Scholte" wrote: > > Yes indeed, I have GitTortoise installed. > You may call it good news, but I've also started the Process Explorer (to keep track of the problematic process) and now I've been able to run the project three times in a row without failures. > So it's a bit frustrating that the result is inconsistent whenever I try to execute the project. > > I think we're ready for SCM 1.9 take 2 > > @Olamy will you pick this up? Sure I can early next week. > > Robert > > Op Mon, 25 Nov 2013 21:04:59 +0100 schreef Bernd Eckenfels < e...@zusammenkunft.net>: > > >> I sometimes have the problem that the explorer extension tgitcache from Tortoise keeps handles open in git directories. Maybe your test machine has that installed? >> >>> Am 25.11.2013 um 19:46 schrieb "Robert Scholte" : >>> >>> I have an appointment tonight, will try it afterwards or tomorrow with a clean checkout. >>> >>> Robert >>> >>> Op Mon, 25 Nov 2013 19:43:58 +0100 schreef Dominik Bartholdi < d...@fortysix.ch>: >>> Thats really disappointing, specially as I have finally managed to get hold on a windows PC and I just run everything 10times in row without any issues… :( I’m pretty much out of ideas :( If anyone has any hand he can share, that would be great! I tried with: Windows 7, Java 1.6.0_17-b04, maven 3.1.1 Domi > On 24.11.2013, at 21:01, Robert Scholte wrote: > > Hmm, maybe I cheered too early. A second run gave me 6 errors. > Still unsure what is keeping a lock of the files. > Both 'mvn clean' and 'rmdir /S target' fail. > > F:\java-workspace\apache-maven-scm\maven-scm\maven-scm-providers\maven-scm-provi > ders-git\maven-scm-provider-jgit>rmdir /S target > target. Weet u het zeker (J/N)? j > target\scm-test\WORKIN~1\GIT~1\objects\pack\pack-3ecde7a8782b53b94510513a4b1275d > 7e33392a9.idx - Toegang geweigerd. > target\scm-test\WORKIN~1\GIT~1\objects\pack\pack-3ecde7a8782b53b94510513a4b1275d > 7e33392a9.pack - Het proces heeft geen toegang tot het bestand omdat het door ee > n ander proces wordt gebruikt. > > translations: > - Are you sure (Y/N) > - Access denied > - The process has no access to the file because it is used by another process. > > Robert > > > Op Sun, 24 Nov 2013 20:43:35 +0100 schreef Robert Scholte < rfscho...@apache.org>: > >> We're getting closer, only one error left: >> >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.926 sec <<< FA >> ILURE! - in org.apache.maven.scm.provider.git.jgit.command.tag.JGitTagCommandTck >> Test >> testTagCommandTest(org.apache.maven.scm.provider.git.jgit.command.tag.JGitTagCom >> mandTckTest) Time elapsed: 1.817 sec <<< ERROR! >> java.io.IOException: Could not delete file F:\java-workspace\apache-maven-scm\ma >> ven-scm\maven-scm-providers\maven-scm-providers-git\maven-scm-provider-jgit\targ >> et\scm-test\updating-copy\.git\objects\pack\pack-3ecde7a8782b53b94510513a4b1275d >> 7e33392a9.idx >> at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:180) >> at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:147) >> at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:149) >> at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:149) >> at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:149) >> at org.apache.maven.scm.provider.git.jgit.command.tag.JGitTagCommandTckT >> est.deleteDirectory(JGitTagCommandTckTest.java:52) >> >> >> Results : >> >> Tests in error: >> JGitTagCommandTckTest>ScmTckTestCase.setUp:106->ScmTestCase.setUp:71->deleteDi >> rectory:52 ╗ IO >> >> Even when Maven has finished I still can't delete these files. >> >> Robert >> >> Op Sun, 24 Nov 2013 19:30:22 +0100 schreef Dominik Bartholdi < d...@fortysix.ch>: >> >>> Hi everyone, >>> I think I solved all the issues we had on windows with the jgit-provider >>> @Robert can you have another try now? >>> The build https://builds.apache.org/job/maven-scm/ currently fails, but this is related to an issue with the upload to the snapshot repository at https://repository.apache.org/content/repositories/snapshots/ >>> regards Domi >>> >>> On 29.10.2013, at 09:27, Olivier Lamy wrote: for the record vote cancel. > On 29 October 2013 17:20, Domi wrote: > I was pointed to Matthias Sohn (jgit commiter) let's see if he has an idea, before we do a release of this. > His first thought was the WindowCache.reconfigure() - but Robert already fixed that. > /Domi > >> Am 28.10.2013 um 20:51 schrieb "Robert Scholte" < rfscho...@apache.org>: >> >> @Kristian: Brilliant data! >> >> @Dennis: the statistics have changed[1]. I mana
Re: git commit: MNG-5530 Introduced mojo execution guice component scope
On 11/27/2013, 3:08, Hervé BOUTEMY wrote: Le samedi 23 novembre 2013 11:43:54 Igor Fedorenko a écrit : but it's good to see a new idea like that tell me if I can help more than with this feedback Do you have any specific maven plugin in mind where this feature can be useful? Not for the moment. That's exactly why i was thinking at documentation, to avoid both unused and undocumented feature stay in place. Do you think current implementation will work as is or will have to be extended or adjusted before it will work? You did an IT that proves the code effectively works, no? I guess I wasn't clear. What I am trying to find is whether the proposed API is sufficient, whether class and method names make sense, etc. I don't think it's possible to tell this without specific components one has to implement, this is why I asked if you have specific usecase for this feature in mind. -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven development tools for m2e
On 11/27/2013, 3:04, Hervé BOUTEMY wrote: I'm interested in such tools: this can help a lot. adding a link in http://maven.apache.org/developers/index.html will be useful to let Maven developers know that such tooling exists for Eclipse I am mostly seeking feedback about this feature at this point, and I will really appreciate if you could try it and see if it works for your plugins and development workflow. I do plan to publish this feature to eclipse marketplace and mention in on maven developers page, but I would like to see the following happen first * somebody else tried the feature and confirmed and both useful and works as advertised. * m2e 1.5 m4 is released (which will happen in few weeks) * verifier 1.5 is released and core ITs are updated to use it I read "Known problems and limitations Maven Plugin metadata, i.e., META-INF/maven/plugin.xml, is "disappears" in some cases. A partial fix is planned in maven-plugin-plugin 3.3" But I didn't see any Jira issue that seems to handle such an issue What's the problem? Can I help find a solution? The problem is poor interaction between maven-plugin-plugin and eclipse workspace java builder. Java builder deletes META-INF/maven/plugin.xml file for some plugins but not for others. The solution is to use plexus BuildContext to write files to disk, like we did in resources-plugin. I don't have jira for this yet. -- Regards, Igor Regards, Hervé Le lundi 25 novembre 2013 08:03:17 Igor Fedorenko a écrit : Hello, I have a couple of m2e extensions that I use to work on maven and maven plugins. In short, they allow running/debugging maven core and maven plugin directly from m2e workspace, without the need to install anything to the local repo after each code change. There is slightly more detailed description and installation instructions at github [1] and I plan to publish this to eclipse marketplace for easier user installation. Let me know what you think. [1] https://github.com/ifedorenko/com.ifedorenko.m2e.mavendev/blob/master/README .md -- Regards, Igor - 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: git commit: MNG-5530 Introduced mojo execution guice component scope
Le samedi 23 novembre 2013 11:43:54 Igor Fedorenko a écrit : > > but it's good to see a new idea like that > > > > tell me if I can help more than with this feedback > > Do you have any specific maven plugin in mind where this feature can be > useful? Not for the moment. That's exactly why i was thinking at documentation, to avoid both unused and undocumented feature stay in place. > Do you think current implementation will work as is or will have > to be extended or adjusted before it will work? You did an IT that proves the code effectively works, no? Regards, Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven development tools for m2e
I'm interested in such tools: this can help a lot. adding a link in http://maven.apache.org/developers/index.html will be useful to let Maven developers know that such tooling exists for Eclipse I read "Known problems and limitations Maven Plugin metadata, i.e., META-INF/maven/plugin.xml, is "disappears" in some cases. A partial fix is planned in maven-plugin-plugin 3.3" But I didn't see any Jira issue that seems to handle such an issue What's the problem? Can I help find a solution? Regards, Hervé Le lundi 25 novembre 2013 08:03:17 Igor Fedorenko a écrit : > Hello, > > I have a couple of m2e extensions that I use to work on maven and maven > plugins. In short, they allow running/debugging maven core and maven > plugin directly from m2e workspace, without the need to install anything > to the local repo after each code change. > > There is slightly more detailed description and installation > instructions at github [1] and I plan to publish this to eclipse > marketplace for easier user installation. > > Let me know what you think. > > [1] > https://github.com/ifedorenko/com.ifedorenko.m2e.mavendev/blob/master/README > .md > > -- > Regards, > Igor > > - > 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
