Maven 2.x Release Plugin

release:prepare fails with Starteam 2006

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-6
  • Fix Version/s: None
  • Component/s: prepare
  • Labels:
    None
  • Environment:
    windows xp, starteam 2006
  • Number of attachments :
    0

Description

when performing release:prepare and issuing the command stcmd, it fails to checkout/checkin, complaining about "Unknown status".

It does not happen with stcmd shipping with Starteam 2005 R2.

It happens only with Starteam 2006 stcmd.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

Can you paste the output stcmd line that generate an "Unknown Status"? I think you can get it by running mvn with -X

Show
Emmanuel Venisse added a comment - Can you paste the output stcmd line that generate an "Unknown Status"? I think you can get it by running mvn with -X
Hide
Permalink
Giovanni Pedone added a comment -

The problem arises when the release:prepare tries to checkin the modified pom. Once again, it does NOT happen with stcmd Starteam 2005.

[INFO] Checking in modified POMs...
[WARNING] Your scm URL use a deprecated format. The new format is :[username[:password]@]hostname:port:/projectName/[viewName/][folderHiearchy/]
[INFO] Working directory: D:\gpedone\Documenti\Projects\PostePerNoi\webcontainer
[INFO] Command line: stcmd ci -x -nologo -stop -p ant@192.168.116.27:49201/epv3_webapps/webcontainer -fp D:/gpedone/Documenti/Projects/PostePerNoi/webcontainer
-r "[maven-release-plugin] prepare release webcontainer-1.2" pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The starteam command failed.
Command output:
Error occurred:
Cannot validate check-in operation for a file with Unknown status. Please check out the file first or use force check-in, if you are confident of your changes.

Show
Giovanni Pedone added a comment - The problem arises when the release:prepare tries to checkin the modified pom. Once again, it does NOT happen with stcmd Starteam 2005. [INFO] Checking in modified POMs... [WARNING] Your scm URL use a deprecated format. The new format is :[username [:password] @]hostname:port:/projectName/ [viewName/] [folderHiearchy/] [INFO] Working directory: D:\gpedone\Documenti\Projects\PostePerNoi\webcontainer [INFO] Command line: stcmd ci -x -nologo -stop -p ant@192.168.116.27:49201/epv3_webapps/webcontainer -fp D:/gpedone/Documenti/Projects/PostePerNoi/webcontainer -r " [maven-release-plugin] prepare release webcontainer-1.2" pom.xml [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to commit files Provider message: The starteam command failed. Command output: Error occurred: Cannot validate check-in operation for a file with Unknown status. Please check out the file first or use force check-in, if you are confident of your changes.
Hide
Permalink
Dan Tran added a comment -

are you able to execute the same command line with additional password argument ( see stdcmd syntax for detail? )

Show
Dan Tran added a comment - are you able to execute the same command line with additional password argument ( see stdcmd syntax for detail? )
Hide
Permalink
Giovanni Pedone added a comment -

Dan, what do you mean ? the password is not the issue, it works just fine.
By the way, I won't be able to modify any of the stcmd commmand line arguments when using thru the release:prepare plugin

Show
Giovanni Pedone added a comment - Dan, what do you mean ? the password is not the issue, it works just fine. By the way, I won't be able to modify any of the stcmd commmand line arguments when using thru the release:prepare plugin
Hide
Permalink
Dan Tran added a comment -

I just want to make sure you can run the stdcmd line outside of release:prepare scope, and use it to trouble shoot the problem.

More likely, starteam 2006 may have changed some syntax.

Also please use starteam gui interface to find out why you to be checked file has a "unknown status"

Show
Dan Tran added a comment - I just want to make sure you can run the stdcmd line outside of release:prepare scope, and use it to trouble shoot the problem. More likely, starteam 2006 may have changed some syntax. Also please use starteam gui interface to find out why you to be checked file has a "unknown status"
Hide
Permalink
Fábio Lima Santos added a comment -

On StartTeam 2006, using the option "-o" on the command line (as the example bellow) we managed to manually checkin the file.

stcmd ci -x -nologo -stop -p guest@foo:49213/Maven/1.2/project -fp D:/temp/1.2/project -r "[maven-release-plugin] prepare release foo-1.2.0" -eol on -o pom.xml

We also have to insert manually the view identifier in order to upload the file to the correct branch.

It has been a while this issue is opened. Are there any workarounds on the way?

Show
Fábio Lima Santos added a comment - On StartTeam 2006, using the option "-o" on the command line (as the example bellow) we managed to manually checkin the file. stcmd ci -x -nologo -stop -p guest@foo:49213/Maven/1.2/project -fp D:/temp/1.2/project -r " [maven-release-plugin] prepare release foo-1.2.0" -eol on -o pom.xml We also have to insert manually the view identifier in order to upload the file to the correct branch. It has been a while this issue is opened. Are there any workarounds on the way?

People

  • Assignee:
    Unassigned
    Reporter:
    Giovanni Pedone
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: