spearofsolomon at gmail
Nov 22, 2009, 11:36 PM
Post #3 of 3
(607 views)
Permalink
|
|
Re: Re: Trac task context sharing with mylyn
[In reply to]
|
|
Earl,
Thanks for the help.
I checked the zip file - it looks as if it references the files in the same
way. But I'm not exactly sure which zip files mean what, so I could be
missing something. In light of the fact that the files are opening in the
package explorer but not the "editor", I think there must be something else
awry. I will recreate the project in svn (it's all for test right now) and
try it again, making sure to check the .project file in first this time. I
do have it checked it and synchronized right now, but I don't remember at
what stage that happened.
Nate
On Fri, Nov 20, 2009 at 7:44 PM, Earl <earlytom [at] gmail> wrote:
> Nate,
>
> > Question setup: I have a project checked out into two workspaces. In
> > workspace 1, I activate a task, open some files, edit some stuff,
> > commit the changes to svn, and attach the context to the task.
> >
> > In workspace 2, I update from svn, retrieve the context of a task and
> > activate it. The correct files show in the Package Explorer (on the
> > left), but the files (which I left open in workspace 1) do not open
> > automatically and the cursor isn't placed at the last edit point.
> >
> > Is it possible to get trac working that way?
>
> It does work for me that way.
>
> The trick I used to make sure all project names were the same was to
> check the .project file into SVN. Then, if you use File -> Import ->
> SVN ->
> Checkout Projects from SVN it seems to name everything consistently.
>
> I suspect you have to do that before you start to create Mylyn
> context,
> though. Have you unzipped the mylyn-context.zip files and looked at
> them to make sure they all reference the same files in the same
> manner?
>
> > ps question: I didn't setup the postcommit hooks from svn to trac yet
> > because it seems like all they do is update ticket status for you. Am
> > I missing some other cool thing they can do, or maybe updating ticket
> > status is a bigger deal than I think it is?
>
> Nope, I think that's mainly what it does, along with listing the SVN
> commit number into the trac ticket so you can find the changeset
> later.
> I don't actually use the post-commit hook because I have multiple trac
> instances and only one subversion repository, so I just copy the SVN
> commit from the Eclipse SVN console and update the ticket manually.
>
> Hope this helps,
>
> --
> Earl Tom
>
> [snip]
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Trac Users" group.
> To post to this group, send email to trac-users [at] googlegroups
> To unsubscribe from this group, send email to
> trac-users+unsubscribe [at] googlegroups<trac-users%2Bunsubscribe [at] googlegroups>
> .
> For more options, visit this group at
> http://groups.google.com/group/trac-users?hl=.
>
>
>
--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=.
|
