Hi,
> Hi,
>> a small question, befor i start working. Should i change the package
>> name from com.isa.jump.plugin to org.openjump.core.ui.plugin.file for
>> example?
>>> I would say yes, rename the package and keep Larry as the original author 
>>> in javadoc.
>>> (I make a copy to Larry so that he can respond and give his opinion),
>>>
>> not necessarily! we've got several packages in core so having another one 
>> wouldn't make a big difference. also, keeping the package name would make it 
>> much more transparent where the plugin stems from.
> Of course, this is also an option.
> I find it more difficult to maintain code when classes are sorted after
> their author
> than when they are sorted after their function though.
That's  just my opinion.
>
> But I'm also fine with keeping code in its own jar with its original
> package name
> and including it in CORE distribution.
One simple reason for an integration into the core, is the much simpler 
development, debugging, packaging, deployment. At the Moment the 
plug-ins/SkyPrinterPlugIn repository only a "storage" for code! No 
(ant/maven) project, that allows everyone to easy build and deploy. On 
the other hand should core code reside in the core repository. Or we 
must discuss the modularisation of OJ in general. A nice task for the 
future ;-)
> Matthias, are you OK with this solution ?
I'm not really happy with it. But we are a community project and we can 
only work together.

Matthias
>
> Michaël
>> btw. there is actually no reason to commit it to CORE! it pretty much can 
>> stay an independent extension with a private svn path but be added as a jar 
>> to lib/ext.
>>
>> ..ede
>>
>> ------------------------------------------------------------------------------
>> November Webinars for C, C++, Fortran Developers
>> Accelerate application performance with scalable programming models. Explore
>> techniques for threading, error checking, porting, and tuning. Get the most
>> from the latest Intel processors and coprocessors. See abstracts and register
>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

-- 

  _ __ ___ _________________________________ ___ __ _
  
   Technologieconsulting
   Matthias Scholz
   Siebigeröder Str 17a
   06308 Klostermansfeld

   T +49 34772 34150
   E m...@jammerhund.de
   W www.openjump.de
_ __ ___ _________________________________ ___ __ _


------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to