-Original Message-
From: Rademacher Tobias [mailto:[EMAIL PROTECTED]
Sent: 14 January 2004 07:36
To: 'Maven Users List'
Subject: RE: aspectj plugin
Dear Vincent,
thank you for your informations. I'll definitivly give it a try.
The only bear in mind I have is unit testing.
Dear Vincent,
thx for your quick reply.
You're right. This is a current limitation of the iajc task
(it can only
weave jars).
Okay. Then I'll go with the old version (1.1) as Unit Testing is essential
for me.
I hope this is okay for you ;-).
It seems this is something that the aspectj
-Original Message-
From: Rademacher Tobias [mailto:[EMAIL PROTECTED]
Sent: 14 January 2004 08:26
To: 'Maven Users List'
Subject: RE: aspectj plugin
Dear Vincent,
thx for your quick reply.
You're right. This is a current limitation of the iajc task
(it can only
weave
whenever I run the maven javadoc plugin, it does not generate any package information
(package-list is blank and package-summary is missing). Any ideas what I am missing?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
What is the explicit purpose of the maven.username property?
Initially I had setup such that maven.username was a generic user for our development
team on the machine serving as our internal remote repository and project web server.
So that worked fine for all the deploy goals pushing out to
I think you can define in a preGoal of site:deploy the maven.username redefinition.
And in a postGoal redefine the properties to the old one.
This could be a way to change this property only for one goal.
Nicolas
Ebersole, Steven [EMAIL PROTECTED]
14/01/2004 13:53
Veuillez répondre à Maven
I have a question about the mantra that a single project should produce a single
artifact. I can buy into that in every case I have run across or have thought about,
except for projects involving ejb creation. Typically an ejb project will produce
both an ejb-jar file as well as a client-jar
-Original Message-
From: Eric Giguere [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 13, 2004 9:34 PM
To: Maven User List
Subject: Multiple remote repository + proxy settings
Hi all
A quick one. We're behind a firewall and use a proxy server
to go on the Net.
And we have
Hi Vincent,
I cannot imagine that this is so hard to solve as a jar is nothing
different
(only that is zipped and containg some meta-inforamation). Should I
ask
them
or could you do?
I'll let you do it... ;-)
*lol* Okay. I'll try to contact the aspectj team and inform you about it.
Jörg Schaible wrote:
with the current version of 1.0-rc2 (from CVS) and all plugins built
fom CVS, I had to notice that the style of new generated sites differ
a lot. I had previsouly used properties mensioned in the
xdoc-plugin-docs to adjust colors to our companies' CI, but they are
not
Yeah, same thing happened to me. I modified the javadoc's plugin.jelly to get it
working. Here's the diff:
93,94c93
packagenames=${pom.package}
sourcepath=${pom.build.sourceDirectory}
---
packagenames=${pom.package}.*
109a108,124
ant:fileset
Hello,
I've notice that sometimes, the HTML produced by maven site:generate cut
words in 2 parts. For example, I wrote in the xdocs dir :
section nameOverview
p
The objectives of this project is to automatised the documentation of a
projet.
/p
/section
and I see in the HTML page :
p
my junit tests always fail with the following exception. In searching, I
have found several proect pages on the net with the same error error
formatting: 'NaN' with '0.00%' in the Success Rate column at teh top of
the junit-report.html page
There is a test to be run.
Thanks in advance,
Cary
Vincent Massol wrote:
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rob Moore
Sent: 13 January 2004 08:19
To: [EMAIL PROTECTED]
Subject: Re: Maven and EJB Testing
I noticed you made a lot of changes in December to assist with testing
EJBs. Any chance you might
Rafal Krzewski wrote on Wednesday, January 14, 2004 3:04 PM:
Jörg Schaible wrote:
with the current version of 1.0-rc2 (from CVS) and all plugins built
fom CVS, I had to notice that the style of new generated sites differ
a lot. I had previsouly used properties mensioned in the
How is it possible to reference a property defined in one of the maven properties
files (specifically the ~/build.properties) in one of the maven jelly tags? The tag I
am trying to use is maven:makeRelativePath/. What I have tried so far is:
1) maven:makeRelativePath var=testDest
Jörg Schaible wrote:
Yeah, but wait ... how does xdoc know anything about a css file in a xdoc/style directory (still searching for some docs ...)? Looking into my project, xdoc generates three css files out of nowhere (maven-base, maven-theme, print ... OK, I know they're coming from the
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rob Moore
Sent: 14 January 2004 16:53
To: [EMAIL PROTECTED]
Subject: Re: Maven and EJB Testing
Vincent Massol wrote:
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rob Moore
Ebersole, Steven wrote:
How is it possible to reference a property defined in one of the maven properties files (specifically the ~/build.properties) in one of the maven jelly tags? The tag I am trying to use is maven:makeRelativePath/. What I have tried so far is:
1) maven:makeRelativePath
Same error message. Tried using a bunch of different plugin contexts (test, java,
idea)...
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 1:43 PM
To: Maven Users List
Subject: Re: maven jelly tag and build.properties properties
I've had various problems when the variable has a . or - in it. I use a
workaround like this:
property name=buildnumber value=${build.number} /
j:if test=${empty(buildnumber)}
failUsage: maven -Dbuild.number=x releaseNotes/fail
/j:if
If I put j:if
I would be very interested to hear other peoples opinion on this as well.
I'm currently working on 4 separate EJB projects and have gone through this
same situation. I have heard talk on the mailing list about adding support
for an artifact type ejb-client.jar, but I don't remember who was
Ebersole, Steven wrote:
Same error message. Tried using a bunch of different plugin contexts (test, java, idea)...
do you import the test context by declaring the 'test' namespace ?
this works for me :
ant:echo xmlns:mytest=testm.t.d =
Hi all
Is there a property somewhere in the projet that can be set to tell a
sub project to use the parents directories? I'm trying to build multiple
jars using multiple maven projects but each uses its own sources and
targets. The class files are in the parent's target.
thx for any advice
Couldn't you just change the child's sourceDirectory to point to the
parent?
sourceDirectory${basedir}/../src/java/sourceDirectory
-Original Message-
From: Eric Giguere [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 2:58 PM
To: Maven Users List
Subject: Child project
Well, it is obviously a bug in the Alpha JVM. The default JVM is the
fast one which is known to have some problems with native code (ie.
the code that access the file system to find jars and other useful
things). So by setting MAVEN_OPTS to -Xmx256mb -classic, I can force
the JVM into classic
but this works for me even without the namespacing:
ant:echm.t.d = ${maven.test.dest}/ant:echo
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 2:51 PM
To: Maven Users List
Subject: Re: maven jelly tag and build.properties properties
Sure can, thx for that one :)
But since maven builds most of its properties on {basedir}, i guess then
that the clean way to change maven.build.dir would be to override in the
same manner this property in the build.properties of that sub-project?
Eric.
Sonnek, Ryan wrote:
Couldn't you just
Ebersole, Steven wrote:
but this works for me even without the namespacing:
ant:echm.t.d = ${maven.test.dest}/ant:echo
uh ! right.. it works when it is defined in the properties file.. i
forgot your original question.. my bad
-- gd
I'm stupid. I set maven.test.skip=true
junitreport blew up because there were no test report files
- Original Message -
From: Cary Coulter [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 9:47 AM
Subject: Junit report failure
my junit tests
actually, my bad. it does not work. it is maven.build.dest that works, not
maven.test.dest
so what I have:
j:set var=outputMode value=${maven.idea.output.mode} /
j:set var=srcDestProp value=${maven.build.dest}/
j:set var=testDestProp value=${maven.test.dest}/
I was premature in my report. Maven still doesn't run on Alpha. I've
tracked the problem down to the maven-xdoc-plugin-1.4/plugin.jelly when
it tries to register a report using the attainGoal
name=${report}:register
I suspect the problem is something similar to junit class loading issue
Silly me, I had the solution just in front of my eyes on a webpage I've
googled an hour ago. I haven't seen it anywhere in the plugins, so here
it goes:
dirset dir=${basedir}/../networks/ id=network.dirs/
pathconvert pathsep=, property=networkDirs
refid=network.dirs/
u:tokenize
I just finished added an entry to the wiki about how I have structured my
EJB project. I would be very interested in hearing some feedback if it is
on target with what other developers are doing.
http://wiki.codehaus.org/maven/CreatingEjbApplications
Ryan
-Original Message-
From:
Ebersole, Steven wrote:
actually, my bad. it does not work. it is maven.build.dest that works, not maven.test.dest
heres my understanding of it, i may be wrong - correct me if am :
maven.build.dest should always be available (core behavorial property),
maven.test.dest is being made
Thanks for the help. What I did was to simply (re?)define it in the specific
plugin.properties file to be its defined default using
maven.test.dest=${maven.build.dir}/test-classes, and everything started working.
Woohoo...
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL
Not sure if any of the developers of the idea plugin are around here, but I basically
modified my plugin locally because it was not fully defining the intellij project
files for me correctly. This change was specifically to the v3 resources.
Specifically, it was not:
1) setting up any compiler
Hi, Ryan,
I just reviewed your wiki posting pretty extensively and found it to be
a great help. However, I've had a problem with the part about running
'maven multiproject:install' in the root project. I get this error:
Starting the reactor...
BUILD FAILED
File.. file:/C:/Documents and
On Wed, 2004-01-14 at 17:55, Gilles Dodinet wrote:
Ebersole, Steven wrote:
actually, my bad. it does not work. it is maven.build.dest that works, not
maven.test.dest
heres my understanding of it, i may be wrong - correct me if am :
maven.build.dest should always be available
39 matches
Mail list logo
