Re: Next Gen JDEE

No, I'm talking about what would replace prj.el.  Create a gradle project and build away but let's write (for starters) only one module which gets environment from a pom (i.e. where is the source, where are the classes to be compiled if it needs it, resources etc).


On Jul 15, 2015, at 5:12 PM, Stephen Leake <[email protected]> wrote:

> Paul Landes <[email protected]> writes:
> 
>> Yes, I did think about gradle, but I think it's probably over kill for
>> what we need. 
> 
> I think there are two separate issues here:
> 
> - the system that builds the components of the JDEE2 project.
> 
> - the build systems that typical JDEE2 users use in their projects.
> 
> I was addressing the latter. Surely there is no reason for JDEE2 to
> impose that choice on users?
> 
>> We could abstract out project information but that complicates things
> 
> Emacs core is making an attempt to define an abstract project interface.
> It's not easy, because people have such different ideas about what a
> "project" is.
> 
> But supporting a specific suite of build tools via a unified front end
> is a well defined project.
> 
> 
> -- 
> -- Stephe
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> jdee-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jdee-devel


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/