Re: Strange behaviour with StarTeam
Olivier I have extracted maven-scm-provider-starteam-1.1-SNAPSHOT.jar from continuum-20080102.12.war and placed it in my directory C:\continuum-1.1\apps\continuum\webapp\WEB-INF\lib, and renamed the older version of the file. However, after doing some more builds, I regret that the same errors are still occurring. -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14578411.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Strange behaviour with StarTeam
Dan I'm a newcomer to everything Java-flavoured, and I don't yet have enough confidence in my Java coding abilities to attempt to patch the StarTeam provider code. I'm a bit puzzled by your comment about using Continuum to do the Maven release: I don't use this option, primarily because I don't understand what it does! -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p1411.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Strange behaviour with StarTeam
looks like you stack trace show NPE At
Caused by: java.lang.NullPointerException
at
org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommand.executeChangeLogCommand(StarteamChangeLogCommand.java:57)
and the exception shows this code
if ( branch != null || StringUtils.isNotEmpty( branch.getName() ) )
{
this.getLogger().warn( "This provider doesn't support
changelog with on a given branch." );
}
this code will surely throw NPE when branch is null. Perhaps you can
fix up this code, build the starteam provider, and patch directly
to your continuum 1.1 and tell us the result?
I also notice you use continuum to do the maven release, perhaps you
should not use this feature until thing settled.
-D
-D
On Dec 30, 2007 11:38 PM, Ken Turner <[EMAIL PROTECTED]> wrote:
>
> Thanks for the suggestion, Dan, but unfortunately none of my projects uses
> the SCM Credentials Cache option.
> --
> View this message in context:
> http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14555090.html
>
> Sent from the Continuum - Users mailing list archive at Nabble.com.
>
>
Re: Strange behaviour with StarTeam
Thanks for the suggestion, Dan, but unfortunately none of my projects uses the SCM Credentials Cache option. -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14555090.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Strange behaviour with StarTeam
this may be related to http://jira.codehaus.org/browse/CONTINUUM-1521 -D On Dec 28, 2007 7:38 AM, Ken Turner <[EMAIL PROTECTED]> wrote: > > http://www.nabble.com/file/p14527241/continuum.log continuum.log > > The attached log from Continuum 1.1 represents three consecutive builds of > exactly the same job. The first one terminates successfully at message ID > 244653; the second one fails during StarTeam checkout at message 293524, > and the third one succeeds at message 438060. > > All my projects appear to exhibit a similar behaviour, with an alternating > fail/success pattern. > > Does anybody know what's going on here? > -- > View this message in context: > http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14527241.html > Sent from the Continuum - Users mailing list archive at Nabble.com. > >
Strange behaviour with StarTeam
http://www.nabble.com/file/p14527241/continuum.log continuum.log The attached log from Continuum 1.1 represents three consecutive builds of exactly the same job. The first one terminates successfully at message ID 244653; the second one fails during StarTeam checkout at message 293524, and the third one succeeds at message 438060. All my projects appear to exhibit a similar behaviour, with an alternating fail/success pattern. Does anybody know what's going on here? -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14527241.html Sent from the Continuum - Users mailing list archive at Nabble.com.
