It hasn’t had activity in over 10 years, but there’s also 
https://commons.apache.org/sandbox/commons-graph/ as a potential component to 
revive.

—
Matt Sicker

> On Apr 27, 2022, at 10:43, Bernd Eckenfels <e...@zusammenkunft.net> wrote:
> 
> I think 20 classes is not small, so probably not good for -lang. But since 
> you already have a List in your API I guess -collections would be ok. (It’s 
> not so good to have your alternative method in ognl).
> 
> But maybe you can share a sandbox project, it’s easier to know what we are 
> talking about.
> 
> I am not sure if we want to have it in for example commons-collections but a 
> Seperate JAR. Would probably only make sense in a sub project which already 
> releases multiple libs.
> 
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> Von: Boo, Guy <g...@informatica.com.INVALID>
> Gesendet: Wednesday, April 27, 2022 5:39:07 PM
> An: Commons Developers List <dev@commons.apache.org>
> Betreff: RE: [lang] how to submit a proposal for a new component?
> 
> My project has no dependencies, and its definition of "graph" is basically 
> java.util.function.Function<X, List<X>>. So the graph doesn't even need to be 
> reified in memory. And it's pretty lightweight - I'd like to do some 
> refactoring, but it currently only has about 20 classes. It's a *very* small 
> set of tools...
> 
> Thanks for your recommendations! I saw -ognl, but wasn't sure that was a good 
> fit as my code would be a tiny subroutine of that project. For example, we 
> have a case where we need to traverse the object graph, but rather than write 
> a separate utility we only define one function to map an object to its fields 
> and all of the existing graph utilities (including graph edits, if a setter 
> function is provided) would be compatible with it.
> 
> I'll look around at your recommendations and see if any of the others may be 
> a better fit, but I suspect my code would be too tiny and off-focus for 
> projects with specific domains like -xpath or -ognl. Maybe collections, but 
> so far I think my best guess is still lang...
> 
> Thanks very much for your help!
> 
> 
> -----Original Message-----
> From: Gary Gregory <garydgreg...@gmail.com>
> Sent: Wednesday, April 27, 2022 23:04
> To: Commons Developers List <dev@commons.apache.org>
> Subject: Re: [lang] how to submit a proposal for a new component?
> 
> Also -scxml
> 
> Gary
> 
>> On Wed, Apr 27, 2022, 11:02 Bernd Eckenfels <e...@zusammenkunft.net> wrote:
>> 
>> Hello Guy,
>> 
>> I think Apache Commons might be a good fit, but it depends a bit on
>> your dependencies.
>> 
>> You could also check -ognl, -xpath or -rdf components, they are all
>> offer similar features.
>> 
>> If you want to traverse POJO then commons-lang might be an option (but
>> then it needs to be leightweigt). If you work with collections, then
>> commons-collections sounds a fit.
>> 
>> Gruss
>> Bernd
>> 
>> 
>> --
>> https://urldefense.com/v3/__http://bernd.eckenfels.net__;!!KpaPruflFCE
>> p!kFRtDx8NdHTdneiVsDnlLvzFeaAjmGzuJ37-qM74sdQGP5If91jryUrPY4WmKfaFsvxV
>> NoUeliw5alVOCYJQwQ$
>> ________________________________
>> Von: Boo, Guy <g...@informatica.com.INVALID>
>> Gesendet: Wednesday, April 27, 2022 4:53:34 PM
>> An: dev@commons.apache.org <dev@commons.apache.org>
>> Betreff: [lang] how to submit a proposal for a new component?
>> 
>> I am extremely sorry if this is spam, but I couldn't find anything on
>> the project page that indicated how to propose new extensions, and I
>> don't even know if lang, math, collections, or a new component would
>> make the most sense. If this is not the appropriate location please
>> just let me know (or ignore this email), thanks!
>> 
>> I'd like to contribute a set of utilities for the definition,
>> traversal, identification, and manipulation of arbitrary graphs. The
>> primary benefit is developer convenience, as it makes it possible to
>> define and execute custom graph operations as succinctly as one can
>> define a for-each loop, even on data structures that do not
>> participate in the package's API. My goal in releasing this to open source 
>> is to see it improved and optimized.
>> 
>> Is Apache commons the appropriate package for this kind of utility? Do
>> I provide the source code first? Should I speak to someone specific
>> rather than spamming the entire mailing list?
>> 
>> Thanks very much!
>> -g
>> 

Reply via email to