Jody Garnett ha scritto:
> In talking with Acuster the inability to grab the JMapPane code as a
> maven dependency is cutting into the ability to write demos. Ian you
> mentioned the idea of where JMapPane might live, and the answer was as
> in the "ext" directory - aka code that is not core to
+1
Simone.
On 7/13/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
In talking with Acuster the inability to grab the JMapPane code as amaven dependency is cutting into the ability to write demos. Ian you
mentioned the idea of where JMapPane might live, and the answer was asin the "ext" directory - a
>>I would like to set up this module, and tag Adrian and Ian as module
>>maintainers ;-) I do need to ask permission first, since this is not my
>>code ... I just want to see Adrian on track for his documentation
>>efforts. I am going to start the work and wait for votes before I commit :-)
>>
As long as you are here I should ask - is the 2.2.x or 2.3.x code ;-)
Hard to tell since 2.2.x seems to lack a spike directory ...
Jody
> On 7/13/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
>> In talking with Acuster the inability to grab the JMapPane code as a
>> maven dependency is cutting into
On 7/13/06, Jody Garnett <[EMAIL PROTECTED]> wrote:
> In talking with Acuster the inability to grab the JMapPane code as a
> maven dependency is cutting into the ability to write demos. Ian you
> mentioned the idea of where JMapPane might live, and the answer was as
> in the "ext" directory - aka c
In talking with Acuster the inability to grab the JMapPane code as a
maven dependency is cutting into the ability to write demos. Ian you
mentioned the idea of where JMapPane might live, and the answer was as
in the "ext" directory - aka code that is not core to the library, but
instead uses th
