RE: SCXML project
> Subject: Re: SCXML project > To: user@commons.apache.org > From: a...@douma.nu > Date: Mon, 1 Feb 2016 23:34:39 +0100 > > 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 ... MG>this is a freebie emailer I picked up in 96 whose primary format is HtmL and not plain text MG>for paying work I use mgaint...@gmail.com (I also have mail username on my own site which supports plain text) MG>Thanks Ate > > 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: * >> Here is the code: >> /** * Set custom class resolver callback, or null when no longer needed. * >> * Typically usage: * * 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); * >> } * } * } * * * @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 and inside comments to bypass >> >> Suggestions are welcomethanksMartin >> __ >> >> >> >>> Subject: Re: SCXML project >>> To: user@commons.apache.org >>> From: a...@douma.nu >>> 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 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: guilhermecgss...@gmail.com > To: user@commons.apache.org > > Ok Folks, >
Re: SCXML project
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: * Here is the code: /** * Set custom class resolver callback, or null when no longer needed. * * Typically usage: * * 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); * } * } * } * * * @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 and inside comments to bypass Suggestions are welcomethanksMartin __ Subject: Re: SCXML project To: user@commons.apache.org From: a...@douma.nu 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 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: guilhermecgss...@gmail.com To: user@commons.apache.org 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 wrote: +1 Thanks Gary! Martin Gainty __ Date: Sat, 23 Jan
Re: [JCS]
It is, github is just a mirror. You submit a patch with the Jira if you prefer. Gary On Feb 1, 2016 8:12 AM, "Mat Jaggard" wrote: > Ah, great, I thought JCS was on subversion at > https://svn.apache.org/repos/asf/commons/proper/jcs/ > > On Mon, 1 Feb 2016 at 16:07 Papendieck, Thomas < > thomas.papendi...@opitz-consulting.com> wrote: > > > https://github.com/apache/commons-jcs > > > > create an account on github > > make a fork > > push your changes > > initiate a pull request > > > > bye > > Thomas > > > > -Ursprüngliche Nachricht- > > Von: Mat Jaggard [mailto:apa...@jaggard.org.uk] > > Gesendet: Montag, 1. Februar 2016 16:23 > > An: Commons Users List > > Betreff: [JCS] > > > > Hi, > > I have two patches to fix some problems I had running build and unit > tests > > on JCS 2.0 - who can I give them to? > > > > Thanks, > > Mat. > > >
Re: [JCS]
Ah, great, I thought JCS was on subversion at https://svn.apache.org/repos/asf/commons/proper/jcs/ On Mon, 1 Feb 2016 at 16:07 Papendieck, Thomas < thomas.papendi...@opitz-consulting.com> wrote: > https://github.com/apache/commons-jcs > > create an account on github > make a fork > push your changes > initiate a pull request > > bye > Thomas > > -Ursprüngliche Nachricht- > Von: Mat Jaggard [mailto:apa...@jaggard.org.uk] > Gesendet: Montag, 1. Februar 2016 16:23 > An: Commons Users List > Betreff: [JCS] > > Hi, > I have two patches to fix some problems I had running build and unit tests > on JCS 2.0 - who can I give them to? > > Thanks, > Mat. >
AW: [JCS]
https://github.com/apache/commons-jcs create an account on github make a fork push your changes initiate a pull request bye Thomas -Ursprüngliche Nachricht- Von: Mat Jaggard [mailto:apa...@jaggard.org.uk] Gesendet: Montag, 1. Februar 2016 16:23 An: Commons Users List Betreff: [JCS] Hi, I have two patches to fix some problems I had running build and unit tests on JCS 2.0 - who can I give them to? Thanks, Mat.
[JCS]
Hi, I have two patches to fix some problems I had running build and unit tests on JCS 2.0 - who can I give them to? Thanks, Mat.