Discussion :

[jerrr]

Je suis toujours dans mes problèmes avec clearcase en maven.
J'ai modifié un tout petit peu le plugin maven-scm-provider-clearcase.
J'arrive à un point ou il me fait bien le checkout dans target/checkout
Le problème est que le pom.xml se trouve dans les sous répertoires ex : target/ckeckout/mavob/monprojet/modules/monmodule/pom.xml

Et j'ai l’erreur suivante :

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
[INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P maestro -DperformRelease=true
    [INFO] Scanning for projects...
    [INFO] ----------------------------------------------------------------------------
    [INFO] Building Maven Default Project
    [INFO]    task-segment: [deploy, site-deploy]
    [INFO] ----------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO] ------------------------------------------------------------------------
    [INFO] Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.
    [INFO] ------------------------------------------------------------------------
    [INFO] For more information, run Maven with the -e switch
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 1 second
    [INFO] Finished at: Fri Oct 20 18:15:48 CEST 2006
    [INFO] Final Memory: 4M/508M
    [INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error executing Maven: Maven execution failed, exit code: '1'
 
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing Maven: Maven execution failed, exit code: '1'
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:327)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:120)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:263)
        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: Error executing Maven: Maven execution failed, exit code: '1'
        at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:96)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        ... 16 more
Caused by: org.apache.maven.plugins.release.ReleaseExecutionException: Error executing Maven: Maven execution failed, exit code: '1'
        at org.apache.maven.plugins.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:411)
        at org.apache.maven.plugins.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:242)
        at org.apache.maven.plugins.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:234)
        at org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:91)
        ... 18 more
Caused by: org.apache.maven.plugins.release.exec.MavenExecutorException: Maven execution failed, exit code: '1'
        at org.apache.maven.plugins.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:97)
        at org.apache.maven.plugins.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:404)
        ... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6 seconds
[INFO] Finished at: Fri Oct 20 18:15:48 CEST 2006
[INFO] Final Memory: 4M/508M
[INFO] ------------------------------------------------------------------------

Car, il me semble qu'il recherche le pom.xml directement dans target/checkout

[jerrr]

Bon, dans un premier temps, je vais utiliser le paramètre pomFileName dans tous mes projets.

J'ai regardé le code de l'étape release:prepare, mais je ne maîtrise pas encore tout le cycle pour faire la modification. (dans la phase check-pom, ne fait pas appel au scm particulier, ici clearcase)

A suivre ...