It looks like I'm getting a test failing with the patch, I will need some
more time to investigate.
It is one of these
tests: testDefault(org.apache.commons.chain2.config.ConfigParserTestCase):
Correct command count expected:<17> but was:<8>
This error message is associated with order dependent t
Hi Sebb and Simo,
I just created an issue to represent the work for renaming the package and
the artifact id.
https://issues.apache.org/jira/browse/CHAIN-65
In it, I have attached a potential patch for the rename. Please take a look
and let me know if it works for you.
Thanks,
-Elijah
On Tue, F
Salut,
>
> There's no need to update both the groupId and tthe artifactId.
> So long as the each unique package name relates to a unique
> groupId:artifactId pair, Maven should be able to resolve dependencies
> correctly.
>
Yes it does, the issue is not technical but rather keeping coherence
with
On 14 February 2012 08:50, Simone Tripodi wrote:
> Hi al guys,
>
> current 2.0 trunk has been updated to fully support Generics[1],
> adding improvement as discussed on 2011 in ML - there is the cost
> anyway of losing the backward compatibility, clirr detects 57 errors.
>
> So, according to what
Hi al guys,
current 2.0 trunk has been updated to fully support Generics[1],
adding improvement as discussed on 2011 in ML - there is the cost
anyway of losing the backward compatibility, clirr detects 57 errors.
So, according to what we already experienced (digester3 ,pool2), I
would proceed on
