[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5128) Runtime "jboss-seam-2.2.0.GA" does not exist

[deanhiller (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12492624#action_12492624 ] 

deanhiller commented on JBIDE-5128:
-----------------------------------

okay, that makes sense.  Would it be possible that the templates be moved into the seam jars then or moved into a jboss-seam-templates.jar that if in the classpath was auto-detected?

This makes it much easier to use with source control.  I remember back when IDEs where not too compatible with source control and it brings back nightmares.  today, nearly all IDE's work seamlessly with source control but jboss tools seems to be violating that bringing back hardcoded paths on the filesystem.  I just would love to see it be perfect EVEN if it is marked as a low priority to be done after the bigger fish to fry(which is why I marked it minor)

> Runtime "jboss-seam-2.2.0.GA" does not exist
> --------------------------------------------
>
>                 Key: JBIDE-5128
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5128
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.1.0.M4
>            Reporter: deanhiller
>            Priority: Minor
>
> This issue shows up in 3.1.0.M4 but M4 is not a choice in affected versions.
> 1. create a seam project and add seam support via the project properties seam settings.
> 2. check in the project
> 3. have someone else checkout the project now
> Error: Runtime "jboss-seam-2.2.0.GA" does not exist.
> Most project are created so that developers can checkout and start coding.  this error is very annoying and not finding the runtime should not be an error seeing as how the project compiles fine, the ant build file works and it even deploys to tomcat from eclipse just fine.  This error should perhaps be a warning or not shown at all if we don't want it to.  People are getting confused and I keep telling them to just ignore the stupid error.

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