New package and new class artifacts

Please use this forum to signal bugs.
Merci d'utiliser ce forum pour signaler des bugs.

New package and new class artifacts

Postby Dan » Mon 14 May 2018 15:27

Hi de-buggers,

Under the browser main project I added a class view, class diagram and a test class.
If I right click on the class I see "create source artifact". ok.

I created new package under the main project browser package, then a class diagram and then a class.
If I right click on the class I DO NOT see "create source artifact". ??

I looked in every menu and right clicked everything I can see but have not found "create source artifact".

What am I doing wrong?
Dan
 
Posts: 33
Joined: Sat 12 May 2018 13:55
Location: England

Re: New package and new class artifacts

Postby Dan » Mon 14 May 2018 15:34

Solved
- the new class view, if edited, has a deployment view drop down, once I select the deployment view then I get a create artifact option for the class.

So may be that should be selected by default if there is only one deployment view?
Dan
 
Posts: 33
Joined: Sat 12 May 2018 13:55
Location: England

Re: New package and new class artifacts

Postby Dan » Mon 14 May 2018 15:45

No - still a problem -

If I edit the test package headers and source settings - say to testPackage ,
call generate c++ the test class is still placed in old deployment location ...
Dan
 
Posts: 33
Joined: Sat 12 May 2018 13:55
Location: England

Re: New package and new class artifacts

Postby Dan » Mon 14 May 2018 15:49

SOLVED ...

So you have to have
edit package-> point to the new headers and source directory
edit class view -> deployment view to testDeployment
edit class edit -> artifact name in testPackage
then call generate c++ and it works ...

so many hoops ....
Dan
 
Posts: 33
Joined: Sat 12 May 2018 13:55
Location: England

Re: New package and new class artifacts

Postby Bruno Pagès » Mon 14 May 2018 16:37

Dan wrote:- the new class view, if edited, has a deployment view drop down, once I select the deployment view then I get a create artifact option for the class.
So may be that should be selected by default if there is only one deployment view?

Yes and no, I prefer to have the association explicit, and to allow the class view and deployment view to be under a different package

Furthermore you can create a class view and its associated deployment view in one step ("new class and deployment views") so it is very easy to have that association between them
ImageAuthor of Bouml
Bruno Pagès
 
Posts: 596
Joined: Mon 20 Feb 2012 09:23
Location: France

Re: New package and new class artifacts

Postby Bruno Pagès » Mon 14 May 2018 16:43

Dan wrote:If I edit the test package headers and source settings - say to testPackage ,
call generate c++ the test class is still placed in old deployment location ...

The generated files are represented by the artifact, so the location where the files are generated is specified by the package containing the deployment view where the artifact is ( the package containing the class is not relevant ), and if the package doesn't specify the directories the code generator look at the directories specified through the generations settings.

Note that the directories can be specified absolute or relative to the project
ImageAuthor of Bouml
Bruno Pagès
 
Posts: 596
Joined: Mon 20 Feb 2012 09:23
Location: France


Return to Bug reports / Rapports de bugs

Who is online

Users browsing this forum: No registered users and 2 guests

cron