Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 827939
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T03:39:02+00:00 2026-05-15T03:39:02+00:00

I have a Scala project in Eclipse that I need to package up so

  • 0

I have a Scala project in Eclipse that I need to package up so I can deploy it to a server. It’s based on Jetty but it runs as a standalone application. It contains Scala classes, Java classes and a number of 3rd party jars.

I assumed there would be some kind of deployment option in the Scala Eclipse plugin but I’ve drawn a blank.

What is the simplest way to package the Scala project into a runnable file so it can be deployed?

Any help greatly appreciated.
Cheers.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T03:39:02+00:00Added an answer on May 15, 2026 at 3:39 am

    After a lot of trial and error, this is the best method I found for packaging the Scala app for distribution:

    First, create a Java class to be the main entry point for the application as described by Gary Boon. This allows you to run the application from a JAR with the java command. I found that running a Scala class with the java command is problematic, even when you have the Scala libs on the source path:

    import java.util.ArrayList;
    
    import scala.tools.nsc.MainGenericRunner;
    
    
    public class Main { 
        public static void main (String[] args) {
            ArrayList<String> argList = new ArrayList<String>();
            argList.add("fully.qualified.ClassName");
            for (String s : args) {
                argList.add(s);
            }
            MainGenericRunner.main(argList.toArray(new String[0]));
        }
    }
    

    Now you can use Eclipse’s Export Runnable JAR command to package up all your classes and libraries into a JAR file. Set the JAR’s main class to the Java entry point. You can also save the Eclipse-generated output settings as an ANT build file so you can make adjustments. Using ANT to create the JAR with a Java entry point yielded best results. You can also package up other JAR dependancies this way which makes it a whole lot simpler when trying to run the JAR on a different host. As a minimum you will need the Scala library and the Scala tools JAR.

    <zipfileset excludes="META-INF/*.SF" src="${scala.lib.jar}"/>
    <zipfileset excludes="META-INF/*.SF" src="${scala.tools.jar}"/>
    

    If you’re using embedded Jetty, as I am, you can run the server as a Daemon process using the following command (source):

    nohup java -jar MyJettyServer.jar < /dev/null >> server.log 2>> server_error.log &
    

    This runs the program as a background process which is independent of the current user session so the process will continue after you logout of the host.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.