Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [mylar-dev] major refactoring

These errors mean that a referenced project is not in the workspace.  My
apologies, I forgot to add:

  -> Check out: org.eclipse.mylar.monitor.usage

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Friday, July 14, 2006 8:13 AM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] major refactoring
> 
> 
>   Mik, am i missing something or org.eclipse.mylar.monitor.reports
> project is broken? I only have it because sandbox project require it but
> it has build errors now:
> 
> Severity and Description    Path    Resource    Location    Creation
> Time    Id
> Bundle 'org.eclipse.mylar.monitor.usage' cannot be resolved
> org.eclipse.mylar.monitor.reports/META-INF    MANIFEST.MF    line 15
> 1152889821791    4383979
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 44    1152889819027    4383969
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 58    1152889819027    4383970
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 63    1152889819027    4383971
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 68    1152889819027    4383972
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 75    1152889819027    4383973
> InteractionEventLogger cannot be resolved to a type
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 80    1152889819027    4383974
> logger cannot be resolved or is not a field
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 209    1152889819027    4383975
> logger cannot be resolved or is not a field
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 212    1152889819027    4383976
> MylarUsageMonitorPlugin cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> EclipseUsageSummaryAction.java    line 68    1152889818907    4383959
> MylarUsageMonitorPlugin cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> EclipseUsageSummaryAction.java    line 103    1152889818907    4383960
> MylarUsageMonitorPlugin cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> MylarUserAnalysisAction.java    line 49    1152889818897    4383955
> MylarUsageMonitorPlugin cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> MylarUserAnalysisAction.java    line 56    1152889818897    4383956
> The import org.eclipse.mylar.internal.monitor.usage cannot be
> resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports
> ReportGenerator.java    line 30    1152889819027    4383968
> The import org.eclipse.mylar.monitor.usage cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> EclipseUsageSummaryAction.java    line 33    1152889818907    4383958
> The import org.eclipse.mylar.monitor.usage cannot be resolved
> org.eclipse.mylar.monitor.reports/src/org/eclipse/mylar/internal/monitor/r
> eports/ui/actions
> MylarUserAnalysisAction.java    line 26    1152889818897    4383954
> 
> 
> Mik Kersten wrote:
> > Done.  To update your workspace delete each of the projects on the left,
> > check out each project on the right, then synch everything.
> >
> > mylar.core 			-> mylar.context.core
> > mylare.core.tests		-> mylar.context.tests
> > mylar.ui 			-> mylar.context.ui
> >
> > mylar.tasks			-> mylar.tasks.core
> > mylar.tasklist		-> mylar.tasks.ui
> > mylar.tasklist.tests 	-> mylar.tasks.tests
> >
> > mylar.xml			-> mylar.resources
> > mylar.xml.tests		-> mylar.resources.tests (may not be renamed
yet)
> >
> > The modularity is now *way* better, and the code easier to reuse and
> test.
> > The updated Frameworks and APIs are summarized on:
> >
> > http://wiki.eclipse.org/index.php/Mylar_Integrator_Reference
> >
> > Clients that use the Tasks framework in headless mode may still want us
> to
> > move AbstractRepositoryConnector from tasks.ui to tasks.core.  These and
> > similar request should come as new bugs.  Please post questions to this
> list
> > or a corresponding task if you have any trouble moving to these changes.
> >
> > Mik
> >
> >
> >> -----Original Message-----
> >> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> >> On Behalf Of Mik Kersten
> >> Sent: Tuesday, July 11, 2006 11:14 AM
> >> To: 'Mylar developer discussions'
> >> Subject: [mylar-dev] major refactoring
> >>
> >> The recent push to add proper support for using the tasks framework
> >> headless
> >> has promoted a long needed refactoring of our plug-ins.  If you are
> >> developing on Mylar please take a look at the new proposed structure
> >> because
> >> we expect to make such a major change only once before 1.0.  The most
> >> major
> >> change is that tasklist is split into tasks.core and tasks.ui, and
> >> mylar.core/ui becomes context.core and context.ui.
> >>
> >> 150290: extract headless frameworks
> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=150290
> >>
> >> I would like to initiate the name change request with webmaster by
> >> tomorrow
> >> AM.  At that point I will ask that contributors hold off on new patches
> >> until the bug is marked resolved and packages are renamed.  Those
> >> extending
> >> the connectors will be able to migrate all but the new plug-in names by
> >> organizing imports, so I will not create refactoring scripts unless
> >> someone
> >> insists.
> >>
> >> Mik
> >>
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev



Back to the top