[Anthill-pro] Stamp Context

Mon Jun 9 10:28:12 CDT 2008

Here is the error I get:

 2008-06-09 10:24:47,522 ERROR 134347 2 - Exception:
 java.security.PrivilegedActionException: org.apache.bsf.BSFException:
The application script threw an exception: java.lang.ClassCastException:
Cannot cast com.urbancode.vcsdriver3.ChangeLog to
com.urbancode.vcsdriver3.ChangeSet [] BSF info: noFile at line: 0
column: columnNo
  at java.security.AccessController.doPrivileged(Native Method)
  at org.apache.bsf.BSFManager.eval(BSFManager.java:442)
  at
com.urbancode.anthill3.runtime.scripting.ScriptEvaluator.doEvaluate(Scri
ptEvaluator.java:247)
  at
com.urbancode.anthill3.runtime.scripting.ScriptEvaluator.evaluate(Script
Evaluator.java:106)
  at
com.urbancode.anthill3.runtime.scripting.ScriptEvaluator.evaluate(Script
Evaluator.java:97)
  at
com.urbancode.anthill3.step.stamp.StampResolver.doResolve(StampResolver.
java:75)
  at
com.urbancode.anthill3.step.stamp.StampResolver.resolve(StampResolver.ja
va:59)
  at
com.urbancode.anthill3.domain.profile.NewStampGenerator.generate(NewStam
pGenerator.java:80)
  at
com.urbancode.anthill3.step.stamp.StampStep.perform(StampStep.java:97)
  at
com.urbancode.anthill3.services.jobs.StepExecutor.execute(StepExecutor.j
ava:279)
  at
com.urbancode.anthill3.services.jobs.StepExecutor.execute(StepExecutor.j
ava:352)
  at
com.urbancode.anthill3.services.jobs.SimpleAgentJobDelegate.perform(Simp
leAgentJobDelegate.java:213)
  at com.urbancode.anthill3.services.jobs.Job.run(Job.java:156)
  at
com.urbancode.commons.util.ThreadPool$WorkerThread.run(ThreadPool.java:2
08)
 Caused by: org.apache.bsf.BSFException: The application script threw an
exception: java.lang.ClassCastException: Cannot cast
com.urbancode.vcsdriver3.ChangeLog to com.urbancode.vcsdriver3.ChangeSet
[] BSF info: noFile at line: 0 column: columnNo
  at
com.urbancode.bsh.BeanShellBSFEngine.eval(BeanShellBSFEngine.java:209)
  at org.apache.bsf.BSFManager$5.run(BSFManager.java:445)  

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko,
Curtis
Sent: Monday, June 09, 2008 9:32 AM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Stamp Context

Can we return to this and get some Urbancode follow up? I'm on 3.4.11
but am using the script from the 3.4 documentation on the website
(different than what I have). When I use the stamp context script I get
a null passed in. Any thoughts?

===
-Curt
W: 860.702.9059
M: 860.881.2050

-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of emerson
cargnin
Sent: Thursday, May 29, 2008 12:54 PM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Stamp Context

I'm on 3.5 and I can't get this to work either.

The pdf documentation show to use ${stampContext:revision}, it should
show instead how to use the only pre-defined property: "changeset", like

${+property:ci_version}-r${stampContext:changeset}

regards
emerson
On 29/05/2008, Yanko, Curtis <curt_yanko at uhc.com> wrote:
>
> So does this only work in 3.5?
>
> ===
> -Curt
> W: 860.702.9059
> M: 860.881.2050
>
> ________________________________
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko, 
> Curtis
> Sent: Wednesday, May 28, 2008 12:30 PM
> To: AnthillPro user and support list.
> Subject: RE: [Anthill-pro] Stamp Context
>
>
> Well, it doesn't. I think it is because I'm on 3.4.11 still and I get 
> a casting exception. Not to mention that your sample script in the 
> documentation is missing a semi-colon on line 12. The script provided 
> with
> 3.4.11 returned a "0" as well so that wasn't doing it either.
>
> ===
> -Curt
> W: 860.702.9059
> M: 860.881.2050
>
> ________________________________
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve 
> Boone
> Sent: Wednesday, May 28, 2008 12:25 PM
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] Stamp Context
>
> Curt,
>
> That should work.
>
> Also, I believe the tail end of the stamping video (linked below) 
> covers exactly what you are looking to do.
>
> Deployments:
> http://downloads.urbancode.com /etm/ahp4/deployment.html
>
> Using Workflow Properties:
> http://downloads.urbancode.com /etm/wf-props/workflow-props.html
>
> How Anthill works with issue trackers:
> http://downloads.urbancode.com/etm/issue-tracking/issue -tracking.html
>
> Complex Project (rockbox)
> http://downloads.urbancode.com /etm/rockbox/rockbox.html
>
> Stamping How-To
> http://downloads.urbancode.com/etm/scripting/stamping/Stamping.html
>
> On Wed, May 28, 2008 at 11:54 AM, Yanko, Curtis <curt_yanko at uhc.com>
wrote:
> >
> >  I'm trying to get me head around this so we can use SVN revision 
> > number as our 'buildNum' in our stamping and tagging strategies.
> >
> > What I am confused about is if I set the advanced options in the 
> > stamping to call the script, how do I reference the value? What's 
> > the 'attributeName'? Do I need a property to go with it and a 'put'
> > in the code? Or do I just use
> >
> > 0.9.0.${stampContext:changeset}
> > ===
> > -Curt
> > W: 860.702.9059
> > M: 860.881.2050

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro

This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.