|
Re: Updates to the wiki [message #415276 is a reply to message #415275] |
Sun, 09 December 2007 12:55 |
Ed Merks Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------060908070807020402060600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Alexandros,
Thanks! Sorry for not finding time sooner to review this. It looks
great to me! It doesn't matter which OS the screen shots come from,
though consistency is nice so the way you've redone them all is
excellent. I think this should replace the old one. Feel free to over
write the contents of the old one.
BTW, I understand that folks are actually working on a design to address
109137 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137>! This
will solve the problem direct for most folks and for our team with our
need to bootstrap, i.e., use a development modified generator to
regenerate our own code, we should be able to omit the step of jarring
the plugins as well as the hack of specifying a jar instead of "." in
the MANIFEST.MF which is later turned into a "." by the build by running
the main Eclipse with a -dev argument that points at the same properties
file that PDE uses to launch the runtime workspace. Well simply be
able to exit Eclipse and start it up again to pick up the bootstrapped
changes in the main Eclipse itself.
Alexandros Karypidis wrote:
> I have tried to create a new version of the "EMF/Getting Source" page
> in the wiki. The current version is:
>
> http://wiki.eclipse.org/EMF/Getting_Source
>
> My updated version is at:
>
> http://wiki.eclipse.org/EMF/Getting_Source_NEW
>
> I've added:
>
> - a section discussing the considerations for setting up the EMF
> development environment due to bug 109137 (Section 1)
> - a description of how to check out the sources in an extension
> location and use the MakeJars script to update the tools when
> modifications are made (Section 3.1).
> - instructions for how to create the ant tasks jar in the "Resolving
> Dependency Problems" (Section 7).
> - took some extra screenshots
>
> Since I am on Ubuntu my screenshots did not "fit in" and therefore I
> replaced all the existing ones with new ones from my system.
>
> This page is not linked to from the main EMF wiki page. Please take a
> look at it and make comments for improvements. If there is no
> objection, perhaps it could replace the existing one.
--------------060908070807020402060600
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alexandros,<br>
<br>
Thanks! Sorry for not finding time sooner to review this. It looks
great to me! It doesn't matter which OS the screen shots come from,
though consistency is nice so the way you've redone them all is
excellent. I think this should replace the old one. Feel free to over
write the contents of the old one.<br>
<br>
BTW, I understand that folks are actually working on a design to
address <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137">109137</a>!
This will solve the problem direct for most folks and for our team with
our need to bootstrap, i.e., use a development modified generator to
regenerate our own code, we should be able to omit the step of jarring
the plugins as well as the hack of specifying a jar instead of "." in
the MANIFEST.MF which is later turned into a "." by the build by
running the main Eclipse with a -dev argument that points at the same
properties file that PDE uses to launch the runtime workspace. Well
simply be able to exit Eclipse and start it up again to pick up the
bootstrapped changes in the main Eclipse itself.<br>
<br>
<br>
Alexandros Karypidis wrote:
<blockquote cite="mid:fjghkl$93m$1@build.eclipse.org" type="cite">I
have tried to create a new version of the "EMF/Getting Source" page in
the wiki. The current version is:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/EMF/Getting_Source">http://wiki.eclipse.org/EMF/Getting_Source</a>
<br>
<br>
My updated version is at:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/EMF/Getting_Source_NEW">http://wiki.eclipse.org/EMF/Getting_Source_NEW</a>
<br>
<br>
I've added:
<br>
<br>
- a section discussing the considerations for setting up the EMF
development environment due to bug 109137 (Section 1)
<br>
- a description of how to check out the sources in an extension
location and use the MakeJars script to update the tools when
modifications are made (Section 3.1).
<br>
- instructions for how to create the ant tasks jar in the "Resolving
Dependency Problems" (Section 7).
<br>
- took some extra screenshots
<br>
<br>
Since I am on Ubuntu my screenshots did not "fit in" and therefore I
replaced all the existing ones with new ones from my system.
<br>
<br>
This page is not linked to from the main EMF wiki page. Please take a
look at it and make comments for improvements. If there is no
objection, perhaps it could replace the existing one.
<br>
</blockquote>
<br>
</body>
</html>
--------------060908070807020402060600--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Re: Updates to the wiki [message #415301 is a reply to message #415300] |
Tue, 11 December 2007 13:37 |
Ed Merks Messages: 33142 Registered: July 2009 |
Senior Member |
|
|
Alexandros,
I'm not sure either. I've added Nick to the CC list since he likely
knows how.
Alexandros Karypidis wrote:
> I made some last edits and put the new page up. It is now at:
> http://wiki.eclipse.org/EMF/Setting_up_a_development_environ ment
>
> I edited the main EMF page and added a link to it under the
> "Documentation & Assistance" section:
> http://wiki.eclipse.org/Eclipse_Modeling_Framework
>
> Alas, my wiki efforts have hit a wall. I can not remove the old pages
> (I think I need administrator access for that) and therefore they show
> up in the index at:
>
> http://wiki.eclipse.org/Category:EMF
>
> Any idea how to fix that?
>
> Ed Merks wrote:
>
>> Alexandros,
>>
>> Thanks! Sorry for not finding time sooner to review this. It looks
>> great to me! It doesn't matter which OS the screen shots come from,
>> though consistency is nice so the way you've redone them all is
>> excellent. I think this should replace the old one. Feel free to
>> over write the contents of the old one.
>>
>> BTW, I understand that folks are actually working on a design to
>> address 109137
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137>! This will
>> solve the problem direct for most folks and for our team with our
>> need to bootstrap, i.e., use a development modified generator to
>> regenerate our own code, we should be able to omit the step of
>> jarring the plugins as well as the hack of specifying a jar instead
>> of "." in the MANIFEST.MF which is later turned into a "." by the
>> build by running the main Eclipse with a -dev argument that points at
>> the same properties file that PDE uses to launch the runtime
>> workspace. Well simply be able to exit Eclipse and start it up
>> again to pick up the bootstrapped changes in the main Eclipse itself.
>>
>>
>> Alexandros Karypidis wrote:
>>> I have tried to create a new version of the "EMF/Getting Source"
>>> page in the wiki. The current version is:
>>>
>>> http://wiki.eclipse.org/EMF/Getting_Source
>>>
>>> My updated version is at:
>>>
>>> http://wiki.eclipse.org/EMF/Getting_Source_NEW
>>>
>>> I've added:
>>>
>>> - a section discussing the considerations for setting up the EMF
>>> development environment due to bug 109137 (Section 1)
>>> - a description of how to check out the sources in an extension
>>> location and use the MakeJars script to update the tools when
>>> modifications are made (Section 3.1).
>>> - instructions for how to create the ant tasks jar in the "Resolving
>>> Dependency Problems" (Section 7).
>>> - took some extra screenshots
>>>
>>> Since I am on Ubuntu my screenshots did not "fit in" and therefore I
>>> replaced all the existing ones with new ones from my system.
>>>
>>> This page is not linked to from the main EMF wiki page. Please take
>>> a look at it and make comments for improvements. If there is no
>>> objection, perhaps it could replace the existing one.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Updates to the wiki [message #415307 is a reply to message #415301] |
Tue, 11 December 2007 17:42 |
Nick Boldt Messages: 481 Registered: July 2009 |
Senior Member |
|
|
Pages [1] and [2] now redirect to [3]. The Category page [4] only lists
the single page now.
[1] http://wiki.eclipse.org/EMF/Getting_Source
[2] http://wiki.eclipse.org/EMF/Getting_Source_New
[3] http://wiki.eclipse.org/EMF/Setting_up_a_development_environ ment
[4] http://wiki.eclipse.org/Category:EMF
In future, you can avoid this mess by simply editing an existing page in
place, rather than creating a new clone.
That said, if you ever need to redirect a page, just replace that page's
entire contents with:
#REDIRECT [[some_wiki_page]]
eg.,
#REDIRECT [[EMF/Setting_up_a_development_environment]]
Cheers,
Nick
Ed Merks wrote:
> Alexandros,
>
> I'm not sure either. I've added Nick to the CC list since he likely
> knows how.
>
> Alexandros Karypidis wrote:
>> I made some last edits and put the new page up. It is now at:
>> http://wiki.eclipse.org/EMF/Setting_up_a_development_environ ment
>>
>> I edited the main EMF page and added a link to it under the
>> "Documentation & Assistance" section:
>> http://wiki.eclipse.org/Eclipse_Modeling_Framework
>>
>> Alas, my wiki efforts have hit a wall. I can not remove the old pages
>> (I think I need administrator access for that) and therefore they show
>> up in the index at:
>>
>> http://wiki.eclipse.org/Category:EMF
>>
>> Any idea how to fix that?
>>
>> Ed Merks wrote:
>>
>>> Alexandros,
>>>
>>> Thanks! Sorry for not finding time sooner to review this. It looks
>>> great to me! It doesn't matter which OS the screen shots come from,
>>> though consistency is nice so the way you've redone them all is
>>> excellent. I think this should replace the old one. Feel free to
>>> over write the contents of the old one.
>>>
>>> BTW, I understand that folks are actually working on a design to
>>> address 109137
>>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=109137>! This will
>>> solve the problem direct for most folks and for our team with our
>>> need to bootstrap, i.e., use a development modified generator to
>>> regenerate our own code, we should be able to omit the step of
>>> jarring the plugins as well as the hack of specifying a jar instead
>>> of "." in the MANIFEST.MF which is later turned into a "." by the
>>> build by running the main Eclipse with a -dev argument that points at
>>> the same properties file that PDE uses to launch the runtime
>>> workspace. Well simply be able to exit Eclipse and start it up
>>> again to pick up the bootstrapped changes in the main Eclipse itself.
>>>
>>>
>>> Alexandros Karypidis wrote:
>>>> I have tried to create a new version of the "EMF/Getting Source"
>>>> page in the wiki. The current version is:
>>>>
>>>> http://wiki.eclipse.org/EMF/Getting_Source
>>>>
>>>> My updated version is at:
>>>>
>>>> http://wiki.eclipse.org/EMF/Getting_Source_NEW
>>>>
>>>> I've added:
>>>>
>>>> - a section discussing the considerations for setting up the EMF
>>>> development environment due to bug 109137 (Section 1)
>>>> - a description of how to check out the sources in an extension
>>>> location and use the MakeJars script to update the tools when
>>>> modifications are made (Section 3.1).
>>>> - instructions for how to create the ant tasks jar in the "Resolving
>>>> Dependency Problems" (Section 7).
>>>> - took some extra screenshots
>>>>
>>>> Since I am on Ubuntu my screenshots did not "fit in" and therefore I
>>>> replaced all the existing ones with new ones from my system.
>>>>
>>>> This page is not linked to from the main EMF wiki page. Please take
>>>> a look at it and make comments for improvements. If there is no
>>>> objection, perhaps it could replace the existing one.
|
|
|
Powered by
FUDForum. Page generated in 0.03472 seconds