Skip to search.

Breaking News Visit Yahoo! News for the latest.

×Close this window

pcgen_developers

The Yahoo! Groups Product Blog

Check it out!

Group Information

  • Members: 70
  • Category: Open Source
  • Founded: Apr 29, 2009
  • Language: English
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Message search is now enhanced, find messages faster. Take it for a spin.

Messages

Advanced
Messages Help
Messages 1014 - 1043 of 3334   Oldest  |  < Older  |  Newer >  |  Newest
Messages: Show Message Summaries Sort by Date ^  
#1014 From: hudson@...
Date: Thu Jul 1, 2010 9:06 am
Subject: Hudson build is back to normal : PCGen 5.16 Branch #27
hudson@...
Send Email Send Email
 
#1015 From: James Dempsey <jdempsey@...>
Date: Fri Jul 2, 2010 4:46 am
Subject: PCGen 5.16.3 RC1 is out
james_dempse...
Send Email Send Email
 
Hi,

I have built, tested and uploaded the 5.16.3 RC1 release (apart from the
Mac installer). Release notes are also available for download.

It is now active and ready for download, so over to Eddy and Eric.

Cheers,
James Dempsey
PCGen Code SB

#1016 From: Eddy Anthony <eddyba@...>
Date: Fri Jul 2, 2010 5:39 am
Subject: Re: PCGen 5.16.3 RC1 is out
mosat22
Send Email Send Email
 
James Dempsey scribed:

> Hi,
>
> I have built, tested and uploaded the 5.16.3 RC1 release (apart from the
> Mac installer). Release notes are also available for download.
>
> It is now active and ready for download, so over to Eddy and Eric.

The Mac build is now active and ready for download.
--
~ Eddy Anthony (MoSaT)
~ PCGen Data, Docs & Tracker Chimp
~ Outputsheet Tamarin & Mac build guru

#1017 From: James Dempsey <jdempsey@...>
Date: Sat Jul 3, 2010 3:47 am
Subject: Developers Meeting on IRC
james_dempse...
Send Email Send Email
 
Hi,

It has been ages since our last developers meeting and Tom suggested a
discussion on integration between our current projects would be useful.
It would also be a good opportunity for anyone looking at the code to
stop by and get a start to things, ask questions etc. Also if you have
any comments on 5.16.3 it would be a good opportunity (if we get the
meeting done next weekend that is)

So, when would people be able to get together? Taking EDT (UTC-4) as a
common comparison time, I can generally make 10pm to 12pm weekdays EDT
(same time slot as the BoD meetings) and can generally do any time
morning or evenings EDT on Friday and Saturday.

Mid next week I'll collate the available times and suggest a meeting
time. I'm presuming we will do the meeting on IRC as we have done in the
past.

Cheers,
James Dempsey
PCGen Code SB

#1018 From: Andrew Maitland <drew0500@...>
Date: Sat Jul 3, 2010 4:03 am
Subject: Re: Developers Meeting on IRC
Drew0500
Send Email Send Email
 
Hi,

As an observer I can attend Friday any time.


On 7/2/2010 8:47 PM, James Dempsey wrote:
--
Andrew Maitland (LegacyKing)
Admin Silverback - PCGen Board of Directors
Data Chimp, Docs Tamarin
Unique Title "Quick-Silverback Tracker Monkey"
Unique Title "The Torturer of PCGen"

#1019 From: Martijn Verburg <martijnverburg@...>
Date: Sat Jul 3, 2010 9:05 am
Subject: Re: Developers Meeting on IRC
karianna03
Send Email Send Email
 
At this stage I'm looking unlikely to make a meeting over the next 2 weeks (trying to get my first chapter of the book out), but since I'm not an active developer it's not 100% vital that I'm there.

K

On Sat, Jul 3, 2010 at 5:03 AM, Andrew Maitland <drew0500@...> wrote:
 

Hi,

As an observer I can attend Friday any time.



On 7/2/2010 8:47 PM, James Dempsey wrote:
Hi,

It has been ages since our last developers meeting and Tom suggested a 
discussion on integration between our current projects would be useful.  
It would also be a good opportunity for anyone looking at the code to 
stop by and get a start to things, ask questions etc. Also if you have 
any comments on 5.16.3 it would be a good opportunity (if we get the 
meeting done next weekend that is)

So, when would people be able to get together? Taking EDT (UTC-4) as a 
common comparison time, I can generally make 10pm to 12pm weekdays EDT 
(same time slot as the BoD meetings) and can generally do any time 
morning or evenings EDT on Friday and Saturday.

Mid next week I'll collate the available times and suggest a meeting 
time. I'm presuming we will do the meeting on IRC as we have done in the 
past.

Cheers,
James Dempsey
PCGen Code SB


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

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/pcgen_developers/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/pcgen_developers/join
    (Yahoo! ID required)

<*> To change settings via email:
    pcgen_developers-digest@yahoogroups.com 
    pcgen_developers-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    pcgen_developers-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/



--
Andrew Maitland (LegacyKing)
Admin Silverback - PCGen Board of Directors
Data Chimp, Docs Tamarin
Unique Title "Quick-Silverback Tracker Monkey"
Unique Title "The Torturer of PCGen"



#1020 From: Connor Petty <mistercpp2000@...>
Date: Sun Jul 4, 2010 10:48 pm
Subject: Re: Developers Meeting on IRC
mistercpp2000
Send Email Send Email
 
I can make 6pm-2am on Wednesday and Friday, 4pm-2am on Tuesday and Thursday and I'm available all of monday and the weekends.

On Fri, Jul 2, 2010 at 8:47 PM, James Dempsey <jdempsey@...> wrote:
 

Hi,

It has been ages since our last developers meeting and Tom suggested a
discussion on integration between our current projects would be useful.
It would also be a good opportunity for anyone looking at the code to
stop by and get a start to things, ask questions etc. Also if you have
any comments on 5.16.3 it would be a good opportunity (if we get the
meeting done next weekend that is)

So, when would people be able to get together? Taking EDT (UTC-4) as a
common comparison time, I can generally make 10pm to 12pm weekdays EDT
(same time slot as the BoD meetings) and can generally do any time
morning or evenings EDT on Friday and Saturday.

Mid next week I'll collate the available times and suggest a meeting
time. I'm presuming we will do the meeting on IRC as we have done in the
past.

Cheers,
James Dempsey
PCGen Code SB




--
Connor Petty

#1021 From: "thpr" <thpr@...>
Date: Mon Jul 5, 2010 2:45 am
Subject: Re: Developers Meeting on IRC
thpr
Send Email Send Email
 
I can also generally make 10-12 Eastern evenings or other times Fri or Sat
evenings if I get enough warning.  Fri/Sat morning is probably a challenge for
me at this point.

TP.

--- In pcgen_developers@yahoogroups.com, James Dempsey <jdempsey@...> wrote:
>
> Hi,
>
> It has been ages since our last developers meeting and Tom suggested a
> discussion on integration between our current projects would be useful.
> It would also be a good opportunity for anyone looking at the code to
> stop by and get a start to things, ask questions etc. Also if you have
> any comments on 5.16.3 it would be a good opportunity (if we get the
> meeting done next weekend that is)
>
> So, when would people be able to get together? Taking EDT (UTC-4) as a
> common comparison time, I can generally make 10pm to 12pm weekdays EDT
> (same time slot as the BoD meetings) and can generally do any time
> morning or evenings EDT on Friday and Saturday.
>
> Mid next week I'll collate the available times and suggest a meeting
> time. I'm presuming we will do the meeting on IRC as we have done in the
> past.
>
> Cheers,
> James Dempsey
> PCGen Code SB
>

#1022 From: James Dempsey <jdempsey@...>
Date: Tue Jul 6, 2010 8:33 am
Subject: Re: Re: Developers Meeting on IRC
james_dempse...
Send Email Send Email
 
Hi,

Thanks for the quick responses everyone.

Looks like 10PM EDT Friday 9 July 2010 for an hour or so might be the
most convenient for everyone. To see that in your time zone go to
http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=7&day=10&ho\
ur=2&min=0&sec=0

The meeting venue will be channel #pcgen on IRC <irc.freenode.net>. You
can join via the web at http://webchat.freenode.net/?channels=pcgen

Agenda:
0. Introductions
1. Sub-project updates
2. Strategy for integrating the various sub-projects
3. Timetable for the integration
4. Open forum

Cheers,
James Dempsey
PCGen Code SB

On 5/07/2010 12:45 PM thpr wrote
> I can also generally make 10-12 Eastern evenings or other times Fri or Sat
evenings if I get enough warning.  Fri/Sat morning is probably a challenge for
me at this point.
>
> TP.
>
> --- In pcgen_developers@yahoogroups.com, James Dempsey <jdempsey@...> wrote:
>
>> Hi,
>>
>> It has been ages since our last developers meeting and Tom suggested a
>> discussion on integration between our current projects would be useful.
>> It would also be a good opportunity for anyone looking at the code to
>> stop by and get a start to things, ask questions etc. Also if you have
>> any comments on 5.16.3 it would be a good opportunity (if we get the
>> meeting done next weekend that is)
>>
>> So, when would people be able to get together? Taking EDT (UTC-4) as a
>> common comparison time, I can generally make 10pm to 12pm weekdays EDT
>> (same time slot as the BoD meetings) and can generally do any time
>> morning or evenings EDT on Friday and Saturday.
>>
>> Mid next week I'll collate the available times and suggest a meeting
>> time. I'm presuming we will do the meeting on IRC as we have done in the
>> past.
>>
>> Cheers,
>> James Dempsey
>> PCGen Code SB
>>

#1023 From: Andrew Maitland <drew0500@...>
Date: Tue Jul 6, 2010 1:13 pm
Subject: New UI Discussion Screenshots up...
Drew0500
Send Email Send Email
 
Hi Folks,
 
John has delivered ahead of time on two new UI Screenshots.
 
I've uploaded the latest versions here:
 

 
--
Andrew

#1024 From: Martijn Verburg <martijnverburg@...>
Date: Wed Jul 7, 2010 10:01 am
Subject: Re: Export Control setting for SourceForge.net projects
karianna03
Send Email Send Email
 
Bump

On Wed, Jun 30, 2010 at 11:16 PM, Martijn Verburg
<martijnverburg@...> wrote:
> Hi Team,
>
> Can someone confirm which camp we lie in?  I'm not sure if our
> networking or install data from website code has any encryption
> elements.
>
> K
>
>
> ---------- Forwarded message ----------
> From: SourceForge.net Team <noreply@...>
> Date: Wed, Jun 30, 2010 at 11:13 PM
> Subject: Export Control setting for SourceForge.net projects
> To: martijnverburg@...
>
>
> Hello SourceForge project administrator,
>
> SourceForge has project settings to help you comply with regulations
> governing distribution of software to persons from certain countries
> (aka Export Controls).  We've had some recent questions about these
> settings, so have sent out this note to all administrators to make
> sure all projects have this information.
>
> By default, software downloads initiated by visitors from Sudan, North
> Korea, Syria, Iran and Cuba are blocked.
>
> A project administrator may disable this blocking if they conclude
> that their project is *not* subject to US export-related regulations
> or any prohibitions of applicable jurisdictions:
> 1. Project Admin -> Project Settings.
> 2. Find the "Export Control" section.
> 3. Tick the first radio button under "Export Control" and click "Update".
>
> We at SourceForge are committed to the ideals of free and open source
> software, including the principle of free exchange of information. Our
> approach to access control is intended to empower you and reward your
> continued trust.  We recognize, however, that our approach isn't the
> completely free access to everything for everyone that some would
> like.  As a US-based web site, SourceForge is committed to complying
> fully with US laws and regulations, including those affecting the
> distribution of software.  We will continue to work as diligently as
> possible to ensure that our legal compliance is coupled with the
> highest quality of service that we can offer to our diverse, global
> user base.
>
> Best regards,
>
> Daniel Hinojosa
> Sr. Manager, SourceForge.net Support
> sfnet_ops@...
>
> ----------------------------------------------------------------------
> SourceForge.net has made this mailing to you as a registered user of
> the SourceForge.net site to convey important information regarding
> your SourceForge.net account or your use of SourceForge.net services.
>
> We make a small number of directed mailings to registered users each
> year regarding their account or data, to help preserve the security of
> their account or prevent loss of data or service access.
>
> If you have concerns about this mailing please contact our Support
> team per: http://sourceforge.net/support
>

#1025 From: "Maredudd" <maredudd@...>
Date: Wed Jul 7, 2010 5:17 pm
Subject: PCG File Format Documentation
maredudd800
Send Email Send Email
 
Hi Folks!

The tracker linked below calls for adding to the current
docs an explanation of the PCG files format and how it
is parsed. I can understand why the developers would
need this but there really is no reason that a regular
user needs this info, especially as messing with the
PCG file is strongly discouraged.

https://sourceforge.net/tracker/?func=detail&aid=1411296&group_id=25576&atid=748\
235

My question is . . .

Is this info currently documented as part of the Code Docs?

If not, is this information something that the developers think
should be documented?

Maredudd
Doc 2nd

#1026 From: Martijn Verburg <martijnverburg@...>
Date: Wed Jul 7, 2010 5:58 pm
Subject: Re: PCG File Format Documentation
karianna03
Send Email Send Email
 
Hi all,

Perhaps this is a good candiate for an extensive piece of Javadoc?  Not sure how extensive the docs need to be.

K

On Wed, Jul 7, 2010 at 6:17 PM, Maredudd <maredudd@...> wrote:
 

Hi Folks!

The tracker linked below calls for adding to the current
docs an explanation of the PCG files format and how it
is parsed. I can understand why the developers would
need this but there really is no reason that a regular
user needs this info, especially as messing with the
PCG file is strongly discouraged.

https://sourceforge.net/tracker/?func=detail&aid=1411296&group_id=25576&atid=748235

My question is . . .

Is this info currently documented as part of the Code Docs?

If not, is this information something that the developers think
should be documented?

Maredudd
Doc 2nd



#1027 From: Tom Parker <thpr@...>
Date: Wed Jul 7, 2010 6:10 pm
Subject: Re: PCG File Format Documentation
thpr
Send Email Send Email
 
From an architecture perspective, this is not a strategic format, so I do not think this is a practical place to invest our resource.

TP.
--
Tom Parker
thpr@... and tppublic@...

--- On Wed, 7/7/10, Martijn Verburg <martijnverburg@...> wrote:

From: Martijn Verburg <martijnverburg@...>
Subject: Re: [pcgen_developers] PCG File Format Documentation
To: pcgen_developers@yahoogroups.com
Date: Wednesday, July 7, 2010, 1:58 PM



Hi all,

Perhaps this is a good candiate for an extensive piece of Javadoc?  Not sure how extensive the docs need to be.

K

On Wed, Jul 7, 2010 at 6:17 PM, Maredudd <maredudd@...> wrote:
 

Hi Folks!

The tracker linked below calls for adding to the current
docs an explanation of the PCG files format and how it
is parsed. I can understand why the developers would
need this but there really is no reason that a regular
user needs this info, especially as messing with the
PCG file is strongly discouraged.

https://sourceforge.net/tracker/?func=detail&aid=1411296&group_id=25576&atid=748235

My question is . . .

Is this info currently documented as part of the Code Docs?

If not, is this information something that the developers think
should be documented?

Maredudd
Doc 2nd



#1028 From: "thpr" <thpr@...>
Date: Wed Jul 7, 2010 9:33 pm
Subject: Re: Export Control setting for SourceForge.net projects
thpr
Send Email Send Email
 
I will not make any confirmation.  I'm not a lawyer, and for the half a dozen or
so countries for which this restricts access, while I regret they would be
restricted from using our SW, I'm not sticking my neck out without a letter from
a lawyer.

TP.

--- In pcgen_developers@yahoogroups.com, Martijn Verburg <martijnverburg@...>
wrote:
>
> Bump
>
> On Wed, Jun 30, 2010 at 11:16 PM, Martijn Verburg
> <martijnverburg@...> wrote:
> > Hi Team,
> >
> > Can someone confirm which camp we lie in?  I'm not sure if our
> > networking or install data from website code has any encryption
> > elements.
> >
> > K
> >
> >
> > ---------- Forwarded message ----------
> > From: SourceForge.net Team <noreply@...>
> > Date: Wed, Jun 30, 2010 at 11:13 PM
> > Subject: Export Control setting for SourceForge.net projects
> > To: martijnverburg@...
> >
> >
> > Hello SourceForge project administrator,
> >
> > SourceForge has project settings to help you comply with regulations
> > governing distribution of software to persons from certain countries
> > (aka Export Controls).  We've had some recent questions about these
> > settings, so have sent out this note to all administrators to make
> > sure all projects have this information.
> >
> > By default, software downloads initiated by visitors from Sudan, North
> > Korea, Syria, Iran and Cuba are blocked.
> >
> > A project administrator may disable this blocking if they conclude
> > that their project is *not* subject to US export-related regulations
> > or any prohibitions of applicable jurisdictions:
> > 1. Project Admin -> Project Settings.
> > 2. Find the "Export Control" section.
> > 3. Tick the first radio button under "Export Control" and click "Update".
> >
> > We at SourceForge are committed to the ideals of free and open source
> > software, including the principle of free exchange of information. Our
> > approach to access control is intended to empower you and reward your
> > continued trust.  We recognize, however, that our approach isn't the
> > completely free access to everything for everyone that some would
> > like.  As a US-based web site, SourceForge is committed to complying
> > fully with US laws and regulations, including those affecting the
> > distribution of software.  We will continue to work as diligently as
> > possible to ensure that our legal compliance is coupled with the
> > highest quality of service that we can offer to our diverse, global
> > user base.
> >
> > Best regards,
> >
> > Daniel Hinojosa
> > Sr. Manager, SourceForge.net Support
> > sfnet_ops@...
> >
> > ----------------------------------------------------------------------
> > SourceForge.net has made this mailing to you as a registered user of
> > the SourceForge.net site to convey important information regarding
> > your SourceForge.net account or your use of SourceForge.net services.
> >
> > We make a small number of directed mailings to registered users each
> > year regarding their account or data, to help preserve the security of
> > their account or prevent loss of data or service access.
> >
> > If you have concerns about this mailing please contact our Support
> > team per: http://sourceforge.net/support
> >
>

#1029 From: Andrew Maitland <drew0500@...>
Date: Thu Jul 8, 2010 8:39 am
Subject: Re: Re: Templating Engine [Freemarker Reply]
Drew0500
Send Email Send Email
 
Hi,

Bump for Stefan


On 6/18/2010 1:52 PM, Andrew Maitland wrote:
Hi,

Looks like everyone is in agreement.

Stefan - How do things look?


On 6/15/2010 7:07 PM, Tom Parker wrote:
For what it's worth, I'm good with the discussion so far and in using Freemarker.
I also agree with James that we should use as much of the current OUTPUT token infrastructure as possible... both for past consistency, for testing, and for ensuring that the output system is detached from the PlayerCharacter object (or facade) [don't want tight core/output linkage]
TP.
--
Tom Parker
thpr@... and tppublic@...
--- On Sun, 6/13/10, James Dempsey <jdempsey@...> wrote:
From: James Dempsey <jdempsey@...>
Subject: Re: [pcgen_developers] Re: Templating Engine [Freemarker Reply]
To: pcgen_developers@yahoogroups.com
Date: Sunday, June 13, 2010, 7:59 AM
Hi,
My concept of how this would work is quite different to
Connor's one :)
The aim would be to utilise the already built output system
and add a function that can be called from a template (output sheet)
to allow the existing output tags to be called. This would give us a
simple change-over and use our existing well tested output code
base.
So for example we might have
<@pcgen tag="NAME"/> or <@pcgen
tag="SPELLMEM.0.1.1.1.|NAME|"/>
Cheers,
James.
On 13/06/2010 9:45 PM Andrew Maitland wrote
Hi,
  I'm not a developer or coder, so pardon my ignorance
here, but what 
exactly is this "Bean" property of which you speak?
  Onto the second part, are you suggesting that the
Templating Engine 
should be developed in tandem with the UI work then as
opposed to 
being tested against the trunk sandbox?
  I understand option #2 sounds like being in the UI dev
sandbox would 
be a better idea, but how would option #1 work, would
we be able to 
develop that in the Trunk?
And playing the Kar devil's advocate, should we
attempt to develop two 
instances using the two methods outlined? I'd think
since we have 
limited Code Hours available, the best theory would be
best to pursue 
and focus solely on that.
  James - Oh, yeah, I got responses from all three
developers, one 
response had been diverted to the spam folder, in fact
it was the 
first reply within a few hours of my inquiry. They are
definitely in 
action and support mode.
    --
Andrew
------------------------------------------------------------------------
*From:* Connor Petty <mistercpp2000@...>
*To:* pcgen_developers@yahoogroups.com
*Sent:* Sun, June 13, 2010 1:19:34 AM
*Subject:* Re: [pcgen_developers] Re: Templating
Engine [Freemarker Reply]
I agree. After looking through the all the javadocs
and general 
documentation for both freemarker and velocity,
freemarker has a 
larger feature set. I will say though that velocity's
developer's 
documentation is far more straight forward than
freemarker's 
documentation. So I guess I'll switch my vote to
Freemarker instead :)
While looking investigating both templating engines
its come to my 
attention that we would need to decide the best way to
allow templates 
to access the character internals. The two options are
either 1. have 
specific keys that a template would use to access
aspects of a 
character, "race", "alignment", etc.. or 2. use the
character itself 
and allow the template to retrieve bean properties
from it.
Given the complexity of character information that the
templates will 
probably deal with I'm thinking that option 2 would be
better. If 
that's the case then it looks like a use for the
character facade. 
There are two problems, first is that the character
facade is still in 
development and second is that the character facade is
in the cdomui 
branch. And it might be a little late to say this but
I'm not so sure 
that making a new sandbox based on the trunk is the
best idea when 
trying to develop use of a new templating engine,
especially if it 
might involve recreating something already in
development.
On Sat, Jun 12, 2010 at 11:42 PM, James Dempsey <jdempsey@...
<mailto:jdempsey@...>>
wrote:
           Hi,
     I think it is pretty clear
that FreeMarker has the better feature
     set.
     My concern was that if we
encountered problems we would have hassles
     getting support. The very
swift response to Andrew's query makes
     me much
     more confident that we have a
support avenue if needed.
     So my vote is to go with the
latest stable version of FreeMarker
     (2.3.16)
     Cheers,
     James Dempsey
     PCGen Code SB
     On 11/06/2010 9:13 AM Andrew
Maitland wrote
     >
     >
     > Hi,
     >
     > (I'm hoping others will
chime in here)
     >
     > Oh, and a quick
correction, a portion of the email response is from
     > Daniel, the main reply
was sent from Jonathan Revusky.
     >
     > Based upon the fine
reading a few points jump out at me that
     leads me
     > to change my stance and
cast a vote for Freemarker:
     >
     > Error Reporting (Error
reporting is a MUST!)
     > Support for
internationalization (A future aspect we are going for)
     > Faster Performance based
upon comparisons (we like faster results)
     >
     > I'd encourage people to
check the blog as it's more detailed.
     >
     >
     >
     > On 6/10/2010 2:23 PM,
Andrew Maitland wrote:
     >> Hi Folks,
     >>
     >> I got a reply from
the Freemarker Admin - Daniel Dekany
     >>
     >> BEGIN FWD:
     >>
     >> A couple of years
ago, I wrote a response to a javaworld
     article that
     >> had made a
ridiculously superficial comparison between
     FreeMarker and
     >> Velocity and put it
on our group blog.
     >>
     >>
     http://freemarker.blogspot.com/2007/12/velocity-of-freemarker-looking-at-5.html
     >>
     >> Unless something
absolutely dramatic has happened since then in the
     >> Velocity camp of
which I am unaware, I don't think there is
     hardly any
     >> reasonable FreeMarker
versus Velocity debate to be had. If you
     just do
     >> some research using
google, in particular blog entries and
     such, you
     >> will see that there
has been (and I think there continues to
     be) quite
     >> a bit of migration
from Velocity to FreeMarker and none in the
     other
     >> direction. Even OSS
projects that are under the Apache
     umbrella, such
     >> as Struts 2 and
OfBiz, tend to use FreeMarker in preference to
     >> Velocity. (What does
that tell you?)
     >>
     >> What I am kind of
surprised about is that after all these
     years, that
     >> these are still
considered to be the two main contenders out there.
     >> But, if the
discussion is being framed as FreeMarker versus
     Velocity,
     >> I don't think there
is much of a discussion to be had. I
     honestly do
     >> not believe that
anybody has done a halfway diligent comparison and
     >> decided that Velocity
was the right choice.
     >>
     >> On Thu, Jun 10, 2010
at 10:35 PM, Daniel Dekany
     <ddekany@...
<mailto:ddekany%40freemail.hu>> wrote:
     >> > This is not
(only) my duty to answer, so I forward the
     question to the
     >> > developer list.
I hope it's not a problem. (So whoever
     answers, use
     >> > "reply to
all".)
     >> >
     >> > As of the
project activity, FreeMarker is maintained for sure
     (2.3.x).
     >> > OTOH it has a
working yet uncompleted 3.0 version in the
     trunk whose
     >> > development
stalled since a good while, and I can't tell if
     when it
     >> > will move again.
There is also a 2.4 branch now (mostly due
     to changes
     >> > needed for GAE
compatibility), which is much more backward
     compatible
     >> > with 2.3. I'm
quite certain that branch will go ahead if 3.0
     will not.
     >>
     >> I am actually
becoming more or less confident that 3.0 will go
     >> forward. I committed
some code for the first time in a nearly 2
     years
     >> the other day. :-)
     >>
     >> But, actually, in the
context of this conversation, where the
     question
     >> is being framed as
FreeMarker versus Velocity, I think it hardly
     >> matters. I am pretty
certain that the better choice would be
     >> FreeMarker even under
the worst case scenario that no further
     >> development ever
occurs on *any* version of FreeMarker. People
     can see
     >> my obvious biases and
take them into account, but it is my
     completely
     >> honest view that
going with Velocity is a decision that you
     would live
     >> to regret. Aside from
the fact that it is underpowered and
     >> underfeatured (unless
something really dramatic has happened in the
     >> last few years, and
if so, correct me) but even besides that, the
     >> features it does have
are implemented in a very sloppy, careless
     >> manner that is pretty
much bound to drive you crazy unless you are
     >> only using it in the
most trivial kind of way. Just look at some of
     >> the blog entries I
cite in the above-linked article.
     >>
     >> I hope that's
helpful.
     >>
     >> >
     >> > As of which
project to use, first of all you should consider
     where the
     >> > two projects
stand right now. Then you can guess how many active
     >> > development
Velocity needs to achieve the feature set or
     stability of
     >> > FreeMarker, or
if how much will it follow the direction of
     FreeMarker
     >> > anyway.
     >>
     >> Is there any serious
development on Velocity? I haven't looked
     at it
     >> for at least a couple
of years, but just observing the culture
     there,
     >> there would have had
to be some kind of revolution, it seems. Very
     >> unlikely. Now, as for
people maybe dismissing my comments I am
     fully
     >> aware that some
people think it is so terribly wrong for me to
     bash a
     >> competing product,
and will dismiss my comments as being sour
     grapes
     >> or whatever. But, you
can look into the issue. I think that if
     you do,
     >> you'll basically just
end up seeing that I'm just telling the
     truth. I
     >> really would prefer
for Velocity to be a serious competing product
     >> that is worthy of
respect. But... it is not... :-(
     >>
     >> JR
     >>
     >> >
     >> >
     >> > Thursday, June
10, 2010, 8:56:26 PM,
     amaitland@...
 
   <mailto:amaitland%40users.sourceforge.net>
wrote:
     >> >
     >> >> Message body
follows:
     >> >>
     >> >> Hi,
     >> >>
     >> >> My name is
Andrew, I'm with the PCGen Project. We are
     >> >> looking at
Velocity and Freemarker to see which Template
     >> >> Engine would
support our needs. However, the majority want
     >> >> to go with
an active development, and it seems Freemarker
     >> >> has stopped
major development. Do you have any plans to get
     >> >> more active
in the near future or should we use Velocity?
     >> >>
     >> >> --
     >> >>
     >> >>
     >> >
     >> > --
     >> > Best regards,
     >> > Daniel Dekany
     >> >
     >> >
_______________________________________________
     >> > FreeMarker-devel
mailing list
     >> > FreeMarker-devel@...
 
   <mailto:FreeMarker-devel%40lists.sourceforge.net>
     >> > https://lists.sourceforge.net/lists/listinfo/freemarker-devel
     >> >
     >>
     >>
     >> --
     >> Andrew Maitland
(LegacyKing)
     >> Admin Silverback -
PCGen Board of Directors
     >> Data Chimp, Docs
Tamarin
     >> Unique Title
"Quick-Silverback Tracker Monkey"
     >> Unique Title "The
Torturer of PCGen"
     >>
     >>
     >>
     >>
     >> On 6/10/2010 12:06
PM, Andrew Maitland wrote:
     >>> Hi,
     >>>
     >>> I just checked
out Freemarker SF site... they have activity, but
     >>> from what I've
sampled it's only support for the eclipse
     plugin, no
     >>> core work is
being done.
     >>>
     >>> I've sent a
message to all three developers and hopefully I'll
     get
     >>> at least a reply
from one of them soon.
     >>>
     >>> I've almost
finished porting Code over (Doing it piece meal is a
     >>> LONG process...
and even then I'm exceeding the message size :( )
     >>>
     >>>
     >>> On 6/10/2010 8:49
AM, Andrew Maitland wrote:
     >>>> Hi,
     >>>>
     >>>> I've gotten
the sandbox set up; I think Stefan decided to go
     with
     >>>> the active
Velocity. I can email the Freemarker guys to see
     what is
     >>>> up, but the
lack of activity on the main page would indicate
     to me
     >>>> that nothing
new has happened in a long while.
     >>>>
     >>>>
     >>>> On 6/8/2010
2:09 AM, karianna03 wrote:
     >>>>>
Freemarker was in an interesting state last time I checked
     with them, the 3 core
committers were somewhat at odds with
     eachother about the direction
Freemarker should go in, I'm not
     sure if that's been resolved.
     >>>>>
     >>>>> Stefan
should probably contact them directly again.
     >>>>>
     >>>>> K
     >>>>>
     >>>>> --- In pcgen_developers@yahoogroups.com
 
   <mailto:pcgen_developers%40yahoogroups.com>,
Connor Petty
     <mistercpp2000@...>
wrote:
     >>>>>
     >>>>>>
Actually from what I can tell Freemarker is still active,
     their sourceforge
     >>>>>> page
shows commits from only 15 hours ago.
     >>>>>>
     >>>>>> On
Mon, Jun 7, 2010 at 5:54 PM, Andrew Maitland
     <drew0500@...> wrote:
     >>>>>>
     >>>>>>
     >>>>>>>
Hi,
     >>>>>>>
     >>>>>>>
Yup, it's claim is that it's an improvement over
     Freemarker and
     >>>>>>>
incorporating Freemarker and Velocity stuff.
     >>>>>>>
     >>>>>>>
Freemarker has also been out of activity for quite a bit.
     Which means we
     >>>>>>>
should likely go with Velocity. The plugins seem very
     nice... one that let's
     >>>>>>>
you preview the output sounds really neat.
     >>>>>>>
     >>>>>>>
     >>>>>>>
     >>>>>>>
On 6/7/2010 3:02 PM, James Dempsey wrote:
     >>>>>>>
     >>>>>>>
Hi.
     >>>>>>>
     >>>>>>> I
think we can discount that one the last activity was in
     October 2008.
     >>>>>>>
     >>>>>>>
Cheers,
     >>>>>>>
James Dempsey
     >>>>>>>
PCGen Code SB
     >>>>>>>
     >>>>>>>
     >>>>>>>
On 8 June 2010 03:23, Andrew Maitland <drew0500@...>
wrote:
     >>>>>>>
     >>>>>>>
 
   >>>>>>>> And just
to throw a wrench into the works...
 
   >>>>>>>>
 
   >>>>>>>> http://code.google.com/p/zipscript/
 
   >>>>>>>>
 
   >>>>>>>> Cheers,
 
   >>>>>>>>
 
   >>>>>>>> --
 
   >>>>>>>> Andrew
 
   >>>>>>>>
 
   >>>>>>>>
------------------------------
 
   >>>>>>>> *From:*
Andrew Maitland <drew0500@...>
 
   >>>>>>>> *To:*
PCGen Developers <pcgen_developers@yahoogroups.com
 
   <mailto:pcgen_developers%40yahoogroups.com>>
 
   >>>>>>>> *Sent:*
Mon, June 7, 2010 10:14:08 AM
 
   >>>>>>>>
*Subject:* [pcgen_developers] Templating Engine
 
   >>>>>>>>
 
   >>>>>>>>
 
   >>>>>>>>
 
   >>>>>>>> Hi
Folks,
 
   >>>>>>>>
 
   >>>>>>>> I'd like
to jumpstart the discussion for a Templating
     Engine. Our two
 
   >>>>>>>> choices
are Freemarker and Velocity. Stefan is taking a
     look at both
 
   >>>>>>>> engines,
but the general feeling is we should go with the
     one that has
 
   >>>>>>>> active
development - which is Velocity. Velocity has a
     nice list of editor
 
   >>>>>>>> plugins
to support it as well :)
 
   >>>>>>>>
 
   >>>>>>>> http://wiki.apache.org/velocity/VelocityEditors
 
   >>>>>>>>
 
   >>>>>>>> Of Note
this has support for Eclipse Plugins, and
     IntelliJ IDEA two of our
 
   >>>>>>>> more
common IDEs on the Code Team.
 
   >>>>>>>>
 
   >>>>>>>>
Freemarker - http://freemarker.org/
 
   >>>>>>>>
 
   >>>>>>>> and a
list of editors (which has the same support, plus
     some like
 
   >>>>>>>>
Netbeans.)
 
   >>>>>>>> http://freemarker.org/editors.html
 
   >>>>>>>>
 
   >>>>>>>>
 
   >>>>>>>> This is
of benefit for the OS Team which does require
     Code Man Hours to
 
   >>>>>>>>
implement.
 
   >>>>>>>>
 
   >>>>>>>> Why is
this important -
 
   >>>>>>>> #1 - It
works towards reducing the number of CSHEETs we
     need to implement
 
   >>>>>>>> a simple
Color Scheme
 
   >>>>>>>> #2 - It
allows us a greater ability to customize the
     Character Sheets
 
   >>>>>>>> without
requiring the people to be fo, xml and xslt
     experts. (Currently it's
 
   >>>>>>>> trial by
fire for me).
 
   >>>>>>>> #3 -
We've had a publisher request a Custom Character
     Sheet for his
 
   >>>>>>>> system.
 
   >>>>>>>>
 
   >>>>>>>>
Discussion Point #1 - Which Engine do we want to use?
 
   >>>>>>>> (This is
important so we can begin)
 
   >>>>>>>>
 
   >>>>>>>>
Discussion Point #2 - What are our goals and does it
     require additional
 
   >>>>>>>> code work
beyond the engine?
 
   >>>>>>>>
 
   >>>>>>>> Outline -
We'll set up the Template Engine in it's own
     sandbox to test
 
   >>>>>>>> it's
capabilities, just like we are doing with the new UI
     implementation.
 
   >>>>>>>> Once it's
felt stable and solid, it'll be merged into the
     trunk.
 
   >>>>>>>>
 
   >>>>>>>> Any
comments?
 
   >>>>>>>>
 
   >>>>>>>> Cheers,
 
   >>>>>>>>
 
   >>>>>>>> --
 
   >>>>>>>> Andrew
 
   >>>>>>>>
-- Connor Petty
------------------------------------
Yahoo! Groups Links
    pcgen_developers-fullfeatured@yahoogroups.com
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/pcgen_developers/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/pcgen_developers/join
(Yahoo! ID required)
<*> To change settings via email:
pcgen_developers-digest@yahoogroups.com pcgen_developers-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
pcgen_developers-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

--
Andrew Maitland (LegacyKing)
Admin Silverback - PCGen Board of Directors
Data Chimp, Docs Tamarin
Unique Title "Quick-Silverback Tracker Monkey"
Unique Title "The Torturer of PCGen"

--
Andrew Maitland (LegacyKing)
Admin Silverback - PCGen Board of Directors
Data Chimp, Docs Tamarin
Unique Title "Quick-Silverback Tracker Monkey"
Unique Title "The Torturer of PCGen"

#1030 From: Stefan Radermacher <radermacher@...>
Date: Thu Jul 8, 2010 9:52 am
Subject: Change to INFOTEXT behavior
zaister
Send Email Send Email
 
I would like to change the behavior of the INFOTEXT tag for PCC files to
behave similar to the COPYRIGHT tag. i.e. so that more than one INFOTEXT
tag can be used. That would mean changing it from a StringKey toa
ListKey in the code.

Does anyone have a problem with that, or is that OK? Tom, whct do you think?

I would like to get this change (along with the proposed Pathfinder PCC
changes) into 5.16.3, if possible.

Regards,
Stefan.

#1031 From: Eric C Smith <maredudd@...>
Date: Thu Jul 8, 2010 11:34 am
Subject: Re: Re: Export Control setting for SourceForge.net projects
maredudd800
Send Email Send Email
 
Hi Folks!

I agree with Tom.

Unless we find an Export Control Expert who can write us a formal
letter, I believe we ARE subject to the Export Control laws.

Eric Smith


On Jul 7, 2010, at 5:33 PM, thpr wrote:

> I will not make any confirmation.  I'm not a lawyer, and for the
> half a dozen or so countries for which this restricts access, while
> I regret they would be restricted from using our SW, I'm not
> sticking my neck out without a letter from a lawyer.
>
> TP.
>
> --- In pcgen_developers@yahoogroups.com, Martijn Verburg
> <martijnverburg@...> wrote:
>>
>> Bump
>>
>> On Wed, Jun 30, 2010 at 11:16 PM, Martijn Verburg
>> <martijnverburg@...> wrote:
>>> Hi Team,
>>>
>>> Can someone confirm which camp we lie in? Â I'm not sure if our
>>> networking or install data from website code has any encryption
>>> elements.
>>>
>>> K
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: SourceForge.net Team <noreply@...>
>>> Date: Wed, Jun 30, 2010 at 11:13 PM
>>> Subject: Export Control setting for SourceForge.net projects
>>> To: martijnverburg@...
>>>
>>>
>>> Hello SourceForge project administrator,
>>>
>>> SourceForge has project settings to help you comply with regulations
>>> governing distribution of software to persons from certain countries
>>> (aka Export Controls). Â We've had some recent questions about these
>>> settings, so have sent out this note to all administrators to make
>>> sure all projects have this information.
>>>
>>> By default, software downloads initiated by visitors from Sudan,
>>> North
>>> Korea, Syria, Iran and Cuba are blocked.
>>>
>>> A project administrator may disable this blocking if they conclude
>>> that their project is *not* subject to US export-related regulations
>>> or any prohibitions of applicable jurisdictions:
>>> 1. Project Admin -> Project Settings.
>>> 2. Find the "Export Control" section.
>>> 3. Tick the first radio button under "Export Control" and click
>>> "Update".
>>>
>>> We at SourceForge are committed to the ideals of free and open
>>> source
>>> software, including the principle of free exchange of information.
>>> Our
>>> approach to access control is intended to empower you and reward
>>> your
>>> continued trust. Â We recognize, however, that our approach isn't
>>> the
>>> completely free access to everything for everyone that some would
>>> like. Â As a US-based web site, SourceForge is committed to
>>> complying
>>> fully with US laws and regulations, including those affecting the
>>> distribution of software. Â We will continue to work as diligently
>>> as
>>> possible to ensure that our legal compliance is coupled with the
>>> highest quality of service that we can offer to our diverse, global
>>> user base.
>>>
>>> Best regards,
>>>
>>> Daniel Hinojosa
>>> Sr. Manager, SourceForge.net Support
>>> sfnet_ops@...
>>>
>>> ----------------------------------------------------------------------
>>> SourceForge.net has made this mailing to you as a registered user of
>>> the SourceForge.net site to convey important information regarding
>>> your SourceForge.net account or your use of SourceForge.net
>>> services.
>>>
>>> We make a small number of directed mailings to registered users each
>>> year regarding their account or data, to help preserve the
>>> security of
>>> their account or prevent loss of data or service access.
>>>
>>> If you have concerns about this mailing please contact our Support
>>> team per: http://sourceforge.net/support
>>>
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

#1032 From: Martijn Verburg <martijnverburg@...>
Date: Thu Jul 8, 2010 11:49 am
Subject: Re: Re: Export Control setting for SourceForge.net projects
karianna03
Send Email Send Email
 
That's good enough for me, thanks both - K

On Thu, Jul 8, 2010 at 12:34 PM, Eric C Smith <maredudd@...> wrote:
 

Hi Folks!

I agree with Tom.

Unless we find an Export Control Expert who can write us a formal
letter, I believe we ARE subject to the Export Control laws.

Eric Smith



On Jul 7, 2010, at 5:33 PM, thpr wrote:

> I will not make any confirmation. I'm not a lawyer, and for the
> half a dozen or so countries for which this restricts access, while
> I regret they would be restricted from using our SW, I'm not
> sticking my neck out without a letter from a lawyer.
>
> TP.
>
> --- In pcgen_developers@yahoogroups.com, Martijn Verburg
> <martijnverburg@...> wrote:
>>
>> Bump
>>
>> On Wed, Jun 30, 2010 at 11:16 PM, Martijn Verburg
>> <martijnverburg@...> wrote:
>>> Hi Team,
>>>
>>> Can someone confirm which camp we lie in? Â I'm not sure if our
>>> networking or install data from website code has any encryption
>>> elements.
>>>
>>> K
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: SourceForge.net Team <noreply@...>
>>> Date: Wed, Jun 30, 2010 at 11:13 PM
>>> Subject: Export Control setting for SourceForge.net projects
>>> To: martijnverburg@...
>>>
>>>
>>> Hello SourceForge project administrator,
>>>
>>> SourceForge has project settings to help you comply with regulations
>>> governing distribution of software to persons from certain countries
>>> (aka Export Controls). Â We've had some recent questions about these
>>> settings, so have sent out this note to all administrators to make
>>> sure all projects have this information.
>>>
>>> By default, software downloads initiated by visitors from Sudan,
>>> North
>>> Korea, Syria, Iran and Cuba are blocked.
>>>
>>> A project administrator may disable this blocking if they conclude
>>> that their project is *not* subject to US export-related regulations
>>> or any prohibitions of applicable jurisdictions:
>>> 1. Project Admin -> Project Settings.
>>> 2. Find the "Export Control" section.
>>> 3. Tick the first radio button under "Export Control" and click
>>> "Update".
>>>
>>> We at SourceForge are committed to the ideals of free and open
>>> source
>>> software, including the principle of free exchange of information.
>>> Our
>>> approach to access control is intended to empower you and reward
>>> your
>>> continued trust. Â We recognize, however, that our approach isn't
>>> the
>>> completely free access to everything for everyone that some would
>>> like. Â As a US-based web site, SourceForge is committed to
>>> complying
>>> fully with US laws and regulations, including those affecting the
>>> distribution of software. Â We will continue to work as diligently
>>> as
>>> possible to ensure that our legal compliance is coupled with the
>>> highest quality of service that we can offer to our diverse, global
>>> user base.
>>>
>>> Best regards,
>>>
>>> Daniel Hinojosa
>>> Sr. Manager, SourceForge.net Support
>>> sfnet_ops@...
>>>
>>> ----------------------------------------------------------
>>> SourceForge.net has made this mailing to you as a registered user of
>>> the SourceForge.net site to convey important information regarding
>>> your SourceForge.net account or your use of SourceForge.net
>>> services.
>>>
>>> We make a small number of directed mailings to registered users each
>>> year regarding their account or data, to help preserve the
>>> security of
>>> their account or prevent loss of data or service access.
>>>
>>> If you have concerns about this mailing please contact our Support
>>> team per: http://sourceforge.net/support
>>>
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>



#1033 From: James Dempsey <jdempsey@...>
Date: Thu Jul 8, 2010 11:51 am
Subject: Re: Change to INFOTEXT behavior
james_dempse...
Send Email Send Email
 
Hi Stefan,

This will need to go through the normal data team approval process.
Could you raise it on the main list and ask Barak to approve it please?

Depending on the number of references to it as a stringkey if  approval
is given in time it should be possible to migrate. However I was
planning on the RC2 going out on Sunday my time, so the approvals would
need to be soon.

Cheers,
James.


On 8/07/2010 7:52 PM Stefan Radermacher wrote
> I would like to change the behavior of the INFOTEXT tag for PCC files to
> behave similar to the COPYRIGHT tag. i.e. so that more than one INFOTEXT
> tag can be used. That would mean changing it from a StringKey toa
> ListKey in the code.
>
> Does anyone have a problem with that, or is that OK? Tom, whct do you think?
>
> I would like to get this change (along with the proposed Pathfinder PCC
> changes) into 5.16.3, if possible.
>
> Regards,
> Stefan.
>

#1034 From: Stefan Radermacher <radermacher@...>
Date: Thu Jul 8, 2010 1:34 pm
Subject: Re: Change to INFOTEXT behavior
zaister
Send Email Send Email
 
Hi Jamess,

> This will need to go through the normal data team approval process.
> Could you raise it on the main list and ask Barak to approve it please?

Certainly.

> Depending on the number of references to it as a stringkey if approval
> is given in time it should be possible to migrate. However I was
> planning on the RC2 going out on Sunday my time, so the approvals would
> need to be soon.

The code change seems easy enough, and I have it running in my sandbox
already.

Regards,
Stefan.

#1035 From: "Maredudd" <maredudd@...>
Date: Thu Jul 8, 2010 1:43 pm
Subject: Name File Location Question
maredudd800
Send Email Send Email
 
Hi Folks!

Is it possible to place the name files (.nam) in a a data set
instead of the system/bio folder?

I'm planning on adding a section to the docs to cover name
files and want to make sure I cover it completely.

Eric Smith
Doc 2nd

#1036 From: Martijn Verburg <martijnverburg@...>
Date: Fri Jul 9, 2010 9:02 am
Subject: Fwd: [pcgen_experimental] JEP count VISIBILITY criteria
karianna03
Send Email Send Email
 
Forwarding this from the currently down experimental group

K

---------- Forwarded message ----------
From: James Dempsey <jdempsey@...>
Date: Tue, Jun 29, 2010 at 10:57 PM
Subject: [pcgen_experimental] JEP count VISIBILITY criteria
To: PCGen Experimental <pcgen_experimental@yahoogroups.com>
Cc: neofax99@...
 

Hi,

Currently, the visibility tag of the JEP count supports the following
options:

* |"VISIBILITY=<text>"|
o "HIDDEN", includes abilities with VISIBLE:NO
o "DEFAULT", includes abilities with VISIBLE:YES or no VISIBLE
tag at all
o "OUTPUT_ONLY", includes abilities with VISIBLE:EXPORT
o "DISPLAY_ONLY", includes abilities with VISIBLE:DISPLAY

Leading to awkward syntax like "VISIBILITY=DEFAULT.or.VISIBILITY=OUTPUTONLY"

Given the primary use for this is in output sheets, I propose to add a
new option:

* "OUTPUT", includes abilities with VISIBLE:EXPORT, VISIBLE:YES or
no VISIBLE tag at all

and a second bonus one for symmetry:

* "DISPLAY", includes abilities with VISIBLE:DISPLAY, VISIBLE:YES or
no VISIBLE tag at all

Thoughts?

Cheers,
James.



#1037 From: hudson@...
Date: Fri Jul 9, 2010 12:13 pm
Subject: Build failed in Hudson: PCGen Nightly Build (Trunk) » PCGen #364
hudson@...
Send Email Send Email
 
See
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/364/changes>

Changes:

[zaister] Adapt source editor GUI to changes to INFOTEXT tag
Issue#: CODE-161

[zaister] fix small C&P oversight from revision 12480

[zaister] Change behavior of PCC file tag INFOTEXT so it can be used more than
only once.

Issue#: CODE-161

[perchrh] indent the file consistently (minor change)

[perchrh] change global default of source file encoding, the files really are
ISO-8859-1, not UTF-8, today

------------------------------------------
[...truncated 367518 lines...]
22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=One.
22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=One.' for TestObj
22:11:49.312 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid reference:
TYPE=One..Two
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=One..Two
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=One..Two' for TestObj
22:11:49.313 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE=.One is not a valid reference: TYPE=.One
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=.One
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=.One' for TestObj
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments may
not end with , : TestWP1,
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP1,
22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP1,' for TestObj
22:11:49.314 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments may
not start with , : ,TestWP1
22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ,TestWP1
22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' ',TestWP1' for TestObj
22:11:49.316 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,Arcane
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,Arcane
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,Arcane' for TestObj
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: Arcane,ANY
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of Arcane,ANY
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'Arcane,ANY' for TestObj
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 ADD may not have empty
argument
22:11:49.317 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments may
not start with , : ,
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ,
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' ',' for TestObj
22:11:49.318 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TYPE=
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=' for TestObj
22:11:49.318 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE=One. is not a valid reference: TYPE=One.
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=One.
22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=One.' for TestObj
22:11:49.319 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid reference:
TYPE=One..Two
22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=One..Two
22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=One..Two' for TestObj
22:11:49.319 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE=.One is not a valid reference: TYPE=.One
22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=.One
22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=.One' for TestObj
22:11:49.319 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments may
not end with , : TestWP1,
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP1,
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP1,' for TestObj
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments may
not start with , : ,TestWP1
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ,TestWP1
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' ',TestWP1' for TestObj
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP2,,TestWP1
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP2,,TestWP1
22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP2,,TestWP1' for TestObj
22:11:49.322 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
Reference: PCClass TestWP2
22:11:49.324 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
Reference: PCClass TestWP2
22:11:49.327 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
Reference: PCClass TestWP2
22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.358 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.365 SEVERE main TokenUtilities:68 Type may not be empty in:
22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.366 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.370 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.371 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.375 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.376 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.379 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:11:49.380 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.383 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.387 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.388 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of -1|TestWP1
22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '-1|TestWP1' for TestObj
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:11:49.392 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of -1|TestWP1
22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '-1|TestWP1' for TestObj
22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of 0|TestWP1
22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '0|TestWP1' for TestObj
22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TestWP1
22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TestWP1' for TestObj
22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TestWP1
22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TestWP1' for TestObj
22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP1,ANY
22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP1,ANY
22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP1,ANY' for TestObj
Tests run: 61, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec
Running
plugin.lsttokens.editcontext.pcclass.KnownSpellsFromSpecialtyIntegrationTest
22:11:49.421 SEVERE main TokenLibrary:148 Duplicate PCClass Token found for
token KNOWNSPELLSFROMSPECIALTY
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
Running plugin.lsttokens.equipmentmodifier.ArmortypeTokenTest
22:11:49.439 SEVERE main TokenLibrary:148 Duplicate EquipmentModifier Token
found for token ARMORTYPE
22:11:49.440 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
start with | : |Medium
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
start with | : |Medium
22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has too many PIPE
characters: Must be of the form old|new
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running plugin.lsttokens.template.LevelAdjustmentTokenTest
22:11:49.453 SEVERE main TokenLibrary:148 Duplicate PCTemplate Token found for
token LEVELADJUSTMENT
22:11:49.454 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have null
argument
22:11:49.454 LSTERROR main AbstractTokenTestCase:224 LEVELADJUSTMENT may not
have empty argument
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running pcgen.cdom.facet.DamageReductionFacetTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec

Results :

Tests run: 14739, Failures: 0, Errors: 0, Skipped: 0

Cobertura: Loaded information on 4029 classes.
Cobertura: Saved information on 4029 classes.
[HUDSON] Recording test results
[INFO] [site:site {execution: default-site}]
[INFO] Skipped "Surefire Report" report, file "JUnit Test Results.html" already
exists for the English version.
[INFO] Skipped "About" report, file "index.html" already exists for the English
version.
[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'action', ignoring!
[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'release', ignoring!
[INFO] Generating "Surefire Report" report.
[WARNING] Unable to locate Test Source XRef to link to - DISABLED
[INFO] Generating "Cobertura Test Coverage" report.
[INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
Cobertura: Loaded information on 4029 classes.
Report time: 41189ms

[INFO] Cobertura Report generation was successful.
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to:
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/changelog.xml>
[INFO] Executing: svn --non-interactive log -v -r "{2010-04-10 12:13:12
+0000}:{2010-07-10 12:13:12 +0000}"
https://pcgen.svn.sourceforge.net/svnroot/pcgen/Trunk/pcgen
[INFO] Working directory:
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/>
[HUDSON] Archiving site from
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/site> to /home/tomcat/.hudson/jobs/PCGen Nightly Build
(Trunk)/site
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------

#1038 From: Stefan Radermacher <radermacher@...>
Date: Fri Jul 9, 2010 12:34 pm
Subject: Re: Build failed in Hudson: PCGen Nightly Build (Trunk) » PCGen #364
zaister
Send Email Send Email
 
Hm... weird. These errors don't look as if my changes could have caused
them. I ran the test suite and the only two failures I got were form
problems with the decimal point ("0.5" vs. 0,5"), probably due to my
machine using German conventions.

Any ideas where this comes from.

Stefan.

On 09.07.2010 14:13, hudson@... wrote:
>
>
> See
>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/364/changes>
>
> Changes:
>
> [zaister] Adapt source editor GUI to changes to INFOTEXT tag
> Issue#: CODE-161
>
> [zaister] fix small C&P oversight from revision 12480
>
> [zaister] Change behavior of PCC file tag INFOTEXT so it can be used
> more than only once.
>
> Issue#: CODE-161
>
> [perchrh] indent the file consistently (minor change)
>
> [perchrh] change global default of source file encoding, the files
> really are ISO-8859-1, not UTF-8, today
>
> ------------------------------------------
> [...truncated 367518 lines...]
> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=One.
> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
> reference: TYPE=One..Two
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=One..Two
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
> reference: TYPE=.One
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=.One
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments may not end with , : TestWP1,
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP1,
> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
> 22:11:49.314 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments may not start with , : ,TestWP1
> 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ,TestWP1
> 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' ',TestWP1' for TestObj
> 22:11:49.316 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,Arcane
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,Arcane
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,Arcane' for TestObj
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: Arcane,ANY
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of Arcane,ANY
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'Arcane,ANY' for TestObj
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 ADD may not have
> empty argument
> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments may not start with , : ,
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ,
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' ',' for TestObj
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TYPE=
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=' for TestObj
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE=One. is not a valid
> reference: TYPE=One.
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=One.
> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
> reference: TYPE=One..Two
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=One..Two
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
> reference: TYPE=.One
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=.One
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments may not end with , : TestWP1,
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP1,
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments may not start with , : ,TestWP1
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ,TestWP1
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' ',TestWP1' for TestObj
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP2,,TestWP1
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP2,,TestWP1
> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP2,,TestWP1' for TestObj
> 22:11:49.322 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> Reference: PCClass TestWP2
> 22:11:49.324 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> Reference: PCClass TestWP2
> 22:11:49.327 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> Reference: PCClass TestWP2
> 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.358 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.365 SEVERE main TokenUtilities:68 Type may not be empty in:
> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.375 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,ANY
> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,ANY
> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> SubToken and argument, found: SPELLCASTER
> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,ANY
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> SubToken and argument, found: SPELLCASTER
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> have empty argument
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of
> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '' for TestObj
> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,ANY
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> SubToken and argument, found: SPELLCASTER
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> have empty argument
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '' for TestObj
> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Count in
> ADD:SPELLCASTER must be > 0
> 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of -1|TestWP1
> 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TYPE=TestType
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TYPE=TestType,ANY
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Error was
> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> reference: TestWP3,TYPE=
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,TYPE=
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> arguments uses double separator ,, : TestWP3,,TestWP4
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,,TestWP4
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP3,ANY
> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> SubToken and argument, found: SPELLCASTER
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> have empty argument
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '' for TestObj
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Count in
> ADD:SPELLCASTER must be > 0
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of -1|TestWP1
> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Count in
> ADD:SPELLCASTER must be > 0
> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of 0|TestWP1
> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' '0|TestWP1' for TestObj
> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TestWP1
> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of ANY,TestWP1
> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP1,ANY
> 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> subtoken: SPELLCASTER of TestWP1,ANY
> 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> subtoken 'SPELLCASTER' 'TestWP1,ANY' for TestObj
> Tests run: 61, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec
> Running
> plugin.lsttokens.editcontext.pcclass.KnownSpellsFromSpecialtyIntegrationTest
> 22:11:49.421 SEVERE main TokenLibrary:148 Duplicate PCClass Token found
> for token KNOWNSPELLSFROMSPECIALTY
> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
> Running plugin.lsttokens.equipmentmodifier.ArmortypeTokenTest
> 22:11:49.439 SEVERE main TokenLibrary:148 Duplicate EquipmentModifier
> Token found for token ARMORTYPE
> 22:11:49.440 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> uses double separator || : Light||Medium
> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> uses double separator || : Light||Medium
> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> PIPE character: Must be of the form old|new
> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> uses double separator || : Light||Medium
> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> PIPE character: Must be of the form old|new
> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> may not end with | : Medium|
> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> uses double separator || : Light||Medium
> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> PIPE character: Must be of the form old|new
> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> may not end with | : Medium|
> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> may not start with | : |Medium
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have empty argument
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> uses double separator || : Light||Medium
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> PIPE character: Must be of the form old|new
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> may not end with | : Medium|
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> may not start with | : |Medium
> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has too
> many PIPE characters: Must be of the form old|new
> Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
> Running plugin.lsttokens.template.LevelAdjustmentTokenTest
> 22:11:49.453 SEVERE main TokenLibrary:148 Duplicate PCTemplate Token
> found for token LEVELADJUSTMENT
> 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> have null argument
> 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 LEVELADJUSTMENT may
> not have empty argument
> Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> Running pcgen.cdom.facet.DamageReductionFacetTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
>
> Results :
>
> Tests run: 14739, Failures: 0, Errors: 0, Skipped: 0
>
> Cobertura: Loaded information on 4029 classes.
> Cobertura: Saved information on 4029 classes.
> [HUDSON] Recording test results
> [INFO] [site:site {execution: default-site}]
> [INFO] Skipped "Surefire Report" report, file "JUnit Test Results.html"
> already exists for the English version.
> [INFO] Skipped "About" report, file "index.html" already exists for the
> English version.
> [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'action',
> ignoring!
> [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'release',
> ignoring!
> [INFO] Generating "Surefire Report" report.
> [WARNING] Unable to locate Test Source XRef to link to - DISABLED
> [INFO] Generating "Cobertura Test Coverage" report.
> [INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
> Cobertura: Loaded information on 4029 classes.
> Report time: 41189ms
>
> [INFO] Cobertura Report generation was successful.
> [INFO] Generating "Change Log" report.
> [INFO] Generating changed sets xml to:
>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/changelog.xml>
> [INFO] Executing: svn --non-interactive log -v -r "{2010-04-10 12:13:12
> +0000}:{2010-07-10 12:13:12 +0000}"
> https://pcgen.svn.sourceforge.net/svnroot/pcgen/Trunk/pcgen
> [INFO] Working directory:
>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/>
> [HUDSON] Archiving site from
>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/site>
> to /home/tomcat/.hudson/jobs/PCGen Nightly Build (Trunk)/site
> [INFO] ----------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------
>
>

#1039 From: "thpr" <thpr@...>
Date: Fri Jul 9, 2010 4:16 pm
Subject: Re: Fwd: [pcgen_experimental] JEP count VISIBILITY criteria
thpr
Send Email Send Email
 
I would like to see us use "VIEW" not "VISIBILITY" for these ("OUTPUT",
"DISPLAY") groupings.  That is a less confusing method of grouping visibilities.

I'm concerned about the potential confusion between "OUTPUT" and "OUTPUT_ONLY"
if both are called Visibility.

TP.

--- In pcgen_developers@yahoogroups.com, Martijn Verburg <martijnverburg@...>
wrote:
>
> Forwarding this from the currently down experimental group
>
> K
>
> ---------- Forwarded message ----------
> From: James Dempsey <jdempsey@...>
> Date: Tue, Jun 29, 2010 at 10:57 PM
> Subject: [pcgen_experimental] JEP count VISIBILITY criteria
> To: PCGen Experimental <pcgen_experimental@yahoogroups.com>
> Cc: neofax99@...
>
>
> Hi,
>
> Currently, the visibility tag of the JEP count supports the following
> options:
>
> * |"VISIBILITY=<text>"|
> o "HIDDEN", includes abilities with VISIBLE:NO
> o "DEFAULT", includes abilities with VISIBLE:YES or no VISIBLE
> tag at all
> o "OUTPUT_ONLY", includes abilities with VISIBLE:EXPORT
> o "DISPLAY_ONLY", includes abilities with VISIBLE:DISPLAY
>
> Leading to awkward syntax like "VISIBILITY=DEFAULT.or.VISIBILITY=OUTPUTONLY"
>
> Given the primary use for this is in output sheets, I propose to add a
> new option:
>
> * "OUTPUT", includes abilities with VISIBLE:EXPORT, VISIBLE:YES or
> no VISIBLE tag at all
>
> and a second bonus one for symmetry:
>
> * "DISPLAY", includes abilities with VISIBLE:DISPLAY, VISIBLE:YES or
> no VISIBLE tag at all
>
> Thoughts?
>
> Cheers,
> James.
>

#1040 From: "thpr" <thpr@...>
Date: Fri Jul 9, 2010 4:20 pm
Subject: Re: Build failed in Hudson: PCGen Nightly Build (Trunk) » PCGen #364
thpr
Send Email Send Email
 
The "errors" in the console are simply output from test cases that intentionally
checking bad input (but the tests are passing since they are expected to produce
a problem in the code).

It looks like all the tests passed, but some other module build failed.  I'm
wondering if the file format change from Per made a difference or whether this
was just another out of memory event.

TP.

--- In pcgen_developers@yahoogroups.com, Stefan Radermacher <radermacher@...>
wrote:
>
> Hm... weird. These errors don't look as if my changes could have caused
> them. I ran the test suite and the only two failures I got were form
> problems with the decimal point ("0.5" vs. 0,5"), probably due to my
> machine using German conventions.
>
> Any ideas where this comes from.
>
> Stefan.
>
> On 09.07.2010 14:13, hudson@... wrote:
> >
> >
> > See
> >
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/364/changes>
> >
> > Changes:
> >
> > [zaister] Adapt source editor GUI to changes to INFOTEXT tag
> > Issue#: CODE-161
> >
> > [zaister] fix small C&P oversight from revision 12480
> >
> > [zaister] Change behavior of PCC file tag INFOTEXT so it can be used
> > more than only once.
> >
> > Issue#: CODE-161
> >
> > [perchrh] indent the file consistently (minor change)
> >
> > [perchrh] change global default of source file encoding, the files
> > really are ISO-8859-1, not UTF-8, today
> >
> > ------------------------------------------
> > [...truncated 367518 lines...]
> > 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=One.
> > 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
> > 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
> > reference: TYPE=One..Two
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=One..Two
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
> > reference: TYPE=.One
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=.One
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments may not end with , : TestWP1,
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP1,
> > 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
> > 22:11:49.314 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments may not start with , : ,TestWP1
> > 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ,TestWP1
> > 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' ',TestWP1' for TestObj
> > 22:11:49.316 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,Arcane
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,Arcane
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,Arcane' for TestObj
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: Arcane,ANY
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of Arcane,ANY
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'Arcane,ANY' for TestObj
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 ADD may not have
> > empty argument
> > 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments may not start with , : ,
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ,
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' ',' for TestObj
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TYPE=
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=' for TestObj
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE=One. is not a valid
> > reference: TYPE=One.
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=One.
> > 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
> > reference: TYPE=One..Two
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=One..Two
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
> > reference: TYPE=.One
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=.One
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
> > 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments may not end with , : TestWP1,
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP1,
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments may not start with , : ,TestWP1
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ,TestWP1
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' ',TestWP1' for TestObj
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP2,,TestWP1
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP2,,TestWP1
> > 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP2,,TestWP1' for TestObj
> > 22:11:49.322 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> > Reference: PCClass TestWP2
> > 22:11:49.324 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> > Reference: PCClass TestWP2
> > 22:11:49.327 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
> > Reference: PCClass TestWP2
> > 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.358 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.365 SEVERE main TokenUtilities:68 Type may not be empty in:
> > 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.375 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,ANY
> > 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> > 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> > 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,ANY
> > 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> > 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> > SubToken and argument, found: SPELLCASTER
> > 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,ANY
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> > SubToken and argument, found: SPELLCASTER
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> > have empty argument
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of
> > 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '' for TestObj
> > 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,ANY
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> > SubToken and argument, found: SPELLCASTER
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> > have empty argument
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '' for TestObj
> > 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Count in
> > ADD:SPELLCASTER must be > 0
> > 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of -1|TestWP1
> > 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TYPE=TestType
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TYPE=TestType,ANY
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
> > 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Error was
> > encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
> > reference: TestWP3,TYPE=
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,TYPE=
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
> > arguments uses double separator ,, : TestWP3,,TestWP4
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,,TestWP4
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP3,ANY
> > 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 ADD requires a
> > SubToken and argument, found: SPELLCASTER
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
> > have empty argument
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '' for TestObj
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Count in
> > ADD:SPELLCASTER must be > 0
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of -1|TestWP1
> > 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
> > 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Count in
> > ADD:SPELLCASTER must be > 0
> > 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of 0|TestWP1
> > 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' '0|TestWP1' for TestObj
> > 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
> > 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TestWP1
> > 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
> > 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
> > 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of ANY,TestWP1
> > 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
> > 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
> > ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP1,ANY
> > 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
> > subtoken: SPELLCASTER of TestWP1,ANY
> > 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
> > subtoken 'SPELLCASTER' 'TestWP1,ANY' for TestObj
> > Tests run: 61, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec
> > Running
> > plugin.lsttokens.editcontext.pcclass.KnownSpellsFromSpecialtyIntegrationTest
> > 22:11:49.421 SEVERE main TokenLibrary:148 Duplicate PCClass Token found
> > for token KNOWNSPELLSFROMSPECIALTY
> > Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
> > Running plugin.lsttokens.equipmentmodifier.ArmortypeTokenTest
> > 22:11:49.439 SEVERE main TokenLibrary:148 Duplicate EquipmentModifier
> > Token found for token ARMORTYPE
> > 22:11:49.440 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > uses double separator || : Light||Medium
> > 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > uses double separator || : Light||Medium
> > 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> > PIPE character: Must be of the form old|new
> > 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > uses double separator || : Light||Medium
> > 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> > PIPE character: Must be of the form old|new
> > 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > may not end with | : Medium|
> > 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > uses double separator || : Light||Medium
> > 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> > PIPE character: Must be of the form old|new
> > 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > may not end with | : Medium|
> > 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > may not start with | : |Medium
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have empty argument
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > uses double separator || : Light||Medium
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
> > PIPE character: Must be of the form old|new
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > may not end with | : Medium|
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
> > may not start with | : |Medium
> > 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has too
> > many PIPE characters: Must be of the form old|new
> > Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
> > Running plugin.lsttokens.template.LevelAdjustmentTokenTest
> > 22:11:49.453 SEVERE main TokenLibrary:148 Duplicate PCTemplate Token
> > found for token LEVELADJUSTMENT
> > 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
> > have null argument
> > 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 LEVELADJUSTMENT may
> > not have empty argument
> > Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
> > Running pcgen.cdom.facet.DamageReductionFacetTest
> > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
> >
> > Results :
> >
> > Tests run: 14739, Failures: 0, Errors: 0, Skipped: 0
> >
> > Cobertura: Loaded information on 4029 classes.
> > Cobertura: Saved information on 4029 classes.
> > [HUDSON] Recording test results
> > [INFO] [site:site {execution: default-site}]
> > [INFO] Skipped "Surefire Report" report, file "JUnit Test Results.html"
> > already exists for the English version.
> > [INFO] Skipped "About" report, file "index.html" already exists for the
> > English version.
> > [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'action',
> > ignoring!
> > [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'release',
> > ignoring!
> > [INFO] Generating "Surefire Report" report.
> > [WARNING] Unable to locate Test Source XRef to link to - DISABLED
> > [INFO] Generating "Cobertura Test Coverage" report.
> > [INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
> > Cobertura: Loaded information on 4029 classes.
> > Report time: 41189ms
> >
> > [INFO] Cobertura Report generation was successful.
> > [INFO] Generating "Change Log" report.
> > [INFO] Generating changed sets xml to:
> >
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/changelog.xml>
> > [INFO] Executing: svn --non-interactive log -v -r "{2010-04-10 12:13:12
> > +0000}:{2010-07-10 12:13:12 +0000}"
> > https://pcgen.svn.sourceforge.net/svnroot/pcgen/Trunk/pcgen
> > [INFO] Working directory:
> >
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/>
> > [HUDSON] Archiving site from
> >
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/site>
> > to /home/tomcat/.hudson/jobs/PCGen Nightly Build (Trunk)/site
> > [INFO] ----------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO] ----------------------------------------------------------
> >
> >
>

#1041 From: James Dempsey <jdempsey@...>
Date: Fri Jul 9, 2010 11:14 pm
Subject: Re: Re: Build failed in Hudson: PCGen Nightly Build (Trunk) » PCGen #364
james_dempse...
Send Email Send Email
 
Hi,

A new version of tomcat was installed a couple of nights ago which broke
hudson. I've since migrated hudson to the new container, but I suspect
that there is still something awry. After digging into the logs held by
hudson, the problem lies with the svn command used to produce the
changelist report for the site. I suspect it cannot find the svn
executable. I will continue to try and resolve the issue.

So this error can be safely ignored for now. The PCGen Trunk CI build
will tell us if there are any code problems. That is currently happy.

Cheers,
James.

On 10/07/2010 2:20 AM thpr wrote
> The "errors" in the console are simply output from test cases that
intentionally checking bad input (but the tests are passing since they are
expected to produce a problem in the code).
>
> It looks like all the tests passed, but some other module build failed.  I'm
wondering if the file format change from Per made a difference or whether this
was just another out of memory event.
>
> TP.
>
> --- In pcgen_developers@yahoogroups.com, Stefan Radermacher <radermacher@...>
wrote:
>
>> Hm... weird. These errors don't look as if my changes could have caused
>> them. I ran the test suite and the only two failures I got were form
>> problems with the decimal point ("0.5" vs. 0,5"), probably due to my
>> machine using German conventions.
>>
>> Any ideas where this comes from.
>>
>> Stefan.
>>
>> On 09.07.2010 14:13, hudson@... wrote:
>>
>>> See
>>>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/364/changes>
>>>
>>> Changes:
>>>
>>> [zaister] Adapt source editor GUI to changes to INFOTEXT tag
>>> Issue#: CODE-161
>>>
>>> [zaister] fix small C&P oversight from revision 12480
>>>
>>> [zaister] Change behavior of PCC file tag INFOTEXT so it can be used
>>> more than only once.
>>>
>>> Issue#: CODE-161
>>>
>>> [perchrh] indent the file consistently (minor change)
>>>
>>> [perchrh] change global default of source file encoding, the files
>>> really are ISO-8859-1, not UTF-8, today
>>>
>>> ------------------------------------------
>>> [...truncated 367518 lines...]
>>> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=One.
>>> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
>>> 22:11:49.312 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
>>> reference: TYPE=One..Two
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=One..Two
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
>>> reference: TYPE=.One
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=.One
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments may not end with , : TestWP1,
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP1,
>>> 22:11:49.313 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
>>> 22:11:49.314 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments may not start with , : ,TestWP1
>>> 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ,TestWP1
>>> 22:11:49.315 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' ',TestWP1' for TestObj
>>> 22:11:49.316 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,Arcane
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,Arcane
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,Arcane' for TestObj
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: Arcane,ANY
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of Arcane,ANY
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'Arcane,ANY' for TestObj
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 ADD may not have
>>> empty argument
>>> 22:11:49.317 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments may not start with , : ,
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ,
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' ',' for TestObj
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TYPE=
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=' for TestObj
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE=One. is not a valid
>>> reference: TYPE=One.
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=One.
>>> 22:11:49.318 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=One.' for TestObj
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE=One..Two is not a valid
>>> reference: TYPE=One..Two
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=One..Two
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=One..Two' for TestObj
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE=.One is not a valid
>>> reference: TYPE=.One
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=.One
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=.One' for TestObj
>>> 22:11:49.319 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments may not end with , : TestWP1,
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP1,
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP1,' for TestObj
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments may not start with , : ,TestWP1
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ,TestWP1
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' ',TestWP1' for TestObj
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP2,,TestWP1
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP2,,TestWP1
>>> 22:11:49.320 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP2,,TestWP1' for TestObj
>>> 22:11:49.322 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
>>> Reference: PCClass TestWP2
>>> 22:11:49.324 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
>>> Reference: PCClass TestWP2
>>> 22:11:49.327 SEVERE main AbstractReferenceManufacturer:992 Unconstructed
>>> Reference: PCClass TestWP2
>>> 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.357 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.358 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.361 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.365 SEVERE main TokenUtilities:68 Type may not be empty in:
>>> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.365 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.366 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.370 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.371 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.375 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.376 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,ANY
>>> 22:11:49.377 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
>>> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.378 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.379 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
>>> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,ANY
>>> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
>>> 22:11:49.380 LSTERROR main AbstractTokenTestCase:224 ADD requires a
>>> SubToken and argument, found: SPELLCASTER
>>> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.382 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.383 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,ANY
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 ADD requires a
>>> SubToken and argument, found: SPELLCASTER
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
>>> have empty argument
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of
>>> 22:11:49.384 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '' for TestObj
>>> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.386 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.387 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.388 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,ANY
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 ADD requires a
>>> SubToken and argument, found: SPELLCASTER
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
>>> have empty argument
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '' for TestObj
>>> 22:11:49.389 LSTERROR main AbstractTokenTestCase:224 Count in
>>> ADD:SPELLCASTER must be > 0
>>> 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of -1|TestWP1
>>> 22:11:49.390 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TYPE=TestType
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TYPE=TestType,ANY
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
>>> 22:11:49.392 LSTERROR main AbstractTokenTestCase:224 Error was
>>> encountered while parsing ADD:SPELLCASTER: TYPE= is not a valid
>>> reference: TestWP3,TYPE=
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,TYPE=
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER
>>> arguments uses double separator ,, : TestWP3,,TestWP4
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,,TestWP4
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP3,ANY
>>> 22:11:49.393 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP3,ANY' for TestObj
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 ADD requires a
>>> SubToken and argument, found: SPELLCASTER
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not
>>> have empty argument
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '' for TestObj
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Count in
>>> ADD:SPELLCASTER must be > 0
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of -1|TestWP1
>>> 22:11:49.394 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '-1|TestWP1' for TestObj
>>> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Count in
>>> ADD:SPELLCASTER must be > 0
>>> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of 0|TestWP1
>>> 22:11:49.395 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' '0|TestWP1' for TestObj
>>> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
>>> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TestWP1
>>> 22:11:49.413 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
>>> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
>>> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of ANY,TestWP1
>>> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'ANY,TestWP1' for TestObj
>>> 22:11:49.415 LSTERROR main AbstractTokenTestCase:224 Non-sensical
>>> ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP1,ANY
>>> 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Failed in parsing
>>> subtoken: SPELLCASTER of TestWP1,ANY
>>> 22:11:49.416 LSTERROR main AbstractTokenTestCase:224 Illegal ADD
>>> subtoken 'SPELLCASTER' 'TestWP1,ANY' for TestObj
>>> Tests run: 61, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.182 sec
>>> Running
>>> plugin.lsttokens.editcontext.pcclass.KnownSpellsFromSpecialtyIntegrationTest
>>> 22:11:49.421 SEVERE main TokenLibrary:148 Duplicate PCClass Token found
>>> for token KNOWNSPELLSFROMSPECIALTY
>>> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec
>>> Running plugin.lsttokens.equipmentmodifier.ArmortypeTokenTest
>>> 22:11:49.439 SEVERE main TokenLibrary:148 Duplicate EquipmentModifier
>>> Token found for token ARMORTYPE
>>> 22:11:49.440 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.443 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> uses double separator || : Light||Medium
>>> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> uses double separator || : Light||Medium
>>> 22:11:49.444 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
>>> PIPE character: Must be of the form old|new
>>> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> uses double separator || : Light||Medium
>>> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
>>> PIPE character: Must be of the form old|new
>>> 22:11:49.445 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> may not end with | : Medium|
>>> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> uses double separator || : Light||Medium
>>> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
>>> PIPE character: Must be of the form old|new
>>> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> may not end with | : Medium|
>>> 22:11:49.446 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> may not start with | : |Medium
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have empty argument
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> uses double separator || : Light||Medium
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no
>>> PIPE character: Must be of the form old|new
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> may not end with | : Medium|
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments
>>> may not start with | : |Medium
>>> 22:11:49.447 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has too
>>> many PIPE characters: Must be of the form old|new
>>> Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
>>> Running plugin.lsttokens.template.LevelAdjustmentTokenTest
>>> 22:11:49.453 SEVERE main TokenLibrary:148 Duplicate PCTemplate Token
>>> found for token LEVELADJUSTMENT
>>> 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not
>>> have null argument
>>> 22:11:49.454 LSTERROR main AbstractTokenTestCase:224 LEVELADJUSTMENT may
>>> not have empty argument
>>> Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
>>> Running pcgen.cdom.facet.DamageReductionFacetTest
>>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 sec
>>>
>>> Results :
>>>
>>> Tests run: 14739, Failures: 0, Errors: 0, Skipped: 0
>>>
>>> Cobertura: Loaded information on 4029 classes.
>>> Cobertura: Saved information on 4029 classes.
>>> [HUDSON] Recording test results
>>> [INFO] [site:site {execution: default-site}]
>>> [INFO] Skipped "Surefire Report" report, file "JUnit Test Results.html"
>>> already exists for the English version.
>>> [INFO] Skipped "About" report, file "index.html" already exists for the
>>> English version.
>>> [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'action',
>>> ignoring!
>>> [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'release',
>>> ignoring!
>>> [INFO] Generating "Surefire Report" report.
>>> [WARNING] Unable to locate Test Source XRef to link to - DISABLED
>>> [INFO] Generating "Cobertura Test Coverage" report.
>>> [INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
>>> Cobertura: Loaded information on 4029 classes.
>>> Report time: 41189ms
>>>
>>> [INFO] Cobertura Report generation was successful.
>>> [INFO] Generating "Change Log" report.
>>> [INFO] Generating changed sets xml to:
>>>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/changelog.xml>
>>> [INFO] Executing: svn --non-interactive log -v -r "{2010-04-10 12:13:12
>>> +0000}:{2010-07-10 12:13:12 +0000}"
>>> https://pcgen.svn.sourceforge.net/svnroot/pcgen/Trunk/pcgen
>>> [INFO] Working directory:
>>>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/>
>>> [HUDSON] Archiving site from
>>>
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/site>
>>> to /home/tomcat/.hudson/jobs/PCGen Nightly Build (Trunk)/site
>>> [INFO] ----------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO] ----------------------------------------------------------
>>>

#1042 From: Andrew Maitland <drew0500@...>
Date: Sat Jul 10, 2010 1:59 am
Subject: Need new OUTPUT Token to round out the unit tests.
Drew0500
Send Email Send Email
 
Hi,

http://jira.pcgen.org/browse/NEWTAG-181

A bug has popped up that wasn't caught due to not having the right test in place. Hence I'd like to have a new Output Tag to track Skill Cost. This would be added to the testsuite xml.

Discuss away...

--
Andrew Maitland (LegacyKing)
Admin Silverback - PCGen Board of Directors
Data Chimp, Docs Tamarin
Unique Title "Quick-Silverback Tracker Monkey"
Unique Title "The Torturer of PCGen"

#1043 From: hudson@...
Date: Sat Jul 10, 2010 12:14 pm
Subject: Build failed in Hudson: PCGen Nightly Build (Trunk) » PCGen #365
hudson@...
Send Email Send Email
 
See
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/365/changes>

Changes:

[Tom Parker] Move Natural Attacks processing to Facets

[Tom Parker] move Natural Weapon processing from setRace to Facets

[Tom Parker] ApplyBonus trigger on Race Facet set

[Tom Parker] Eliminate AssociationListKey.BONUS

[Tom Parker] AssociationListKey.BONUS cleanup preparation

[Tom Parker] AppliedBonusFacet

[Tom Parker] Start of CharacterSpell changes

------------------------------------------
[...truncated 367600 lines...]
22:12:40.550 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:12:40.550 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:12:40.551 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:12:40.551 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:12:40.552 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:12:40.552 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:12:40.552 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:12:40.553 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:12:40.554 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:12:40.554 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:12:40.555 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:12:40.556 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:12:40.557 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:12:40.557 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:12:40.558 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:12:40.558 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:12:40.559 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:12:40.560 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:12:40.560 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:12:40.562 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:12:40.562 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:12:40.563 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of -1|TestWP1
22:12:40.564 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '-1|TestWP1' for TestObj
22:12:40.566 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TYPE=TestType
22:12:40.566 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TYPE=TestType
22:12:40.566 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TYPE=TestType' for TestObj
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TYPE=TestType,ANY
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TYPE=TestType,ANY
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TYPE=TestType,ANY' for TestObj
22:12:40.567 LSTERROR main AbstractTokenTestCase:224   Error was encountered
while parsing ADD:SPELLCASTER: TYPE= is not a valid reference: TestWP3,TYPE=
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,TYPE=
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,TYPE=' for TestObj
22:12:40.567 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER arguments uses
double separator ,, : TestWP3,,TestWP4
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,,TestWP4
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,,TestWP4' for TestObj
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP3,ANY
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP3,ANY
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP3,ANY' for TestObj
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 ADD requires a SubToken and
argument, found: SPELLCASTER
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 SPELLCASTER may not have
empty argument
22:12:40.568 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '' for TestObj
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of -1|TestWP1
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '-1|TestWP1' for TestObj
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Count in ADD:SPELLCASTER
must be > 0
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of 0|TestWP1
22:12:40.569 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' '0|TestWP1' for TestObj
22:12:40.587 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
22:12:40.587 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TestWP1
22:12:40.587 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TestWP1' for TestObj
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: ANY,TestWP1
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of ANY,TestWP1
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'ANY,TestWP1' for TestObj
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Non-sensical
ADD:SPELLCASTER: Contains ANY and a specific reference: TestWP1,ANY
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Failed in parsing subtoken:
SPELLCASTER of TestWP1,ANY
22:12:40.590 LSTERROR main AbstractTokenTestCase:224 Illegal ADD subtoken
'SPELLCASTER' 'TestWP1,ANY' for TestObj
Tests run: 61, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.314 sec
Running
plugin.lsttokens.editcontext.pcclass.KnownSpellsFromSpecialtyIntegrationTest
22:12:40.595 SEVERE main TokenLibrary:148 Duplicate PCClass Token found for
token KNOWNSPELLSFROMSPECIALTY
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec
Running plugin.lsttokens.equipmentmodifier.ArmortypeTokenTest
22:12:40.613 SEVERE main TokenLibrary:148 Duplicate EquipmentModifier Token
found for token ARMORTYPE
22:12:40.614 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.617 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.617 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:12:40.618 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.618 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:12:40.618 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:12:40.619 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.619 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:12:40.619 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:12:40.619 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:12:40.620 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.620 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:12:40.620 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:12:40.620 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:12:40.620 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
start with | : |Medium
22:12:40.621 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have
empty argument
22:12:40.621 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments uses
double separator || : Light||Medium
22:12:40.621 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has no PIPE
character: Must be of the form old|new
22:12:40.621 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
end with | : Medium|
22:12:40.622 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE arguments may not
start with | : |Medium
22:12:40.622 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE has too many PIPE
characters: Must be of the form old|new
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec
Running plugin.lsttokens.template.LevelAdjustmentTokenTest
22:12:40.629 SEVERE main TokenLibrary:148 Duplicate PCTemplate Token found for
token LEVELADJUSTMENT
22:12:40.630 LSTERROR main AbstractTokenTestCase:224 ARMORTYPE may not have null
argument
22:12:40.630 LSTERROR main AbstractTokenTestCase:224 LEVELADJUSTMENT may not
have empty argument
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec
Running pcgen.cdom.facet.DamageReductionFacetTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec

Results :

Tests run: 14739, Failures: 0, Errors: 0, Skipped: 0

Cobertura: Loaded information on 4031 classes.
Cobertura: Saved information on 4031 classes.
[HUDSON] Recording test results
[INFO] [site:site {execution: default-site}]
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates
from ibiblio.repo
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates
from pcgen.repo
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates
from maven-plugins.repo
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates
from emma.repo
[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates
from central
[INFO] Skipped "Surefire Report" report, file "JUnit Test Results.html" already
exists for the English version.
[INFO] Skipped "About" report, file "index.html" already exists for the English
version.
[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'action', ignoring!
[WARNING] [XHTML Sink] No HTML tag found for unknown event: 'release', ignoring!
[INFO] Generating "Surefire Report" report.
[WARNING] Unable to locate Test Source XRef to link to - DISABLED
[INFO] Generating "Cobertura Test Coverage" report.
[INFO] Cobertura 1.9.2 - GNU GPL License (NO WARRANTY) - See COPYRIGHT file
Cobertura: Loaded information on 4031 classes.
Report time: 32056ms

[INFO] Cobertura Report generation was successful.
[INFO] Generating "Change Log" report.
[INFO] Generating changed sets xml to:
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/changelog.xml>
[INFO] Executing: svn --non-interactive log -v -r "{2010-04-11 12:14:08
+0000}:{2010-07-11 12:14:08 +0000}"
https://pcgen.svn.sourceforge.net/svnroot/pcgen/Trunk/pcgen
[INFO] Working directory:
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/>
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: Can't open file '/root/.subversion/servers': Permission denied

[HUDSON] Archiving site from
<http://ci.pcgen.org/hudson/job/PCGen%20Nightly%20Build%20(Trunk)/net.sourceforg\
e.pcgen$pcgen/ws/target/site> to /home/tomcat/.hudson/jobs/PCGen Nightly Build
(Trunk)/site
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error during page generation

Embedded error: Error rendering Maven report: An error has occurred during
changelog command :
Command failed.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl\
eExecutor.java:719)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def\
aultLifecycleExecutor.java:556)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle\
Executor.java:535)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures\
(DefaultLifecycleExecutor.java:387)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL\
ifecycleExecutor.java:348)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec\
utor.java:180)
	 at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecuto\
rInterceptor.java:65)
	 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
	 at java.lang.reflect.Method.invoke(Method.java:597)
	 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	 at hudson.maven.agent.Main.launch(Main.java:165)
	 at hudson.maven.MavenBuilder.call(MavenBuilder.java:165)
	 at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:696)
	 at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:640)
	 at hudson.remoting.UserRequest.perform(UserRequest.java:114)
	 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	 at hudson.remoting.Request$2.run(Request.java:270)
	 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	 at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8\
86)
	 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	 at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
	 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:114)
	 at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja\
va:490)
	 at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor\
.java:182)
	 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl\
eExecutor.java:694)
	 ... 28 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: An error has occurred during changelog command :
	 at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocume\
ntRenderer.java:174)
	 at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSite\
Renderer.java:328)
	 at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRender\
er.java:132)
	 at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:142)
	 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:109)
	 ... 31 more
Caused by: org.apache.maven.reporting.MavenReportException: An error has
occurred during changelog command :
	 at
org.apache.maven.plugin.changelog.ChangeLogReport.generateChangeSetsFromSCM(Chan\
geLogReport.java:555)
	 at
org.apache.maven.plugin.changelog.ChangeLogReport.getChangedSets(ChangeLogReport\
.java:393)
	 at
org.apache.maven.plugin.changelog.ChangeLogReport.executeReport(ChangeLogReport.\
java:340)
	 at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java\
:98)
	 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav\
a:25)
	 at java.lang.reflect.Method.invoke(Method.java:597)
	 at hudson.maven.agent.ComponentInterceptor.invoke(ComponentInterceptor.java:47)
	 at
hudson.maven.agent.PluginManagerInterceptor$3.invoke(PluginManagerInterceptor.ja\
va:229)
	 at $Proxy5.generate(Unknown Source)
	 at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocume\
ntRenderer.java:164)
	 ... 35 more
Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
	 at
org.apache.maven.plugin.changelog.ChangeLogReport.checkResult(ChangeLogReport.ja\
va:705)
	 at
org.apache.maven.plugin.changelog.ChangeLogReport.generateChangeSetsFromSCM(Chan\
geLogReport.java:467)
	 ... 46 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11 minutes 25 seconds
[INFO] Finished at: Sat Jul 10 22:14:40 EST 2010
[INFO] Final Memory: 60M/120M
[INFO] ------------------------------------------------------------------------

Messages 1014 - 1043 of 3334   Oldest  |  < Older  |  Newer >  |  Newest
Add to My Yahoo!      XML What's This?

Copyright © 2010 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines NEW - Help