[ http://jira.andromda.org/browse/AAAA-3?page=all ]
Tim Dysinger updated AAAA-3:
----------------------------
Attachment: classpath.txt
> Eclipse (by far the most popular java IDE) isn't very well supported in
> AndroMDA sources
> ----------------------------------------------------------------------------------------
>
> Key: AAAA-3
> URL: http://jira.andromda.org/browse/AAAA-3
> Project: AndroMDA 4
> Type: Bug
> Environment: OS X 10.4, JDK 1.4.2, Eclipse 3
> Reporter: Tim Dysinger
> Assignee: Matthias Bohlen
> Attachments: classpath.txt
>
> The .classpath entries in andromda-all are completly old and not in sync with
> the poms. I have hacked together a hand written .classpath file for myself
> that works, but in the long run there is a need to automatically generate
> this .classpath file from the poms recursively for eclipse users (like
> myself).
> Ideally, this .classpath file should not be in CVS but instead should be
> generated by running Maven2 on the project - much like the andromdapp /
> eclipse maven2 plugin that is used in andromda applications.
> I have an improved andromdapp patch (See bug AAAA-2) for generating
> .classpath which I am using for my andromda projects. Could we use a
> "dog-food" like approach for andromda-all (and maybe all the multi-projects
> in andromda)?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
