Re: Purpose of jde-autoloads

Przemysław Wojnowski <[email protected]> writes:

> W dniu 13.08.2015 o 00:07, Phillip Lord pisze:
>> If jdee becomes ELPA packaged (when it needs to be), jde-autoloads.el is
>> generated client side at install side anyway.
> I didn't know that.
>
> What I don't know either is how to make Cask to create jde-autoloads,

It doesn't. It shouldn't. package.el does that.


> to make it available during compilation (although only jde.el has
> (require 'jde-autoload), which IMHO can be removed, because user is
> requiring JDE anyway).

Oh. So, it does. Well, that's broken, and yes, it should be removed.


> Another thing is how to make Cask compile elisp files with specified load-path.
> Cask has an issue for this (https://github.com/cask/cask/issues/275) and there
> is a branch with "load-path" option, but nothing happens since January.
> In Ant we can do that easily.

This gets back to the general vision for how JDEE should look. The only
reason we have the project structure we do at the moment, it to support
a single build. I think we need two builds with a runtime dependency
between them, then we move the elisp files to top level.

This is the elisp standard, and the tools will support this as, er,
standard.

Phil

------------------------------------------------------------------------------
_______________________________________________
jdee-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jdee-devel