Re: [jdee-users] Call to Fork or simply for JDEE TODO items

Gian Uberto Lauri <[email protected]> writes:
>> 1. Easy installation and configuration
>>    No one will use JDEE if it takes a weekend to make it up and
>>    running.
>>    For example available JDKs (jde-jdk-registry) usually can be setup
>>    automatically from: JAVA_HOME, default paths in OS (/usr/lib/jvm,
>>    "C:\Program Files\java", etc.).
>
> Beware that the use of an oracle JVM may still lead to the use of /opt or
> /usr/local. I would take PATH into account an keep the thing easily editable by
> means of The True One Editor, may its name be blessed for ever.
Sure. This was just an example of how to go with autoconfiguration.

>> 2. Integration with build tools (especially Maven)
>>    By that I mean loading project configuration (source/test
>>    classpaths) form build tool definition - pom.xml in case of Maven.
>>    This is a must for any non-HelloWorld project.
>
> Keep Maven optional. As said in another e-mail, Maven behind an authenticating proxy is all but fun
Definitely. I indicated Maven, because it's the most prevalent tool out
there, so it has to be supported in the first place.

> --
> Gian Uberto Lauri
> Messaggio inviato da un tablet

Przemek

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1