Wim,

Do you have a new patch to apply to clearcase provider before the release?
I'll release it today.

Emmanuel

Wim Deblauwe a écrit :
None, it is the calling of 'cleartool ci' that fails. It's strange that you say that the checkin seems to have proceeded.

2005/12/7, Dandeneau, David J. (LNG-DAY) < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    What commands to you run after the checkin? That checkResult command
    is the one that is failing for me.

    Thanks,

    Dave

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto:[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>]
    *Sent:* Wednesday, December 07, 2005 2:27 AM
    *To:* scm-dev@maven.apache.org <mailto:scm-dev@maven.apache.org>
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    Hmm... I don't see the problem really.

    It seems that clearcase gives this error:

    cleartool: Error: No branch of element is checked out to view
    
"LNGDAYD-4130684:D:\view_storage\statemanager_int\dandendj_statemanager_int.vws".

    cleartool: Error: Unable to find checked out version for
    "D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2\pom.xml".

    any idea why this is?

    regards,

    Wim

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    That nullpointer was actually a different error then the first one.
    I think that when it dies it leaves the release.properties in a bad
    state.

    I deleted the release.properties and ran it again and I got this:

    [INFO] Transforming sm2 to snapshot

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    [DEBUG] executing edit command...

    [INFO] Checking out file:
    D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2\pom.

    xml

    [DEBUG] Checked out
    "D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2\pom.xml"

    from version "\main\statemanager_INT\11".

    [DEBUG]   Attached activities:

    [INFO] Checking in development POMs

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    [DEBUG] Loading "retools_comps\sm\sm2\pom.xml" (4972 bytes).

    [DEBUG] Checked in
    "D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2\pom.xml" v

    ersion "\main\statemanager_INT\12".

    [DEBUG]   Attached activities:

    Provider message:

    The cleartool command failed.

    Command output:

    cleartool: Error: No branch of element is checked out to view
    "LNGDAYD-4130684:D:\view_sto

    rage\statemanager_int\dandendj_statemanager_int.vws".

    cleartool: Error: Unable to find checked out version for
    "D:\snapshots\dandendj_statemanag

    er_int\retools_comps\sm\sm2\pom.xml".

    [INFO]
    ----------------------------------------------------------------------------

    [ERROR] BUILD ERROR

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] An error is occurred in the checkin process.

    Embedded error: Error!

    [INFO]
    ----------------------------------------------------------------------------

    [DEBUG] Trace

    org.apache.maven.lifecycle.LifecycleExecutionException: An error is
    occurred in the checki

    n process.

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecyc

    leExecutor.java:544)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(Defau

    ltLifecycleExecutor.java:482)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycl

    eExecutor.java:452)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailure

    s(DefaultLifecycleExecutor.java:301)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Default

    LifecycleExecutor.java:214)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExe

    cutor.java:137)

            at
    org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)

            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)

            at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at
    
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at
    
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja

    va:25)

            at java.lang.reflect.Method.invoke(Method.java:585)

            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: An error
    is occurred in the che

    ckin process.

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.checkIn(PrepareReleaseMojo.

    java:1305)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.checkInNextSnapshot(Prepare

    ReleaseMojo.java:1283)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.

    java:297)

            at
    
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.j

    ava:399)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecyc

    leExecutor.java:519)

            ... 16 more

    Caused by: org.apache.maven.scm.ScmException: Error!

            at
    
org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper.java:1

    47)

            at
    
org.apache.maven.plugins.release.helpers.ScmHelper.checkin(ScmHelper.java:239)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.checkIn(PrepareReleaseMojo.

    java:1301)

            ... 20 more

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] Total time: 43 seconds

    [INFO] Finished at: Tue Dec 06 14:59:32 EST 2005

    [INFO] Final Memory: 3M/6M

    [INFO]
    ----------------------------------------------------------------------------

    The line it fails on is the checkResult() line. Also, it appears
    that the file was successfully checked in.

            File[] files = (File[])pomFiles.toArray( new
    File[pomFiles.size()] );

            ScmRepository repository = getScmRepository();

            CheckInScmResult result =
    getScmManager().getProviderByRepository( repository )

                .checkIn( repository, new ScmFileSet( new File(
    workingDirectory ), files ), tag, message );

            *checkResult( result );*

    Thanks,

    Dave

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> ]
    *Sent:* Tuesday, December 06, 2005 2:57 PM


    *To:* Dandeneau, David J. (LNG-DAY)
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    whoops, a nullpointer :(

    I don't have the code here at home, I will have to check tomorrow.
    You are sure you are using the latest code from svn for the release
    plugin?

    regards,

    Wim

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    Here is the output with the –X option. I just used the part that I
    thought you might be interested in. Let me know if you need more.

    Thanks,

    Dave:

    [DEBUG] maven-scm-provider-clearcase: using locally installed snapshot

    [DEBUG] Configuring mojo
    'org.apache.maven.plugins:maven-release-plugin:2.0-beta-4-SNAPSHO

    T:prepare' -->

    [DEBUG]   (f) basedir =
    D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2

    [DEBUG]   (f) generateReleasePoms = false

    [DEBUG]   (f) interactive = true

    [DEBUG]   (f) localRepository = [local] -> file://D:\Documents and
    Settings\dandendj\.m2\r

    epository

    [DEBUG]   (f) reactorProjects =
    [EMAIL PROTECTED]

    [DEBUG]   (f) resume = true

    [DEBUG]   (f) settings = [EMAIL PROTECTED]

    [DEBUG]   (f) urlScm =
    scm:clearcase:\\lngdayd-4130684\view_storage\statemanager_int\dande

    ndj_statemanager_int.vws\config_spec

    [DEBUG]   (f) useEditMode = false

    [DEBUG] -- end configuration --

    [INFO] [release:prepare]

    [INFO] Checking in development POMs

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    [INFO]
    ----------------------------------------------------------------------------

    [ERROR] FATAL ERROR

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] null

    [INFO]
    ----------------------------------------------------------------------------

    [DEBUG] Trace

    java.lang.NullPointerException

            at
    
org.apache.maven.plugins.release.helpers.ScmHelper.checkin(ScmHelper.java:233)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.checkIn(PrepareReleaseMojo.

    java:1301)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.checkInNextSnapshot(Prepare

    ReleaseMojo.java:1283)

            at
    
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.

    java:297)

            at
    
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.j

    ava:399)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecyc

    leExecutor.java:519)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(Defau

    ltLifecycleExecutor.java:482)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycl

    eExecutor.java:452)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailure

    s(DefaultLifecycleExecutor.java:301)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Default

    LifecycleExecutor.java:214)

            at
    
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExe

    cutor.java:137)

            at
    org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)

            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)

            at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at
    
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

            at
    
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja

    va:25)

            at java.lang.reflect.Method.invoke(Method.java:585)

            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)

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] Total time: 4 seconds

    [INFO] Finished at: Tue Dec 06 14:40:38 EST 2005

    [INFO] Final Memory: 3M/6M

    [INFO]
    ----------------------------------------------------------------------------

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> ]
    *Sent:* Tuesday, December 06, 2005 2:40 PM


    *To:* Dandeneau, David J. (LNG-DAY)
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    I don't use streams, I use base ClearCase. Maybe that might be a
    difference. Can you re-run with the -X option?

    regards,

    Wim

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    I am a bit further now. Thanks for being patient with me since I am
    new to mavens scm plugins. Everything appears to work fine until it
    tries to checkin the pom.xml. Here is the output.

    [INFO] Checking in modified POMs

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    [INFO] Tagging release with the label sm2-0.8.

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    [INFO] What is the new development version for "reedelsevier:sm2"?
    [0.9-SNAPSHOT]

    [INFO] Transforming sm2 to snapshot

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    [INFO] Checking out file:
    D:\snapshots\dandendj_statemanager_int\retools_comps\sm\sm2\pom

    xml

    [INFO] Checking in development POMs

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\conf

    g_spec

    Provider message:

    The cleartool command failed.

    Command output:

    cleartool: Error: No branch of element is checked out to view
    "LNGDAYD-4130684:D:\view_st

    rage\statemanager_int\dandendj_statemanager_int.vws".

    cleartool: Error: Unable to find checked out version for
    "D:\snapshots\dandendj_statemana

    er_int\retools_comps\sm\sm2\pom.xml".

    [INFO]
    ----------------------------------------------------------------------------

    [ERROR] BUILD ERROR

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] An error is occurred in the checkin process.

    Embedded error: Error!

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] For more information, run Maven with the -e switch

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] Total time: 35 seconds

    [INFO] Finished at: Tue Dec 06 14:27:10 EST 2005

    [INFO] Final Memory: 3M/7M

    [INFO]
    ----------------------------------------------------------------------------

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> ]
    *Sent:* Tuesday, December 06, 2005 2:10 PM


    *To:* Dandeneau, David J. (LNG-DAY)
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    The error means that the version you have specified in the pom.xml
    does not contain 'SNAPSHOT' in the version. For instance, while you
    are working on version 1.0, you should put 1.0-SNAPSHOT as version.
    When you are ready to release, call 'mvn release:prepare', then
    maven will ask for the label, the release version (will default to
    1.0) and the pom.xml will be automatically updated to the correct
    version.

    regards,

    Wim

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    I should probably also mention that I am using clearcase UCM setup
    for single stream development and that the view that I have pointed
    to is a snapshot view. Here is the complete output:

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] Building StateManager

    [INFO]    task-segment: [release:prepare] (aggregator-style)

    [INFO]
    ----------------------------------------------------------------------------

    Downloading:
    
http://mirrors.sunsite.dk/mirrors/maven2//websphere/runtime/5.1.1.2/runtime-5
    
<http://mirrors.sunsite.dk/mirrors/maven2/websphere/runtime/5.1.1.2/runtime-5>

    .1.1.2.pom

    [WARNING] Unable to get resource from repository central
    (http://repo1.maven.org/maven2)

    Downloading:
    http://mirrors.sunsite.dk/mirrors/maven2//oracle/jdbc/1.4/jdbc-1.4.pom
    <http://mirrors.sunsite.dk/mirrors/maven2/oracle/jdbc/1.4/jdbc-1.4.pom>

    [WARNING] Unable to get resource from repository central
    (http://repo1.maven.org/maven2)

    Downloading:
    
http://mirrors.sunsite.dk/mirrors/maven2//websphere/j2ee/5.1.1.2/j2ee-5.1.1.2
    
<http://mirrors.sunsite.dk/mirrors/maven2/websphere/j2ee/5.1.1.2/j2ee-5.1.1.2>

    .pom

    [WARNING] Unable to get resource from repository central
    (http://repo1.maven.org/maven2)

    Downloading:
    
http://mirrors.sunsite.dk/mirrors/maven2//websphere/ivjejb35/5.1.1.2/ivjejb35
    
<http://mirrors.sunsite.dk/mirrors/maven2/websphere/ivjejb35/5.1.1.2/ivjejb35>

    -5.1.1.2.pom

    [WARNING] Unable to get resource from repository central
    (http://repo1.maven.org/maven2)

    Downloading:
    
http://mirrors.sunsite.dk/mirrors/maven2//websphere/servletevent/5.1.1.2/serv
    
<http://mirrors.sunsite.dk/mirrors/maven2/websphere/servletevent/5.1.1.2/serv>

    letevent-5.1.1.2.pom

    [WARNING] Unable to get resource from repository central
    (http://repo1.maven.org/maven2)

    [INFO] [release:prepare]

    [INFO] Verifying there are no local modifications ...

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    spec =
    
\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\confi

    g_spec

    [ERROR] executing status command...

    [INFO] Checking lineage for snapshots ...

    [INFO] Checking dependencies for snapshots ...

    [INFO] Checking plugins for snapshots ...

    [INFO]
    ----------------------------------------------------------------------------

    [ERROR] BUILD ERROR

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] The project reedelsevier:sm2 isn't a snapshot (1.0-alpha-1).

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] For more information, run Maven with the -e switch

    [INFO]
    ----------------------------------------------------------------------------

    [INFO] Total time: 5 seconds

    [INFO] Finished at: Tue Dec 06 13:56:31 EST 2005

    [INFO] Final Memory: 3M/7M

    [INFO]
    ----------------------------------------------------------------------------

    Thanks for the help,

    Dave Dandeneau

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> ]
    *Sent:* Tuesday, December 06, 2005 1:53 PM
    *To:* Dandeneau, David J. (LNG-DAY)
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    best is to get maven-release-plugin and maven-scm from svn. Then run
    'mvn -Dmaven.test.skip=true install' and then try again. You should
    not include any dependencies in your pom.xml, that is not needed.

    hth,

    Wim

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    I am getting this when I do mvn release:prepare:

    Embedded error: Can't load the scm provider.

    No such provider: 'clearcase'.

    I am not sure how you force it to use the latest greatest plugins. I
    installed them, and I changed my pom.xml to have:

      <scm>

<connection>scm:clearcase:\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\config_spec</connection>


<developerConnection>scm:clearcase:\\lngdayd-4130684\view_storage\statemanager_int\dandendj_statemanager_int.vws\config_spec</developerConnection>


      </scm>

    And

      <!-- SCM plugins -->

            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

</plugin>
            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm-api</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

</plugin>
            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm-providers</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

            </plugin>

            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm-managers</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

            </plugin>

            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm-client</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

            </plugin>

            <plugin>

               <groupId>org.apache.maven.scm</groupId>

               <artifactId>maven-scm-provider-clearcase</artifactId>

               <version>1.0-beta-2-SNAPSHOT</version>

</plugin>
    I don't think that it is using the latest though. I did run a mvn
    scm:update and that seemed to work (well I didn't get an error). Do
    I need to use a different version of release too?

    Thanks,

    Dave

    ------------------------------------------------------------------------

    *From:* Wim Deblauwe [mailto: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> ]
    *Sent:* Tuesday, December 06, 2005 9:29 AM
    *To:* Dandeneau, David J. (LNG-DAY)
    *Subject:* Re: [vote] Release SCM 1.0-beta-2

    2005/12/6, Dandeneau, David J. (LNG-DAY) <
    [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>:

    Maven-release-plugin.

    Thanks,

    dave

    For the release plugin only the release:prepare works. First declare
    that you use clearcase in your pom.xml:

    <scm>
<connection>scm:clearcase:\\myserver\clearcase\configspecs\my_configspec.txt</connection> <developerConnection>scm:clearcase:\\myserver\clearcase\configspecs\my_configspec.txt</developerConnection>

      </scm>

    Then try 'mvn release:prepare' and see how it goes.

    regards,

    Wim
    PS: I don't know if you need to provide <developerConnection/> if it
    is the same as <connection/>, might be that you don't have to, I'm
    not sure.



Reply via email to