[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2709) Checking out projects using Subclipse voids certain Eclipse files

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-2709:
---------------------------------------

    Fix Version/s: 3.0.0.cr1
                       (was: 3.0.0.beta1)


slip all minor and below

> Checking out projects using Subclipse voids certain Eclipse files
> -----------------------------------------------------------------
>
>                 Key: JBIDE-2709
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2709
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.1.2
>         Environment: JBoss Tools 2.1.2.GA; Eclipse 3.3.4; Windows XP SP2
>            Reporter: Chris Simons
>            Priority: Minor
>             Fix For: 3.0.0.cr1
>
>
> When checking out a project from SVN for the first timeusing Subclipse, I have to "fix" the following files:
> /workspace/project/.project
> /workspace/project/.settings/jboss....wst.xml
> Reason: Even if these two files are checked-into the project/branch, these will be "hard-coded" for the previous project.  Therefore, I have to go into the two files above and replace project names.  Also, the JSF Capabilities are removed from .project.  What I normally do w/ this file is copy/paste from a good .project into the new .project file.
> Before I do any of this, I notice a few things about this newly checked out project:
> 1) Right-click, Properties...
> a) "Java Compiler" is not available.
> b) Seam settings is set to null even though the file should show that it is Seam 2.0
> After I set Seam settings properly, custom Seam components do not get recognized until I restart the project and fix the above two files.
> I hope this makes some sense.  I can attach .project and .xml files if you'd like.
> Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira