[jbosstools-issues] [JBoss JIRA] (JBDS-2387) Scala jars added to deployment when they should not
[
https://issues.jboss.org/browse/JBDS-2387?page=com.atlassian.jira.plugin....
]
Fred Bricon commented on JBDS-2387:
-----------------------------------
Individual Classpath entries of the Scala Library need to be properly set with the
(non-)deployed attribute.
We're gonna need to do some name matching between artifacts in pom.xml and jars
defined in the scala lib.
Scala jars added to deployment when they should not
---------------------------------------------------
Key: JBDS-2387
URL: https://issues.jboss.org/browse/JBDS-2387
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.0.0.GA
Reporter: Galder Zamarreño
Assignee: Fred Bricon
Labels: scala, upstream
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: http://www.atlassian.com/software/jira
