You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2022/12/02 18:24:35 UTC
Support for maven
There are some java apps that no longer support ant and
instead rely on maven. Last I checked, I don't think we
support that, do we?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Support for maven
Posted by Peter Kovacs <pe...@apache.org>.
Am 26.12.22 um 19:37 schrieb Damjan Jovanovic:
> On Fri, Dec 2, 2022 at 9:10 PM Jim Jagielski <ji...@jagunet.com> wrote:
>
>> There are some java apps that no longer support ant and
>> instead rely on maven. Last I checked, I don't think we
>> support that, do we?
>>
>>
>>
> But why are we compiling Java projects?
>
> We compile C/C++ projects because (1) upstream often doesn't provide
> binaries, and/or (2) we need to patch the source.
>
> For Java projects, (1) is almost universally false, and (2) is often false.
>
> Why can't we just download and use the upstream .jar files in those cases,
> instead of needing Maven to build the source ourselves?
I think we should not build any dependencies if we rebuild AOO.
If we create a release build then we should have stashed the dependencies.
In case of Java files this is easy because we can use JAR files as you
suggested.
For C++ dependencies we should build a repository with maven like tools
like conan [1] Maybe even build an own Maven Repository for all if this
is possible.
However, We should also look into the software Architecture that we can
handle different Versions of One dependency, or can switch to concurrent
libraries without much maintenance work. Going more in the direction of
Clean Code Architecture.
All the best
Peter
[1] https://conan.io/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Support for maven
Posted by Damjan Jovanovic <da...@apache.org>.
On Fri, Dec 2, 2022 at 9:10 PM Jim Jagielski <ji...@jagunet.com> wrote:
> There are some java apps that no longer support ant and
> instead rely on maven. Last I checked, I don't think we
> support that, do we?
>
>
>
But why are we compiling Java projects?
We compile C/C++ projects because (1) upstream often doesn't provide
binaries, and/or (2) we need to patch the source.
For Java projects, (1) is almost universally false, and (2) is often false.
Why can't we just download and use the upstream .jar files in those cases,
instead of needing Maven to build the source ourselves?
Regards
Damjan
Re: Support for maven
Posted by Jim Jagielski <ji...@jaguNET.com>.
The later versions of beanshell, starting w/ 3.x will be maven only, I think
> On Dec 2, 2022, at 5:05 PM, Carl Marcum <cm...@apache.org> wrote:
>
> Hi Jim,
>
> On 12/2/22 13:24, Jim Jagielski wrote:
>> There are some java apps that no longer support ant and
>> instead rely on maven. Last I checked, I don't think we
>> support that, do we?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> Not sure what you mean by they no longer support Ant.
> Do you mean they are now built with Maven instead of Ant?
>
> I'm not aware of anything Java in AOO itself that is being built with Maven.
> Only Ant or Make.
>
> That also goes for other things like the NetBeans plugins for Addons, Addins, client apps, etc.
> There are thousands of lines of Ant in those.
>
> Also the automated test suites are Ant built.
>
> I tend to use Gradle in the AOO extension templates (replaces NetBeans) due to it's excellent support for including Ant tasks and I prefer the Groovy DSL to XML build files.
> And I was able to reuse those thousands of lines of Ant instead of porting it to Maven.
>
> That being said most things could probably be ported to Maven (or Gradle) if we decided to.
>
> Best regards,
> Carl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Support for maven
Posted by Carl Marcum <cm...@apache.org>.
Hi Jim,
On 12/2/22 13:24, Jim Jagielski wrote:
> There are some java apps that no longer support ant and
> instead rely on maven. Last I checked, I don't think we
> support that, do we?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Not sure what you mean by they no longer support Ant.
Do you mean they are now built with Maven instead of Ant?
I'm not aware of anything Java in AOO itself that is being built with
Maven.
Only Ant or Make.
That also goes for other things like the NetBeans plugins for Addons,
Addins, client apps, etc.
There are thousands of lines of Ant in those.
Also the automated test suites are Ant built.
I tend to use Gradle in the AOO extension templates (replaces NetBeans)
due to it's excellent support for including Ant tasks and I prefer the
Groovy DSL to XML build files.
And I was able to reuse those thousands of lines of Ant instead of
porting it to Maven.
That being said most things could probably be ported to Maven (or
Gradle) if we decided to.
Best regards,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org