[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4869) cannot mount existing projects with custom dir structure

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-4869:
---------------------------------------

    Fix Version/s: 3.2.next


This jira describes a common issue on what users will see when importing/migrating fromother IDE's and project structures.

The problem is it involves many parts, i.e. Seam facets behavior but also how Eclipse core and WTP behaves....we should at least look at our parts not making the situation worse.

> cannot mount existing projects with custom dir structure
> --------------------------------------------------------
>
>                 Key: JBIDE-4869
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4869
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.0.0.GA, 3.0.1.GA, 3.1.0.M1, 3.1.0.M2
>         Environment: any
>            Reporter: deanhiller
>             Fix For: 3.2.next
>
>
> We currently work in MyEclipse and everything works awesome.  JBoss tools has some other features we want, but alas, we can't set our project up in jboss tools.  There seem to be too many issues.  Not sure if this is a feature request or bug (ie. I can't use the product without this feature so does that make it a bug?)
> Issue #1 : We have a dependency on an EJB3 project and those class files never get deployed to the server so the server ends up with ClassNotFoundException(ie. we can't debug unless we do attach source and then hot deploy fails unlike MyEclipse which works like a charm).
> Issue #2 : As soon as we give jboss tools our webroot which is project/input/webroot/WEB-INF, it copies all the libraries and class files there which is causing havoc with our source control and our ant build system as generated files are NOT suppose to ever be put in project/input directories.  We have a special output directory if you need a location OR you could change to the way MyEclipse does it and put it on the server....either way, this should be configurable so it is not screwing with people's build systems.
> Our custom directory structure works for jar projects and war projects and looks like so
> project
> ---input
> ------javasrc - the *.java files 
> ------libexclude - the jar files that do not go to WEB-INF/lib
> ------libinclude - the jar files that should be put in WEB-INF/lib
> ------webroot - all the xhtml files and jpgs
> ---------WEB-INF - all descriptor files
> jboss tools throws all this junk stuff in WEB-INF/lib and WEB-INF/classes when it should not generate anything unless there is an override for it.  All of this stuff works in MyEclipse and we would love to switch but can't.  I have seen other posts related to this same issue.

-- 
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