Done
On Sun, 22 Oct 2023 at 14:40, Rob Tompkins wrote:
>
> +1
>
> > On Oct 21, 2023, at 7:46 PM, Gary Gregory wrote:
> >
> > Seems reasonable to me.
> >
> > Gary
> >
> > On Sat, Oct 21, 2023, 6:49 PM sebb wrote:
> >
> >> Rev
+1
> On Oct 21, 2023, at 7:46 PM, Gary Gregory wrote:
>
> Seems reasonable to me.
>
> Gary
>
> On Sat, Oct 21, 2023, 6:49 PM sebb wrote:
>
>> Reviving this thread.
>>
>> I think we should now change chain to dormant.
>>
>> Sebb
Seems reasonable to me.
Gary
On Sat, Oct 21, 2023, 6:49 PM sebb wrote:
> Reviving this thread.
>
> I think we should now change chain to dormant.
>
> Sebb
>
> On Sun, 8 Oct 2017 at 16:10, Pascal Schumacher
> wrote:
> >
> > Looks like Apache Tiles 3 does not
+1
On Sun, 22 Oct 2023 at 00:48, sebb wrote:
> Reviving this thread.
>
> I think we should now change chain to dormant.
>
> Sebb
>
> On Sun, 8 Oct 2017 at 16:10, Pascal Schumacher
> wrote:
> >
> > Looks like Apache Tiles 3 does not use commons-chain.
> &g
Reviving this thread.
I think we should now change chain to dormant.
Sebb
On Sun, 8 Oct 2017 at 16:10, Pascal Schumacher wrote:
>
> Looks like Apache Tiles 3 does not use commons-chain.
>
> The only mention of commons-chain I could find in
> https://github.com/apache/tiles/tr
t; On Sun, Oct 23, 2022, 14:34 Gary Gregory wrote:
>
>>
>> [image: GitHub] [apache/commons-csv] Scorecards supply-chain security
>> workflow run, Attempt #2
>>
>> Scorecards supply-chain security, Attempt #2: All jobs have failed
>>
>> View workfl
ecards supply-chain security
> workflow run, Attempt #2
>
> Scorecards supply-chain security, Attempt #2: All jobs have failed
>
> View workflow run
> <https://github.com/apache/commons-csv/actions/runs/3308068828>
>
> [image: Scorecards analysis]
>
> *Sc
hi,
is someone able to review this pr please.
https://github.com/apache/commons-chain/pull/3
It's the last commons project that doesn't have a .gitignore file. My
other pr's adding a .gitignore have either been merged or someone
noticed and added one themselves
Looks like Apache Tiles 3 does not use commons-chain.
The only mention of commons-chain I could find in
https://github.com/apache/tiles/tree/trunk was an exclusion a of
transitive commons-chain dependency.
https://tiles.apache.org/framework/tiles-compat/dependencies.html also
does not list
What’s the largest project that depends upon it? Apache “Tiles” seems to.
-Rob
> On Oct 8, 2017, at 9:44 AM, Benedikt Ritter wrote:
>
>
>
>> Am 07.10.2017 um 12:35 schrieb Pascal Schumacher :
>>
>> Hello everybody,
>>
>> the last commons-chain re
> Am 07.10.2017 um 12:35 schrieb Pascal Schumacher :
>
> Hello everybody,
>
> the last commons-chain release is from 2008.
>
> The last bugfix/feature commits are from 2013.
>
> Since 2013 only one bugfix/feature released issue was created in JIRA.
>
> Maybe
Are there any bug fixes that could be released first?
Gary
On Oct 7, 2017 04:35, "Pascal Schumacher" wrote:
> Hello everybody,
>
> the last commons-chain release is from 2008.
>
> The last bugfix/feature commits are from 2013.
>
> Since 2013 only one bugfix/fea
Hello everybody,
the last commons-chain release is from 2008.
The last bugfix/feature commits are from 2013.
Since 2013 only one bugfix/feature released issue was created in JIRA.
Maybe it is time to move the component to dormant?
What do you think?
-Pascal
Hello Manfred.
> Am 19.09.2017 um 09:03 schrieb Manfred Wolff :
>
> Hi everybody
>
> In the early 2000 I used to use commons chain very often. The approach is
> nice: Small pieces of software, well testable, configurable via XML or
> Spring, what ever.
>
> I ha
Hi everybody
In the early 2000 I used to use commons chain very often. The approach is nice:
Small pieces of software, well testable, configurable via XML or Spring, what
ever.
I have an own framework, modern implemented with generics, and I wonder if the
"commons" community is int
DER.html
> release/commons/betwixt/HEADER.html
> release/commons/chain/HEADER.html
> release/commons/cli/HEADER.html
> release/commons/collections/HEADER.html
> release/commons/configuration/HEADER.html
> release/commons/csv/HEADER.html
> release/commo
FYI, for anyone maintaining the site, the javadoc is not present from the
site's links.
--
Cheers,
Paul
Comment: developed at->developed by
Files changed:
/commons/proper/chain/trunk/dist/src/main/assembly/NOTICE-with-deps.txt (
1534730 )
Dependencies Changes:
***
Hi Lin,
I've worked on it a while back. But at the moment there is no development
activity.
Benedikt
2013/11/14 Lin Di
> does it have anybody developing Apache Chain?
>
> --
> Lin Di
> lindib...@gmail.com
>
--
http://people.apache.org/~britter/
http://www.sy
does it have anybody developing Apache Chain?
--
Lin Di
lindib...@gmail.com
"2.6.32-41-server" arch: "amd64" Family:
"unix"
SCM Changes:
Changed: simonetripodi @ Mon 8 Jul 2013 16:53
"2.6.32-41-server" arch: "amd64" Family:
"unix"
SCM Changes:
Changed: britter @ Sat 15 Jun 2013 11:53:34 +
C
2013/7/5 sebb
> On 5 July 2013 08:13, Benedikt Ritter wrote:
> > Hi,
> >
> > since I got no replies, I'm moving this to a new thread to get some more
> > attention ;-)
> >
> > I'm having a problem with Contiuum. This all started, when I added
On 5 July 2013 08:13, Benedikt Ritter wrote:
> Hi,
>
> since I got no replies, I'm moving this to a new thread to get some more
> attention ;-)
>
> I'm having a problem with Contiuum. This all started, when I added a new
> module to [CHAIN], a test-utils modu
Hi,
since I got no replies, I'm moving this to a new thread to get some more
attention ;-)
I'm having a problem with Contiuum. This all started, when I added a new
module to [CHAIN], a test-utils module, that contains code used for testing
used across the other modules.
Shortly
Oh, no blame taken. I'm actually really excited about all of the changes.
Unfortunately, I've been missing for a while due to increased work
responsibilities.
The changes are all things way beyond what I was initially envisioning as a
2.0. What led me to contribute was that I was using
_21 ;)
>>
>> Gary
>>
>>
>> On Tue, Jun 25, 2013 at 3:10 PM, Benedikt Ritter wrote:
>>
>>> Hi,
>>>
>>> when building [CHAIN] trunk with:
>>>
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-0
enigmas that I encountered, however if you look at the
> date of the original project I don't think it is unusual.
>
Thanks for the insights! My mail was not intended to blame you. You did
great work on chain.
Would be great if you could manage to share your thoughts about the
upcoming design
their own states if needed?
>
> Thanks,
> -Elijah
>
>
> On Sat, Jun 22, 2013 at 4:30 AM, Benedikt Ritter >wrote:
>
> >
> > Am 22.06.2013 um 12:57 schrieb Simone Tripodi >:
> >
> > > Hi Jonas,
> > >
> > >>
> > >> I will
one Tripodi :
>
> > Hi Jonas,
> >
> >>
> >> I will provide a patch for
> >> CHAIN-98<https://issues.apache.org/jira/browse/CHAIN-98>tomorow. The
> >> patch will only cover the refactoring of CONTINUE and
> >> COMPLETED processing results.
>
luck,
-Elijah
On Tue, Jun 25, 2013 at 11:24 AM, Benedikt Ritter wrote:
> I have created CHAIN-101 [1]
>
> Benedikt
>
> [1] https://issues.apache.org/jira/browse/CHAIN-101
>
> Am 24.06.2013 um 20:57 schrieb Adrian Crum <
> adrian.c...@sandglass-software.com>:
>
And the properties have been changed to the standard maven.compileR.*
(lower case though!)
On 25 June 2013 20:17, Gary Gregory wrote:
> OT: you should be using Java 7 _25, not _21 ;)
>
> Gary
>
>
> On Tue, Jun 25, 2013 at 3:10 PM, Benedikt Ritter wrote:
>
>> Hi,
>&g
OT: you should be using Java 7 _25, not _21 ;)
Gary
On Tue, Jun 25, 2013 at 3:10 PM, Benedikt Ritter wrote:
> Hi,
>
> when building [CHAIN] trunk with:
>
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 14:51:28+0100)
> Maven home: /Applicat
Hi,
when building [CHAIN] trunk with:
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
14:51:28+0100)
Maven home: /Applications/dev/maven/apache-maven-3.0.5
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk
I have created CHAIN-101 [1]
Benedikt
[1] https://issues.apache.org/jira/browse/CHAIN-101
Am 24.06.2013 um 20:57 schrieb Adrian Crum :
> I have always preferred the "has-a" approach over the "is-a" approach. It
> makes things easier to refactor down the road.
>
I have always preferred the "has-a" approach over the "is-a" approach.
It makes things easier to refactor down the road.
-Adrian
On 6/24/2013 7:30 PM, Benedikt Ritter wrote:
Hi,
I just wonder why ContextMap inherits from ConcurrentHashMap. This seems like
an unnecessary restriction. The cont
Hi,
I just wonder why ContextMap inherits from ConcurrentHashMap. This seems like
an unnecessary restriction. The context interface makes explicit, that
implementations do not have to be thread safe. Beside that we loose all thread
safety a ConcurrentHashMap provides with our not-so-thread-safe
Am 22.06.2013 um 12:57 schrieb Simone Tripodi :
> Hi Jonas,
>
>>
>> I will provide a patch for
>> CHAIN-98<https://issues.apache.org/jira/browse/CHAIN-98>tomorow. The
>> patch will only cover the refactoring of CONTINUE and
>> COMPLETED processing re
Hi Jonas,
>
> I will provide a patch for
> CHAIN-98<https://issues.apache.org/jira/browse/CHAIN-98>tomorow. The
> patch will only cover the refactoring of CONTINUE and
> COMPLETED processing results.
>
nice to read that, looking forward to the patch! :)
> But, I do no
Hi Simone,
more meat as I expected, thats for sure.
I will provide a patch for
CHAIN-98<https://issues.apache.org/jira/browse/CHAIN-98>tomorow. The
patch will only cover the refactoring of CONTINUE and
COMPLETED processing results.
But, I do not understand how exceptions should be hand
> I'm not sure if we need ABORTED. What is the difference between COMPLETE
> and ABORTED from the PoV of the Chain? Chain defines an algorithm for
> processing and I currently don't see how ABORTED fits in there.
>
OTOH I see some potential here:
* COMPLETE: all chain c
Hi guys,
> >
> > so we talk about an enum 'PROCESSING' providing at least 3 states?
> >
> > - CONTINUE
> > - COMPLETE
> > - ABORTED
>
Hi,
I'm not sure if we need ABORTED. What is the difference between COMPLETE
and ABORTED from the PoV of the Chai
tes?
>
> - CONTINUE
> - COMPLETE
> - ABORTED
>
> Ticket CHAIN-98 <https://issues.apache.org/jira/browse/CHAIN-98> has been
> created to cover this task.
>
> regards,
> Jonas
>
> 2013/6/20 Simone Tripodi
>
>> Hallo Bene,
>>
>> > * JavaDo
Hi guys,
so we talk about an enum 'PROCESSING' providing at least 3 states?
- CONTINUE
- COMPLETE
- ABORTED
Ticket CHAIN-98 <https://issues.apache.org/jira/browse/CHAIN-98> has been
created to cover this task.
regards,
Jonas
2013/6/20 Simone Tripodi
> Hallo Bene,
Hallo Bene,
> * JavaDoc of Command says that commands have to be designed in a
> thread-safe manner, yet all the base implementations are not thread safe! I
> have created CHAIN-96 [1] for this, because this definitely has to be fixed
> before 2.0
+1
> * The same is true for o.a
have created CHAIN-96 [1] for this, because this definitely has to be fixed
before 2.0
* The same is true for o.a.c.chain2.Chain and its base implemenation. For
example there is a race condition in o.a.c.chain2.impl.ChainBase.add(CMD).
The method first checks the forzen flag and then acts... An
2013/6/18 Benedikt Ritter
> Hi guys,
>
> I recently fixed CHAIN-92 [1] but I just realized that I've probably
> broken the nightly build. From what I can see the new module
> (commons-chain2-test-utils is not published to the snapshot repository. Can
> anybody point me to
I have created CHAIN-95 [1] for this, since I don't have the time to think
this through right now :-)
Benedikt
[1] https://issues.apache.org/jira/browse/CHAIN-95
2013/6/19 Simone Tripodi
> Nice thought, feel free to give a try - I'd use the
> observer/observable pattern f
a CopyCommand that copies a value from one key to another
>>>> * an OverrideCommand, that overrides a value with a provided value.
>>>
>>> We could even extract a RemoveCommand from CopyCommand. A RemoveCommand
>>> simply removes getKey() from the context.
>>
ExceptionHandler to Chain. It would look like
> the following:
>
> public interface ExceptionHandler> {
>
> /**
> * Tries to handle the given exception that was thrown during chain
> execution.
> *
> * @return tru
Hi guys,
I recently fixed CHAIN-92 [1] but I just realized that I've probably broken the
nightly build. From what I can see the new module (commons-chain2-test-utils is
not published to the snapshot repository. Can anybody point me to docs what I
have to do to enable this? I thought add
s two commands:
>>>
>>> * a CopyCommand that copies a value from one key to another
>>> * an OverrideCommand, that overrides a value with a provided value.
>>
>> We could even extract a RemoveCommand from CopyCommand. A RemoveCommand
>> simply re
Am 18.06.2013 um 09:40 schrieb Emmanuel Bourg :
> Le 18/06/2013 09:24, Benedikt Ritter a écrit :
>
>>> commons/proper/chain/trunk/base/src/test/java/org/apache/commons/chain2/impl/NonDelegatingFilter.java
>>>commons/proper/chain/trunk/test-utils/test-utils.iml
>
Le 18/06/2013 09:24, Benedikt Ritter a écrit :
>> commons/proper/chain/trunk/base/src/test/java/org/apache/commons/chain2/impl/NonDelegatingFilter.java
>> commons/proper/chain/trunk/test-utils/test-utils.iml
>>
>
> whoops, that one doesn't belong there... I
2013/6/16
> Author: britter
> Date: Sun Jun 16 17:09:33 2013
> New Revision: 1493534
>
> URL: http://svn.apache.org/r1493534
> Log:
> CHAIN-92 - Create a new module containing common test code and utilities;
> move common commands used in tests to new module
>
> A
o another
>> * an OverrideCommand, that overrides a value with a provided value.
>
> We could even extract a RemoveCommand from CopyCommand. A RemoveCommand
> simply removes getKey() from the context.
I have created CHAIN-91 [1] for this. If no one objects, I'll implement this
to
Hi,
I'm thinking about adding an ExceptionHandler to Chain. It would look like the
following:
public interface ExceptionHandler> {
/**
* Tries to handle the given exception that was thrown during chain
execution.
*
* @return true if the handler was
Am 14.06.2013 um 22:36 schrieb Benedikt Ritter :
> Hi,
>
> the o.a.c.chain2.generic.CopyCommand IMHO really implements two commands:
>
> * a CopyCommand that copies a value from one key to another
> * an OverrideCommand, that overrides a value with a provided value.
We could even extract a Rem
"2.6.32-41-server" arch: "amd64" Family:
"unix"
SCM Changes:
Changed: britter @ Fri 14 Jun 2
Hi,
the o.a.c.chain2.generic.CopyCommand IMHO really implements two commands:
* a CopyCommand that copies a value from one key to another
* an OverrideCommand, that overrides a value with a provided value.
What do you think about splitting this up into two separate classes?
Regards,
Benedikt
-
"2.6.32-41-server" arch: "amd64" Family:
"unix"
SCM Changes:
Changed: britter @ Fri 14 Jun 2013 18:41:09 +00
Comment: Remove unneeded hyphens in JavaDoc
Files changed:
/commons/proper/chain/trunk/configuration/api/src/main/java/org/apache/commons/chain2/config/ConfigParser.java
( 1493152 )
/commons/proper/chain/trunk/configuration/xml/src/main/java/org/apache/com
Jun 13 19:50:01 2013
>> New Revision: 1492833
>>
>> URL: http://svn.apache.org/r1492833
>> Log:
>> Pull up common methods in abstract base class
>>
>> Added:
>>
>> commons/proper/chain/trunk/configuration/xml/src/test/java/org/apache/commons
"2.6.32-41-server" arch: "amd64" Family:
"unix"
SCM Changes:
Changed: britter @ Thu 13 Jun 2013 20:32:1
nedikt
Am 13.06.2013 um 21:50 schrieb brit...@apache.org:
> Author: britter
> Date: Thu Jun 13 19:50:01 2013
> New Revision: 1492833
>
> URL: http://svn.apache.org/r1492833
> Log:
> Pull up common methods in abstract base class
>
> Added:
>
> commons/proper/
code, so better revert it?
>>
>> Am 11.06.2013 um 21:47 schrieb brit...@apache.org:
>>
>>> Author: britter
>>> Date: Tue Jun 11 19:47:16 2013
>>> New Revision: 1491924
>>>
>>> URL: http://svn.apache.org/r1491924
>>> Log:
>
t; Log:
>> Use var args instead of array as parameter
>>
>> Modified:
>>
>> commons/proper/chain/trunk/core/src/main/java/org/apache/commons/chain2/impl/ChainBase.java
>>
>> Modified:
>> commons/proper/chain/trunk/core/src/main/java/org/apache/commons/chain2/
rameter
>
> Modified:
>
> commons/proper/chain/trunk/core/src/main/java/org/apache/commons/chain2/impl/ChainBase.java
>
> Modified:
> commons/proper/chain/trunk/core/src/main/java/org/apache/commons/chain2/impl/ChainBase.java
> URL:
> http://svn.apache.org/viewvc/c
Hi again,
I have started created some tasks in JIRA to track this changes [1]. Feel free
to add what is missing.
Benedikt
[1] https://issues.apache.org/jira/browse/CHAIN-84
Am 01.06.2013 um 15:04 schrieb Benedikt Ritter :
> Hi Simo,
>
> Am 01.06.2013 um 14:28 schrieb Simon
like is not the Digester dependency itself, but rather
> the fact that:
>
> * The XML config module *exposes* Digester APIs - the contract should
> work strictly to chain configuration APIs, it should have nothing to
> do with the underlying implementation;
>
> * The config
le *exposes* Digester APIs - the contract should
work strictly to chain configuration APIs, it should have nothing to
do with the underlying implementation;
* The configuration module relies on the ConfigParser#parse() method
behaviour, and returns nothing - that means that 2 different parsers
cou
Am 31.05.2013 um 21:33 schrieb Benedikt Ritter :
> Hi again,
>
> Simo and I had a chat about chain lately. We agreed on the points he has
> already mentioned (see below). Some additional issues that we came across:
>
> * The xml module has dependencies to digister. This sh
Hi again,
Simo and I had a chat about chain lately. We agreed on the points he has
already mentioned (see below). Some additional issues that we came across:
* The xml module has dependencies to digister. This should be removed if
possible
* Base classes of the API are currently in
On Tue, May 28, 2013 at 8:43 AM, Benedikt Ritter wrote:
> Hi Simo,
>
>
> 2013/5/27 Simone Tripodi
>
>> Hi all Chain-ers,
>>
>> I had yet another small review yesterday[1] at current Configuration
>> APIs and I am not satisfied yet for the following
Hi Simo,
2013/5/27 Simone Tripodi
> Hi all Chain-ers,
>
> I had yet another small review yesterday[1] at current Configuration
> APIs and I am not satisfied yet for the following reasons:
>
> * org.apache.commons.chain2.CatalogFactory should maybe moved from
> `cor
Hi all Chain-ers,
I had yet another small review yesterday[1] at current Configuration
APIs and I am not satisfied yet for the following reasons:
* org.apache.commons.chain2.CatalogFactory should maybe moved from
`core` module to the `api` module;
* org.apache.commons.chain2.CatalogFactory is
points:
>
>- Support for same features of 1.x
>
> this comes, fortunately, for free: Chain2 is not a complete redesign of
Chain, but rather a restyle
>
>- Increased modularisation
>
> Goal achieved - we no longer have a god module, but everything is splitted
in sma
On 24 April 2013 14:48, Steve Westwood wrote:
> Christian Trimble recently sent to the list details of the XChain project
> (see<http://xiantrimble.com/xchain/> and<
> https://github.com/ctrimble/xchain> )
> and pondered on whether aspects of this could be accommo
Christian Trimble recently sent to the list details of the XChain project
(see<http://xiantrimble.com/xchain/> and<https://github.com/ctrimble/xchain> )
and pondered on whether aspects of this could be accommodated in commons-chain.
There has not been any response to this email (
pache Chain package. You
may want to consider opening up the type of the context object. Combining
expression languages with chains is very powerful. Forcing the type of the
context object restricts use to simple key/value based logic. If you can find
a way to separate the chain of responsib
Hello Simon and Steve,
Here is a brief overview of the XChains package up on GitHub:
High Level Overview:
We fused the Chain and JXPath projects together with some XML bindings to
create a light XML driven programming language. This let us do some
interesting model driven programming
On 23 March 2013 00:25, sebb wrote:
> On 23 March 2013 00:19, Jörg Schaible wrote:
>> sebb wrote:
>>
>>> On 22 March 2013 19:58, Gary Gregory wrote:
I published the CSV site after your commit, but some links are still
incorrect, for example:
https://commons.apache.org/proper/relea
hor: sebb
>>>> Date: Fri Mar 22 17:49:27 2013
>>>> New Revision: 1459912
>>>>
>>>> URL: http://svn.apache.org/r1459912
>>>> Log:
>>>> Fix up URLs so they point to actual sites; this allows relative URLs to
>>>> work pr
t;>> work properly
>>>
>>> Modified:
>>> commons/proper/bcel/trunk/pom.xml
>>> commons/proper/beanutils/trunk/pom.xml
>>> commons/proper/betwixt/trunk/pom.xml
>>> commons/proper/bsf/trunk/pom.xml
>>> commons/p
l sites; this allows relative URLs to
>> work properly
>>
>> Modified:
>> commons/proper/bcel/trunk/pom.xml
>> commons/proper/beanutils/trunk/pom.xml
>> commons/proper/betwixt/trunk/pom.xml
>> commons/proper/bsf/trunk/pom.xml
>> commons/proper
l
> commons/proper/betwixt/trunk/pom.xml
> commons/proper/bsf/trunk/pom.xml
> commons/proper/chain/trunk/pom.xml
> commons/proper/cli/trunk/pom.xml
> commons/proper/codec/trunk/pom.xml
> commons/proper/collections/trunk/pom.xml
> commons/proper/compre
Hi Christian,
thanks a lot for sharing those info, much more than appreciated!
In commons-chain 2.0 we are basically trying to revamp the old chain
1.X, providing the same features, but keeping in mind a bottom-up
approach (people are interested on using chain even outside the web
context
>
> Hello,
>
> I am not sure where you are looking to take the commons chain project, but you
> may be interested
> in some code that meltmedia has open sourced. The project is called xchain and
> it fuses the
> Commons JXPath project with Commons Chain to be used as a web fram
Hello,
I am not sure where you are looking to take the commons chain project, but
you may be interested
in some code that meltmedia has open sourced. The project is called xchain and
it fuses the
Commons JXPath project with Commons Chain to be used as a web framework. You
can find the
config
>> implementation to resolve commands class name to instance,
>
> Resolving classes by name will cause problems with OSGi.
not if you are using the right ClassLoader - which is anyway the
reason why current CatalogFactory cannot work there
> Are there other possibilities to c
not in the best way.
> With new Configuration design, we thought delegating the config
> implementation to resolve commands class name to instance,
Resolving classes by name will cause problems with OSGi. Are there other
possibilities to configure [chain]? Sorry I haven't looked at the
--
> From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of
> Simone Tripodi
> Sent: 16 March 2013 21:04
> To: Commons Developers List
> Subject: Re: [Chain] Any future plans for commons-chain?
>
> Hi again Steve,
>
> another thing that came i
2013 21:04
To: Commons Developers List
Subject: Re: [Chain] Any future plans for commons-chain?
Hi again Steve,
another thing that came in my mind, is about a discussion between Elijah and I
about dropping completely the CatalogFactory and moving the
ChainConfigurationException to the
Hi again Steve,
another thing that came in my mind, is about a discussion between
Elijah and I about dropping completely the CatalogFactory and moving
the ChainConfigurationException to the configuration API module.
IIRC this is still related to CHAIN-76...
TIA!
-Simo
http://people.apache.org
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Mar 15, 2013 at 1:53 PM, Steve Westwood
wrote:
> Hi Simone,
>
> Thanks for the response;
>
> My first thought on commons-chain relate to the other 2.0 issues apart from
> CHAIN-76 that have been delivered (
Hi Simone,
Thanks for the response;
My first thought on commons-chain relate to the other 2.0 issues apart from
CHAIN-76 that have been delivered (which is a lot I notice - congratulations on
getting to this point!). Are the changes in your view stable and do they need
further tests/samples to
Hi Steve,
very nice to hear there is someone willing to put new energies on Chain! :)
So, the latest step IMHO before to cut the first chain RC, is
CHAIN-76[1] where some work has already been done but far to be
completed.
If you want to give a help here, there's enough space to get involve
I wanted to get a sense of what (if anything) is planned for commons-chain. I
used this in some years ago, and for various reasons I now find myself returning
to it. In examining the SVN trunk things have not stood still:
- Discussions (and subsequent work) in 2011 to accommodate work as a
developed by => developed at
Files changed:
/commons/proper/attributes/trunk/NOTICE.txt ( 1440692 )
/commons/proper/bcel/trunk/NOTICE.txt ( 1440692 )
/commons/proper/beanutils/trunk/NOTICE.txt ( 1440692 )
/commons/proper/betwixt/trunk/NOTICE.txt ( 1440692 )
/commons/proper/chain/t
Comment: as dscusses to dev@, configuration stuff have been moved to a proper
subdirectory
Files changed:
/commons/proper/chain/trunk/configuration ( 1366630 )
/commons/proper/chain/trunk/configuration/api (from
/commons/proper/chain/trunk/configuration-api:1366602) ( 1366630 )
/commons/
1 - 100 of 445 matches
Mail list logo
