Jörg Schaible wrote:
Hi Ceki,
Ceki Gulcu wrote at Dienstag, 19. Mai 2009 22:00:
Dennis Lundberg wrote:
Yes I'm aware of that. My concern is for those people who don't know
about that. What will happen if they declare
commons-logging:commons-logging without a version in their POM? Or
declare
- "Jörg Schaible" a écrit :
> Luc Maisonobe wrote at Dienstag, 19. Mai 2009 22:06:
>
> [snip]
>
> > So let's vote on this proposal: change the top level package name
> on
> > [math] from org.apache.commons.math to org.apache.commons.math2.
> >
> > [] +1 change the top level package name
On 20/05/2009, Henri Yandell wrote:
> Good news - I think 3.3 is ready to go out. Interested if anyone
> thinks there are any JIRA items that should go in.
>
> Bad news - Both Clirr and Jardiff fall over with the following error:
>
> Unable to locate enclosing class
> org.apache.commons.collec
On Tue, May 19, 2009 at 11:08 PM, Jin Mingjian wrote:
> the top level package renaming seem rare in the current big java project.
> Binding the version to the package name is not a common strategy as well.
>
Yes and that's why we have "jar hell" situations
---
On 20/05/2009, sebb wrote:
> On 20/05/2009, Henri Yandell wrote:
> > Good news - I think 3.3 is ready to go out. Interested if anyone
> > thinks there are any JIRA items that should go in.
Assuming that collections 3.3 is the one in trunk, I think the POM
should include the java source and ta
>
> [math] from org.apache.commons.math to org.apache.commons.math2.
>
> [] +1 change the top level package name
> [] 0 I don't care
> [] -1 keep the old name
>
> Vote open for 72 hours (up to Friday May 19th 20h00 UTC)
>
Suggestion:
* keep as many package names as possible (i.e. org.apache.commo
On Wed, May 20, 2009 at 3:51 AM, sebb wrote:
> On 20/05/2009, Henri Yandell wrote:
>> Good news - I think 3.3 is ready to go out. Interested if anyone
>> thinks there are any JIRA items that should go in.
>>
>> Bad news - Both Clirr and Jardiff fall over with the following error:
>>
>> Unable
On Wed, May 20, 2009 at 10:28 AM, Cyril Briquet
wrote:
>>
>> [math] from org.apache.commons.math to org.apache.commons.math2.
>>
>> [] +1 change the top level package name
>> [] 0 I don't care
>> [] -1 keep the old name
>>
>> Vote open for 72 hours (up to Friday May 19th 20h00 UTC)
>>
>
> Suggest
>
> >> [math] from org.apache.commons.math to org.apache.commons.math2.
> >>
> >> [] +1 change the top level package name
> >> [] 0 I don't care
> >> [] -1 keep the old name
> >>
> >> Vote open for 72 hours (up to Friday May 19th 20h00 UTC)
> >>
> >
> > Suggestion:
> > * keep as many package names
Sam Halliday wrote:
Bill, I strongly discourage adding these methods at this time. We will regret
it.
If you don't want to change (i.e. add new methods) to an interface, then the
sensible thing is to omit these interfaces for 2.0 and introduce them with
2.1.
+1. Unless we are either a) agree
Luc Maisonobe wrote:
This issue affects 1 projects,
and has been outstanding for 5 runs.
The current state of this project is 'Failed', with reason 'Build
Failed'.
For reference only, the following projects are affected by this:
- commons-math : The Jakarta Mathematics Library
Full deta
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-math has an issue affecting its community integration.
This issue
On 20/05/2009, Cyril Briquet wrote:
> >
> > >> [math] from org.apache.commons.math to org.apache.commons.math2.
> > >>
> > >> [] +1 change the top level package name
> > >> [] 0 I don't care
> > >> [] -1 keep the old name
> > >>
> > >> Vote open for 72 hours (up to Friday May 19th 20h00 UT
luc.maison...@free.fr wrote:
Hello,
Considering the ongoing discussion in another thread, the current changes that
have been done on [math] for the last months belong to the major changes with
large incompatibilities with previous versions. We have already decided that
the version number will
I believe I have addressed all the currently known issues standing
between the pool code and a 1.5 release.
I know Phil is doing / will be doing various performance tests. If
anyone else has any issues now would be a good time to mention it.
Mark
On 20/05/2009, Mark Thomas wrote:
> I believe I have addressed all the currently known issues standing
> between the pool code and a 1.5 release.
>
> I know Phil is doing / will be doing various performance tests. If
> anyone else has any issues now would be a good time to mention it.
Just spo
On 20/05/2009, sebb wrote:
> On 20/05/2009, Mark Thomas wrote:
> > I believe I have addressed all the currently known issues standing
> > between the pool code and a 1.5 release.
> >
> > I know Phil is doing / will be doing various performance tests. If
> > anyone else has any issues now
-1
IMO breaking compatibility should be decided on a case-by-case basis
for components. For the widely used variety such as lang, logging,
collections etc then I agree lets avoid jar-hell and not do it. But
for other components that are not so widely used then such as Math I
think its better to mi
On Tue, May 19, 2009 at 1:03 PM, Ceki Gulcu wrote:
>
>
> Jörg Schaible wrote:
>
>>> Forgive me for asking, but were you aware of the above. And if you
>>> were, would you care to explain a scenario in mind which is troubling
>>> you?
>>
>> First: The solution is perfect for a normal user i.e. some
- Original Message -
From: "Phil Steitz"
To: "Commons Developers List"
Sent: Wednesday, May 20, 2009 11:05 AM
Subject: Re: [math] Re: commons-math, matrix-toolkits-java and consolidation
Sam Halliday wrote:
Bill, I strongly discourage adding these methods at this time. We will
reg
The test failed because it couldn't detect equality between two NaN
values. I modified the TestUtils.assertEquals method for double arrays
to use our TestUtils.assertEquals method for doubles instead of
Assert.assertEquals. Our method has the needed NaN checks. With this
changed, I enabled t
- Original Message -
From: "Brent Worden"
To: "Commons Developers List"
Sent: Wednesday, May 20, 2009 8:28 PM
Subject: [math] Re: [g...@vmgump]: Project commons-math (in module
apache-commons) failed
The test failed because it couldn't detect equality between two NaN
values. I m
22 matches
Mail list logo
