Re: Apache OpenMeetings build fails on Maven 3.4-SNAPSHOT
Thanks, Christian. Is there a Maven ticket for this? On Mon, Sep 5, 2016 at 5:30 PM, Maxim Solodovnik <solomax...@gmail.com> wrote: > I'll keep this email and will double-check everything after 3.4 will be > released > > On Mon, Sep 5, 2016 at 10:25 PM, Christian Schulte <c...@schulte.it> wrote: > > > Am 09/05/16 um 16:48 schrieb Maxim Solodovnik: > > > I have merged your PR, Thanks! :)) > > > > I cannot tell in what version this has stopped working. It will be > > working again in 3.4+. Maybe that PR isn't correct and the old behaviour > > really was intended years ago. > > > > Regards, > > -- > > Christian > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > -- > WBR > Maxim aka solomax > -- -- Behrooz Nobakht
Re: Use maven-invoker-plugin to run a Maven plugin on itself
Hi Karl, Thanks again for the argument. For me it's still a valid question of how for example the license plugin would apply itself on its source structure to fix/update Java header before a release? (Of course, I understand the principle of linearizability to fix the circular issue). Just in case, this is what I've been trying to apply this to: https://github.com/google/google-java-format/issues/69 The plugin should be able to apply the formatter to itself before any commit for example. Regards, Behrooz On Mon, Jul 18, 2016 at 9:59 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > Hi, > > On 7/18/16 9:31 PM, Behrooz Nobakht wrote: > >> Hi, >> >> Thanks for the reply and I agree with the logical circular dependency >> argument. >> But I still believe that this is valid test/use case for a Maven plugin >> being developed. >> > > I don't agree with that...cause for those things it is best having IT's > based on maven-invoker-pluginwhich will solves the problem here.. > > >> The profile idea 'self-test/run' works in this case for what I'm working >> on; >> but I think main reason is that logic here only applies to Java sources >> and >> the default is process-sources. In this, the plugin needs to run against >> itself >> before any release. >> > > The problem here is simply you need to do a mvn install before anything > else..without a preliminary install you won't get it working...cause during > the release process you need an installed version of your plugin..but this > must be a SNAPSHOT version which can't be used during a release cause you > will rely on an unstable non reproducible artifact (it does not matter if > its a plugin or a dependency)...You will create a tag from that state which > makes that permanent which is simply wrong! (Apart from that the release > plugin will prevent that already)... > > Nevertheless that profile does not really change a thing here... > > In it's consquence it's wrong...This kind of bootstrap can be handled by > using maven-invoker-plugin to write appropriate integration tests... > > Apart from that I don't see any change here if this would be > C++/Kotlin/Groovy or something else ? > > Kind regards > Karl Heinz > > > >> Regards, >> Behrooz >> >> >> On Mon, Jul 18, 2016 at 1:00 PM, Karl Heinz Marbaise <khmarba...@gmx.de> >> wrote: >> >> >>> Hi, >>> >>> trying to run your own plugin which you are developing within the same >>> project will not work cause that already sounds like a circle .. >>> >>> That's the reason to use invoker-plugin to have full fledged project >>> running as tests... >>> >>> A profile will not really help, cause you need to do a `mvn install` >>> first >>> and than run your project with something like `mvn -Pself-testing >>> verify` ? >>> Not a good idea? >>> >>> And finally this is not best practice... >>> >>> What you can do is to define a previous released version of your plugin >>> in >>> your pom ...That's what for example maven-invoker-plugin itself is >>> doing.. >>> ;-) >>> >>> >>> Kind regards >>> Karl Heinz Marbaise >>> >>> On 7/18/16 9:43 AM, Behrooz Nobakht wrote: >>> >>> Hi, >>>> >>>> I am developing a Maven Plugin and trying to follow documentation[1] to >>>> use >>>> maven-invoker-plugin >>>> from the auto-generated profile 'run-its' to run an execution of the >>>> plugin >>>> under dev on itself. >>>> >>>> As an example, let's consider mojouas/license-maven-plugin. One of it's >>>> goals is 'update-file-header'. >>>> And, it actually has an integration-test executed by >>>> maven-invoker-plugin >>>> but it's on a sample project. >>>> What if I wanted to run the update-file-header on the >>>> license-maven-plugin >>>> itself? How? >>>> >>>> One straight way would be introduce another profile to configure the >>>> plugin >>>> to run on itself, but is this a >>>> good practice on Maven plugin development? >>>> >>>> Thanks, >>>> Behrooz >>>> >>>> >>>> >>>> [1]: http://maven.apache.org/plugins/maven-invoker-plugin/ >>>> [2]: >>>> >>>> >>>> https://github.com/mojohaus/license-maven-plugin/tree/master/src/it/update-file-header-test-mojo >>>> >>>> >>>> > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- Behrooz Nobakht
Re: Use maven-invoker-plugin to run a Maven plugin on itself
Hi, Thanks for the reply and I agree with the logical circular dependency argument. But I still believe that this is valid test/use case for a Maven plugin being developed. The profile idea 'self-test/run' works in this case for what I'm working on; but I think main reason is that logic here only applies to Java sources and the default is process-sources. In this, the plugin needs to run against itself before any release. Regards, Behrooz On Mon, Jul 18, 2016 at 1:00 PM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > > Hi, > > trying to run your own plugin which you are developing within the same > project will not work cause that already sounds like a circle .. > > That's the reason to use invoker-plugin to have full fledged project > running as tests... > > A profile will not really help, cause you need to do a `mvn install` first > and than run your project with something like `mvn -Pself-testing verify` ? > Not a good idea? > > And finally this is not best practice... > > What you can do is to define a previous released version of your plugin in > your pom ...That's what for example maven-invoker-plugin itself is doing.. > ;-) > > > Kind regards > Karl Heinz Marbaise > > On 7/18/16 9:43 AM, Behrooz Nobakht wrote: > >> Hi, >> >> I am developing a Maven Plugin and trying to follow documentation[1] to >> use >> maven-invoker-plugin >> from the auto-generated profile 'run-its' to run an execution of the >> plugin >> under dev on itself. >> >> As an example, let's consider mojouas/license-maven-plugin. One of it's >> goals is 'update-file-header'. >> And, it actually has an integration-test executed by maven-invoker-plugin >> but it's on a sample project. >> What if I wanted to run the update-file-header on the license-maven-plugin >> itself? How? >> >> One straight way would be introduce another profile to configure the >> plugin >> to run on itself, but is this a >> good practice on Maven plugin development? >> >> Thanks, >> Behrooz >> >> >> >> [1]: http://maven.apache.org/plugins/maven-invoker-plugin/ >> [2]: >> >> https://github.com/mojohaus/license-maven-plugin/tree/master/src/it/update-file-header-test-mojo >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- Behrooz Nobakht
Use maven-invoker-plugin to run a Maven plugin on itself
Hi, I am developing a Maven Plugin and trying to follow documentation[1] to use maven-invoker-plugin from the auto-generated profile 'run-its' to run an execution of the plugin under dev on itself. As an example, let's consider mojouas/license-maven-plugin. One of it's goals is 'update-file-header'. And, it actually has an integration-test executed by maven-invoker-plugin but it's on a sample project. What if I wanted to run the update-file-header on the license-maven-plugin itself? How? One straight way would be introduce another profile to configure the plugin to run on itself, but is this a good practice on Maven plugin development? Thanks, Behrooz [1]: http://maven.apache.org/plugins/maven-invoker-plugin/ [2]: https://github.com/mojohaus/license-maven-plugin/tree/master/src/it/update-file-header-test-mojo
Re: Full migration to Git
We have also used Subgit[1] to do a one-time migration to Git from a large SVN. We also needed to use specific branch/tag filtering for which Subgit took around 5 days to complete. Hope this helps. Regards, Behrooz [1]: http://www.subgit.com/ On Fri, Oct 2, 2015 at 11:37 PM, Jörg Schaible <joerg.schai...@gmx.de> wrote: > Kristian Rosenvold wrote: > > > This did not go well. I was able to get a full backup of asf svn up on > > my server, but unfortunately git-svn barfed on it. So I suppose some > > heavy filter-branching over the current git-svn clones is the only way > > to go, > > Never tried myself, but reposurgeon is supposed to work also directly on > svn > dumps: > > http://www.catb.org/esr/reposurgeon/reposurgeon.html > > Cheers, > Jörg > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- -- Behrooz Nobakht
Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder
Thank you, Vincent for the link. It completely describes the way to create default execution without the need to configure it when using the plugin. I learnt a lot! On Mon, Jun 8, 2015 at 7:53 PM, Vincent Latombe vincent.lato...@gmail.com wrote: This annotation just allows you to skip the phase declaration when you add the execution to your pom. If you want to skip the execution block, you'll need to create a custom packaging [1]. Then you'd specify packagingmy-packaging/packaging in your pom, instead of packagingjar/packaging (or any other value you currently use) Cheers, Vincent [1] http://blog.sonatype.com/2009/08/create-a-customized-build-process-in-maven/#.VXXWhUZ5zaU Vincent 2015-06-08 19:21 GMT+02:00 Behrooz Nobakht nob...@gmail.com: Let me continue with another question. Currently, my Mojo implementation has @Mojo(name = my-goal-name, defaultPhase = LifecyclePhase.GENERATE_SOURCES) However, I still need to add `execution` when I'm using the plugin; otherwise it's just ignored. I was expecting that the Mojo annotation would remove this requirement. What am I missing? Thanks, Behrooz On Mon, Jun 8, 2015 at 6:36 PM, Behrooz Nobakht nob...@gmail.com wrote: Hi Andreas, Thank you for the pointer. It helped and it worked. I was using an improper life cycle phase as the default. Cheers, Behrooz On Mon, Jun 8, 2015 at 6:13 PM, Andreas Gudian andreas.gud...@gmail.com wrote: Hi, You can check the build-helper-maven-plugin, which has a tiny goal to add a source directory to the project: https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java The maven-eclipse-plugin picks up all source directories listed in the model of the build. Hope that helps, Andreas Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht : Hi, I am trying to follow what `maven-plugin-plugin` Mojo does when generating HelpMojo.java. It also updates eclipse's .classpath some way (?) that I can see the `target/generated-sources/plugin` as a source folder in my IDE. Similarly, this is also what maven-jaxb2-plugin does when generating sources files from a schema. I'm a bit clueless at this moment how to achieve the same for a custom plugin I'm developing. Any specific documentation, hints, or example sources I can look into for this? Thanks in advance, Behrooz -- -- Behrooz Nobakht -- -- Behrooz Nobakht -- -- Behrooz Nobakht
Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder
Let me continue with another question. Currently, my Mojo implementation has @Mojo(name = my-goal-name, defaultPhase = LifecyclePhase.GENERATE_SOURCES) However, I still need to add `execution` when I'm using the plugin; otherwise it's just ignored. I was expecting that the Mojo annotation would remove this requirement. What am I missing? Thanks, Behrooz On Mon, Jun 8, 2015 at 6:36 PM, Behrooz Nobakht nob...@gmail.com wrote: Hi Andreas, Thank you for the pointer. It helped and it worked. I was using an improper life cycle phase as the default. Cheers, Behrooz On Mon, Jun 8, 2015 at 6:13 PM, Andreas Gudian andreas.gud...@gmail.com wrote: Hi, You can check the build-helper-maven-plugin, which has a tiny goal to add a source directory to the project: https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java The maven-eclipse-plugin picks up all source directories listed in the model of the build. Hope that helps, Andreas Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht : Hi, I am trying to follow what `maven-plugin-plugin` Mojo does when generating HelpMojo.java. It also updates eclipse's .classpath some way (?) that I can see the `target/generated-sources/plugin` as a source folder in my IDE. Similarly, this is also what maven-jaxb2-plugin does when generating sources files from a schema. I'm a bit clueless at this moment how to achieve the same for a custom plugin I'm developing. Any specific documentation, hints, or example sources I can look into for this? Thanks in advance, Behrooz -- -- Behrooz Nobakht -- -- Behrooz Nobakht
Mojo API to add target/generated-sources/DIR to eclipse's source folder
Hi, I am trying to follow what `maven-plugin-plugin` Mojo does when generating HelpMojo.java. It also updates eclipse's .classpath some way (?) that I can see the `target/generated-sources/plugin` as a source folder in my IDE. Similarly, this is also what maven-jaxb2-plugin does when generating sources files from a schema. I'm a bit clueless at this moment how to achieve the same for a custom plugin I'm developing. Any specific documentation, hints, or example sources I can look into for this? Thanks in advance, Behrooz
Re: Mojo API to add target/generated-sources/DIR to eclipse's source folder
Hi Andreas, Thank you for the pointer. It helped and it worked. I was using an improper life cycle phase as the default. Cheers, Behrooz On Mon, Jun 8, 2015 at 6:13 PM, Andreas Gudian andreas.gud...@gmail.com wrote: Hi, You can check the build-helper-maven-plugin, which has a tiny goal to add a source directory to the project: https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java The maven-eclipse-plugin picks up all source directories listed in the model of the build. Hope that helps, Andreas Am Montag, 8. Juni 2015 schrieb Behrooz Nobakht : Hi, I am trying to follow what `maven-plugin-plugin` Mojo does when generating HelpMojo.java. It also updates eclipse's .classpath some way (?) that I can see the `target/generated-sources/plugin` as a source folder in my IDE. Similarly, this is also what maven-jaxb2-plugin does when generating sources files from a schema. I'm a bit clueless at this moment how to achieve the same for a custom plugin I'm developing. Any specific documentation, hints, or example sources I can look into for this? Thanks in advance, Behrooz -- -- Behrooz Nobakht
Re: [CHANGES PLUGIN] 'webUser' is ignored for JIRA report
Trust Decision is assumed. can it be the root cause? And, if so, how can I fix this? I'd appreciate any help on this. Thanks, Behrooz -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- -- Behrooz Nobakht
