osdir.com
mailing list archive

Subject: [argouml-dev] SVN Migration: argouml-core-model and argouml-core-model-mdr eclipse projects are wrong - msg#00104

List: db.axion.devel

Date: Prev Next Index Thread: Prev Next Index
There is a little bit problem with argouml-core-model and
argouml-core-model-mdr eclipse projects.

After doing the checkout, they appear like src/model and
src/model-mdr, not argouml-core-model and argouml-core-model-mdr
respectively. This makes bad references when building.

Maybe you can fix that. Thanks in advance. :)

--
Christian LÃpez EspÃnola
Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

RE: [argouml-dev] What replaces PluggableImport and Generator2? (and other language module questions)

Linus said: > It says already in the deprecation statement of > PluggableImport that the Import class has no registration > method so it should come as no surprise. Oops, missed that part! > The details on the Import interface and registration are not > decided. If it were, the registration method would most > likely be there. Who owns this decision about what these details are? I'm not sure I understand how the old interface can be deprecated if there's nothing to replace it. From the documentation it appears that this "new" architecture is 2 years old. What action are module implementers expected to take? As I understand it, the general thrust is to: a) distribute the plugin mechanism among the various subsystems rather than having it be centralized and b) invert the registration responsibility so that modules explicitly register themselves rather than being implicitly registered based on the interfaces that they implement. Is there an example which demonstrates how this general theory works in practice? Perhaps not for Import, but maybe for one of the other pluggable module types? As a general principle, I think we should make the plugin API only as wide as is necessary. The more surface area it has, the less flexibility we have in changing things in the future. Speaking of the future, if this is completely undefined territory, is there any reason not to just adopt a complete working specification and/or implementation from somewhere else? Perhaps the Eclipse, OSGi, NetBeans, or some other API? That would save us from having to design and implement another proprietary framework API. I'd really like to see us get out of the business of doing non-core infrastructure work. Tom

Next Message by Date: click to view message preview

RE: [argouml-dev] FW: ArgoUML: invitation to join Conservancy

Linus said: > About the governance structure I didn't see any need to make > changes for this purpose either. That means a single supreme > leader as it is documented in the "About box" and on the > Project ArgoUML Members with Responsibilities page. As opposed to the top of the home page where there are four owners listed (including one who works for a competitor). I had hoped that part of this formalization process would be cleaning up some of the the historical ownership issues and formalizing the governance with a charter and process that everyone bought into. Admittedly the project is on the small side for any great degree of formality, but if things are going to be controlled unilaterally, why even go to the trouble of signing up with the Conservancy? We could just have the Google funds and other donations deposited in the project leader's bank account and dispersed from there. Tom

Previous Message by Thread: click to view message preview

[argouml-dev] how to generate code from the sequence diagram?

Hello to all,     I want to generate code from the sequence diagram ,but argouml generates code  from the  class diagram .How should i start and which classes are involved in code generation and is this posible to generate code from sequence diagram?   Regards , Saad   Send instant messages to your online friends http://uk.messenger.yahoo.com

Next Message by Thread: click to view message preview

RE: [argouml-dev] SVN Migration: argouml-core-model and argouml-core-model-mdr eclipse projects are wrong

> There is a little bit problem with argouml-core-model and > argouml-core-model-mdr eclipse projects. > > After doing the checkout, they appear like src/model and > src/model-mdr, not argouml-core-model and > argouml-core-model-mdr respectively. This makes bad > references when building. This shouldn't have happened if you checked out those directories separately (the same way you used to with CVS). The .project file in those directories contains the correct name and other Eclipse project info. I'm in the process of updating the project set file, so if you want to wait a little while you can use that to automate the process, but you should also be able to get things set up correctly without it. I successfully checked out all the projects from SVN without problems. Tom
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by