Re: [VOTE] Release math 2.2 based on RC6

+1 Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, Feb 28, 2011 at 6:56 AM, Dimitri Pourbaix wrote: > Luc, > >> Votes, please. This vote will close in 72 hours, 2011-03-01T20:00:00 UTC >> >> [ ] +1 Release these artifacts >> [ ] +0 OK, but... >> [ ] -0 OK, but real

Re: [VOTE] Release math 2.2 based on RC6

Luc, Votes, please. This vote will close in 72 hours, 2011-03-01T20:00:00 UTC [ ] +1 Release these artifacts [ ] +0 OK, but... [ ] -0 OK, but really should fix... [ ] -1 I oppose this release because... here is my +1. Dim. -

Re: [VOTE] Release math 2.2 based on RC6

+1 Thanks!! Phil On 2/26/11 2:26 PM, Luc Maisonobe wrote: > Tag: > > > All artifacts in Nexus staging repository: >

Re: [VOTE] Release math 2.2 based on RC6

+1 Looks good. Minor comments: - I still get these strange checkstyle errors that the files do not end with newline. - The RAT report on the site looks a bit bloated. It lists 203 unknown licenses. When I build the site locally I get only 12 unknown licenses. Oliver Am 26.02.2011 20:26, schr

Re: [scxml] semantics of nested history in parallel state

Hi, I think I have identified the source of my confusion. I thought that function getChildStates would also return history states, but I believe that this interpretation is incorrect, and leads to a number of conflicts, like the one I already described. I now think that getChildStates would return

[scxml] semantics of nested history in parallel state

Hi, I'm currently working on revising scxml-js so that it implements the semantics defined by the step algorithm of the SCXML specification (as opposed to the mixture of SCXML semantics and Rhapsody semantics which it currently implements). I've run into a part of the step algorithm which is somew

Re: [SITE] Prettify code rendering - alternate way to implement

agreed, but unfortunately I don't have any idea how to do it ATM to avoid it is included in every site, we could upload the prettify.(js|css) in the main site, then refer it always with an absolute link in projects, but to allow users choosing if having it or not, I don't know. What's wrong on ha

Re: [SITE] Prettify code rendering - alternate way to implement

Would it not be reasonable to expect all components to provide code examples? It seems like a shortcoming for a component to exclude examples. Gary On Feb 27, 2011, at 9:05, sebb wrote: > The current skin snapshot template unconditionally includes the code > needed to implement the Google code

[SITE] Prettify code rendering - alternate way to implement

The current skin snapshot template unconditionally includes the code needed to implement the Google code prettifier. This means that all component sites get the code, whether they want it or not. Perhaps a simpler method would be to use the a section in the individual site.xml ? This would als

Re: svn commit: r1074931 - /commons/proper/commons-skin/trunk/src/main/resources/META-INF/maven/site.vm

On 27 February 2011 10:26, Simone Tripodi wrote: > Hi Dennis, > Sebastian copied it from o.a.hc.maven-skin:1.1 because of the brand > requirements, since that work was already done there, it was easier > then reimporting the base skin and modifying it again. I have raised a JIRA against Doxia [1]

[GUMP@vmgump]: Project commons-proxy-test (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This

Re: svn commit: r1074931 - /commons/proper/commons-skin/trunk/src/main/resources/META-INF/maven/site.vm

Hi Dennis, Sebastian copied it from o.a.hc.maven-skin:1.1 because of the brand requirements, since that work was already done there, it was easier then reimporting the base skin and modifying it again. Have a nice weekend, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On

Re: svn commit: r1074931 - /commons/proper/commons-skin/trunk/src/main/resources/META-INF/maven/site.vm

On 2011-02-26 22:25, s...@apache.org wrote: > Author: sebb > Date: Sat Feb 26 21:25:58 2011 > New Revision: 1074931 > > URL: http://svn.apache.org/viewvc?rev=1074931&view=rev > Log: > Replace with copy from o.a.hc.maven-skin:1.1 Why? Is there something missing in the default-site.vm? If so what?

[GUMP@vmgump]: Project commons-scxml-test (in module apache-commons) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project commons-scxml-test has an issue affecting its community integration. This