RE: [mylar-dev] refactoring and dev build

["Mik Kersten" <beatmik@xxxxxxx>]

Progress on the refactoring:
- part done for the tasklist, will be done for other projects tomorrow
morning
- I took this opportunity to update the copyrights to 2006, so most files
have changed
- I also formatted all the files according to our formatting guidelines in
order to make applying patches easier

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Mik Kersten
> Sent: January 23, 2006 4:43 PM
> To: 'Mylar developer discussions'
> Subject: RE: [mylar-dev] refactoring and dev build
> 
> 
> The costs of moving and refactoring code that you bring up is exactly why
> it's important to make these changes sooner rather than later.
> Officially,
> Mylar can't promise any APIs until the 1.0 release.  We're a technology
> project that's exploring novel functionality, and the user interface and
> interaction need to stabilize considerably more before APIs can follow
> suit.
> 
> However, for those willing to innovate on the bleeding edge (hi Brock ;),
> we
> are starting to form the very initial, and guaranteed to change, APIs for
> task and repository integration.  I expect that these will become a bit
> more
> stable by Mylar 0.5.  And yes, making the Jira support part of Mylar is on
> the table, in order to make that better integrated, easier to contribute
> to,
> and have it evolve gracefully along with the formation of the APIs.  I'll
> post more regarding that on:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=120952
> 
> Mik
> 
> > -----Original Message-----
> > From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> > On Behalf Of Eugene Kuleshov
> > Sent: January 20, 2006 10:12 PM
> > To: Mylar developer discussions
> > Subject: Re: [mylar-dev] refactoring and dev build
> >
> >   I am not sure if it is a good idea because CVS does not allow to track
> > changes for renamed artifacts and also because you are going to make
> > this API public anyway. Renaming will also create incompatibilities with
> > 3rd party service providers (I mostly worried about Jira provider),
> > unless it will be provided by Mylar out of the box.
> >
> >   regards,
> >   Eugene
> >
> >
> > Mik Kersten wrote:
> >
> > >Please note that I've started a package name migration in order to move
> > to
> > >the Eclipse conventions about internal package naming:
> > >http://dev.eclipse.org/naming.html (i.e. moving mylar.tasklist.internal
> > to
> > >mylar.internal.tasklist).  This will help make it clear that that the
> > >tasklist extensibility is still very preliminary, and more refactoring
> of
> > >this sort will happen next week.
> > >
> > >Today's dev build contains a couple of notable changes:
> > >- there is a preliminary generic Add Query Page mechanism
> > >  https://bugs.eclipse.org/bugs/show_bug.cgi?id=123845
> > >- Add Existing Task is now generic in a similar way and requires the
> > >repository to be selected
> > >- Active Folding is using the new Eclipse 3.2 APIs we requested, no
> > longer
> > >requires a custom folding provider, is working much better, and will
> > improve
> > >further by 0.4.8.
> > >
> > >Mik
> > >
> > >
> > >
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev