Hi Martin,
I've disabled JDK 8 javadoc doclint which should 'fix' your below problem.
BTW: can you please use properly wrapped/formatted plain text for your email?
Like your previous message, content below is pretty much unreadable ...
Ate
On 2016-01-28 14:32, Martin Gainty wrote:
Hi Atecurrently testing what happens when log4j.properties or log4j.xml is
missing (cured by inserting a working log4j.properties into scxml classpath)
I am currently experiencing this failure:
Javadoc failure with:
Caused by: org.apache.maven.plugin.MojoExecutionException: Error generating
maven-javadoc-plugin:2.10.3:javadoc:Exit code: 1 -
\scxml\src\main\java\org\apache\commons\scxml2\SCInstanceObjectInputStream.java:80: error:
unexpected end tag: </p> * </p>
Here is the code:
/** * Set custom class resolver callback, or null when no longer needed. * <p> * Typically
usage: * <pre><code> * private void readObject(ObjectInputStream in) throws
IOException,ClassNotFoundException { * ClassResolver currentClassResolver = null; * try { *
if (in instanceof SCInstanceObjectInputStream) { * currentClassResolver =
((SCInstanceObjectInputStream)in).setClassResolver(customClassResolver); * } * ... // read
Object(s) * } * finally { * if (in instanceof SCInstanceObjectInputStream) { *
((SCInstanceObjectInputStream)in).setClassResolver(currentClassResolver); * } * } *
} * </code></pre> * </p> * @see
org.apache.commons.scxml2.env.groovy.GroovyContext#readObject(ObjectInputStream) * @param classResolver custom
class resolver */ public ClassResolver setClassResolver(ClassResolver classResolver) {
ClassResolver old = this.classResolver; this.classResolver =
classResolver; return old; }
fubars javadoc and fails the build..for now i can comment out the <p> and </p>
inside comments to bypass
Suggestions are welcomethanksMartin
______________________________________________
Subject: Re: SCXML project
To: [email protected]
From: [email protected]
Date: Wed, 27 Jan 2016 22:10:50 +0100
On 2016-01-26 22:36, Martin Gainty wrote:
mvn package doesnt package (testcase fails) currently
<testcase name="testSCXMLExecutorTransitions02Sample"
classname="org.apache.commons.scxml2.SCXMLExecutorTest" time="0.03">
<error type="java.lang.NullPointerException:">
java.lang.NullPointerException: null at
org.apache.commons.logging.impl.SLF4JLog.isDebugEnabled(SLF4JLog.java:49) at
org.apache.commons.scxml2.env.SimpleContext.setLocal(SimpleContext.java:178) at
org.apache.commons.scxml2.SCXMLExecutionContext.initializeIOProcessors(SCXMLExecutionContext.java:358)
at
org.apache.commons.scxml2.SCXMLExecutionContext.attachInstance(SCXMLExecutionContext.java:397)
at
org.apache.commons.scxml2.SCXMLExecutor.attachInstance(SCXMLExecutor.java:398)
at
org.apache.commons.scxml2.SCXMLTestHelper.testInstanceSerializability(SCXMLTestHelper.java:258)
at
org.apache.commons.scxml2.SCXMLExecutorTest.testSCXMLExecutorTransitions02Sample(SCXMLExecutorTest.java:139)
correct this small bug lurking in
org.apache.commons.scxml2.env.SimpleContext.java
/**
* Assigns a new value to an existing variable or creates a new one.
* The method allows to shaddow a variable of the same name up the
* Context chain.
*
* @param name The variable name
* @param value The variable value
* @see org.apache.commons.scxml2.Context#setLocal(String, Object)
* as someone forgot to initialize log toss a System.out.println
*/
public void setLocal(final String name, final Object value) {
getVars().put(name, value);
try {
if (log.isDebugEnabled()) {
log.debug(name + " = " + String.valueOf(value));
}
}
catch(NullPointerException npe) {
System.out.println("SimpleContext::setLocal log.isDebugEnabled() where log="+log+"
name="+name+" throws NPE");
}
}
*Obrigado Guilherme*
MartÃn
AFAICT the above NPE only can occur when configuring an invalid/wrong logging
class (like in the pom.xml for the maven-surefire-plugin) and/or through
explicitly set the the Log instance to null in SimpleContext.java.
When using a clean checkout/clone of the current SCXML git repository (master)
this definitely is not the case, and mvn package works just fine.
So possibly you have local modifications, either to the pom.xml logging
configuration or otherwise causing this exception?
Regards, Ate
Date: Mon, 25 Jan 2016 23:42:01 -0200
Subject: Re: SCXML project
From: [email protected]
To: [email protected]
Ok Folks,
I will evaluate SCXML.
BTW, I found these paper and it sounds interesting:
http://cdn.intechopen.com/pdfs-wm/46457.pdf
It looks like it exports Stateflow to SCXML
MG>will Stateflow support Harel FSM?
MG>Please confirmMG>Obrigado!
On Sun, Jan 24, 2016 at 10:32 AM, Martin Gainty <[email protected]> wrote:
+1
Thanks Gary!
Martin Gainty
______________________________________________
Date: Sat, 23 Jan 2016 14:07:08 -0800
Subject: Re: SCXML project
From: [email protected]
To: [email protected]
Guilherme,
I have not seen much activity. We are all volunteers here, if you want
the
project to move forward, feel free to talk on this list, create Jiras,
and
provide patches.
Gary
On Jan 22, 2016 8:58 AM, "Guilherme Silveira" <
[email protected]>
wrote:
Hi Folks
I am new to FSM and new to SCXML. On the other hand, I am expert in
Simulink, expert in Java and expert in model based systems engineering.
I am currently evaluating SCXML and I would like a*honest, non biased
opinion *on the status of SCXML project.
What I would like to assert if this project has a future, the number of
developers, if the SCXML specification will ever reach a stable
status....and so on
So far, I have noticed few integrations with proprietary softwares....
Simulink Stateflow does not export to SCXML, neither does IBM Rhapsody.
How difficult would it be to create custom tool for these
integrations? And
most important, is it REALLY possible to implement in Java all the
functionalities of Simulink Stateflow, without any drawback, with a
friendly user experience and a steep learning curve?
ps: I am not from telecom industry
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
