[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Need to use VCM heavily
|
Thanx for putting me on the right track.. ;)
Mvgr,
Martin
On Thu, 2002-06-13 at 02:07, Kevin McGuire wrote:
>
> Hi Martin,
>
> You've got the right idea, and Eclipse will support the level of
> integration that you want. Its just that the mechanisms for doing this are
> a little "deeper".
>
> For example,
>
> - there is a delta mechanism to inform you of projects being created or
> changed
> - there is a builder mechanism which you can use to keep your information
> up to date (e.g. JDT uses this when java files are saved to produce
> required classes).
> - natures, as I mentioned.
>
> You should start by investigating org.eclipse.core, where all that good
> stuff is.
>
> Cheers,
> Kevin
>
>
>
>
>
> Martin van den Bemt
> <mllist@xxxxxxxx> To: platform-vcm-dev@xxxxxxxxxxx
> Sent by: cc:
> platform-vcm-dev-admin@ Subject: Re: [platform-vcm-dev] Need to use VCM heavily
> eclipse.org
>
>
> 06/12/02 05:10 PM
> Please respond to
> platform-vcm-dev
>
>
>
>
>
> Hi Kevin,
>
> Never looked at the netures yet, so I probably must have a look at that.
> What my intensions were, is to integrate maven tightly into eclipse, so
> people can just say "If you find something that is maven, please handle
> the rest for me". On first exploration, that would be a bit too much to
> achieve (don't want a custommade eclipse for this..). So the next best
> thing is to to start intercepting at points were a project starts, gets
> checkedout (or for that matter any team provider) or a current project
> gets mavenized (in which a nature can help probably a lot). Since the
> start of the project can already be a maven project, I was looking at
> the way to intercept the checkout (as), read the project.xml
> automaticcaly, and setup the project according to that xml file, so
> people don't have to hit the mouse again to process the current team
> project as a maven project.
>
> Maybe I am still pushing to far in flexibility, but if it is possible in
> any way, I will love to try to get it to work..
>
> Thanx for the quick reply, which is really appreciated..
>
> Mvgr,
> Martin
>
> PS (OT) Are you located in Amsterdam, or is that just a subsidiary?
>
>
> On Wed, 2002-06-12 at 22:44, Kevin McGuire wrote:
> >
> > Hi Martin,
> >
> > I'm not sure I understand what you are asking, but it sounds like you
> would
> > like an easy way to mark an existing project as a "Maven" project? This
> > seems unrelated to Team/VCM.
> >
> > For things like JDT or PDE, the projects are marked as being 'of that
> type'
> > (using this term loosely) via an IProjectNature which gets stored with
> the
> > project in the .project file. This allows you a place to hang builders,
> > and to make JDT/PDE menus appear on such projects in the IDE. Once a
> > project has either been created as a JDT project (you do this via the
> "New"
> > wizards), or an existing project converted (this is what PDE does), then
> > the project will retain this nature wherever it goes. For example,
> sharing
> > it via a repository.
> >
> > >From the description I just briefly read about Maven, it sounds like you
> > want to do as PDE does and 'attach' Maven'ness to an existing project via
> > the builders/natures. Presumably the conversion step would also generate
> > your project.xml file.
> >
> > Trying to hack the CVS support will I believe not give you want you want,
> > and will besides tie you to a specific repository provider. If you go
> the
> > nature/builder route you will work against any provider.
> >
> > Hope this helps,
> > Kevin
> >
> >
> >
> >
> >
> >
>
> > Martin van den Bemt
>
> > <mllist@xxxxxxxx> To:
> platform-vcm-dev@xxxxxxxxxxx
> > Sent by: cc:
>
> > platform-vcm-dev-admin@ Subject:
> [platform-vcm-dev] Need to use VCM heavily
> > eclipse.org
>
> >
>
> >
>
> > 06/12/2002 04:16 PM
>
> > Please respond to
>
> > platform-vcm-dev
>
> >
>
> >
>
> >
> >
> >
> > Hi everyone,
> >
> > Sorry for the bad subject, but couldn't find the right punchline for
> > it..
> >
> > I am currently writing a plugin for maven, which is a a project
> > management and comprehension tool (would be nice for the eclipse java
> > development too btw..) (see http://jakarta.apache.org/turbine/maven for
> > more details).
> >
> > Since maven is heavily used in cvs projects and builds around 1 file
> > called project.xml, I am currently adding functionality to do a New-Team
> > Maven project.
> > I want to do several things :
> > 1. The current wizard of checkout project As, should only ask the
> > projectname and team specifics and not the other tabs.
> > 2. Add a popmenu item to the repository popupmenu saying checkout as
> > maven project and offer the same wizard as described at point 1.
> > 3. From the File new, I should be able to do the same.
> > 4. If 1, 2 or 3 are very difficult to achieve, is it possible to add
> > functionality after the checkout, since the project settings can be
> > completely extracted from the project.xml file, which is normally in the
> > root of the project.
> > 5. I rather not change the VCM modules, since that needs your approval
> > too, and is easily breakable at the release rate eclipse is at..
> >
> > Hope someone can give any hints on where to look for those extension
> > points (I looked and couldn't really find the solution to what I want)
> > and maybe a pointer to classes where I can have some example code and
> > which I have to use to get this done correctly. As every lazy
> > programmer, I like to reuse code, or just calling something that is
> > there, so if that is possible too, I am all ears ;)..
> >
> > Mvgr,
> > Martin
> >
> >
> >
> >
> >
> > _______________________________________________
> > platform-vcm-dev mailing list
> > platform-vcm-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
> >
> >
> >
> >
> > _______________________________________________
> > platform-vcm-dev mailing list
> > platform-vcm-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
> >
>
>
> _______________________________________________
> platform-vcm-dev mailing list
> platform-vcm-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
>
>
>
>
> _______________________________________________
> platform-vcm-dev mailing list
> platform-vcm-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
>
