You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mario Ivankovits (JIRA)" <de...@myfaces.apache.org> on 2007/10/20 20:38:51 UTC
[jira] Resolved: (ORCHESTRA-5) Unable to load orchestra into
eclipse
[ https://issues.apache.org/jira/browse/ORCHESTRA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mario Ivankovits resolved ORCHESTRA-5.
--------------------------------------
Resolution: Won't Fix
Assignee: Mario Ivankovits
Looks like we wont fix this just for eclipse.
Sorry!
> Unable to load orchestra into eclipse
> -------------------------------------
>
> Key: ORCHESTRA-5
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-5
> Project: MyFaces Orchestra
> Issue Type: Wish
> Environment: xp, eclipse 3.3
> Reporter: Dan Tran
> Assignee: Mario Ivankovits
>
> this problem is related to http://jira.codehaus.org/browse/MECLIPSE-317 where one can generate eclipse project files using
> mvn eclipse:eclipse. However after loading the project into eclipse, core15 and examples are not buildable
> However, rather waiting for this fix, I would suggest we rename all module directory names to match with corresponding artifactIds
> - svn move core myfaces-orchestra-core
> - svn move core15 myfaces-orchestra-core15
> - svn move examples myfaces-orchestra-examples
> - remove SCM elements in all sub module, we dont need them any more
> - rename artifactId of the example from myface-orchestra-examples-project to myfaces-orchestra-examples
> This will make the Orchestra adoption a bit easier for new developer who main IDE is eclipse.
> I just did it in my local disk, It works great.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.