./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 subproject file. That should be easy to implement in gradle given that it has a lot of API calls to control the .classpath and .project files. I think perhaps adding this .project file would force other committers to use your setup because you've split the project into two projects. Having it as a command to be issued in gradle might be cleaner and more independent of your specific development environment setup. One of the main advantages we gained by converting to gradle was to get rid of this manual setup of .classpath for example. So perhaps we need to take advantage of automation as much as we can. On Sat, Aug 19, 2017 at 5:54 PM, Jacques Le Roux <[email protected]> wrote: > 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 the .project and following the info "Mostly for committers..." I > added at https://cwiki.apache.org/confluence/display/OFBIZ/Eclipse+Tips I > was able to use only the ofbiz Eclipse project with the plugins embedded. > I have then all what I need to work with plugins from the ofbiz project. I > suggest all committers to do the same, so we would be sure that the plugins > get the love they deserve, but your YMMV... > > BTW Taher, I'd be interested by your thoughts about how to automatically > create the relationship between the 2 projects in the eclipse Gradle task. > > Jacques > > > > Le 19/08/2017 à 14:18, Taher Alkhateeb a écrit : >> >> 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, <[email protected]> wrote: >>> >>> Author: jleroux >>> Date: Fri Aug 11 12:13:43 2017 >>> New Revision: 1804782 >>> >>> URL: http://svn.apache.org/viewvc?rev=1804782&view=rev >>> Log: >>> No functional change >>> >>> Adds an Eclipse .project file to the ofbiz-plugins branch in order to >>> handle >>> as a project in Eclipse and to follow https://s.apache.org/BLzU >>> >>> This is mostly (if not only) for committers >>> >>> Added: >>> ofbiz/ofbiz-plugins/trunk/.project (with props) >>> >>> Added: ofbiz/ofbiz-plugins/trunk/.project >>> URL: >>> http://svn.apache.org/viewvc/ofbiz/ofbiz-plugins/trunk/.project?rev=1804782&view=auto >>> >>> ============================================================================== >>> --- ofbiz/ofbiz-plugins/trunk/.project (added) >>> +++ ofbiz/ofbiz-plugins/trunk/.project Fri Aug 11 12:13:43 2017 >>> @@ -0,0 +1,16 @@ >>> +<?xml version="1.0" encoding="UTF-8"?> >>> +<projectDescription> >>> + <name>ofbiz-plugins</name> >>> + <comment></comment> >>> + <projects/> >>> + <natures> >>> + <nature>org.eclipse.jdt.core.javanature</nature> >>> + </natures> >>> + <buildSpec> >>> + <buildCommand> >>> + <name>org.eclipse.jdt.core.javabuilder</name> >>> + <arguments/> >>> + </buildCommand> >>> + </buildSpec> >>> + <linkedResources/> >>> +</projectDescription> >>> >>> Propchange: ofbiz/ofbiz-plugins/trunk/.project >>> >>> ------------------------------------------------------------------------------ >>> svn:eol-style = native >>> >>> Propchange: ofbiz/ofbiz-plugins/trunk/.project >>> >>> ------------------------------------------------------------------------------ >>> svn:keywords = Date Rev Author URL Id >>> >>> Propchange: ofbiz/ofbiz-plugins/trunk/.project >>> >>> ------------------------------------------------------------------------------ >>> svn:mime-type = text/xml >>> >>> >
