[
https://issues.apache.org/jira/browse/SCXML-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar resolved SCXML-93.
--------------------------------
Resolution: Won't Fix
I think the aspect of tidying up here is no different from what folks using any
of the builds should expect -- to elaborate, lets say you execute this command:
mvn test
(or 'maven test', or 'ant'), you'll find a bunch of artifacts created in the
target directory. These persist until you clean the build, so in the above case
a:
mvn clean
will do the trick. The serialization files follow a similar pattern, they can
be cleaned using the corresponding clean command.
A useful advantage of using File I/O is that the artifacts can be introspected
once you run the tests and you can observe how certain changes to the datamodel
or history affect size on disk etc.
You are right that this can be replaced by using ByteArray I/O instead, but at
this point its unclear we should (its much harder to introspect serializations
or track serialization timelines that way).
Resolving as Won't Fix.
> SCXMLTestHelper generates a lot of serialisation files which are not tidied up
> ------------------------------------------------------------------------------
>
> Key: SCXML-93
> URL: https://issues.apache.org/jira/browse/SCXML-93
> Project: Commons SCXML
> Issue Type: Bug
> Reporter: Sebb
> Priority: Minor
>
> SCXMLTestHelper generates files to test serialisation of classes in
> testExecutorSerializability() and testModelSerializability().
> These files are only used temporarily, but are not cleared up at the end of a
> run.
> They can be replaced by using ByteArray classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
