[ https://issues.apache.org/jira/browse/LABS-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736397#action_12736397 ]
Simone Gianni commented on LABS-397: ------------------------------------ No modifications were required for the case of a project depending on another one. In that case, AJDT will correctly use the output folder from the other project to use in the current one. Sporadically, a complete rebuild has been necessary. This is mostly due, IMO, to the fragility of the system as a whole, like all the state AJDT is preserving between builds. It could also be a side effect of the recursive builds, making some of the builders working on partial and inconsistent data. After the complete rebuild, the project see all the classes of the other project, weaved correctly. The project is build having also the "extra-classes" output dir in its classpath. This should not be a problem, cause the proprity is source folders -> maven jar files -> other projects, so those classes should nearly never been used. It could be nice to exclude them completely, just to avoid possible collisions and to make the process faster, but I haven't found a way to avoid exporting certain output-folders. Setting an exclude on the dependency's IClasspathEntry could work, but that dependency is managed by M2e and I'd like to avoid hacking more than strictly needed. > [build] Eclipse support for Magma projects > ------------------------------------------ > > Key: LABS-397 > URL: https://issues.apache.org/jira/browse/LABS-397 > Project: Labs > Issue Type: New Feature > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > Basic support in Eclipse for Magma projects. This should include : > - A Magma project nature > - Maven -> ADJT hooks (and hacks) as per LABS-385 > - Predefined maven build goals (for magma:run/magma:war) > - Generating magma.locals automagically based on workspace resolution > It could in the future include also : > - A Magma specific "Add dependency" wizard > - magma:war as an export/WTP integrated function > - Host of a revamped developers tools plugin > The overall goal of this issue is, however, setting up the user Eclipse to > have him start coding with Magma as fast as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscr...@labs.apache.org For additional commands, e-mail: labs-h...@labs.apache.org