(more) easily roll out newer
minor/patch releases thereafter for improved js language support if and
when we get that incorporated.
Regards,
Ate
Let me know what you think. Thank you,
Jake
On Apr 18, 2019, at 3:46 PM, Ate Douma wrote:
On 18/04/2019 18.00, Jacob Beard wrote:
Hi Ate,
On A
On 18/04/2019 18.00, Jacob Beard wrote:
Hi Ate,
On Apr 18, 2019, at 11:23 AM, Ate Douma wrote:
Only for the javascript language (using Java 8 Nashorn, now deprecated
since Java 11...) there are still 3/188 W3C IRP tests failing.
And those 3 test failures are really, really difficult to
Hi developers/community,
I've received an out-of-band request about the current status of
commons-scxml-2.0 and its release schedule.
As there might be more (hopefully at least a few) people interested in
this, and I don't like answering out-of-band questions, I'm giving
a heads-up here for the
On 2016-02-02 12:43, Gilles wrote:
On Mon, 1 Feb 2016 10:06:40 -0700, Phil Steitz wrote:
Please select your top choice among the following suggested names
for the new [math]-based TLP. All are welcome and encouraged to
respond. This POLL will be open for 72 hours, at which time two
tallies wil
+1
Ate
On 2016-01-16 16:18, Phil Steitz wrote:
The discussion has thus far been generally favorable. I would like
therefore to put the proposal to split [math] out into a separate
TLP to a VOTE. Assuming a favorable vote, we can discuss how to go
about doing it. Votes, please. All are welco
We'll now make a start with executing on the below proposal, moving to Java 8
first and then introducing JSON datamodel support to replace and drop XML/XPath
datamodel thereafter.
Regards, Ate
On 2015-12-09 10:15, Ate Douma wrote:
Since early this year the progress and development of Co
uming
lazy consensus otherwise), we would like to start on these changes shortly,
before the end of the year.
Kind regards,
Ate Douma
Woonsan Ko
[1] http://www.w3.org/TR/2015/REC-scxml-20150901/
-
To unsubscribe, e-mail: de
Sorry for the too late response, but I would have voted +1 too :)
Ate
On 2015-07-08 20:27, Woonsan Ko wrote:
Apache Commons Developers,
This VOTE has passed with the following votes:
+1 Dave Brosius
+1 James Carman (PMC)
+1 Gary Gregory (PMC)
+1 Woonsan Ko
Thank you all f
Dave,
Thanks for detecting and fixing the potential NPE below, much appreciated!
But your fix had a potential functional side-effect, which I now fixed in
http://svn.apache.org/r1621831
Maybe it would be good if you (or whoever) applies such micro fixes to also send
a heads-up to the dev@ lis
Hi all,
Sorry for chiming in this late but I definitely think it would be cool, and very
useful, to organize a dedicated Commons track at the ApacheCon, and promote this
project as a whole.
Siegfried and I discussed this a bit in Denver, and I also talked about it with
Rich Bowen if a specia
SCXML developers,
I've just created the second Commons SCXML 2.0-M1 milestone tag on the roadmap
towards Commons SCXML 2.0 [1].
This milestone incorporates some major (and drastic) changes, and completely
replaces the old SCXMLSemantics with a new implementation which now is fully
compliant
Darn.
Thanks for spotting this Matt.
I actually did have a commit message prepared but must have either forgotten to
paste it in or something else went wrong there.
I'll update the revision log right away.
Thanks again, Ate
On 23-03-14 05:34, Matt Benson wrote:
Ate,
It would probably be n
SCXML developers,
I've just created a first Commons SCXML 2.0-M0 milestone tag as baseline for the
roadmap [1] towards Commons SCXML 2.0.
Please read the roadmap for further details.
It would be great if you can test this first baseline to validate everything is
still working as expected, for
On 11-03-14 12:24, sebb wrote:
On 11 March 2014 09:11, Ate Douma wrote:
On 11-03-14 01:00, Gary Gregory wrote:
IMO, if you make artifacts available through MC, then it is a "release",
whatever you label it, alpha, beta, milestone, and so on, which requires a
VOTE.
Right. Alth
On 11-03-14 10:11, Ate Douma wrote:
On 11-03-14 01:00, Gary Gregory wrote:
IMO, if you make artifacts available through MC, then it is a "release",
whatever you label it, alpha, beta, milestone, and so on, which requires a
VOTE.
Right. Although in my book at the ASF we only formal
se an SVN
revision # or a tag for a more developer oriented milestone marker.
Gary
On Mon, Mar 10, 2014 at 6:52 PM, Ate Douma wrote:
Hi,
I just published a high-level roadmap plan towards SCXML 2.0 [1]
Part of that plan, which consists of working through a set of milestone
targets, is also tag
Hi,
I just published a high-level roadmap plan towards SCXML 2.0 [1]
Part of that plan, which consists of working through a set of milestone targets,
is also tagging these milestones "as is", see [2].
As I also described there, these milestone tags will "not represent a formal
release and th
ortly...
Regards, Ate
On 27-02-14 14:46, Matt Benson wrote:
On Feb 27, 2014 4:35 AM, "Ate Douma" wrote:
On 27-02-14 11:30, Benedikt Ritter wrote:
Hello Ate,
without knowing SCXML or the specs here are my thought about your
proposals
(just from a apache commons point of view ;-):
On 02-03-14 00:02, a...@apache.org wrote:
Author: ate
Date: Sat Mar 1 23:02:28 2014
New Revision: 899664
Log:
Site checkin for project Apache Commons SCXML
This turned out to be an unexpected large site checkin ...
I only fixed a few menu items, so I expected a minor update.
Turned out, the
:00 Ate Douma :
On 27-02-14 13:36, Benedikt Ritter wrote:
Hi,
I've worked on the website today. It uses the new design now.
I've fixed
some broken links also. If you find anything that's not
working, just
drop
me a message.
Wow, many thanks!
It looks great
On 27-02-14 13:36, Benedikt Ritter wrote:
Hi,
I've worked on the website today. It uses the new design now. I've fixed
some broken links also. If you find anything that's not working, just drop
me a message.
Wow, many thanks!
It looks great and 'refreshed' :)
After only a quick check I see th
On 27-02-14 11:30, Benedikt Ritter wrote:
Hello Ate,
without knowing SCXML or the specs here are my thought about your proposals
(just from a apache commons point of view ;-):
2014-02-27 0:48 GMT+01:00 Ate Douma :
Hi SCXML and other community members/developers,
After working on the new
Hi SCXML and other community members/developers,
After working on the new Commons SCXML 2.0 code base for a few months, doing
some cleaning up and providing minor fixes and improvements, I think we now need
some more serious and drastic changes...
The goal (as it always has been) for Commons
On 01/24/2014 04:20 PM, Gary Gregory wrote:
Hi All,
Please give a warm welcome to Duncan Jones, our latest committer.
Welcome aboard Duncan!
Welcome Duncan!
Regards, Ate
Gary
-
To unsubscribe, e-mail: dev-unsubscr...@
ks, Ate
p.s: I've no idea who manages the Continuum build configurations for Commons.
Original Message
Subject: [jira] [Created] (SCXML-188) OpenJDK 1.6 Rhino ScriptEngine error
causes JSEvaluationTest to fail
Date: Mon, 20 Jan 2014 16:04:22 + (UTC)
From: Ate Douma (JIRA)
On 12/05/2013 11:26 PM, Woonsan Ko wrote:
Hi,
The current code is taking care of 'src' attribute for state, parallel, assign
and invoke element.
Invoke element should still accept 'src' attribute, but it seems to have been
removed for the other elements in the current specification.
The src
Woonsan, Bernd,
To be able to edit the wiki, you'll need to provide your Wiki username.
A Wiki username should be a *wiki* name, e.g. 'Woonsan Ko' AFAIK isn't a
qualified one, but something like WoonsanKo would.
Then, someone with the right permissions (someone on the AdminGroup) can add you
Sebb,
Was the bump to commons-el 1.0.1-SNAPSHOT intentional, and if so can you explain
why?
In general I prefer not depending on external SNAPSHOT dependencies if not
absolutely needed. And in this case it actually caused the tests to fail.
For now I've reverted back to commons-el 1.0.
Regar
On 10/16/2013 09:36 AM, Jörg Schaible wrote:
Hi Ate,
Ate Douma wrote:
On 10/16/2013 08:54 AM, Jörg Schaible wrote:
It seems it is unnecessary for committers to be added here, otherwise I
would not have been able to add myself.
I don't think so. AFAIK the moinmoin security is not
On 10/16/2013 08:54 AM, Jörg Schaible wrote:
It seems it is unnecessary for committers to be added here, otherwise I
would not have been able to add myself.
I don't think so. AFAIK the moinmoin security is not wired into the ASF LDAP
security system, except maybe for (root) admins.
The moin
On 10/15/2013 10:31 AM, Torsten Curdt wrote:
I monitor commits, rarely check JIRA, follow and sometimes answer mails and
close to never develop code for that component anymore - maybe once or
twice a year when I go through JIRAs.
Now what?
I appreciate the initiative but don't see this working
Hi SCXML community,
I'd like to propose dropping Ant build support for the next major SCXML version
1.0, which development now has been reactivated on trunk.
Both Woonsan and myself are 'Maven' adepts, and have no use nor interest in
maintaining and updating/fixing the already outdated Ant bu
On 10/14/2013 09:33 PM, Mark Thomas wrote:
On 14/10/2013 20:27, Ate Douma wrote:
On 10/14/2013 09:23 PM, Ate Douma wrote:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in
JIRA for at
least Commons SCXML so we can start picking up and assigning issues
On 10/14/2013 09:23 PM, Ate Douma wrote:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Forgot to mention my ASF JIRA handle is: adouma
and for Woonsan: woon_san
Thanks
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Thanks, Ate
-
To unsubscribe, e-mail: dev-unsubscr...@common
Can someone add my wiki name (AteDouma) to the Contributors Group page [1]?
Thanks, Ate
[1] https://wiki.apache.org/commons/ContributorsGroup
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands,
Thank you all for the trust and the warm welcome!
Regards, Ate
On 10/14/2013 07:51 PM, Luc Maisonobe wrote:
Hi all,
Please welcome Ate Douma and Woonsan Ko as a new committers of the
Apache Commons project. The Commons PMC has voted to grant committership
to them and they accepted.
Both
e released code in a < 1.0
version number. So, the artifact/package will have to be scxml1,
which looks funky IMHO. I guess that follows the pattern, though.
On Thu, Oct 10, 2013 at 7:49 PM, Ate Douma wrote:
On 10/11/2013 01:41 AM, James Carman wrote:
If you are breaking backward compatib
confluence/display/MAVENOLD/Versioning
[2]
http://maven.apache.org/ref/3.0.4/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
On Thu, Oct 10, 2013 at 9:25 AM, Ate Douma wrote:
On 10/10/2013 03:00 PM, James Carman wrote:
On Thu, Oct 10, 2013 at 8:35 AM, Gary Gregory
wr
'll have to bump the major version anyway.
On Thursday, October 10, 2013, Ate Douma wrote:
On 10/11/2013 01:16 AM, Emmanuel Bourg wrote:
Commons SCXML has only one reverse dependency in Maven Central,
flexistate, so I wouldn't bother with the binary compatibility and just
keep the pac
On 10/11/2013 01:16 AM, Emmanuel Bourg wrote:
Commons SCXML has only one reverse dependency in Maven Central,
flexistate, so I wouldn't bother with the binary compatibility and just
keep the package as is.
Hmm. That might be the only reverse dependency of artifacts also deployed to
Maven Centr
On 10/10/2013 09:39 PM, Rahul Akolkar wrote:
On Thu, Oct 10, 2013 at 7:26 AM, Ate Douma wrote:
Case in point: SCXML
If we are allowed to start working on this component shortly, we intend to,
and HAVE to switch to a 1.0 version first, as there already is a 0.9 version
release out, while we
On 10/10/2013 04:31 PM, James Carman wrote:
On Thu, Oct 10, 2013 at 10:19 AM, Ate Douma wrote:
I'm a bit unfamiliar yet with the 'rules' within Commons concerning such
changes. I'm willing to create an issue for this and draft up a
documentation patch for it, but may
ing to create an issue for this and draft up a documentation
patch for it, but maybe this needs formal voting by the PMC first?
Thanks, Ate
On Thu, Oct 10, 2013 at 10:06 AM, Gary Gregory wrote:
On Thu, Oct 10, 2013 at 9:55 AM, Ate Douma wrote:
On 10/10/2013 03:47 PM, Gary Gregory wrote:
On 10/10/2013 04:06 PM, Gary Gregory wrote:
On Thu, Oct 10, 2013 at 9:55 AM, Ate Douma wrote:
On 10/10/2013 03:47 PM, Gary Gregory wrote:
On Thu, Oct 10, 2013 at 9:06 AM, James Carman
wrote:
On Thu, Oct 10, 2013 at 8:25 AM, Emmanuel Bourg
wrote:
I'm afraid this is more t
On 10/10/2013 03:47 PM, Gary Gregory wrote:
On Thu, Oct 10, 2013 at 9:06 AM, James Carman
wrote:
On Thu, Oct 10, 2013 at 8:25 AM, Emmanuel Bourg wrote:
I'm afraid this is more than a perceived issue, the plexus-container
example given by Jörg is a very good one. Pushing drastically
incompati
On 10/10/2013 03:00 PM, James Carman wrote:
On Thu, Oct 10, 2013 at 8:35 AM, Gary Gregory wrote:
I think "milestone" releases works if you have a clear development
plan and schedule. I've never seen it be the case in Commons. Calling
"releases" to Maven and dist, Alphas and Betas make more sens
On 10/10/2013 03:06 PM, James Carman wrote:
On Thu, Oct 10, 2013 at 8:25 AM, Emmanuel Bourg wrote:
I'm afraid this is more than a perceived issue, the plexus-container
example given by Jörg is a very good one. Pushing drastically
incompatible versions to Maven Central is not a good service for
On 10/10/2013 01:36 PM, Emmanuel Bourg wrote:
Le 10/10/2013 13:26, Ate Douma a écrit :
Thoughts?
A solution could be to change the package for every preview release.
Something like:
org.apache.commons.experimental.
So, for CSV we could release a 0.8 and 0.9 version under the packages
Sigh, typical mistake of forgetting to provide the link referenced further
below:
[1] http://commons.apache.org/releases/versioning.html#Milestone_Releases
On 10/10/2013 01:26 PM, Ate Douma wrote:
I've move this into a separate [DISCUSS] thread as I think it needs separate
discussion.
good example is [csv]. I would
have no problem with releasing the current trunk as 0.9. At the moment [csv] is
just another component we don't releaese because we want to come up with a
perfect API (and I take responsibility for that :-)
Benedikt
Send from my mobile device
Am 10.10.2013 um
On 10/10/2013 12:24 AM, Torsten Curdt wrote:
Every now and then I keep getting requests via private mail asking to
release javaflow as it seems to be working for people. Yet I know there is
still so much essential stuff to fix for a 1.0 release.
Crossing over to the other thread: I know on githu
ose important changes first, so you still be able to
chime in any time you feel like it.
And knowing you'll still be lurking is cool: we'll assume no feedback as a good
sign then :)
Thanks and regards, Ate
On Mon, Oct 7, 2013 at 10:40 AM, Ate Douma wrote:
Hi SCXML developers/com
On 10/07/2013 11:59 PM, Phil Steitz wrote:
On Oct 7, 2013, at 2:15 PM, Emmanuel Bourg wrote:
Le 07/10/2013 20:30, Phil Steitz a écrit :
Great. We give sandbox commit to any ASF committer. Reply with
your availIds and we can get that done immediately. Commit to
commons proper requires a
states.
We definitely will need good performance too, with the least possible overhead.
I'm looking forward to work on this together.
Regards, Ate
Cheers
On 10/07/2013 10:23 PM, Ate Douma wrote:
On 10/07/2013 09:52 PM, Juan Antonio Breña Moral wrote:
Hi Great Idea.
In my case I could
On 10/07/2013 08:14 PM, Benedikt Ritter wrote:
Hi,
since we have discussed a lot of different aspects, it may be time to sum
things up a bit (please correct me or add things I've missed):
Release Management - Releases take too long
- Build is overly complex
- dependencies to parent pom seem to
hanks, Ate
Juan Antonio
On 10/07/2013 08:30 PM, Phil Steitz wrote:
On 10/7/13 7:40 AM, Ate Douma wrote:
Hi SCXML developers/community,
We are trying to figure out what the status and activity of SCXML
development is, and and/or who in the community might be
interested in re-activating it.
On 10/07/2013 08:30 PM, Phil Steitz wrote:
On 10/7/13 7:40 AM, Ate Douma wrote:
Hi SCXML developers/community,
We are trying to figure out what the status and activity of SCXML
development is, and and/or who in the community might be
interested in re-activating it.
From the mailing lists and
, Ate
[1] http://markmail.org/message/kvclice322ea45yh
2013/10/7 Ate Douma
Hi SCXML developers/community,
We are trying to figure out what the status and activity of SCXML
development is, and and/or who in the community might be interested in
re-activating it.
From the mailing lists and J
Hi SCXML developers/community,
We are trying to figure out what the status and activity of SCXML development
is, and and/or who in the community might be interested in re-activating it.
From the mailing lists and JIRA activity we gather not much has been happening
here for a very long time: t
Mark Thomas wrote:
Ate Douma wrote:
Mark Thomas wrote:
I have seen similar issues in Tomcat's internal logging with
java.util.logging, log4j and commons-logging. Why will this be any
different with slf4j?
Because sfl4j does not use the ContextClassLoader to determine the
logger instanc
Hi John,
While your example proxy solution is nice enough by itself, imo its way too
much over-engineering for the issue at hand.
We're trying to get rid of the ContextClassLoader use for *only* the logging,
not add more overhead to it!
And, in practice this solution wouldn't work for us anyway
Mark Thomas wrote:
Ate Douma wrote:
When Pluto needs to "aggregate" the content of this TestPortlet, it
invokes it render(PortletRequest, PortletResponse) method using a
"cross-context" call from the Pluto web application to the "test" web
application.
The TestPort
Date: April 20, 2009 1:47:42 PM PDT
To: pluto-...@portals.apache.org
Subject: Re: commons-logging unsuited for cross-context webapplication
invocation usage - migrating to slf4j?
Reply-To: pluto-...@portals.apache.org
Reply-To: pluto-...@portals.apache.org
+1 to SLF4J several Jasig projects are also l
64 matches
Mail list logo