[
https://issues.jboss.org/browse/JBDS-2259?page=com.atlassian.jira.plugin....
]
Galder Zamarreño reopened JBDS-2259:
------------------------------------
Hmmm, seems like we've gone the opposite way now.
My lift dependencies, which bring in Scala, are defined as provided:
<dependency>
<groupId>net.liftweb</groupId>
<artifactId>lift-mapper_${version.scala}</artifactId>
<version>2.4</version>
<scope>provided</scope>
</dependency>
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?
Scala jar missing in WAR when project uses JBDS and Scala IDE
-------------------------------------------------------------
Key: JBDS-2259
URL:
https://issues.jboss.org/browse/JBDS-2259
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Upstream
Affects Versions: 5.0.0.GA
Reporter: Galder Zamarreño
Assignee: Fred Bricon
Labels: scala, upstream
Fix For: 5.x, 6.0.0.Beta1
Attachments: m2e-scala-0.4.2-SNAPSHOT-site.zip, standard-lift-app-JDBS.png,
standard-lift-app-Maven.png
I've discovered a bug in JBDS/Eclipse.
The application is:
https://github.com/escalante/escalante-quickstart/tree/master/standard-he...
If I build a war with Maven, it includes all the jars, see:
https://dl.dropbox.com/u/6148072/standard-lift-app-Maven.png
If I build the war, it seems to forget the scala-library jar (at least), see:
https://dl.dropbox.com/u/6148072/standard-lift-app-JDBS.png
Of course, without the scala-library jar, the application fails to deploy when deployed
via JDBS.
Note: This is a JDBS instance installed with Scala 2.9 IDE, and the IDE correctly
identifies the project being a Scala project.
--
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