Hi All
I have a maven based application, well now i want to run it in cmd mode, it
means just executing the compiled class.
How do i extract the classpath for this application from my pom easilly ?
Thanks in advance.
Roman
This might be handy for this:
http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/
2009/3/7 Roman Kournjaev kournj...@gmail.com
Hi All
I have a maven based application, well now i want to run it in cmd mode, it
means just executing the compiled class.
How do i extract the
Thanks , that's a nice plugin.
But i see it places the jars into some assembled repository, but it would be
really nice to get the classpath to the jars that are in my local maven
repository.
Thanks in advance
On Sat, Mar 7, 2009 at 1:23 PM, Wim Deblauwe wim.debla...@gmail.com wrote:
This
this should a properties file, which is available in your test classpath.
your can retrieve it in your testcase, like:
File testFile = new File(target/test-classes/test.properties);
Note that all files under src/test/resources will be moved to
target/test-classes/ when you run mvn test
On Sat,
Hi Sagara
the text inserted in the catalog is:
- the description or
- the name or
- Unamed - groupId:artifactId:packaging:
version.
The update catalog mojo uses the description of the project and if
empty uses the name.
the name attribute of the project is given Unamed... when no name is
My project is dependent of some library. I want to always use the latest
bugfix but not any new features. So I added version[1.0,1.1)/version
which allows me to use all bugfixes of the 1.0 release. But when I check the
actually used version, I see that 1.1-SNAPSHOT is getting used! How can I
Ryan de Laplante wrote:
Wayne Fay wrote:
On Fri, Mar 6, 2009 at 11:19 AM, Ryan de Laplante r...@ijws.com wrote:
For anyone following this thread now or in the future, here is the
solution
I used:
Ryan, you're a model citizen... I assume this will go on your blog
too, right? ;-)
2009/3/7 Juven Xu ju...@sonatype.com
this should a properties file, which is available in your test classpath.
your can retrieve it in your testcase, like:
File testFile = new File(target/test-classes/test.properties);
n
access it as a resource from the classpath
Note that all
On Mar 7, 2009, at 3:11 AM, Roman Kournjaev wrote:
I have a maven based application, well now i want to run it in cmd
mode, it
means just executing the compiled class.
I use exec:java for this.
Trevor
-
To unsubscribe,
[1.0,1.1-!)
1.0-SNAPSHOT 1.0 1.1-SNAPSHOT 1.1
But in ASCII ! is A
therefore
1.1-! 1.1-SNAPSHOT 1.1
1.1-! is also 1.1-alpha-1
2009/3/7 Markus KARG markus.k...@gmx.net
My project is dependent of some library. I want to always use the latest
bugfix but not any new features. So I added
On Fri, Mar 6, 2009 at 2:03 PM, Seb Martel smar...@real.com wrote:
YOiioOOoouyh
Sent via BlackBerry by ATT
I think someone has their BlackBerry in the back pocket, and their
butt is emailing us...
Wayne
-
To unsubscribe,
I am facing this problem where maven is not including the sources in
src/main/java.
With jetty:run on the develpoment everthing is fine.
But, when I create the war, the directory is not included.
?xml version=1.0?
project xmlns=http://maven.apache.org/POM/4.0.0;
did you try *mvn clean install jetty:run -e*
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
your projects pom.xml will have a directory specifying the sourcedir
properties
jsp.precompilation.java${pom.basedir}/../src/main/java/jsp.precomilcation.java
..
/properties
then in maven.xml your javac task will use the predefined
jsp.precompilation.java property..
I don't think that the war plugin includes source for your Java classes
in the WAR, at least, not by default. The classes that are generated in
the compile phase would be included, but not the source. Sources in
src/main/webapp would be included, I think. Looking at the
maven-war-plugin
The Maven team is pleased to announce the release of the Maven Doxia,
Doxia Sitetools, version 1.1 and Maven Doxia Tools, version 1.0.
Doxia is a content generation framework which aims to provide its
users with powerful techniques for generating static and dynamic
content: Doxia can be used in
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.3.2
This version supports JBoss5 and filtering of the ear resources
directory, namely.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
17 matches
Mail list logo