[
https://issues.jboss.org/browse/JBDS-2259?page=com.atlassian.jira.plugin....
]
Fred Bricon commented on JBDS-2259:
-----------------------------------
So this is a known issue in
[
m2e-scala|https://github.com/sonatype/m2eclipse-scala/issues/8]. I left some instructions
on how to fix it upstream. I can provide a patch if [~maxandersen] wants it, otherwise,
I'll close this JIRA as WON'T FIX.
As a workaround, you should open your project .settings/.classpath and mark the Scala
classpath library as deployable :
{code:xml}
<classpathentry kind="con"
path="org.scala-ide.sdt.launching.SCALA_CONTAINER">
<attributes>
<attribute name="org.eclipse.jst.component.dependency"
value="/WEB-INF/lib"/>
</attributes>
</classpathentry>
{code}
Then clean/republish on your server.
!http://content.screencast.com/users/fbricon/folders/Jing/media/ba6fa90d-573b-42e8-9ad2-276b71de227f/2012-09-03_1050.png!
Scala jar missing in WAR when project using JDBS 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
Attachments: 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