Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] [platform-swt-dev] [cdt-dev] swt-binaries and maven

There is interest from the people working on CBI to improve the way we build natives but it's not unrelated to maven-nar being Eclipse project we can still use it (depending on licensing of course).
I can not speak for the Foundation but every project is welcome to join eclipse.org as long as the licensing, IP clearance, release process and etc. suites their needs. See for some initial info http://wiki.eclipse.org/Development_Resources/HOWTO/Starting_A_New_Project . Mentors are official part of every Eclipse.org project and I'm pretty sure there will be candidates. Unofficially I can serve as one if needed (aka reply to your questions :).

Alexander Kurtakov
Red Hat Eclipse team

----- Original Message -----
> From: "Martin Eisengardt" <martin.eisengardt@xxxxxxxxx>
> To: "Common-build Developers discussion" <cbi-dev@xxxxxxxxxxx>
> Sent: Wednesday, October 17, 2012 10:47:47 AM
> Subject: Re: [cbi-dev] [platform-swt-dev] [cdt-dev] swt-binaries and maven
> 
> 
> 
> To make it clear:
> 
> The plugin was activly developed. But there had been about 25 forks
> (or even more). Most of them are still alive at github. Only the
> original project lead was inactive, did not merge pull requests etc.
> Thats the reason so many forks exists.
> 
> Actually at the moment I am very active to become an maven-nar guru.
> Someone who is knowing the deep aspects of the code. The main reason
> is that I am the project lead of "maven for php" and there is need
> to compile/use php binaries and php extension binaries (dll/so) with
> maven. There are others being very active in the past three years.
> 
> We are currently doing our homework (merging the most recent forks).
> 
> 
> Do I understand you? You are saying that there is interest from
> eclipse foundation and that we should first become a new project in
> incubation phase (for one or two years)? I personally did not ever
> lead an eclipse project. So hopefully there will be some kind of
> mentor leading us through the terms of conditions for eclipse
> projects :)
> If this is correct I will send this offer to the community and we
> will see if they agree.
> 
> 
> Greetings
> Martin
> 
> 
> 
> On Wed, Oct 17, 2012 at 9:03 AM, Krzysztof Daniel <
> kdaniel@xxxxxxxxxx > wrote:
> 
> 
> 
> On Mon, 2012-10-15 at 15:02 +0200, Martin Eisengardt wrote:
> 
> > Of course this does not match the current SWT-binaries project
> structure and you might need some refactoring. However I think this
> 
> could be done in future. If you choose to use maven-nar-plugin one
> day
> it does not mean to migrate swt today.
> 
> This is not the simplest path. To migrate anything to Eclipse
> Foundation
> you need to gather some community around your tool [1], and given
> that
> the plugin itself was not quite actively developed, it does sound
> like a
> risk for a project to rely on it. My concerns are:
> a. will it suite projects needs
> b. is there someone who knows how to use/fix it?
> 
> In the CBI, we are in the huge need of a good native build of SWT,
> filesystem, network support and launchers. Currently we use
> maven-ant-runner, which has many limitations, and were unable to find
> out a better solution, which is a big opportunity for the NAR plugin
> -
> patches for the mentioned project would definitely help nar...
> 
> [1]
> http://wiki.eclipse.org/Development_Resources/Process_Guidelines/What_is_Incubation
> 
> PS. Let's limit further discussion only to cbi-dev.
> --
> Krzysztof Daniel < kdaniel@xxxxxxxxxx >
> Red Hat
> 
> 
> 
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cbi-dev
> 
> 
> _______________________________________________
> cbi-dev mailing list
> cbi-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cbi-dev
> 


Back to the top