| Re: [mdt-papyrus.dev] How to recompile Papyrus standalone |
I'm pretty sure that in this instance it was my fault. I was trying to guess at what variables could be active in the
text box for the Papyrus Git Folder location. At the time I didn't realize that "org.eclipse.papyrus" would be appended
to the folder that I specified, so I entered:
Git clone location rule: "Located in the specified absolute folder location",
which then showed "${@id.location}
and Papyrus Git clone location: ${papyrus.git.clone.location/}${papyrus.git.clone.remoteURI|uriLastSegment}
which I based on some other variables I found in the same window.
This caused Oomph to dutifully create a folder of that name. My conclusion was that these variables are not available
in that context. I think that the only way for the Oomph team to fix that problem would be to force me to read the manual.
I had a second problem this morning where the domain findbugs.cs.umd.edu was not resolving. After seeing the Oomph
exception I used dig to lookup the domain and confirmed that it really was not found. It is working now and my install
completed.
I feel like I should also add some good news. My posts have tended to describe the problems and work arounds that I've
found. However overall I'm quite happy with what Oomph provides. There are some rough edges, but this is much better
than trying to manage all these pieces manually. I think that given more time the rough spots will be worked out. I
feel that the majority of my problems have been caused by my own experimentation, not by large problems in the
underlying tool.
-Andrew
On 14-07-22 05:16 PM, Christian W. Damus wrote:
> Hi, Andrew,
>
> Most interesting. If you were an early adopter of this Papyrus setup model, there may have been a conflict between
> git-repo variable values stored by Oomph in your user setup and a change I made in the Papyrus model to align with Oomph
> best practice for the git clone (on Ed's advice). But, this was very early on in the development of the model.
>
> If you see something like this again and can characterise the problem precisely, I'll be very interested. There's
> probably a bug we can raise for the Oomph team.
>
> Thanks,
>
> Christian
>
>
> On Jul 22, 2014, at 4:11 PM, Andrew Eidsness <eclipse@xxxxxxxxxx <mailto:eclipse@xxxxxxxxxx>> wrote:
>
>> This morning I had a problem similar to what Yilong described -- I wound up with only that one project in my workspace.
>>
>> My error turned out to be an invalid value in the git location text box. I had guessed at some variables that turned
>> out to be wrong. Oomph created folders explicitly named something like "${...}/${...}" and had cloned the git repo
>> into it. However, when trying to import projects into my workspace it didn't resolve the folder correctly, so it found
>> nothing to import.
>>
>> My fix was to repeat the operation replacing the complicated git repo location value with a simple path.
>>
>> -Andrew
>>
>>
>> On July 22, 2014 2:58:15 PM EDT, "Christian W. Damus" <give.a.damus@xxxxxxxxx <mailto:give.a.damus@xxxxxxxxx>> wrote:
>>
>> Hi, Yilong,
>>
>> If you included any of the "Papyrus -> Main -> UML (...)" sub-projects in your set-up, then you should have a lot
>> more than one project imported into the workspace.
>>
>> I don't understand what you're asking about the git repository. Oomph clones it for you and imports projects from
>> it according to your selections in the wizard. You don't have to clone it yourself or import all of those projects.
>>
>> If you select specific projects as shown below, you should have only a subset of the projects dealing specifically
>> with UML in your workspace.
>>
>> HTH,
>>
>> Christian
>>
>>
>>
>>
>> On Jul 22, 2014, at 2:49 PM, Yilong Yang <yylonly@xxxxxxxxx <mailto:yylonly@xxxxxxxxx>> wrote:
>>
>>> Hey Christian,
>>> Thanks for your help, Oomph Install is less pain for set up the new platform for development. However,
>>> following your tutorial only for the UML portions of papyrus, I get the clean eclipse for development(including
>>> papyrus), only one project org.eclipse.papyrus.junit.utils one the package explorer. Then I check the workplace
>>> of this new eclipse. The papyrus Repos under .get directory. Moreover, I import this git repos into eclipse. But
>>> still almost 700 projects in the workspace.
>>> So the problem is remain here:
>>> 1. how to only import the projects required by UML ?
>>> 2. which is main project i can run the standalone eclipse based on this platform.
>>> Thanks,
>>> Yilong
>>>
>>> On Wed, Jul 16, 2014 at 1:34 AM, Christian W. Damus <give.a.damus@xxxxxxxxx <mailto:give.a.damus@xxxxxxxxx>> wrote:>>> <http://eclipse.org/> node. Now you'll be able to choose the specific sub-components of Papyrus that you
>>>
>>> Hi,
>>>
>>> I'd recommend using the new Oomph setup model for Papyrus.
>>>
>>> Download and run the Oomph installer [1]. Choose an Eclipse package to base your setup on (I'd suggest the
>>> Standard package; in any case, it must be the Luna version) and on the second page of the wizard, drag and
>>> drop the papyrus.setup file [2] from your Git clone of Papyrus onto the Eclipse.org
>>> want to import from Git into your workspace to edit; just expand Eclipse.org/>>> <http://eclipse.org/><User>/Papyrus/Main and add the UML component to your set-up. The PDE target is taken
>>> care of for you, ensuring that it includes all of the dependencies needed to compile Papyrus.
>>>
>>> HTH,
>>>
>>> Christian
>>>
>>>
>>> [1] https://wiki.eclipse.org/Eclipse_Oomph_Installer
>>> [2] Find the papyrus.setup file in the releng/org.eclipse.papyrus.oomph folder in your Git clone.
>>>
>>>
>>> <PastedGraphic-1.tiff>
>>>
>>>
>>> On Jul 15, 2014, at 11:54 AM, yylonly <yylonly@xxxxxxxxx <mailto:yylonly@xxxxxxxxx>> wrote:>>>> http://yylife.me <http://yylife.me/>
>>>
>>>> Dear Papyrus`s team,
>>>>
>>>> Papyrus has very good features for UML and SysUML, I wanna make some change for supporting new features
>>>> (such as privacy on UML), then I clone Papyrus from Repos, but i found there almost 700 projects here. then
>>>> i try to import all but failures. I suppose not all the projects used for Parpus, i just need basic function.
>>>>
>>>> Hence I`d like to know,
>>>>
>>>> 1. Which projects are enough for the UML parts, then I can import them to eclipse, compile, run it into a
>>>> standalone eclipse?
>>>>
>>>> 2. Which project is the main project to run?
>>>>
>>>> Thanks,
>>>> Yilong
>>>>
>>>> --------------------------------------------------------------------------------------------
>>>> Yilong Yang
>>>> Software Engineering Lab
>>>> Department of Computer and Information Science
>>>> Faulty of Science and Technology
>>>> University of Macau (New Campus)
>>>> Taipa, Macau
>>>> E11, Room 2014
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> mdt-papyrus.dev mailing list
>>>> mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit>>> mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>>>
>>>
>>> _______________________________________________
>>> mdt-papyrus.dev mailing list
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit>>> mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
>>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>>>
>>>
>>> _______________________________________________
>>> mdt-papyrus.dev mailing list
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit>> ------------------------------------------------------------------------------------------------------------------------
>>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>>
>>
>>
>> mdt-papyrus.dev mailing list
>> mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit>> mdt-papyrus.dev@xxxxxxxxxxx <mailto:mdt-papyrus.dev@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>>
>> _______________________________________________
>> mdt-papyrus.dev mailing list
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>
>
>
> _______________________________________________
> mdt-papyrus.dev mailing list
> mdt-papyrus.dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
>
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev