RE: running project

[dion]

Do you have a project.xml in that directory?
--
dIon Gillard, Multitask Consulting
Blog:  http://blogs.codehaus.org/people/dion/
Work:  http://www.multitask.com.au


"David Liles" <[EMAIL PROTECTED]> wrote on 18/06/2003 02:37:13 PM:

> Thanks for the info however, when I entered the below line I got the
> following error.
> 
> I'm not sure what I need to do at this point
> 
> Thanks
> 
> 
> C:\projects>maven -Dpackage=com.example.test testapp
>  __  __
> |  \/  |__ Jakarta _ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT
> 
> java.lang.NullPointerException
> at org.apache.maven.plugin.PluginManager.
> attainGoals(PluginManager.java:
> 376)
> at 
org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
> at org.apache.maven.cli.App.doMain(App.java:524)
> at org.apache.maven.cli.App.main(App.java:1080)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.
> invoke(NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.
> invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:543)
> at com.werken.forehead.Forehead.main(Forehead.java:573)
> Total time:  7 seconds
> 
> 
>-Original Message- 
>From: Brian Ewins [mailto:[EMAIL PROTECTED] 
>Sent: Mon 6/16/2003 9:19 AM 
>To: Maven Users List 
>Cc: 
>Subject: Re: running project
> 
> 
> 
>Maven (like ant and make) depends on a build descriptor - project.xml 
-
>that it expects to find in the base directory of your project. e.g. 
if
>you have a file named:
>~/myproject/src/com/foo/Example.java
>... then its very likely the directory '~/myproject/' is where you 
want
>to place your project.xml. If you want to compile the current project
>from anywhere at or below this directory, you can just do:
>maven -f project.xml java:compile
> 
>the '-f' tells maven to look for the first available 'project.xml' in
>this dir or any of its parents, and use that as the project.xml for 
the
>build.
> 
>The best way to see how this works isn't to start with an existing
>project, but to get maven to generate a project for you. In an empty
>directory, type:
>maven -Dpackage=com.example.foo genapp
>maven will generate a project.xml for you, and an example directory
>structure, including examples of how to use unit tests with 
> maven. Now type:
>maven test:test
>This will compile the sample code and its tests, and run the tests.
> 
>As for the site:deploy problem: by default maven will try to 'deploy' 
to
>a secure server using scp, which requires a username and password. 
This
>is used for deploying to remote live sites. Look at
>
>especially at the "maven.site.deploy.method" property which should 
help
>you do what you're after. You set this in a properties file called
>project.properties - again in the project root.
> 
>You don't need to use the maven folder structure, but it helps. You 
can
>configure maven to look elsewhere (in a *single* source folder, 
though),
>see the manual:
>
>(sourceDirectory is the thing you're looking for - its in your
>project.xml). You can set up multiple source dirs for code generation
>and the like, but you'd be better coming back and asking about that 
once
>you have simple projects working.
> 
>Hope this helps
>Baz
> 
>David Liles wrote:
> 
>> I just configured Maven and am having trouble understanding the
> structure and getting my project to run.
>> 
>> The documentation states that all projects must have a project.
> xml file. I've modified an example file but now how do I execute it,
> what is the call statement I should use?
>>
>> How do I get Maven to compile my source code? I have tried 
> using the physical path, relative path, everything so far I've 
> had no luck. I get a message that states there was no source code found.
>> 
>> Also, when I call maven site:deploy I get and error stating 
> that I need to provide a username in order to deploy the project. 
> The username can be placed in the build.property file but where 
> does the build.property file need to be located?
>> 
>> Finally, do I need to place all of my project source code in 
> the maven folder structure now?
>> 
>> Thanks.
>> 
>> Dave
>>
>> 
-
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
>-

RE: running project

[David Liles]

Thanks for the info however, when I entered the below line I got the following error.
 
I'm not sure what I need to do at this point
 
Thanks
 
 
C:\projects>maven -Dpackage=com.example.test testapp
 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT

java.lang.NullPointerException
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:
376)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time:  7 seconds
 

-Original Message- 
From: Brian Ewins [mailto:[EMAIL PROTECTED] 
Sent: Mon 6/16/2003 9:19 AM 
To: Maven Users List 
Cc: 
Subject: Re: running project



Maven (like ant and make) depends on a build descriptor - project.xml -
that it expects to find in the base directory of your project. e.g. if
you have a file named:
~/myproject/src/com/foo/Example.java
... then its very likely the directory '~/myproject/' is where you want
to place your project.xml. If you want to compile the current project
from anywhere at or below this directory, you can just do:
maven -f project.xml java:compile

the '-f' tells maven to look for the first available 'project.xml' in
this dir or any of its parents, and use that as the project.xml for the
build.

The best way to see how this works isn't to start with an existing
project, but to get maven to generate a project for you. In an empty
directory, type:
maven -Dpackage=com.example.foo genapp
maven will generate a project.xml for you, and an example directory
structure, including examples of how to use unit tests with maven. Now type:
maven test:test
This will compile the sample code and its tests, and run the tests.

As for the site:deploy problem: by default maven will try to 'deploy' to
a secure server using scp, which requires a username and password. This
is used for deploying to remote live sites. Look at

especially at the "maven.site.deploy.method" property which should help
you do what you're after. You set this in a properties file called
project.properties - again in the project root.

You don't need to use the maven folder structure, but it helps. You can
configure maven to look elsewhere (in a *single* source folder, though),
see the manual:

(sourceDirectory is the thing you're looking for - its in your
project.xml). You can set up multiple source dirs for code generation
and the like, but you'd be better coming back and asking about that once
you have simple projects working.

Hope this helps
Baz

David Liles wrote:

> I just configured Maven and am having trouble understanding the structure 
and getting my project to run.
> 
> The documentation states that all projects must have a project.xml file. 
I've modified an example file but now how do I execute it, what is the call statement 
I should use?
>
> How do I get Maven to compile my source code? I have tried using the 
physical path, relative path, everything so far I've had no luck. I get a message 
that states there was no source code found.
> 
> Also, when I call maven site:deploy I get and error stating that I need to 
provide a username in order to deploy the project. The username can be placed in the 
build.property file but where does the build.property file need to be located?
> 
> Finally, do I need to place all of my project source code in the maven 
folder structure now?
> 
> Thanks.
> 
> Dave
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-
To unsubscribe, e-mail: [EMAIL

RE: Removing ${pom.X} usage in properties files.

[Jason van Zyl]

On Tue, 2003-06-17 at 12:59, Vincent Massol wrote:
> We're using it in a few places on the project I'm working on. We have
> the following for example, in our project.properties:
> 
> "
> maven.xdoc.version = ${pom.name}-${pom.currentVersion}

Yah, this is a standard one.

> # Override default installation directory for ejb jars in order to put
> the 
> # ejbs in the jar artfiact repository directory.
> maven.ejb.install.dir=${maven.repo.local}/${pom.artifactDirectory}/jars
> "
> 
> The second is obviously due to a problem in a plugin. But that should be
> a typical use cases. There are lots of small problems in the existing
> plugins where this makes sense.

Is there anyway around this? How about a property defined in the POM?
I'm just trying to narrow the interpolation behavior a little to make
things simpler (and easier internally).


> -Vincent
> 
> 
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 17 June 2003 17:37
> > To: Maven Users List
> > Subject: Removing ${pom.X} usage in properties files.
> > 
> > Hi,
> > 
> > I wanted to check with users about the frequency of using ${pom.X}
> > notation in properties files. I would like to remove this feature as
> it
> > is causing some grief internally and the only place I see it being
> used
> > internally is driver.properties which isn't visible to most users.
> > 
> > I don't believe this 'feature' is being used but I wanted to check
> > because I believe I made an error in judgement letting this usage into
> > existence.
> > 
> > So for example in driver.properties we have:
> > 
> > maven.final.name = ${pom.artifactId}-${pom.currentVersion}
> > 
> > This is the type of usage I want to remove.
> > 
> > --
> > jvz.
> > 
> > Jason van Zyl
> > [EMAIL PROTECTED]
> > http://tambora.zenplex.org
> > 
> > In short, man creates for himself a new religion of a rational
> > and technical order to justify his work and to be justified in it.
> > 
> >   -- Jacques Ellul, The Technological Society
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clover generates 0% code coverage reports

[Jon Strayer]

** Reply to message from "S. Radhakrishnan"
<[EMAIL PROTECTED]> on Tue, 17 Jun 2003 11:08:41 +0530

> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
> doing the clover test and clover report in two seperate commands
> >maven clover test
> >maven clover
> but still the report gives 0% code coverage. Is there any wrong in the
> clover plugin ?.. please can anybody help me out.

My current workaround is to just run maven clover again. 
Usually that works.  And occasional maven clean seems to
help too.

-- 



And your crybaby whiny-assed opinion would be. . . ?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clover generates 0% code coverage reports

[Ben Walding]

It was just that as I was writing Maven's Clover 1.2 plugin I couldn't 
find any documentation on the property configuration for 1.2.  If the 
1.0 property config method still works and is supported for 1.2 then I 
can probably use that.

I was getting all kinds of weirdness with the clover dbs getting 
corrupted and having to clean them out.  And the reason I didn't like 
the ant tasks is that it clouded the issue of jvm shutdown which was 
required to flush the data to the db.

(Btw.  I think clover is great, it's just that I couldn't get the maven 
plugin reliably working on my first pass that frustrated me - and if I 
can't get it to work, then I pity the poor end-user who will be saddled 
with it!   - I want the plugin to be fire and forget - 
clover:html-report is all they should need to know.)

I'll have another crack at reading the doco for 1.0.

Conor MacNeill wrote:

On Tue, 17 Jun 2003 03:56 pm, Ben Walding wrote:
 

I blame Clover's absurd insistence on migrating everything to Ant
tasks.  But I'm just a grumpy mongrel.
   

Clover's Ant tasks are provided as a convenience. The alternate property-based 
operation from Clover 1.0 is still supported and even the new filesets are 
made available through Ant references. So really, nothing has been migrated, 
as such.

Actually, we thought having Ant tasks would make the Clover plugin for Maven 
easier to develop and maintain, although I'll admit I don't know much about 
Maven plugins.

Anyway, what would you prefer? What could Clover provide to make the Maven 
Clover plugin development easier? 

Conor

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clover generates 0% code coverage reports

[Jason van Zyl]

On Tue, 2003-06-17 at 20:56, Conor MacNeill wrote:
> On Tue, 17 Jun 2003 03:56 pm, Ben Walding wrote:
> >
> > I blame Clover's absurd insistence on migrating everything to Ant
> > tasks.  But I'm just a grumpy mongrel.
> >
> 
> Clover's Ant tasks are provided as a convenience. The alternate property-based 
> operation from Clover 1.0 is still supported and even the new filesets are 
> made available through Ant references. So really, nothing has been migrated, 
> as such.
> 
> Actually, we thought having Ant tasks would make the Clover plugin for Maven 
> easier to develop and maintain, although I'll admit I don't know much about 
> Maven plugins.
> 
> Anyway, what would you prefer? What could Clover provide to make the Maven 
> Clover plugin development easier? 

Something like the AspectJ compiler API would be nice. It's just a
simple Java class that allows you to set the sourceroots as a standard
classpath looking string (/home/jason/source;/home/bob/source or
/home/jason/source:/home/bob/source) or the individual files. It
basically leaves it up to you how you get those files. As a result it
took me only a few minutes to make an AspectJ compiler plugin component
(for maven-new).

> Conor
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Clover generates 0% code coverage reports

[Conor MacNeill]

On Tue, 17 Jun 2003 03:56 pm, Ben Walding wrote:
>
> I blame Clover's absurd insistence on migrating everything to Ant
> tasks.  But I'm just a grumpy mongrel.
>

Clover's Ant tasks are provided as a convenience. The alternate property-based 
operation from Clover 1.0 is still supported and even the new filesets are 
made available through Ant references. So really, nothing has been migrated, 
as such.

Actually, we thought having Ant tasks would make the Clover plugin for Maven 
easier to develop and maintain, although I'll admit I don't know much about 
Maven plugins.

Anyway, what would you prefer? What could Clover provide to make the Maven 
Clover plugin development easier? 

Conor


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Developer Activity

[FrancisJones, Richard]

Hi all,

Is it possible to get maven to produce the developer activity and file
activity reports just for a particular cvs branch? My reports are currently
empty so I am guessing that maven is perhaps looking at the wrong branch???

Thanks,

Richard.

This communication is confidential and may contain privileged material.
If you are not the intended recipient you must not use, disclose, copy or retain it.
If you have received it in error please immediately notify me by return email
and delete the emails.
Thank you.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Using a remote repo instead of ibiblio- error Messages

[Moretti, Luciano (MED)]

Hi-

I'm trying to establish my own Repo server so that I can access
resources that I don't want to publish to the net.

I've added the following line to my build.properties file in my home
dir-

maven.repo.remote =
http://lin4.moneng.mei.com/maven/,http://www.ibiblio.org/maven

The error message I get are the following-

Error retrieving artifact from
[http://www.ibiblio.org/maven/JXTA/jars/jarname.jar]:
java.lang.Exception: Can't get jarname.jar.incomplete to
/home/morettil/3P/maven/jarname/jars/jarname.jar.incomplete

The thing is that the get from the local repo is successfully completed
before it tries to get it from ibiblio.org.  Is there a way to say that
if you get it from one, you don't have to get it from the other?

Luciano Moretti

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: eclipse:external-tools goal in Maven's eclipse plugin

[Michal Maczka]

I think that it was quite useless...so nobody wants to fix it :)

mm

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 9:22 PM
> To: [EMAIL PROTECTED]
> Subject: RE: eclipse:external-tools goal in Maven's eclipse plugin
>
>
> I have noticed as well that it hasn't worked in a while, just haven't dug
> into it yet..
>
> Eric
>
> -Original Message-
> From: Thomas Burns [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 12:20 PM
> To: [EMAIL PROTECTED]
> Subject: eclipse:external-tools goal in Maven's eclipse plugin
>
>
> I'm running Maven with Eclipse and found the
> eclipse:external-tools goal in
> maven's eclipse plugin that is supposed to automatically create external
> tool entries in eclipse for maven.  When properly set up and executed, an
> externaltools.xml is placed in eclipse's
> workspace\.metadata\.plugins\org.eclipse.ui.externaltools
> directory but this
> doesn't seem to be enough for eclipse.  I suspect that this used
> to work in
> an earlier version of eclipse, but that the interface has since
> changed and
> this particular goal hasn't been updated to reflect the changes made in
> eclipse.
>
> I've browsed the mailing list archive to no avail trying to
> figure this out.
> Any suggestions?  Is this supposed to work in the current eclipse release?
> (I'm running Eclipse 2.1.0).
>
> Thanks!
>
> t
> --
> Thomas Burns
> [EMAIL PROTECTED]
>
>
> --
> Newsowy portal INTERIA.PL >>> http://link.interia.pl/f1735
>



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: eclipse:external-tools goal in Maven's eclipse plugin

[EPugh]

I have noticed as well that it hasn't worked in a while, just haven't dug
into it yet..

Eric

-Original Message-
From: Thomas Burns [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 12:20 PM
To: [EMAIL PROTECTED]
Subject: eclipse:external-tools goal in Maven's eclipse plugin


I'm running Maven with Eclipse and found the eclipse:external-tools goal in
maven's eclipse plugin that is supposed to automatically create external
tool entries in eclipse for maven.  When properly set up and executed, an
externaltools.xml is placed in eclipse's
workspace\.metadata\.plugins\org.eclipse.ui.externaltools directory but this
doesn't seem to be enough for eclipse.  I suspect that this used to work in
an earlier version of eclipse, but that the interface has since changed and
this particular goal hasn't been updated to reflect the changes made in
eclipse.

I've browsed the mailing list archive to no avail trying to figure this out.
Any suggestions?  Is this supposed to work in the current eclipse release?
(I'm running Eclipse 2.1.0).

Thanks!

t
--
Thomas Burns
[EMAIL PROTECTED]

RE: Removing ${pom.X} usage in properties files.

[Vincent Massol]

We're using it in a few places on the project I'm working on. We have
the following for example, in our project.properties:

"
maven.xdoc.version = ${pom.name}-${pom.currentVersion}

# Override default installation directory for ejb jars in order to put
the 
# ejbs in the jar artfiact repository directory.
maven.ejb.install.dir=${maven.repo.local}/${pom.artifactDirectory}/jars
"

The second is obviously due to a problem in a plugin. But that should be
a typical use cases. There are lots of small problems in the existing
plugins where this makes sense.

-Vincent


> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 17 June 2003 17:37
> To: Maven Users List
> Subject: Removing ${pom.X} usage in properties files.
> 
> Hi,
> 
> I wanted to check with users about the frequency of using ${pom.X}
> notation in properties files. I would like to remove this feature as
it
> is causing some grief internally and the only place I see it being
used
> internally is driver.properties which isn't visible to most users.
> 
> I don't believe this 'feature' is being used but I wanted to check
> because I believe I made an error in judgement letting this usage into
> existence.
> 
> So for example in driver.properties we have:
> 
> maven.final.name = ${pom.artifactId}-${pom.currentVersion}
> 
> This is the type of usage I want to remove.
> 
> --
> jvz.
> 
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
> 
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
> 
>   -- Jacques Ellul, The Technological Society
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

eclipse:external-tools goal in Maven's eclipse plugin

[Thomas Burns]

I'm running Maven with Eclipse and found the eclipse:external-tools goal in maven's 
eclipse plugin that is supposed to automatically create external tool entries in 
eclipse for maven.  When properly set up and executed, an externaltools.xml is placed 
in eclipse's workspace\.metadata\.plugins\org.eclipse.ui.externaltools directory but 
this doesn't seem to be enough for eclipse.  I suspect that this used to work in an 
earlier version of eclipse, but that the interface has since changed and this 
particular goal hasn't been updated to reflect the changes made in eclipse.

I've browsed the mailing list archive to no avail trying to figure this out.  Any 
suggestions?  Is this supposed to work in the current eclipse release? (I'm running 
Eclipse 2.1.0).

Thanks!

t
--
Thomas Burns
[EMAIL PROTECTED]

Re: How to specify encoding for generated xdoc files?

[Arthur Suilin]

"Martin Skopp" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On Tue, 2003-06-17 at 15:33, Arthur Suilin wrote:
> > Problem is: all files in generated-xdocs directory have "ISO-8859-1" or
just
> > no encoding specified. How can I set default encoding for all generated
xdoc
> > files?
>
> See http://maven.apache.org/reference/plugins/xdoc/properties.html
>
> maven.docs.outputencoding

Yes, I've set this parameter. But this is works only for HTML generation at
final stage (if all input xdoc files are in VALID windows-1251 encoding).
Some maven plugins still generate intermediate xdoc files in ISO-8859-1
encoding, or without specified encoding at all. These files just don't
contain Russian letters.


--
Arthur




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Removing ${pom.X} usage in properties files.

[Jason van Zyl]

On Tue, 2003-06-17 at 11:53, Colin Sampaleanu wrote:
> Jason van Zyl wrote:
> 
> >On Tue, 2003-06-17 at 11:37, Jason van Zyl wrote:
> >  
> >
> >>Hi,
> >>
> >>I wanted to check with users about the frequency of using ${pom.X}
> >>notation in properties files. I would like to remove this feature as it
> >>is causing some grief internally and the only place I see it being used
> >>internally is driver.properties which isn't visible to most users.
> >>
> >>I don't believe this 'feature' is being used but I wanted to check
> >>because I believe I made an error in judgement letting this usage into
> >>existence.
> >>
> >>So for example in driver.properties we have:
> >>
> >>maven.final.name = ${pom.artifactId}-${pom.currentVersion}
> >>
> >>This is the type of usage I want to remove.
> >>
> >>
> >Just a clarification: there seem to be a few places in plugins where the
> >${pom.X) interpolation is used and I can catch those to make sure things
> >work. I really just wanted to know if this feature is in widespread use.
> >
> >I would really like to move to properties files that strictly contain
> >user defined values and not pom defined values.
> >
> I've used it once in a while, to do stuff like
> maven.ejb.final.name=${pom.artifactId}-beans-${pom.currentVersion}
> 
> Now this was to get around a limitation of the ejb plugin, which can't 
> (or couldn't) let you override the final name. It would not necessarilly 
> be that big a deal if this went away, I suppose, as long as I could 
> still acess the value in maven.xml///

Thanks, this one I can work around as well because the driver.properties
uses ${pom.artifactId} and ${pom.currentVersion}.

> >
> >
> >  
> >
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Removing ${pom.X} usage in properties files.

[Jason van Zyl]

On Tue, 2003-06-17 at 11:50, Martin Skopp wrote:
> On Tue, 2003-06-17 at 17:37, Jason van Zyl wrote:
> > I wanted to check with users about the frequency of using ${pom.X}
> > notation in properties files. I would like to remove this feature as it
> > is causing some grief internally and the only place I see it being used
> > internally is driver.properties which isn't visible to most users.
> 
> 
> find . -name project.properties | xargs grep pom
> 
> 
> gives me frequent use of
> 
> maven.xdoc.version=${pom.currentVersion}
> 
> but can't remember why - must have copied it from somewhere in my early
> maven startup times...

Anywhere I have let these slip in I can catch. If it is only these one
that are in use then I can stop interpolating POM values into properties
file. If it's in widespread use then I will not remove it for the 1.0
release. This is what I'm trying to determine.


-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Removing ${pom.X} usage in properties files.

[Colin Sampaleanu]

Jason van Zyl wrote:

On Tue, 2003-06-17 at 11:37, Jason van Zyl wrote:
 

Hi,

I wanted to check with users about the frequency of using ${pom.X}
notation in properties files. I would like to remove this feature as it
is causing some grief internally and the only place I see it being used
internally is driver.properties which isn't visible to most users.
I don't believe this 'feature' is being used but I wanted to check
because I believe I made an error in judgement letting this usage into
existence.
So for example in driver.properties we have:

maven.final.name = ${pom.artifactId}-${pom.currentVersion}

This is the type of usage I want to remove.
   

Just a clarification: there seem to be a few places in plugins where the
${pom.X) interpolation is used and I can catch those to make sure things
work. I really just wanted to know if this feature is in widespread use.
I would really like to move to properties files that strictly contain
user defined values and not pom defined values.
I've used it once in a while, to do stuff like
maven.ejb.final.name=${pom.artifactId}-beans-${pom.currentVersion}
Now this was to get around a limitation of the ejb plugin, which can't 
(or couldn't) let you override the final name. It would not necessarilly 
be that big a deal if this went away, I suppose, as long as I could 
still acess the value in maven.xml///



 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Removing ${pom.X} usage in properties files.

[Martin Skopp]

On Tue, 2003-06-17 at 17:37, Jason van Zyl wrote:
> I wanted to check with users about the frequency of using ${pom.X}
> notation in properties files. I would like to remove this feature as it
> is causing some grief internally and the only place I see it being used
> internally is driver.properties which isn't visible to most users.


find . -name project.properties | xargs grep pom


gives me frequent use of

maven.xdoc.version=${pom.currentVersion}

but can't remember why - must have copied it from somewhere in my early
maven startup times...
-- 
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com

This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4  5C0D 29E6 6A95 3D40 27B5


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Removing ${pom.X} usage in properties files.

[Jason van Zyl]

On Tue, 2003-06-17 at 11:37, Jason van Zyl wrote:
> Hi,
> 
> I wanted to check with users about the frequency of using ${pom.X}
> notation in properties files. I would like to remove this feature as it
> is causing some grief internally and the only place I see it being used
> internally is driver.properties which isn't visible to most users.
> 
> I don't believe this 'feature' is being used but I wanted to check
> because I believe I made an error in judgement letting this usage into
> existence.
> 
> So for example in driver.properties we have:
> 
> maven.final.name = ${pom.artifactId}-${pom.currentVersion}
> 
> This is the type of usage I want to remove.

Just a clarification: there seem to be a few places in plugins where the
${pom.X) interpolation is used and I can catch those to make sure things
work. I really just wanted to know if this feature is in widespread use.

I would really like to move to properties files that strictly contain
user defined values and not pom defined values.


-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Removing ${pom.X} usage in properties files.

[Jason van Zyl]

Hi,

I wanted to check with users about the frequency of using ${pom.X}
notation in properties files. I would like to remove this feature as it
is causing some grief internally and the only place I see it being used
internally is driver.properties which isn't visible to most users.

I don't believe this 'feature' is being used but I wanted to check
because I believe I made an error in judgement letting this usage into
existence.

So for example in driver.properties we have:

maven.final.name = ${pom.artifactId}-${pom.currentVersion}

This is the type of usage I want to remove.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to specify encoding for generated xdoc files?

[Martin Skopp]

On Tue, 2003-06-17 at 15:33, Arthur Suilin wrote:
> Problem is: all files in generated-xdocs directory have "ISO-8859-1" or just
> no encoding specified. How can I set default encoding for all generated xdoc
> files?

See http://maven.apache.org/reference/plugins/xdoc/properties.html

maven.docs.outputencoding 

Specifies the output encoding of the DVSL generated docs. The default
value is ISO-8859-1 , an encoding supporting english characters as well
as most european languages. 
-- 
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com

This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4  5C0D 29E6 6A95 3D40 27B5


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to specify encoding for generated xdoc files?

[Arthur Suilin]

Hi!

I have a problem when generating site from mavenized project (via
site:generate).
Project description file and some sources had some Russian characters
(windows-1251 encoding). Generated site had question marks in place of all
Russian letters. When I set "maven.docs.outputencoding" property to
"windows-1251", some Russian letters appeared, but most of them are still
"???"

Problem is: all files in generated-xdocs directory have "ISO-8859-1" or just
no encoding specified. How can I set default encoding for all generated xdoc
files?

--
Arthur








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Generating Multiple JARs

[Chris . Rauschuber]

Hello,

I've currently got maven building two projects, A and B, where B has a
dependency on A.  The compile goal works fine, but test does not build
because B's tests reference A's Mock objects.
Is there a way to generate two jars in A: one from source and one from
test?

Thanks,
Chris


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: INTERNAL ERROR question

[Kristine Weissbarth]

Thanks, but If I'm now starting maven via 'maven site' the following
output appears:

 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT


BUILD FAILED
Goal "site" does not exist in this project.
Total time:  8 seconds


and if I'm trying 'maven site:generate' I get the same like the last
time:

 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT


Starting the reactor...
Our processing order:
Utilities
+
| Building site Utilities
| Memory: 1M/2M
+
site:generate:
all-build:
[echo] Processing whoweare.xml template ...
[echo] Processing source-repos.xml template ...
[echo] Processing mail.xml template ...
[echo] Processing navigation.xml template ...
INTERNAL ERROR
Reference made to goal 'site:generate' which has no definition.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: INTERNAL ERROR question

[S. Radhakrishnan]

Hi,

I think, it will work if you change your maven.xml a bit.,

  

  

try this,

RK

-Original Message-
From: Kristine Weissbarth [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 4:09 PM
To: [EMAIL PROTECTED]
Subject: INTERNAL ERROR question


Hi,

I'm using the reactor to set up maven for my project which has several
subproject (e.g. subproject utilities). It already worked some time ago
but now I'm always getting the following output and error when I try to
start maven (with 'maven site'). In my opinion there is I defined 'site'
in the maven.xml and maven even starts but than aborts. I have no clue
why. Can anybody help me, please?!

-- output --
 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT


Starting the reactor...
Our processing order:
Utilities
+
| Building site Utilities
| Memory: 1M/2M
+
site:
all-build:
[echo] Processing whoweare.xml template ...
[echo] Processing source-repos.xml template ...
[echo] Processing mail.xml template ...
[echo] Processing navigation.xml template ...
INTERNAL ERROR
Reference made to goal 'site' which has no definition.

-- output end --


That's what my maven.xml looks like:



  

  

  




  

  




  
  Processing ${templateName} template ...

  



  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

INTERNAL ERROR question

[Kristine Weissbarth]

Hi, 

I'm using the reactor to set up maven for my project which has several
subproject (e.g. subproject utilities). It already worked some time ago
but now I'm always getting the following output and error when I try to
start maven (with 'maven site'). In my opinion there is I defined 'site'
in the maven.xml and maven even starts but than aborts. I have no clue
why. Can anybody help me, please?!

-- output --
 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0-beta-9-SNAPSHOT


Starting the reactor...
Our processing order:
Utilities
+
| Building site Utilities
| Memory: 1M/2M
+
site:
all-build:
[echo] Processing whoweare.xml template ...
[echo] Processing source-repos.xml template ...
[echo] Processing mail.xml template ...
[echo] Processing navigation.xml template ...
INTERNAL ERROR
Reference made to goal 'site' which has no definition.

-- output end --


That's what my maven.xml looks like:


  
  

  
  
  
  



  

  



  
  
  Processing ${templateName} template ... 

  

 

  




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Clover generates 0% code coverage reports

[S. Radhakrishnan]

Hello Andy,

when I use maven clover 1.0 plugin then I am getting clover:test target. but
when I execute the same, I am getting
"Compiler Adapter 'org.apache.tools.ant.taskdefs.CloverCompilerAdapter'
can't be found error". I referred the sites and placed clover.jar inside
ANT_HOME/lib and in classpath but still I am getting the same error. Is
there any way to resolve this.
I am trying with clover 1.0 plugin just because I am getting continuous
failures in clover 1.2 plugin.



-Original Message-
From: Andy Pols [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 12:24 PM
To: Maven Users List
Subject: Re: Clover generates 0% code coverage reports


Sorry should have said:

clover:on test

But that is not the reason it is not working as you have been using two
separate tasks.

It should work with your settings  - are your tests in the correct place?
Does the junit plugin work?

Andy

On 17/6/03 7:31 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:

> Hi Andy,
>
> I am using maven beta 9 version and clover 1.0. and
> if I run the command "maven clover:test"  it says no such target exists.
> and as I mentioned earlier, I am executing the same using two seperate
> commands.
> and my source directory and unit test source directory are same.
> and also I am having the maven.junit.fork=true property in
> project.properties.
>
> but still I am getting..the same error..
>
> RK
>
> -Original Message-
> From: Andy Pols [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 11:48 AM
> To: Maven Users List
> Subject: Re: Clover generates 0% code coverage reports
>
>
> The problem is that clover database logs are written on JVM shutdown.
> Thus if you call the clover test goal and then the report immediately
> after, you'll get an empty report.
>
> There are two solutions:
>
> So, to make it work, simply run :
>
> maven clover:test
>
> and then, in a separate command:
>
> maven clover:html-report
>
>
>
> Or placing the following in the project.properties file should also work:
> maven.junit.fork = true
>
> Andy
>
> On 17/6/03 6:38 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:
>
>> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
>> doing the clover test and clover report in two seperate commands
>>> maven clover test
>>> maven clover
>> but still the report gives 0% code coverage. Is there any wrong in the
>> clover plugin ?.. please can anybody help me out.
>>
>>
>> Thanks & Regards,
>> S.Radhakrishnan,


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Clover generates 0% code coverage reports

[S. Radhakrishnan]

Hello Andy,

Heres what I have,

1. I am having project.xml (included tag for clover).
2. maven.xml (included  tag for clover)
3. project.properties (fork is true and other stuffs)
4. src directory with package structure and in the same package test files
also avilable.
5. Using maven beta 9 and clover 1.0 versions
6. typed maven clover:on test command at first and the result build is
successful.
7. then I typed maven clover:html-report command, the result is also
successful but no coverage recordings found., however the database
containing valid information.
8. Is there any other configuration needed?.. do I missing something..

RK

-Original Message-
From: Andy Pols [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 12:24 PM
To: Maven Users List
Subject: Re: Clover generates 0% code coverage reports


Sorry should have said:

clover:on test

But that is not the reason it is not working as you have been using two
separate tasks.

It should work with your settings  - are your tests in the correct place?
Does the junit plugin work?

Andy

On 17/6/03 7:31 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:

> Hi Andy,
>
> I am using maven beta 9 version and clover 1.0. and
> if I run the command "maven clover:test"  it says no such target exists.
> and as I mentioned earlier, I am executing the same using two seperate
> commands.
> and my source directory and unit test source directory are same.
> and also I am having the maven.junit.fork=true property in
> project.properties.
>
> but still I am getting..the same error..
>
> RK
>
> -Original Message-
> From: Andy Pols [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 11:48 AM
> To: Maven Users List
> Subject: Re: Clover generates 0% code coverage reports
>
>
> The problem is that clover database logs are written on JVM shutdown.
> Thus if you call the clover test goal and then the report immediately
> after, you'll get an empty report.
>
> There are two solutions:
>
> So, to make it work, simply run :
>
> maven clover:test
>
> and then, in a separate command:
>
> maven clover:html-report
>
>
>
> Or placing the following in the project.properties file should also work:
> maven.junit.fork = true
>
> Andy
>
> On 17/6/03 6:38 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:
>
>> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
>> doing the clover test and clover report in two seperate commands
>>> maven clover test
>>> maven clover
>> but still the report gives 0% code coverage. Is there any wrong in the
>> clover plugin ?.. please can anybody help me out.
>>
>>
>> Thanks & Regards,
>> S.Radhakrishnan,


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Clover generates 0% code coverage reports

[S. Radhakrishnan]

Hi Andy,

When are all the times I will get no Coverage recordings.. any idea.?

RK

-Original Message-
From: Andy Pols [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 12:24 PM
To: Maven Users List
Subject: Re: Clover generates 0% code coverage reports


Sorry should have said:

clover:on test

But that is not the reason it is not working as you have been using two
separate tasks.

It should work with your settings  - are your tests in the correct place?
Does the junit plugin work?

Andy

On 17/6/03 7:31 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:

> Hi Andy,
> 
> I am using maven beta 9 version and clover 1.0. and
> if I run the command "maven clover:test"  it says no such target exists.
> and as I mentioned earlier, I am executing the same using two seperate
> commands.
> and my source directory and unit test source directory are same.
> and also I am having the maven.junit.fork=true property in
> project.properties.
> 
> but still I am getting..the same error..
> 
> RK
> 
> -Original Message-
> From: Andy Pols [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 11:48 AM
> To: Maven Users List
> Subject: Re: Clover generates 0% code coverage reports
> 
> 
> The problem is that clover database logs are written on JVM shutdown.
> Thus if you call the clover test goal and then the report immediately
> after, you'll get an empty report.
> 
> There are two solutions:
> 
> So, to make it work, simply run :
> 
> maven clover:test
> 
> and then, in a separate command:
> 
> maven clover:html-report
> 
> 
> 
> Or placing the following in the project.properties file should also work:
> maven.junit.fork = true
> 
> Andy
> 
> On 17/6/03 6:38 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:
> 
>> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
>> doing the clover test and clover report in two seperate commands
>>> maven clover test
>>> maven clover
>> but still the report gives 0% code coverage. Is there any wrong in the
>> clover plugin ?.. please can anybody help me out.
>> 
>> 
>> Thanks & Regards,
>> S.Radhakrishnan,


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Clover generates 0% code coverage reports

[S. Radhakrishnan]

Hi Andy,

clover:on test successfully builds the test cases and updates the database
too by instrumenting all source files. but the reports are again 0% coverage
recordings. However, my junit plugin is working fine and I can get to see
all my junit test reports with statistics.

RK

-Original Message-
From: Andy Pols [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2003 12:24 PM
To: Maven Users List
Subject: Re: Clover generates 0% code coverage reports


Sorry should have said:

clover:on test

But that is not the reason it is not working as you have been using two
separate tasks.

It should work with your settings  - are your tests in the correct place?
Does the junit plugin work?

Andy

On 17/6/03 7:31 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:

> Hi Andy,
>
> I am using maven beta 9 version and clover 1.0. and
> if I run the command "maven clover:test"  it says no such target exists.
> and as I mentioned earlier, I am executing the same using two seperate
> commands.
> and my source directory and unit test source directory are same.
> and also I am having the maven.junit.fork=true property in
> project.properties.
>
> but still I am getting..the same error..
>
> RK
>
> -Original Message-
> From: Andy Pols [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 11:48 AM
> To: Maven Users List
> Subject: Re: Clover generates 0% code coverage reports
>
>
> The problem is that clover database logs are written on JVM shutdown.
> Thus if you call the clover test goal and then the report immediately
> after, you'll get an empty report.
>
> There are two solutions:
>
> So, to make it work, simply run :
>
> maven clover:test
>
> and then, in a separate command:
>
> maven clover:html-report
>
>
>
> Or placing the following in the project.properties file should also work:
> maven.junit.fork = true
>
> Andy
>
> On 17/6/03 6:38 am, "S. Radhakrishnan" <[EMAIL PROTECTED]> wrote:
>
>> Hi I am using maven beta 9 and clover 1.0. after referred the sites i am
>> doing the clover test and clover report in two seperate commands
>>> maven clover test
>>> maven clover
>> but still the report gives 0% code coverage. Is there any wrong in the
>> clover plugin ?.. please can anybody help me out.
>>
>>
>> Thanks & Regards,
>> S.Radhakrishnan,


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]