Re: [stellation-res] Website reorganization: doc folder moved to top l

[Jim Wright - IBM Research <jwright@xxxxxxxxxxxxxx>]

I've been avoiding checking in .project and .classpath files
for the doc directory -- there's no classpath as such; do you think there's
any value in having a .project file for docs?

For building javadoc, it would make sense to have both, of course.
I think javadoc build files belong in one (or more) of the actual plugin
projects, so that developers can easily build fresh javadoc locally.
When generating javadoc for the website, I've specified the appropriate
output folder as a build property.

What makes sense to you?

Regards,

Jim

At 11:33 AM 1/23/2003, Jonathan Gossage wrote:
> The reason that I thought we should use a common structure is so we don't
> step on each other's toes with .project and .classpath files, unless you
> think that such files should not be under revision control.
>
> Regards
>
> Jonathan
>
>
> ----- Original Message -----
> From: "Jim Wright - IBM Research" <jwright@xxxxxxxxxxxxxx>
> To: <stellation-res@xxxxxxxxxxxxxxx>
> Sent: Thursday, January 23, 2003 9:52 AM
> Subject: RE: [stellation-res] Website reorganization: doc folder moved to
> top level
>
>
> > Jonathan,
> >
> > At 06:26 PM 1/22/2003, Jonathan Gossage wrote:
> > >Where do you want to put this when it is downloaded into Eclipse. Should
> we
> > >create a new "simple" project to hold it?
> >
> > The short answer is 'whatever works for you'.
> > I should probably have clarified that in my earlier post.
> >
> > For general website maintenance, I have an Eclipse workspace with a single
> > 'project' rooted at 'org.eclipse.stellation' (in CVS repositories view,
> > select /home/technology/org.eclipse.stellation and just 'Check Out As
> > Project').  AFAIK, that's the only way to access the top-level website
> > folder, and it gives direct access to everything in the site in a single
> > local workspace.
> >
> > If you don't want the whole site mirrored locally, you can get just the
> > 'doc' folder:
> > * In CVS repositories view, select
> /home/technology/org.eclipse.stellation/doc
> > * Right-click, select 'Check Out As Project'
> >
> > That adds a single project 'doc' to your current Eclipse workspace.
> > While 'doc' doesn't follow Eclipse naming conventions for plug-ins, it's
> > not a plug-in,
> > so I don't think anyone will complain ;->
> >
> > The same approach works for the 'downloads' folder, of course, or any
> other
> > top-level folder.
> >
> > Regards,
> > Jim
> >
> >
> >
> > > > >-----Original Message-----
> > > > >From: stellation-res-admin@xxxxxxxxxxxxxxx
> > > > >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Jim
> Wright -
> > > > >IBM Research
> > > > >Sent: January 21, 2003 4:25 PM
> > > > >To: stellation-res@xxxxxxxxxxxxxxx
> > > > >Subject: [stellation-res] Website reorganization: doc folder moved to
> > > > >top level
> > > > >
> > > > >
> > > > >Hi,
> > > > >
> > > > >I've just finished moving the 'doc' folder to the top level of the
> > > > >org.eclipse.stellation website.  I believe I've updated all the
> relevant
> > > > >links;
> > > > >please let me know if you find any broken ones.
> > > > >
> > > > >This change was done to make it easier to download the actual
> > > > >project code
> > > > >by itself, from org.eclipse.stellation/plugins, without getting
> > > > >the full set
> > > > >of 'doc' files at the same time.  There should be no change in the
> visual
> > > > >appearance of the web site (unless I screwed up).
> > > > >
> > > > >Over time, it's possible that the org.eclipse.stellation.misc
> > > > >project will
> > > > >disappear entirely (if we find a better place for the existing
> > > > >scripts and
> > > > >tests).

--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email: 
jim.wright@xxxxxxx