Developer Studio (JBoss Developer Studio)
  1. Developer Studio (JBoss Developer Studio)
  2. JBDS-2259

Scala jar missing in WAR when project uses JBDS and Scala IDE

    Details

    • Similar Issues:
      Show 10 results 

      Description

      I've discovered a bug in JBDS/Eclipse.

      The application is: https://github.com/escalante/escalante-quickstart/tree/master/standard-helloworld-lift

      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.

        Issue Links

          Activity

          Hide
          Fred Bricon
          added a comment -

          Resolving as PR has been merged upstream, new 0.4.2 version should be made available soon(tm) : https://github.com/sonatype/m2eclipse-scala/pull/22#issuecomment-9061146

          Show
          Fred Bricon
          added a comment - Resolving as PR has been merged upstream, new 0.4.2 version should be made available soon(tm) : https://github.com/sonatype/m2eclipse-scala/pull/22#issuecomment-9061146
          Hide
          Galder Zamarreño
          added a comment -

          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.45%20PM.png

          Who's responsibility is this?

          Show
          Galder Zamarreño
          added a comment - 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.45%20PM.png Who's responsibility is this?
          Hide
          Fred Bricon
          added a comment -

          Galder, you're right the whole scala library is deployed, regardless of each individual jar scope (https://github.com/sonatype/m2eclipse-scala/commit/b69842b4fc3004aac271da091e9d9933f4448de1#L0R361). This is clearly an oversight. But can you please open a separate issue?

          Show
          Fred Bricon
          added a comment - Galder, you're right the whole scala library is deployed, regardless of each individual jar scope ( https://github.com/sonatype/m2eclipse-scala/commit/b69842b4fc3004aac271da091e9d9933f4448de1#L0R361 ). This is clearly an oversight. But can you please open a separate issue?
          Hide
          Galder Zamarreño
          added a comment -

          Added: JBDS-2387

          Show
          Galder Zamarreño
          added a comment - Added: JBDS-2387
          Hide
          Vlado Pakan
          added a comment -

          Verified with JBT 4.0.0.CR1-v20121128-2332-B107.

          Show
          Vlado Pakan
          added a comment - Verified with JBT 4.0.0.CR1-v20121128-2332-B107.

            People

            • Assignee:
              Fred Bricon
              Reporter:
              Galder Zamarreño
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: