Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylar-dev] Developing Mylar on Eclipse

I think what you checked out from CVS head and tring to build Mylar under Eclipse 3.2. For Building from CVS HEAD you need latest Integrity build.

2007/3/22, Naveed Jauhar < njauhar@xxxxxxxx>:
Hey Eugene,

I am sending some of the errors in the e-mail. Most of the errors follow this general pattern, where the variable cannot be resolved. Maybe this will help you point me to the right direction.


Severity and Description        Path    Resource        Location        Creation Time   Id
_gc cannot be resolved  org.eclipse.mylar/sandbox/org.eclipse.mylar.zest.core/src/org/eclipse/mylar/zest/core/internal/gefx     ThreadedGraphicalEditor.java    line 42 1174508770429   6598
_internalNodes cannot be resolved       org.eclipse.mylar/sandbox/org.eclipse.mylar.zest.layouts/src/org/eclipse/mylar/zest/layouts/algorithms  AbstractLayoutAlgorithm.java     line 372        1174508764634   1556
_viewer cannot be resolved      org.eclipse.mylar/sandbox/org.eclipse.mylar.zest.tests/src/org/eclipse/mylar/zest/tests SampleNestedView.java   line 83 1174508762776   503
AbstractActiveChangeSetProvider cannot be resolved to a type     org.eclipse.mylar/org.eclipse.mylar.team/src/org/eclipse/mylar/internal/team    ContextActiveChangeSetManager.java      line 77 1174508778894   13328
AbstractAttributeFactory cannot be resolved to a type   org.eclipse.mylar /org.eclipse.mylar.tasks.ui/src/org/eclipse/mylar/tasks/ui/wizards     NewTaskWizard.java      line 71 1174508779660   13962
AbstractCommitTemplateVariable cannot be resolved to a type     org.eclipse.mylar/org.eclipse.mylar.team/src/org/eclipse/mylar/internal/team/template   CommitTemplateManager.java      line 142        1174508778832   13025


Also, It seems like I am some how not linking any of the packages. In the source code for a major chunck of the packages, there is the following error:

package org.eclipse.mylar.internal.team.template; The declared package doesn't match the expected package. Does the package name included depend on the physical path of the source? Also how do I go about fixing missing or misnamed packages?

Thanks Again.

Warm regards,
Naveed



-----Original Message-----
From: mylar-dev-bounces@xxxxxxxxxxx
[mailto: mylar-dev-bounces@xxxxxxxxxxx]On Behalf Of Eugene Kuleshov
Sent: Wednesday, March 21, 2007 3:43 PM
To: Mylar developer discussions
Subject: Re: [mylar-dev] Developing Mylar on Eclipse



  I am running out of ideas. Have you tried to close all those projects
(but don't delete then!) then open them again and run Project / Clean...
on all of them after that?

  You can also try Open Type dialog (Ctrl-Shift-T) to see if type X is
anywhere in your workspace. It should show you the project as well...
Also, package names usually match the project name, so you may be able
to track down missing project if project set is actually out of date.
Though I saw Mik updated those not long time ago and they should be
completely self contained.

  regards,
  Eugene


Naveed Jauhar wrote:
> Thanks again Eugene for your timely help.
>
> I have followed the directions in the instructions page.
>
> 1) I created a new workspace and imported the mylar source.
>
> 2) I Ran the source as an Eclipse Application. This started a new 3.2 work bench and gave me about 21,000 errors before it ran out of memory and crashed.
>
> 3) It seems like I am missing some packages because all the visible errors seem to be of type "X cannot be resolved". Do I have to manually add packages. I would think the source always comes preconfigured with all the necessary packages. Any advice? Perhaps I need to edit the compiler settings?
>
> 4) Also, Is this the correct path to follow? If the compilation goes thought correctly, will I be able to see the Mylar changes I have made in the new workbench?
>
> Thanks again for all your timely help.
>
> Warm Regards,
> Naveed
>
>
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx
> [mailto: mylar-dev-bounces@xxxxxxxxxxx]On Behalf Of Naveed Jauhar
> Sent: Wednesday, March 21, 2007 2:24 PM
> To: Mylar developer discussions
> Subject: RE: [mylar-dev] Developing Mylar on Eclipse
>
>
> Thanks Eugene. I am following the instrucitons for the build process right now. The instructions seem to be self contained. I will keep you guys posted.
>
> Also, I made a small error earlier. I infact checked out from the e_3_2 branch and wrote that I check out from the CVS HEAD.
>
> Thank You for your timely support.
>
> Warm Regards,
> Naveed
>
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx
> [mailto:mylar-dev-bounces@xxxxxxxxxxx]On Behalf Of Eugene Kuleshov
> Sent: Wednesday, March 21, 2007 2:01 PM
> To: Mylar developer discussions
> Subject: Re: [mylar-dev] Developing Mylar on Eclipse
>
>
>
>   First of all CVS HEAD requires Eclipse 3.3M6
>
>   You can checkout from e_3_2 branch if you need version for Eclipse
> 3.2. The wiki page has separate project set for that branch.
>
>   See "Self hosting" section for instruction how to run/debug Mylar from
> within Eclipse. The key point is that you should use "Eclipse
> Application" as a launch configuration type.
> http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Self-hosting
>
>    See Build Section on the same wiki page with the instructions how to
> build the distribution.
> http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Building_a_distribution
>
>   regards,
>   Eugene
>
>
> Naveed Jauhar wrote:
>
>> Thank you for replying Eugene. I have followed the instructions found at:
>>
>> http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Workspace
>>
>> 1) My JRE is up to date and the J2SE points to the JRE correctly.
>>
>> 2) I have downloaded the entire source head from the cvs. I need to modify the bugzilla UI and Connector to implement the changes needed for our needs. I then need to compile the plugin into a jar to use it internally at my workplace.
>>
>> 3) I have tried running the source as a java 5 application. However, i don't think that's the path to follow. Firstly, the compiler throws about 5000 errors before it crashes. Also, I am not sure how the java 5 run command will create a 3.2 workbunch to test the plugin.
>>
>> 4) I have also tried making a sample "Hello World" PDE application and linking the mylar source to the source folder. That also throws 500+ errors.
>>
>> 5) The ANT build files are not being created using the pde tools options either.
>>
>> Again, I am sure I am making this more complicated than it's really is. The source should be able to compile and run with little effore, since active modification and development takes place on a daily basis.
>>
>> I have also tried reading up on PDE dev environment, but that doesn't lead me anywhere.
>>
>> Any help/suggestion will be immensely appreciated.
>>
>> Warm Regards,
>> Naveed
>>
>>
>>
>>
>
> _______________________________________________
> 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
> _______________________________________________
> 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
_______________________________________________
mylar-dev mailing list
mylar-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylar-dev


Back to the top