Re: Installation

On Wed, 2003-06-18 at 09:47, Tim Lebedkov wrote:
> Hello Tor,
> 
> I have some questions:
> 1.  There is a pmd-netbeans.nbm on http://sourceforge.net/projects/pmd. 
> Shouldn't we
>     define a dependency from tasklist-pmd to it?

What do you mean by define a dependency? Document it somewhere?
tasklist-pmd's manifest already declares a dependency on it:

OpenIDE-Module-Module-Dependencies: pmd > 0.70, ...

> 2. What do you think about the integration of 
> http://checkstyle.sourceforge.net/

That would be interesting. Last time I looked at it, there was a
lot of overlap between pmd and checkstyle, and pmd seemed like
a more active project.

Are there rules implemented by checkstyle that are not in pmd?
The only ones I noticed earlier were for things like indentation
which I didn't find all that compelling.

> 3. Wouldn't it be better to place nbm files instead of jar files on
>     http://tasklist.netbeans.org/servlets/ProjectDownloadList?

The problem with that is that a nbm can only contain a single
module! (Yes, I was very surprised to discover that.)

So the download page would have 10 nbm files for each version
(3.4, 3.5 stable, 3.5 dev, 4.0 dev)

> 4. Why is jtidy not a part of tasklist download?

It's a bug I guess. I just need to go update the tarballs. Do
you know which of the downloads are not including it?

> 5. Could you please explain the way how you build files for TaskList 
> Download page
>     and for the Update Server (How often do you do this, which branches 
> do you use, ...)

It's very haphazard.  For the Update Server, only the 3.5 stable
set is contributed. I build it by hand whenever a critical bug
has been fixed, and send it to Robert Novak.

The 4.0 dev modules (the alpha center) is built automatically
from the tasklist cluster defined in nbbuild/build.properties.

For the download page, I update the modules occasionally (haven't
lately, since I've been really busy). I have a tree (which is
exactly the tree you get when you unzip one of the download
pages; I update my build, copy the modules into the tree, and
zip it up, then upload it.

> 6. Is it possible to make the tasklist-compiler available through Alpha 
> Update Server and what
>     should be done to move it to the Beta/Final?

Yes, to get it through alpha update you need to get it added
to nbbuild/build.properties's tasklist cluster.

Before you go to final I really think you should negotiate an
API change in 4.0 so that you can depend on official APIs instead
of reimplementing/code-duplicating the compiler engine.

> 7. What about making dev35 branch content available through the Beta 
> Update Server?

That's a good idea - do you think it's possible for the update center
to contain two different versions of the same module? And they
would have to be labelled differently in some way so people knew
why they would download version 1.2 instead of 1.0.5 for example.

-- Tor