I've been playing around with class path scanning lately. I've put
together some code ideas that I'd like to share. The library is located
here:
https://github.com/jwcarman/scaninator
I still have some work to do on specifying exactly what to scan, but I
think there are some good ideas here.
Hi,
On 03/03/2012 02:21, Simone Tripodi wrote:
first of all: yes, I will play with this stuff as soon as I find the time :)
this is scaring... go Orb.io, go! :)
constant), but still there is one more step of indirection. So we would need
to test and compare performances, hopefully with
Good morning Marco,
I had the chance to have a deeper look at your yesterday's night work
and think your additions are good improvements - I just wonder if we
can replace the lock object with the handler itself, referencing
`this` instead.
Thoughts?
best and have a nice WE,
-Simo
Morning Simo,
my doubt is this: opening a synchronized block into handler implementation on
'this', in my opinion is not enough, because the method
CommonsGraph.synchronize() returns a instance of the Proxy and not an
instance of handler.
So an user cannot use the same lock in order to
Hola Claud.io,
* a set of interfaces: e.g. HasWeightedEdges#getWeight(edge),
HasWeightedVertices#getWeight(vertex), etc.
* #1 implementation with external properties: the graph keeps the
mapping between edge/vertex and weight, so that any type can be used
for edges/vertices
* #2
Hi Sebb,
Le 03/03/2012 00:41, sebb a écrit :
On 2 March 2012 00:59, Gilles Sadowski gil...@harfang.homelinux.org wrote:
Hi.
I managed to complete part of the release process:
Tag on SVN:
https://svn.apache.org/repos/asf/commons/proper/math/tags/MATH_3_0_RC1/
Artefacts on Nexus:
Hola Marco,
my doubt is this: opening a synchronized block into handler implementation
on 'this', in my opinion is not enough, because the method
CommonsGraph.synchronize() returns a instance of the Proxy and not an
instance of handler.
true, but *all* methods executions (synchronized
Thomas,
checkstyle is not needed because we are using the one brought by the
plugin (the maven one), you can safety drop it.
thanks,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Sat, Mar 3, 2012
I think it is good to have control over what is actually checked by
checkstyle. Having a customised version is quite common practice also in
other commons components.
I would have preferred you would have discussed first before changing
configurations. Control and customizations, if needed,
Hi,
Apologize but I still don't understand what the benefit is on storing
nodes/arcs data in the Graph data structure
back to James' first email: any type could be immediately used as
edge/vertex without wrappers, while specific data related to the domain
of graphs (weights, labels) would
Am 03.03.2012 14:52, schrieb Simone Tripodi:
I think it is good to have control over what is actually checked by
checkstyle. Having a customised version is quite common practice also in
other commons components.
I would have preferred you would have discussed first before changing
Ciao
rue, but *all* methods executions (synchronized and not) are
performed inside the handler, contained in the proxy instance anyway.
So an user cannot use the same lock in order to synchronize a block
like this:
Let's give you an example.
here is our handler implementation, and
Ciao
sorry I didn't understand very well. How could help a read/write lock?
bye
--
Marco Speranza marco.speranz...@gmail.com
Flickr: http://www.flickr.com/photos/marcosperanza79/
Google Code: http://code.google.com/u/marco.speranza79/
Il giorno 03/mar/2012, alle ore 14:40, James Carman ha
it would allow thread safety without synchronizing readers
On Mar 3, 2012 9:34 AM, Marco Speranza marco.speranz...@gmail.com wrote:
Ciao
sorry I didn't understand very well. How could help a read/write lock?
bye
--
Marco Speranza marco.speranz...@gmail.com
Flickr:
Hi Marco,
yes I know it, what doesn't convince me is not the problem, but the
solution. Have a look at Collections.* source code to see how this
problem is fixed in synchronizedMap.
Anyway that confirms that maybe proxies are not the best to handle
that situation - unless James has a solution
just ro make it clear: nobody vetoed it - did someone expressed a -1?
- I just asked you to discuss it first on ML and rollback *pom*
settings.
thanks
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On
On 03/03/2012 03:55 PM, Simone Tripodi wrote:
just ro make it clear: nobody vetoed it - did someone expressed a -1?
- I just asked you to discuss it first on ML and rollback *pom*
settings.
ok, then I misinterpreted your last post.
Anyway, I did not do any changes in the pom itself, so
Cloud.io,
back to James' first email: any type could be immediately used as
edge/vertex without wrappers, while specific data related to the domain of
graphs (weights, labels) would be handled separately. I actually think this
is useful: back to my days of DIY Java graphs I implemented
Hi Thomas,
sorry for the misunderstanding :(
If it helps, I can point you to
http://maven.apache.org/developers/maven-eclipse-codestyle.xml that
is the Eclipse settings.
best and have a nice WE,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
Yes code will speak volumes. Perhaps a couple proposal branches if we have
incompatible ideas?
On Mar 3, 2012 10:47 AM, Simone Tripodi simonetrip...@apache.org wrote:
Cloud.io,
back to James' first email: any type could be immediately used as
edge/vertex without wrappers, while specific
Hi, if I am allowed to throw in some (unfinished) thoughts into this
discussion:
My preference would also be to keep the actual graph data structure lean
and simple. As James pointed out, if algorithms need additional
information, a function from the vertex/edge type to the target type is
Hi Oliver,
of course that you can, everybody here is invited on giving his
contribution! And every contribution is always much more than
appreciated :)
best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
Hi Simone,
answering briefly below:
Vertex is something we can safety drop because we
know its nature at priori, markers are unnecessary.This is fine.
+1.
what is the sense, at that point, on keeping the Edge?!! It would be
more than enough to know which is the Head and which is the Tail
please follow up code modifications on SANDBOX-404
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Sat, Mar 3, 2012 at 5:11 PM, Claudio Squarcella
squar...@dia.uniroma3.it wrote:
Hi Simone,
answering
hola again,
good observation. My 2 cents: it might still make sense for users to map
their existing domain (including edges) to the graph (e.g. Routers to
Vertices and Cables to Edges) and get it back as soon as they are done
with graph operations (e.g. once they find the shortest path, they
Hi again Marco,
I though once again on this and maybe having a synchronized Graph
would be different than having a ConcurrentGraph, like
Collections.synchronizedMap() and ConcurrentHashMap, so my suggestion
is keeping the synchronized proxy as they are AND provide Concurrent*
version of actual
You're right! The build is OK with Java 6, but not 7.
Thank you!
Gary
On Sat, Mar 3, 2012 at 1:42 PM, Benedikt Ritter b...@systemoutprintln.dewrote:
Hi Gary,
that somehow reminds of a problem we had in BeanUtils2 (see
Hello Commons-Fellowers,
this is meant for us
Cheers,
Christian
On Sat, Mar 3, 2012 at 11:41 PM, Nadia Sokolova
nadia.sokol...@icann.org wrote:
Dear Apache Software Foundation,
I am contacting you in regards to the DomainValidator code in Java that you
have listed at:
We also need to consider k-partite graphs. Not all nodes will be of the
same type.
Sent from tablet device. Please excuse typos and brevity.
On Mar 3, 2012 11:19 AM, Simone Tripodi simonetrip...@apache.org wrote:
hola again,
good observation. My 2 cents: it might still make sense for users
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-digester3 has an issue affecting its community integration.
This
Hello.
Please review the deliverables for Math 3.0.
Tag:
https://svn.apache.org/repos/asf/commons/proper/math/tags/MATH_3_0_RC2/
Site:
http://people.apache.org/builds/commons/math/3.0/RC2/
Binaries:
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-exec-test has an issue affecting its community integration.
This
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-lang3-test has an issue affecting its community integration.
This
Hi Simo,
I will take a look at the thin pom modules.
Right now, I'm working on editing the cookbook so that it contains
examples that include generics. As part of this, I want to create
another module under apps called cookbook-examples. In side of that
module, I would put the source code used
As I've been working on the examples and the documentation for v2 of
chain, I've noticed that the API for exception handling of Command and
Chain is clunky.
When executing a command like:
ProfileContext context = new ProfileContext();
CommandString, Object, ProfileContext command
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
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-configuration-test has an issue affecting its community
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
I hate checked exceptions. +1
On Sat, Mar 3, 2012 at 11:07 PM, Elijah Zupancic eli...@zupancic.name wrote:
As I've been working on the examples and the documentation for v2 of
chain, I've noticed that the API for exception handling of Command and
Chain is clunky.
When executing a command
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-vfs2-test has an issue affecting its community integration.
This
40 matches
Mail list logo
