I had this problem too recently, I think that that tutorial is out of date… The key.alias etc directives need to be in a file named ant.properties. There’s no file called build.properties any more.
mvn clean test if [[ “$?” -ne 0 ]] ; then echo ‘could not perform tests’; exit $rc fi $? is a special shell variable that contains the exit code (whether it terminated successfully, or not) of the most immediate recently executed command. -ne stands for “not equal”. So here we are testing if the … Read more
Maven versions 2.1.0-M1 or newer have built in special variable maven.build.timestamp. <build> <finalName>${project.artifactId}-${project.version}-${maven.build.timestamp}</finalName> </build> See Maven documentation for more details. For older Maven versions a look at maven-timestamp-plugin or buildnumber-maven-plugin. If you use maven-timestamp-plugin, you can use something like this to manipulate resulting artifact name. <build> <finalName>${project.artifactId}-${project.version}-${timestamp}</finalName> </build> And this configuration for buildnumber-maven-plugin should create … Read more
The biggest difference is that Ant will ensure that dependencies declared via depends are called at most once. For example: <target name=”a” /> <target name=”b” depends=”a” /> <target name=”c” depends=”a” /> <target name=”d” depends=”b, c” /> If I call target d, b and c are called. However, a is only called once (even though both … Read more
You should use ant -version command instead. The -v option is equivalent of -verbose option. See Command-line Options Summary
You could do this with profiles… If you really wanted to use two separate profiles and customize the JAR plugin to include and exclude patterns of class and package names, you could easily do this by putting something like this in your POM: <profiles> <profile> <id>everything</id> <build> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId> <configuration> <classifier>everything</classifier> <includes> <include>**/*</include> </includes> … Read more
Since you imported the project as a General Project, it does not have the java nature and that is the problem. Add the below lines in the .project file of your workspace and refresh. <natures> <nature>org.eclipse.jdt.core.javanature</nature> </natures>
It looks like this has been reported as a Java bug. It appears to be caused by using annotations from a 3rd party library (like JUnit) and not including the jar with that annotation in the javadoc invocation. If that is the case, just use the -classpath option on javadoc and include the extra jar … Read more
An example from the Ant documentation of how to get an environment variable into a property: <property environment=”env”/> <echo message=”Number of Processors = ${env.NUMBER_OF_PROCESSORS}”/> <echo message=”ANT_HOME is set to = ${env.ANT_HOME}”/> In your case, you would use ${env.RELEASE_VER}. Then for the conditional part, the documentation here says that there are three possible attributes: Attribute Description … Read more
First of all, read the Ivy / Maven comparison from the Ivy website. The key information: First, the most important difference is that they aren’t at all the same kind of tools. Apache Maven is a software project management and comprehension tool, whereas Apache Ivy is only a dependency management tool, highly integrated with Apache … Read more