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

  • Home
  • SEARCH
  • 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 8382099
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T16:51:20+00:00 2026-06-09T16:51:20+00:00

The default ant system I have set up for my Android app has two

  • 0

The default ant system I have set up for my Android app has two different options: release and debug. I can differentiate between the two using ${build.is.packaging.debug}. I can build these in one step by doing either ant release or ant debug.

I’d like to be able to add a third option: beta. This way I can enable certain flags for beta users that I don’t want normal users to see while still leaving out my debugging code. Where in the ant build system do I specify a new target?

  • 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-06-09T16:51:21+00:00Added an answer on June 9, 2026 at 4:51 pm

    If you open your project build.xml you will find there targets release and debug. You should create new one similar with name beta and set apply your specific parameters there.

    Here is mine example of simple ant build process:

    <project name="j2me_library" default="build" basedir=".">
       <property name="build.version" value="1.0.0" />
       <property name="build.name" value="library-${build.version}" />
    
       <property name="src" value="src" />
       <property name="lib" value="lib" />
    
       <property name="build" value="build" />
       <property name="classes" value="${build}/classes" />
       <property name="dist" value="${build}/dist" />
    
    
       <!--
        the "build" target is the default entry point of this script
       -->
       <target name="build" depends="package" />
    
       <!--
        the "clean" target will delete the build directory which contains lots of mess from the previous build
       -->
       <target name="clean">
        <delete dir="${build}" />
       </target>
    
       <target name="prepare" depends="clean">
        <mkdir dir="${classes}"/>
        <mkdir dir="${dist}"/>
       </target>
    
       <!--
        the "compile" target generates the .class files from the .java sources
       -->
       <target name="compile" depends="prepare">
        <path id="lib.files">
          <fileset dir="${lib}">
            <include name="*.jar" />
          </fileset>
        </path>
    
        <property name="lib.classpath" refid="lib.files" />
    
        <javac srcdir="${src};"
            destdir="${classes}"
            includeantruntime="false"
            classpath="${lib.classpath}"
            bootclasspath="${lib.classpath}"
            target="1.1"
            source="1.2"
        />
       </target>
    
       <!--
        the "package" target creates the jar file
       -->
       <target name="package" depends="compile">
        <jar destfile="${dist}/${build.name}.jar" basedir="${classes}"/>
       </target>
      </project>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an Android application that is by default built with Ant. There is
I have the default generated ant script for my netbeans java project and it
Is there an easy way to have the Ant logger (default or other) add
I use Eclipse with ant scripts, and Eclipse works well with the default JRE
Default JVM uses maximum 1.5 GB RAM/JVM Java application. But my Server have 8
By default, an unstyled set of nested <ul> lists looks like this (in Chrome,
Let's suppose I have a valid Ant build script which packs up and prepares
I have a question about Beanshell that I can't find an answer to anywhere.
ext-Myself and two co-workers have been working on a GWT project and coding in
I have a jar file I produced from compiled class files using an ant

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.