I would like to change the fomat of the timestamp set on the files when I do
artifact:deploy-snapshot.
Is this possible? how?
Arne Berner
System Developer
Security Solutions
Nordea Bank Norway ASA
-
To unsubscribe, e-mail:
I think the JUnit Report plug-in should do it. Just run :
maven junit-report
This will only work if your test output files are generated in the standard directory,
if not you'll have to override the maven.test.reportsDirectory property.
James Norman [EMAIL PROTECTED] wrote:
Hey All,
I'm
There will always be some hairy cases where something Maven does isn't
compatible with a given method but the
generatedSourceDirectory/ would
go a long way to making things better. In the cases where things are
hairy, as John said, you can always whip something together in your
maven.xml
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 8:36 AM
To: [EMAIL PROTECTED]
Subject: artifact:deploy-snapshot, howto change the dateformat
I would like to change the fomat of the timestamp set on the
files when I do
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 8:36 AM
To: [EMAIL PROTECTED]
Subject: artifact:deploy-snapshot, howto change the dateformat
I would like to change the fomat of the timestamp set on the
files when I do
You can start with checking the maven cvs. There you will find the
project.xml and maven.xml
Check this files how maven will be built with maven.
Heiko
Freddy wrote:
HI,
Whwre I can find good examples of how to use Maven to build a project?And configure a exinting project to be build by
Sorry, wrong mailing list :p
-Original Message-
From: Stephane Nicoll
Sent: Friday, January 09, 2004 11:00 AM
To: Maven user list (E-mail)
Subject: Jdom 0.7.jar with META-INF/info.xml displays a uncomplete
deployment when put in the deploy directory
Hello list,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 3:12 AM
To: Maven Users List
Subject: Re: Dependency issues for junit tests
Cary Coulter [EMAIL PROTECTED] wrote on 09/01/2004
11:29:38 AM:
Wouldn't it just be better to
One solution (which I adapted from a post on the turbine-maven-user list) is to add
the extra dependencies to the classpath prior to test compilation and remove them
after your tests are done. What we do is let each project optionally define a separate
POM file, 'project-tests.xml', which lists
I always see this happening too, especially as the EAR gets larger, contains
WARs etc.
It starts to fill up your server.log with a bunch of junk. If you use JMX
to deploy your EAR from a directory not under JBoss, the next time you
restart JBoss it isn't deployed anymore!
We tried having our
oops, I meant touch server/conf/log4j.xml
- Original Message -
From: Kevin Hagel [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Friday, January 09, 2004 2:28 AM
Subject: Re: Jdom 0.7.jar with META-INF/info.xml displays a uncomplete
deployment when put in the deploy
Hi All,
I started exploring Maven recently.
We already have a project in place which we were compiling using ant. We
have various scripts from cvs checkout to development set up to production
build all in bits and pieces.
I want to integrate them using maven. Am I using the correct framework?
Hi all
We have a specified lib folder where we have our library files. We want to
use that for compiling the source and not download from the repository.
Please tell me how to do that.
I struggled with setting up various parameters in dependencies but could
not succeed.
If some one can give a
Maven is indeed the right for the job you mention!
Start with a small project and get a feel about it!
Marco
-Original Message-
From: Tapan Nanawati [mailto:[EMAIL PROTECTED]
Sent: vrijdag 9 januari 2004 12:58
To: '[EMAIL PROTECTED]'
Subject: Using Maven for project install /
Tapan,
We use a multiproject maven setup and extend the base project.xml file with
a sub-project specific project.xml.
The snippet below downloads everything from a repository local or remote,
that can be setup by using a build.properties file.
It builds a common-1.0.jar file that is put into a
The best way:
Maven works only with repositories (local and remote), but you can define a
remote repository with the file protocol.
maven.remote.repo = http://www.ibiblio.org/maven,file:///your_directory/
If you use the file protocol, you must respect the repository structure in
your directory.
Is there a directive to point all projects to a single
project.properties ?
Thanks
Pat
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Emmanuel,
Please correct If I did not understood correctly :-
1) I will need to create directory structure like a repository for my
library files something like this :-
lib-|
|
xerces |
|
jars
+xerces-1.0.2.jar
Is my structure
Before doing anything I would suggest you to read some documenation (at
maven web site)
how maven works and what are key concepts.
What you are trying to do is rather off stream and maybe maven is just
not for your team
(specially if your ant based build system works fine).
To use Maven you
I'm totally agree with Michal.
- Original Message -
From: Maczka Michal [EMAIL PROTECTED]
To: 'Maven Users List' [EMAIL PROTECTED]
Sent: Friday, January 09, 2004 1:35 PM
Subject: RE: Classpath issue - Want to use jars from my directory and not
from maven repository
Before doing
What version of the JVM were you using?
I've currently using 1.4.1-1 but I believe I have access to other
versions which I will be trying today and reporting on.
I don't have the option to move to Linux for this process.
Jake Ewerdt wrote:
I had exactly the same problem with Maven (1.0-rc1)
The 1.3.1 version included with Tru64 in the /usr/java1.3 directory.
java version 1.3.1
Java(TM) 2 Runtime Environment, Standard Edition
Fast VM (build 1.3.1-6, native threads, mixed mode, precompiled rt.jar,
07/14/2003-13:20)
On Friday 09 January 2004 09:18 am, Erik Husby wrote:
What version
On Friday 09 January 2004 13:28, Bateman Pat UK MYT wrote:
Is there a directive to point all projects to a single
project.properties ?
Thanks
http://maven.apache.org/reference/user-guide.html#Properties%20Processing
-
To
Why is it a bad idea? How is it any different than having /target/docs a
property that all plugins CAN use? It's not hardcoded and can be changed
by users that want to change the location of the files. I'm not seeing how
this is any different. The target directory is not a free-for-all where
+1 for adding dependencies / to both the build / and unitTest /
directories. The current dependencies element could be inherited into the
build and unitTest dependencies. This would allow for the specification
jar to be used for the build, and the implementation jar used for
packaging by
-Original Message-
From: Sonnek, Ryan [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 4:59 PM
To: 'Maven Users List'
Subject: RE: Mutliple source directories in project.xml
Why is it a bad idea? How is it any different than having
/target/docs a
property that all
On Fri, 2004-01-09 at 03:06, Maczka Michal wrote:
There will always be some hairy cases where something Maven does isn't
compatible with a given method but the
generatedSourceDirectory/ would
go a long way to making things better. In the cases where things are
hairy, as John said, you
On Fri, 2004-01-09 at 05:07, Maczka Michal wrote:
I don't like neither this idea nor what Jason has proposed.
First of all I will explain why dislike the idea of using typetest/type.
I would like to have a match between Project and Dependency tags
(artifactId, groupId, type, version).
First off, I think this has been a great topic of discussion, and a lot of
very good ideas are coming out of it. As somewhat of a test to see what
will pan out as the best solution, how much work would it be to try out this
idea using the dependency properties? This would alleviate the need to
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote:
Because it is not necessary to have this aspect configurable
How do you know this for certain? The answer is you can't without
feedback from users over time.
There is many plugin which are generating reports and which have hardcoded
the
On Fri, 2004-01-09 at 12:21, Sonnek, Ryan wrote:
First off, I think this has been a great topic of discussion, and a lot of
very good ideas are coming out of it. As somewhat of a test to see what
will pan out as the best solution, how much work would it be to try out this
idea using the
I have:
aproject
-- project.xml
-- modules
--subproject
-- project.xml
in which the subprojects project.xml declares
extends${basedir}/../../project.xml/extends
in the aproject project.xml i have a dependency
dependencies
dependency
Would this be more or less work than actually changing
the POM and necessary plugins?
dependency
groupIdfoo/groupId
artifactIdbar/artifactId
typejar/type
version1.2/version
properties
maven.dependency.typeruntime|compile|test/maven.dependency.type
/properties
On Fri, 2004-01-09 at 14:32, Tim Chen wrote:
Ahh.. Here's a case where copy and paste would have caught that ;)
Thanks Jason :)
The appends instead of overrides is perfect as it is exactly what I was
looking for :)
It's generally what people were looking for and was added when the Jelly
tags
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 6:28 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote:
Because it is not necessary to have this
No, I don't think so. The properties were specifically introduced for
the benefit of plugins and while the properties could
certainly be used
the type element was specifically made for the handling of a type of
dependency.
Really? Is that how it is used? I thought it was used to specify
Just to clarify, I never intended that the type element be used for
anything other than the filetype (jar, war, ear, etc). It's a confusing
topic and I intended it to be a completely separate identifier. The term
kind has been thrown around, so just to clarify, here is what I should
have posted
Hi, just getting started with Maven...
I believe this problem comes from not understanding Jelly, but I've searched
around (even in trying to understand the JellyContext that is put together)
and can't find much yet. Source as documentation can be slow going :-)
I have a project.properties that
I already did this, and I believe I submitted an issue and attached a
patch, but apparently there are problems with the artifact plugin, so no
one used the patch. It's working just fine for me using FTP, so you're
welcome to have my changes if you're interested...
-Original Message-
I'm trying to include the maven-jdepend-plugin in my site and I was
wondering if I can generate this report without compiling the source
code from Maven. The java files are previously compiled from an ant
script and I would prefer that they are not compiled through Maven as
well. There are other
Hmm, this is odd.
I got a little deeper into the source and found JellyUtils.runScript() and
the variables that are defined for the context. Of six properties that are
defined in my project.properties, only two of them made it into the Jelly
context.
The project.properties is as follows:
I'm having no luck with this. Running
maven junit-report
fails because it's not a valid goal. If I don't set the
unitTestSourceDirectory then I won't get a Unit test report, even if I
had set the maven.test.reportsDirectory. If I do include the
unitTestSourceDirectory in project.xml then
I do the same thing -- run everything from ant, then use maven to build the
web site. I think you can put:
maven.test.skip = true
in your project.properties to tell maven not to run the tests.
I also override the java:compile goal in my maven.xml:
goal name=java:compile
ant target=compile/
Hi Jason, thanks for the response. That solved the problem. So I have two
Q's, in order of importance:
Q1: Is there some hidden cache of knowledge that I could have learned that
from?
Q2: Is there potentially some exception that should be thrown to indicate one
is about to enter an alternate
I use the jar override feature for libraries that aren't on ibiblio.org.
I check these jars into our SCM system so that the other developers
can easily get them.
This works great when building individual projects, but when attempting
to run multiproject:site the jars aren't found due to a
The best way:
Maven works only with repositories (local and remote), but
you can define a remote repository with the file protocol.
maven.remote.repo =
http://www.ibiblio.org/maven,file:/// your_directory/
If
you use the file protocol, you must
respect the repository structure in
On Fri, 2004-01-09 at 18:55, Brian Topping wrote:
Hi Jason, thanks for the response. That solved the problem. So I have two
Q's, in order of importance:
Q1: Is there some hidden cache of knowledge that I could have learned that
from?
Possibly the mailing list archives. But in Jelly
On Fri, 2004-01-09 at 20:18, Incze Lajos wrote:
In the long run and in the new Maven code I won't be promoting Jelly for
plugins at all, but will be promoting the use of beanshell. I'm sure XML
programming will remain wildly popular and if that is the case I will be
reimplementing Jelly
48 matches
Mail list logo
