Minimum Ant version is now 1.9.1

2018-04-08 Thread Damjan Jovanovic
Hi

In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
up doing considerable development in Ant, adding the ability to call IDL
tools (idlc, regmerge, javamaker) from Ant, and with the features I've
used, the minimum Ant version is now 1.9.1.

Please let me know if you have any problems.

Regards
Damjan


Re: Minimum Ant version is now 1.9.1

2018-04-08 Thread Matthias Seidel
Hi Damjan,

Am 08.04.2018 um 14:59 schrieb Damjan Jovanovic:
> Hi
>
> In porting main/jurt to gbuild in commits 1828636 and 1828638, I've ended
> up doing considerable development in Ant, adding the ability to call IDL
> tools (idlc, regmerge, javamaker) from Ant, and with the features I've
> used, the minimum Ant version is now 1.9.1.
>
> Please let me know if you have any problems.

Hi Damjan,

Thank you for your work!

My Windows builds for trunk are done with Ant 1.10.3, so I don't expect
problems here.
However I will start a new build and will let you know... ;-)

(BTW: Windows BB is on 1.9.7 and both Linux BBs are on 1.9.3)

Regards,
   Matthias

>
> Regards
> Damjan
>




smime.p7s
Description: S/MIME Cryptographic Signature


Proofing Tool GUI - Hyphenation support

2018-04-08 Thread Marco A.G. Pinto
Hello!

Just to let the development community know that after five years
planning to add hyphenation support to Proofing Tool GUI, it is finally
implemented.

It took me just around a couple of weeks to have it ready since only now
I was told about the algorithm.

You can give it a try (PTG 3.0 - build 123) at:
www.proofingtoolgui.org

Don't hesitate to report any issues or give suggestions.

Thank you!

Kind regards,
 >Marco A.G.Pinto
   --

-- 


signature.asc
Description: OpenPGP digital signature


gbuild migration (Was: Re: Building module store error on macOS)

2018-04-08 Thread Matthias Seidel
Am 04.04.2018 um 15:06 schrieb Jim Jagielski:
>> On Apr 4, 2018, at 9:01 AM, Jim Jagielski  wrote:
>>
>>
>> I will start another thread on the gbuild topic...
>>
> First and foremost, I am incredibly impressed with the work
> being done on the gbuild migration. I really am.
>
> However, and there's always a "however", there must come
> a time where we "hold the line" on migration in hopes of getting
> a 4.2.0 out. As such, I think some sort of plan might be due
> (and apologies if we have such a documented plan already
> in place)...

I don't know if there is already a plan, but what about voting for a
release manager and get the thing going?

Regards, Matthias

> Does it make sense to spend time to list modules that still
> need that migration and then prioritize them? As well as
> create a policy such that all "new and updated" modules
> must use gbuild but for existing modules, "if it ain't broke,
> don't fix it"?
>
> I'm not trying to stifle the migration, it's just that it appears
> to me that we need better management about it.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>



smime.p7s
Description: S/MIME Cryptographic Signature