Andreas Rückert wrote:
Hi!

(...)
I had to modify the Argo manifest to include the cpp now. Would be better, if it
would be enough if it's in the ext/lib directory, or so. But seems like the java
module also uses the antlr jar from the main Argo app?

Luis, do you want to look at the code? Would be great, if could fix the next 
issues
together, so this little subproject goes forward and Jan can use it soon...

Hi Andreas,

sure I would like to see it and help in anything like revision and "light testing" :-)

Concerning jcpp integration into ArgoUML I think it should be possible for modules to declare additional jars that must be loaded or, if it isn't we should create an issue for the ArgoUML module loader to support it.

Another option is to do what Eclipse does: repackage the jcpp into a jar that has a slightly modified MANIFEST.MF and has a class that implements ModuleInterface with empty implementations for enable and disable. Or better, place it as a new module of argouml-cpp.jar, say org.argouml.language.cpp.preprocessor.Preprocessor, that includes the jcpp - I don't know right now how this is achievable, but, the Eclipse guys do it for Ant and other libraries wrapped as plugins.
Or should I create an attachment to issue 2947, or so?

I think a branch of argouml-cpp is the ideal way to proceed for now in things related to the preprocessor new development since we're approaching 0.26. But, anything that is necessary in the existing reveng code could go directly to trunk - the reveng is still pre-alpha and mainly the result of a spike, so any improvements coming from your work or needs related to it are welcome.

So, I think you have commit rights to argouml-cpp as you're a core developer. Therefore, please make a SVN branch for the preprocessor and any changes you want in reveng. I will look into it as you proceed and try to integrate as much as possible into trunk.

Is this strategy OK for you?
Ciao,
Andreas


Regards,

Luis

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to