From: Paul Landes [mailto:firstname.lastname@example.org]
Sent: Wednesday, May 01, 2013 5:48 PM
To: Gian Uberto Lauri
Cc: JDEE Development; JDEE Users; Dave Paroulek
Subject: Re: [jdee-devel] [jdee-users] Call to Fork or simply for JDEE TODO items
My thinking is that maven will be a dependency. JDEE supporting ant, maven, javac compilations is one huge contributing reason for its bloat.
Would declaring offline mode in the ~/.m2/settings.xml and making all needed dependencies available for download from SF be sufficient? Should be a one line file change and a unzip/untar in ~/.m2/repository.
Would you then be able to use JDEE without installing maven? Pretty much all of our java project use Ant for building, and maven is often not even installed.
On May 1, 2013, at 12:56 PM, Gian Uberto Lauri <email@example.com> wrote:
- Maven: either as a separate JVM process or preferably in the same JVM as the development services JVM
And most of all, KEEP MAVEN OPTIONAL.
I ask this is because Maven behind an http proxy that requires authentication is an unpleasant experience at least.
If someone has a clean, safe - no passwords on the command line - solution to that problem, the recipe is welcome.
Messaggio inviato da un tablet