Re: Maven Release Plugin
Hello again. In my usecase all submodules SHOULD include a common set of dependencies. The submodules have no dependencies to other submodules. Thats why declaring the dependencies in the parent pom. The configuration option autoVersionSubmodulestrue/autoVersionSubmodules is only responsible to auto update the parent of all submodules. Independent from whether declaring the dependencies in the parent or in the submodules the plugin should reuse dependency version mappings once entered by the user for all subsequent/dependent modules. If it finds a unmapped artifact/version in a module it can prompt the user for it and reuse this mapping for the whole process without prompting again. This behavior should work for all usecases, shouln't it? Marcus Maven Users List users@maven.apache.org writes: The previous replies seem to miss the mark, your set up sounds good to me. The missing configuration you are looking for is: configuration autoVersionSubmodulestrue/autoVersionSubmodules /configuration Kalle On Thu, Sep 16, 2010 at 8:07 AM, Marcus Linke li...@newsaktuell.de wrote: Hello, i 've the following problem releasing a multi-module project with the maven-release-plugin (Version 2.0). The top (parent) pom-style project defines a set of snapshot dependencies that are inherited to all of its submodules. When using the release plugin in interactive mode, the plugin prompts for the new versions of these snapshot dependencies. So far, so good. But when diving into the submodules this is repeated for each module again. This is really annoying me because i have 20 submodules in that project. Is this is a know problem or a type of misconfiguration. Thanks Marcus Linke - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Mit freundlichen Grüßen Marcus Linke -- Softwareentwicklung, IT news aktuell GmbH - Ein Unternehmen der dpa-Gruppe Mittelweg 144, 20148 Hamburg Tel: +49 (0)40-4113-2588 Fax: +49 (0)40-4113-2595 www.newsaktuell.de www.presseportal.de www.newsaktuell.de/blog www.twitter.com/newsaktuell www.youtube.com/newsaktuell www.facebook.com/pages/newsaktuell/152372075544 www.friendfeed.com/newsaktuell -- Registergericht: Hamburg, Registernummer: HRB 42 738 Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE118617411 Vertretungsberechtigte Personen: Carl-Eduard Meyer (Geschäftsführer), Frank Stadthoewer (Geschäftsführer) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Release Plugin
Hello, i 've the following problem releasing a multi-module project with the maven-release-plugin (Version 2.0). The top (parent) pom-style project defines a set of snapshot dependencies that are inherited to all of its submodules. When using the release plugin in interactive mode, the plugin prompts for the new versions of these snapshot dependencies. So far, so good. But when diving into the submodules this is repeated for each module again. This is really annoying me because i have 20 submodules in that project. Is this is a know problem or a type of misconfiguration. Thanks Marcus Linke - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Release Plugin
Thanks for the replies first. The goal of declaring the dependencies in the parent pom project is to force all submodules to use these dependencies. When using dependencyManagement in parent pom each submodule have to declare this set of dependencies itself which seems really redundant to me. By the way, when declaring the dependencies in each submodule the maven-release-plugin behavior should be the same (promting repeately for the same artifact versions). So the question is whether this behavior of the plugin should be changed or exists a usecase where submodules uses different versions of the same artifact. Regards Marcus Maven Users List users@maven.apache.org schreibt: I would agree that having dependencies in a POM project is curious, and cannot think of a good use case for them. Are you really looking for dependencyManagement where you can declare what versions should be used by inherited projects? On Thu, Sep 16, 2010 at 10:11 AM, Antonio Petrelli antonio.petre...@gmail.com wrote: 2010/9/16 Marcus Linke li...@newsaktuell.de: i 've the following problem releasing a multi-module project with the maven-release-plugin (Version 2.0). The top (parent) pom-style project defines a set of snapshot dependencies that are inherited to all of its submodules. When using the release plugin in interactive mode, the plugin prompts for the new versions of these snapshot dependencies. So far, so good. But when diving into the submodules this is repeated for each module again. This is really annoying me because i have 20 submodules in that project. Is this is a know problem or a type of misconfiguration. Sincerely having dependencies in a pom project is curious, definitely I'd remove them. I suppose that your modules have a precedence, i.e. a module depends on another. If you play with transitive dependencies I think you'll get a clean (and real) dependency tree. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Mit freundlichen Grüßen Marcus Linke -- Softwareentwicklung, IT news aktuell GmbH - Ein Unternehmen der dpa-Gruppe Mittelweg 144, 20148 Hamburg Tel: +49 (0)40-4113-2588 Fax: +49 (0)40-4113-2595 www.newsaktuell.de www.presseportal.de www.newsaktuell.de/blog www.twitter.com/newsaktuell www.youtube.com/newsaktuell www.facebook.com/pages/newsaktuell/152372075544 www.friendfeed.com/newsaktuell -- Registergericht: Hamburg, Registernummer: HRB 42 738 Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE118617411 Vertretungsberechtigte Personen: Carl-Eduard Meyer (Geschäftsführer), Frank Stadthoewer (Geschäftsführer) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mac OS 10.5.5: mvn release:prepare fails with Exec format error
Hello, if i run the release:prepare goal on Mac OS 10.5.5 maven aborts with the following error message. is this a bug or a case of misconfiguration? What can i do. Please help! Regards Marcus mvn -e -DdryRun=true release:prepare own maven starter + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building devel-tools [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Resuming release from phase 'run-preparation-goals' [INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones [INFO] Executing goals 'clean verify'... [INFO] Executing: mvn clean verify --no-plugin-updates -P development,sonar,sonar Java: UNIXProcess:forkAndExec: exec failed: Exec format error [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Maven execution failed, exit code: '-1' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution failed, exit code: '-1' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:324) 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.MojoExecutionException: Maven execution failed, exit code: '-1' at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:140) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed, exit code: '-1' at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42) at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.simulate(RunPrepareGoalsPhase.java:54) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:190) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:131) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:94) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:136) ... 18 more Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution failed, exit code: '-1' at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:108) at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:126) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59) ... 24 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Oct 08 10:12:38 CEST 2008 [INFO] Final Memory: 6M/11M [INFO]
Re: Mac OS 10.5.5: mvn release:prepare fails with Exec format error
) at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59) ... 24 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Oct 08 10:12:38 CEST 2008 [INFO] Final Memory: 6M/11M [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcus Linke Softwareentwicklung, IT news aktuell GmbH - Ein Unternehmen der dpa-Firmengruppe Mittelweg 144, 20148 Hamburg Tel: +49(0)40-4113-2588 Fax: +49(0)40-4113-2595 [EMAIL PROTECTED] www.newsaktuell.de Registergericht: Hamburg, Registernummer: HRB 42 738 Umsatzsteuer-Identifikationsnummer gemäß § 27 a Umsatzsteuergesetz: DE118617411 Vertretungsberechtigte Personen: Carl-Eduard Meyer (Geschäftsführer), Frank Stadthoewer (Geschäftsführer) +++ news aktuell - Ihre Nachricht kommt an +++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
