]
Max Rydahl Andersen commented on JBIDE-13127:
---------------------------------------------
since this is not jbds specific moving to JBIDE.
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.4...
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: