Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-ocl.dev] CVS Clean Up

Hi Adolfo

Well done on the Javadoc build. Looks like it's just what's needed. You might want to post a clear 5-10 line announcement/explanation to cross-project-dev.

a) The policy:
Javadoc in a separate downloads directory: where?
referenced from doc plugin: how?
maintained manually per minor release
b) The manual build action
check MANAGE_JAVADOC
c) The releng tooling
see Bugzilla ... comment ...

I'm not sure if the "org.eclipse.ocl.test.examples" was an erroneous created folder...

Well it's empty, so probably. Need to check for branches.
On the other hand, there are some projects which are not used anymore (org.eclipse.emf.ocl.*) but we agreed on maintain said projects with a README.TXT so that every body could easily switch to a tagged old version.
No. We can only delete accidents that only very briefly had 'valid' contents. It must always be possible for someone to get all the code for e.g. MDT/OCL 1.1 which will be in emf.ocl.*.
In any case, I've detected some projects which could probably be "cleaned" with a simple README.txt:

- org.eclipse.emf.ocl.tests-feature
- org.eclipse.ocl.standalone.tests (I think this were an obsolete tests project)
Yes. All yours. I'm kind of busy on last M6 fixes/tutorial.

Could you (ed) have a look to the examples projects, you might have a better criteria about which projects are relevant for the project (perhaps there might be some obsolete projects which came from the IMP-based editors).
I was going to leave them for one more year when we should have some ANTLR - LPG compatibility.

And since I haven't had any time for QVTd, QVTd still uses the LPG parsers/editors.

    Regards

        Ed


Back to the top