Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [vtp-dev] VTP 2.0 in CVS?

I would vote to use new space for the project. However, the code from 1.0 that survives will need to keep its structure below the topmost directory, or dependencies will get messy.

-- Mike

Trip Gilman wrote:
Mike -
    The codebase is available in the current CVS repository.  Tyler is
working on updating the website to reflect the correct repository location.
We definitely have some repository maintenance to perform.  I'll put out the
question of what we should do with the repository.  Should we utilize the
current repository space (would involve deleting any legacy code not
surviving into the next release) or request a new location to house our
project in the future?  The latter of these offers the opportunity to
reorganize our repository structure to include a level of versioning and
branching that could provide many more options to our development process in
the future.  This would be my vote, but I'd like to get everyone's feedback.

Trip


On 9/19/07 8:37 PM, "Mike Greenawalt" <mike@xxxxxxxxxxxxxx> wrote:

Trip, et al -

Is the VTP 2.0 codebase, including openVXML contribution from
openMethods, stored in an Eclipse Foundation CVS repository yet? I have
been reviewing the threads on vtp-dev, and I don't see an announcement
to that effect, and the CVS links on the vtp webpage still point to the
VTP 1.0 code.

I would like to see the current project structure to see how the debug
launcher plugin plays in the new environment.

When will the new structure be in place?

-- Mike

_______________________________________________
vtp-dev mailing list
vtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vtp-dev

_______________________________________________
vtp-dev mailing list
vtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vtp-dev




Back to the top