Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

I had the community interest in mind when I wrote the info "Mostly for committers..." at https://cwiki.apache.org/confluence/display/OFBIZ/Eclipse+Tips But I agree it would be better if we could have it done by Gradle Jacques Le 20/08/2017 à 10:35, Michael Brohl a écrit : I think we should

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

In fact messing without eclipsr API is overcomplication. I think IT is enough to idę spacje maven 19.08.2017 14:19 "Taher Alkhateeb" napisał(a): > I'm not sure I understand the purpose of the .project file? Plugins > are not a standalone project. Perhaps I'm missing

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

I think we should not commit single committer's personal needs or temp. solutions for it. It's a community project. Michael Am 19.08.17 um 22:12 schrieb Jacques Le Roux: Hi Michael, Of course because I was in need and it was easy, I'm lazy you know :D But yes it's only a temporary

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

Le 19/08/2017 à 17:54, Taher Alkhateeb a écrit : ./gradlew pullAllPluginsSource + ./gradlew eclipse = unified code base. You will be able to access to everything, search for everything and fetch the source jars for everything. Yes even too much sometimes. For external classes, you have sometimes

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

Hi Michael, Of course because I was in need and it was easy, I'm lazy you know :D But yes it's only a temporary solution, I agree... Jacques Le 19/08/2017 à 17:32, Michael Brohl a écrit : Hi Jacques, why don't you just generate the .project file with Gradle just as it is done in the

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

./gradlew pullAllPluginsSource + ./gradlew eclipse = unified code base. You will be able to access to everything, search for everything and fetch the source jars for everything. Now for the specific case of subclipse, I think a cleaner solution would be to use gradle to indicate that there is a

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

Hi Jacques, why don't you just generate the .project file with Gradle just as it is done in the framework? People who want to use it can simply generate it and people who don't want to use it are not concerned. Regards, Michael Am 19.08.17 um 16:54 schrieb Jacques Le Roux: In Eclipse, I

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

In Eclipse, I wanted to use Subclipse on plugins from the sole ofbiz (ofbiz-framework) project (ie to embed the plugins in the ofbiz project). When only using pullAllPLuginsSource I was able to search in code and such, but not using Subclipse, notably for history, annotations, etc. By adding

Re: svn commit: r1804782 - /ofbiz/ofbiz-plugins/trunk/.project

I'm not sure I understand the purpose of the .project file? Plugins are not a standalone project. Perhaps I'm missing something? On Fri, Aug 11, 2017 at 3:13 PM, wrote: > Author: jleroux > Date: Fri Aug 11 12:13:43 2017 > New Revision: 1804782 > > URL: