[jbosstools-issues] [JBoss JIRA] (JBIDE-13127) Scala jars added to deployment when they should not

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-13127:
-------------------------------------

Problem is even if we modify each IClasspathEntry of the scala library, those changes won't be serialized and will be lost on subsequent workspace restart.
One solution would be to start a background job to "fix" all scala classpath libs on workspace startup, but this is the kind of thing that happily leads to deadlocks while JDT/m2e initializes.

If anyone has a better solution, please let me know.
                
> Scala jars added to deployment when they should not
> ---------------------------------------------------
>
>                 Key: JBIDE-13127
>                 URL: https://issues.jboss.org/browse/JBIDE-13127
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.3.0.Final
>            Reporter: Galder Zamarreño
>            Assignee: Fred Bricon
>              Labels: scala, upstream
>             Fix For: 4.1.x
>
>
> Hmmm, seems like we've gone the opposite way now.
> My lift dependencies, which bring in Scala, are defined as provided:
> {code}<dependency>
> <groupId>net.liftweb</groupId>
> <artifactId>lift-mapper_${version.scala}</artifactId>
> <version>2.4</version>
> <scope>provided</scope>
> </dependency>{code}
> And now, you're adding the Scala jars to the WAR when it shouldn't? See screenshot:
> https://dl.dropbox.com/u/6148072/Screen%20Shot%202012-11-14%20at%206.26.45%20PM.png
> Who's responsibility is this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira