[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-4262) Bad classpath for eclipse project in seam-gen generated .classpath file

[Norman Richards (JIRA)]

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

Norman Richards closed JBSEAM-4262.
-----------------------------------

    Fix Version/s: 2.2.0.GA
       Resolution: Done


Fixed.

> Bad classpath for eclipse project in seam-gen generated .classpath file
> -----------------------------------------------------------------------
>
>                 Key: JBSEAM-4262
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4262
>             Project: Seam
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 2.2.0.CR1
>            Reporter: Ondrej Skutka
>            Assignee: Norman Richards
>             Fix For: 2.2.0.GA
>
>         Attachments: unusedlibs.txt
>
>
> There is a bad classpathentry in a .classpath file (for eclipse) in generated project. lib/hibernate.jar should be lib/hibernate-core.jar due to hibernate upgrade. 
> There are also libraries in created projects lib dir that are not in a .classpath file. Please consider adding those, which may be utilized by eclipse (trinidad-api ?). In attached file there are libraries which are in project's lib directory, but are not in the .classpath file.
> Following are libraries that were added to project's lib directory since 2.1.2 version:
> darkX.jar
> drools-decisiontables.jar
> drools-templates.jar
> ejb3-persistence.jar
> glassX.jar
> hibernate-core.jar
> jstl.jar
> laguna.jar
> meldware.deployable
> mvel2.jar
> trinidad-api.jar
> trinidad-impl.jar
> xml-apis.jar

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