date:20051108





Hi guys,

Maven 2.0 has been released for quite a while now, and I was wondering when
the Maven Distributed Plugins of the Maven Plugin Matrix would all be
released in their final versions. As for me, I'm looking forward to the
site plugin and the war plugin (which has only 4 issues left, amongst which
MNG-1038 is important to me).

Thanks for your answer!

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


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

[m2] How dependency versions are resolved with transitivity?





Hi,

Does anyone know how Maven resolves a version for a specific depedency when
this dependency comes with different versions due to transitivity?

I have the following case: I'm developing a framework where I use
commons-lang version 2.0, along with other libs that have commons-lang in
their POM, but with a different version (1.0.1 most of the time). In my
WAR, I end up with version 1.0.1 of commons-lang.
I know that projects using my framework can handle that by using dependency
management. However, I would expect that version 2.0 of commons-lang would
be used as I specified it in the deps of the POM of my framework (shouldn't
that override the version 1.0.1 given by transitivity of other libs ?).

Thanks for you answer !

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


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

built in project properties

2005-11-08 Thread David Sag


Where can I find a doc on the built
in maven 2 pom properties such as ${project.build.directory}

specifically I need one that is the
project's base directory. ${project.directory} is not it apparently.

Kind regards,
Dave Sag

First Release of Maven?

2005-11-08 Thread Bernd Mau

Hi,

can anybody tell when the first public and stable version of Maven has
been released?

Bernd


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

Re: built in project properties

you could use ${project.basedir} or ${basedir} to get a reference to the
path containing the pom.xml. note that in multi-module applications these
will resolve to the directory of the module being built.
 i too am looking for a list of the project properties. my previous
question[1] is still unanswered though but i just used the basedir to
navigate to the directory i wanted. ugly but it works. :)
 [1] http://www.mail-archive.com/users@maven.apache.org/msg27441.html
 ciao!


 On 11/8/05, David Sag [EMAIL PROTECTED] wrote:


 Where can I find a doc on the built in maven 2 pom properties such as ${
 project.build.directory}

 specifically I need one that is the project's base directory. ${
 project.directory} is not it apparently.

 Kind regards,
 Dave Sag







--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else better
to do

Re: Can't use maven2 (offline)

2005-11-08 Thread Eric Parpal


Offline actually avoids all remote repositories (even file ones, as
they might be on a shared drive).
But I had said that offline=false. So, I don't understand why my defined 
repository is ignored.



On 11/8/05, Eric Parpal [EMAIL PROTECTED] wrote:
 I tried with offline=false and file:///mypath/ibiblio/maven2 (in
 settings.xml and in the command line).
So, assuming that I don't set offline to true, what is wrong with my 
settings :

profiles
   profile
   repositories
   repository
   idrepo1/id
   namerepo1/name
   urlfile:/mypath/ibiblio/maven2/url
   /repository
   /repositories
   pluginRepositories
   pluginRepository
   idrepo2/id
   namerepo2/name
   urlfile:/mypath/ibiblio/maven2/url
   /pluginRepository
   /pluginRepositories
   idMyProfile/id
   /profile
   activeProfiles
   activeProfileMyProfile/activeProfile
   /activeProfiles

Moreover, what's the difference between a repository and a 
pluginRepository ?


Thanks.

_
10 Mo pour vos pièces jointes avec MSN Hotmail ! 
http://www.imagine-msn.com/hotmail/default.aspx?locale=fr-FR



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

RE: First Release of Maven?

2005-11-08 Thread Vincent Siveton

Hi Bernd,

Maven 2: 19 Oct 2005
Maven 1: 13 Jul 2004

Regards,

Vincent

 -Original Message-
 From: Bernd Mau [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, November 08, 2005 5:51 AM
 To: users@maven.apache.org
 Subject: First Release of Maven?
 
 Hi,
 
 can anybody tell when the first public and stable version of Maven has
 been released?
 
 Bernd
 
 
 -
 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]

M2 Getting started guide

2005-11-08 Thread Pete

The M2 getting starting guide used to go on to explain how to set up a
parent project and child projects with a simple example (parent etc) ,
this seems to have gone completely from the guide.

I have this working myself, but was pointing others in the this
direction for information.

The mini guides have nothing on multi project.

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

Re: [m2] How dependency versions are resolved with transitivity?

Hi Fabrice,

mvn currently mediates dependency versions using a nearest-wins
strategy.  This means that the dependency version specified highest in
the dependency tree (i.e. nearest to the project being built) is used.

As a side note, I really need the highest-wins strategy - any pointers
to open issues or code required?

Mark

On 08/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:




 Hi,

 Does anyone know how Maven resolves a version for a specific depedency when
 this dependency comes with different versions due to transitivity?

 I have the following case: I'm developing a framework where I use
 commons-lang version 2.0, along with other libs that have commons-lang in
 their POM, but with a different version (1.0.1 most of the time). In my
 WAR, I end up with version 1.0.1 of commons-lang.
 I know that projects using my framework can handle that by using dependency
 management. However, I would expect that version 2.0 of commons-lang would
 be used as I specified it in the deps of the POM of my framework (shouldn't
 that override the version 1.0.1 given by transitivity of other libs ?).

 Thanks for you answer !

 Best Regards / Cordialement,
 Fabrice BELLINGARD
 DINQ/DSIN/INSI/EATE/IDVS/AIDV
 (+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


 -
 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]

Guide to creating archetypes

2005-11-08 Thread Alexander Hars


Hi,

Two weeks ago I wrote a significantly expanded Guide to Creating 
Archetypes. It was immediately posted to CVS, but it is still not 
available on the website.


Is there some reason why the Maven2 site is not updated regularly (last 
update was 10/21). Shouldn't it be very easy using Maven2?
I am sure that lots of  improvements have been made to the documentation 
in the last weeks.


The documentation is really essential for all us newbies to Maven2 and 
it would help very much if you could update the site.


Thank you very much
Alexander


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

CVS: extssh

2005-11-08 Thread Rafael Silva

Hi,

I'm using Continuum with Maven in my project (opensource project), and I'm 
using a extssh connection to the CVS. I put my project.xml file on Maven 1.x 
Project. I can see my project at the Show Projects. When I click to build, 
it left just 1 second and stop. No logs were created. I think that what happens 
with it is the type of my connection (extssh - scm:cvs:ext:[EMAIL 
PROTECTED]:/home/persapiens/cvs:base). May someone help me about this?! I'd 
like to know if I can use extssh connection, or I need to change my type of 
connection?!

Thanks in advance,

Rafael Silva
[EMAIL PROTECTED]
Bolsista PIBIC

Re: Guide to creating archetypes

2005-11-08 Thread Richard Allen

I second that one. My biggest stumbling block so far with adopting Maven 
has been lack of documentation. However, I do understand how difficult 
it can be to get the docs written.


Richard

Alexander Hars wrote:


Hi,

Two weeks ago I wrote a significantly expanded Guide to Creating 
Archetypes. It was immediately posted to CVS, but it is still not 
available on the website.


Is there some reason why the Maven2 site is not updated regularly 
(last update was 10/21). Shouldn't it be very easy using Maven2?
I am sure that lots of  improvements have been made to the 
documentation in the last weeks.


The documentation is really essential for all us newbies to Maven2 and 
it would help very much if you could update the site.


Thank you very much
Alexander


-
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: Guide to creating archetypes

maybe we can use http://wiki.apache.org/maven/ for a collaborative
effort? there is no specific wiki site for maven2 but from what i can
see that wiki is relatively unused by maven1.

finalized documents could then be promoted to the official site as the
maintainers see fit. not everybody has ready access to the development
branch so i guess there will be people who will benefit in this
effort.

ciao!

On 11/8/05, Richard Allen [EMAIL PROTECTED] wrote:
 I second that one. My biggest stumbling block so far with adopting Maven
 has been lack of documentation. However, I do understand how difficult
 it can be to get the docs written.

 Richard

 Alexander Hars wrote:

  Hi,
 
  Two weeks ago I wrote a significantly expanded Guide to Creating
  Archetypes. It was immediately posted to CVS, but it is still not
  available on the website.
 
  Is there some reason why the Maven2 site is not updated regularly
  (last update was 10/21). Shouldn't it be very easy using Maven2?
  I am sure that lots of  improvements have been made to the
  documentation in the last weeks.
 
  The documentation is really essential for all us newbies to Maven2 and
  it would help very much if you could update the site.
 
  Thank you very much
  Alexander
 
 
  -
  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]




--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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

WebDav

2005-11-08 Thread Alexandre Poitras

Hi,

I just wanted to know what is the current status of WebDav support. It is
still written on progess on maven wagon web site. Is there some features
already available from the svn version. Thank.

--
Alexandre Poitras
Québec, Canada

Re: [m102] bad results when including custom.css

2005-11-08 Thread Thomas_Perry







hi Lukas,

Thank you for responding with help.

However, I was not able to get  ${basedir}/xdocs/style/custom.css to work.

The rendered html did not use my css, and when I viewed the html source,
it was not importing custom.css

I put the file everywhere in my project.  The xdoc plugin *did* copy it to
the output folders, but it was never used.

I finally google'd on   maven.xdoc.theme.url  and found a jira reference at
http://jira.codehaus.org/browse/MPXDOC-85  that mentioned just using
the name project.css for a custom stylesheets file.

That *does* work.   ${basedir}/xdocs/style/project.css   is picked up
by xdoc, the html imports it, and my stylesheet is used.

Maybe I was doing something else wrong, and maybe this works because
of some other change I made, but at least it works and I'm not touching
the project.

Thanks again for your help.

Tom



   
 Lukas Theussl 
 [EMAIL PROTECTED] 
 org   To 
   Maven Users List
 11/04/2005 06:45  users@maven.apache.org
 PM cc 
   
   Subject 
 Please respond to Re: [m102] bad results when 
   Maven Usersincluding custom.css
   List   
 [EMAIL PROTECTED] 
  he.org  
   
   
   




Hi Thomas,

The maven.xdoc.theme.url property only works as an absolute URL (the
documentation on this has recently been updated), what you want is a
project.css file in xdocs/style/, this will automatically be picked up.

HTH,
-Lukas


[EMAIL PROTECTED] wrote:




 hello,

 I put a custom.css file under xdocs/style  and added
maven.xdoc.theme.url
 =./style/custom.css
 to project.properties

 The m1 doc says ...a css file that can be used in addition to
 maven-base.css

 However, when the site is generated, the pages do not look like a
standard
 maven
 project page.

 it looks like none of the standard maven css files are being used or
found.

 Do I need to specify anything else to make all the maven css files
 available?

 Thanks
 Tom




 This message is intended for the recipient only and is not meant to be
forwarded or distributed in any other format. This communication is for
informational purposes only.  It is not intended as an offer or
solicitation for the purchase or sale of any financial instrument, or
security, or as an official confirmation of any transaction.  Putnam does
not accept purchase or redemptions of securities, instructions, or
authorizations that are sent via e-mail.   All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice.  Any comments or statements made herein
do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments)
and its subsidiaries and affiliates.  If you are not the intended recipient
of this e-mail, please delete the e-mail.

 -
 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]





 
This message is intended for the recipient only and is not meant to be 
forwarded or distributed in any other format. This communication is for 
informational purposes only.  It is not intended as an offer or solicitation 
for the purchase or sale of any financial instrument, or security, or as an 
official confirmation of any transaction.  Putnam does not accept purchase or 
redemptions of securities, instructions, or authorizations that are sent via 
e-mail.   All market prices, data and other information are not warranted as to 
completeness or accuracy and are subject to change without notice.  Any 
comments or statements made herein do not necessarily reflect those of Putnam, 
LLC (DBA Putnam Investments) and its subsidiaries and affiliates.  If you are 
not the intended recipient of this e-mail, please delete the e-mail.

-
To

Re: mvn site for parent does not create site info for children?

2005-11-08 Thread Dietrich Schulten

Something seems to be wrong. I defined:

distributionManagement
site
identer-easy/id
urlfile://G:/entereasy/trunk/EnterEasyServer/target/mysite/url
/site
/distributionManagement

but no folder mysite is created, rather everything goes to the
respective target/site folders of each module.
It seems that the site url is ignored. Or do I miss something?

Regards,
Dietrich

Yann Le Du schrieb:
 Hi Dietrich,
 
 Calling mvn site on the parent also creates sites for modules (if you don't
 provide a site url for the module, it will be parentSiteUrl/module).
 
 Automatically creating links between parent and modules is due for 2.0.1 :
 http://jira.codehaus.org/browse/MNG-661
 
 Regards,
 Yann
 
 --- Dietrich Schulten [EMAIL PROTECTED] a écrit :
 
 
Hi,

does the site plugin only work for single projects or can I use it with
a parent POM to create a site for the whole project tree?

mvn site on the parent seems to create a site without any links to the
submodules.

Regards,
Dietrich


-

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
   
 
   
   
 ___ 
 Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
 Téléchargez cette version sur http://fr.messenger.yahoo.com
 
 -
 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: [m2] JAXB Plugin

2005-11-08 Thread Geoffrey


Hi Wilfried,

Maven 1
===

Brett and me did some work for the maven 1 jaxb plugin @sf, but as 
neither of us is using jaxb with maven 1 at the moment it's a plugin 
with out a maintainer. Maven 2 has 
http://mojo.codehaus.org/xjc-maven-plugin/index.html.


If it's ok with Brett, I 'd put up this notice on the jaxb plugin 
website to and make a link to the maven 2 plugin.


However it shouldn't be hard to update the jaxb plugin to jswdp 1.6:
- checkout the latest version from the sf CVS.
- adjust the maven-jaxb-plugin version to 1.1.1.wilfried.1 (so your 
version doesn't collide with ours) (The current version in cvs is 1.1.1)

- adjust the dependencies's version
- make sure those dependency versions are in your repo
- maven plugin:install
- and try it out.

And if you send me the adjusted project.xml, I can update it and release 
a new version of the jaxb plugin for jswdp 1.6.


Maven 2
===

It's probably more usefull to put your time into maven 2.
Checkout the xjc-maven-plugin and see if it's adjustable to using jaxb 
of jswdp 1.6.

Send that patch to its maintainer (Ashley Williams).

--
With kind regards,
Geoffrey De Smet

Wilfred Springer wrote:

All,

Just to make sure: did anybody ever run into a Maven 2 JAXB plugin?
AFAIK, the only existing plugin is the one for Maven 1 and a JAXME
plugin at mojo.codehaus.org. I am looking for a JWSDP 1.6 based version.

Thanks,

Wilfred




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

[M2] How to add generation-only dependencies like junitdoclet

2005-11-08 Thread Dietrich Schulten

Hi,

some dependencies are used as external tools for generation only, for
instance junitdoclet. They are not needed in the distribution. The
scopes compile, test, runtime do not suffice as it seems.

What is best-practice to use such tools with Mvn?

Regards,
Dietrich

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

RE: [m2] Guide to creating archetypes

2005-11-08 Thread Tony Steele

Please update website, my biggest problem is finding out how to do
things.

Tony
-Original Message-
From: Alexander Hars [mailto:[EMAIL PROTECTED] 
Sent: 08 November 2005 12:53
To: Maven Users List
Subject: Guide to creating archetypes

Hi,

Two weeks ago I wrote a significantly expanded Guide to Creating 
Archetypes. It was immediately posted to CVS, but it is still not 
available on the website.

Is there some reason why the Maven2 site is not updated regularly (last 
update was 10/21). Shouldn't it be very easy using Maven2?
I am sure that lots of  improvements have been made to the documentation

in the last weeks.

The documentation is really essential for all us newbies to Maven2 and 
it would help very much if you could update the site.

Thank you very much
 Alexander

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

http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system. 
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received. 
Further communication will signify your consent to this.

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

Re: WebDav

Hi there,

My colleague has written the WebDAV wagon referred to on the website
and I'm bugging him to submit it :)

It's based on apache slide and we use it fine internally.  The blocker
to submitting was sorting out the slide pom on ibiblio - I've just
submitted an issue summarising the problem:

http://jira.codehaus.org/browse/MEV-190

Once this is resolved we can submit the code.  We also intend to
rewrite the provider to not depend on slide but just implement a
lightweight WebDAV implementation, although it'd be good to get a
version up there first.

Cheers,

Mark

On 08/11/05, Alexandre Poitras [EMAIL PROTECTED] wrote:
 Hi,

 I just wanted to know what is the current status of WebDav support. It is
 still written on progess on maven wagon web site. Is there some features
 already available from the svn version. Thank.

 --
 Alexandre Poitras
 Québec, Canada



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

Re: Guide to creating archetypes

On Tue, 2005-11-08 at 13:53 +0100, Alexander Hars wrote:
 Hi,
 
 Two weeks ago I wrote a significantly expanded Guide to Creating 
 Archetypes. It was immediately posted to CVS, but it is still not 
 available on the website.

http://maven.apache.org/guides/mini/guide-creating-archetypes.html

Is that not it?

 Is there some reason why the Maven2 site is not updated regularly (last 
 update was 10/21). Shouldn't it be very easy using Maven2?

mvn site-deploy

 I am sure that lots of  improvements have been made to the documentation 
 in the last weeks.

It is usually deployed once a day if not more.

 The documentation is really essential for all us newbies to Maven2 and 
 it would help very much if you could update the site.

We usually update the site when changes are made, but like all human
beings we sometimes miss things. If the guide you are referring does not
have the expected content just let me know.

 Thank you very much
  Alexander
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

 -- Eric Hoffer, Reflections on the Human Condition


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

Re: Guide to creating archetypes

On Tue, 2005-11-08 at 08:02 -0500, Richard Allen wrote:
 I second that one. My biggest stumbling block so far with adopting Maven 
 has been lack of documentation. However, I do understand how difficult 
 it can be to get the docs written.

If there is something lacking then it is best to use one of the four
components we have for documentation:

http://jira.codehaus.org/secure/BrowseProject.jspa

As far as the site goes I've tried to make the first quick links give a
clear path to the documentation if that is lacking just let us know:

Features
Download 
Installation Instructions 
Getting Started 
Documentation
Available Plug-ins 
Plug-in Matrix
Where is it?

The plug-in matrix is particularly helpful when looking for specific
things you need and we now have 34 mini guides, and 11 guides on
introductory material. We can only help with users' direction. Saying
there is a lack of documentation doesn't really help anyone. We need
to know where it is lacking in order to fix it.



 Richard
 
 Alexander Hars wrote:
 
  Hi,
 
  Two weeks ago I wrote a significantly expanded Guide to Creating 
  Archetypes. It was immediately posted to CVS, but it is still not 
  available on the website.
 
  Is there some reason why the Maven2 site is not updated regularly 
  (last update was 10/21). Shouldn't it be very easy using Maven2?
  I am sure that lots of  improvements have been made to the 
  documentation in the last weeks.
 
  The documentation is really essential for all us newbies to Maven2 and 
  it would help very much if you could update the site.
 
  Thank you very much
  Alexander
 
 
  -
  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
jason at maven.org
http://maven.apache.org

Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.

 -- Eric Hoffer, Reflections on the Human Condition


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

[M2] single source tree - multiple artifacts - summary of options

2005-11-08 Thread Ruel Loehr

Guys,

I was looking for a faq or doc that spelled out the options for those of
us who have single source trees but need to produce multiple artifacts
but can't find one.

I realize that my #1 option is to split the tree (this is in fact that
path I will pursue), but I also want to be able to defend my position
and state something like, 

I split the source tree due to the fact that there are no workarounds
in maven2 for producing multiple artifacts from a single source tree.

Is this in fact true?   I want to make sure before I pursue this route
that it could not be accomplished by somehow creating multiple pom's in
a single root dir or something.



Ruel Loehr
JBoss QA
 
-
512-626-2782
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

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

RE: JCOVERAGE for MAVEN 2

2005-11-08 Thread REBOISSON Eric

jcoverage in  http://www.ibiblio.org/maven2/ seems to be a library and not a
plugin.

The plugin jcoverage is not yet implemented ?

Eric

-Message d'origine-
De : SCHNEIDER Sebastien [mailto:[EMAIL PROTECTED]
Envoyé : mardi 8 novembre 2005 10:19
À : Maven Users List
Objet : RE : JCOVERAGE for MAVEN 2


Hi!
 
You can find last maven2 plugins version on http://www.ibiblio.org/maven2/
http://www.ibiblio.org/maven2/ .
There's one for jcoverage, jblanket, etc ...
 
but I didn't test it yet,
good luck.
 
Sébastien Schneider.
 

__

Ce message (et toutes ses pièces jointes éventuelles) est confidentiel et
établi à l'intention exclusive de ses destinataires. Toute utilisation de ce
message non conforme à sa destination, toute diffusion ou toute publication,
totale ou partielle, est interdite, sauf autorisation expresse. L'IFP
décline toute responsabilité au titre de ce message.

This message and any attachments (the message) are confidential and intended
solely for the addressees. Any unauthorised use or dissemination is
prohibited. IFP should not be liable for this message.

Visitez notre site Web / Visit our web site : http://www.ifp.fr
__





-
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: Guide to creating archetypes

On Tue, 2005-11-08 at 15:11 +0200, Anuerin Diaz wrote:
 maybe we can use http://wiki.apache.org/maven/ for a collaborative
 effort? there is no specific wiki site for maven2 but from what i can
 see that wiki is relatively unused by maven1.

Anyone is welcome to use the wiki but we have a decent pattern started
for the doco. People can help by adding to the FAQs, creating mini
guides and creating introductory guides. If they are placed in JIRA they
are usually processed pretty quickly. Full documents if they are new are
preferred and patches for everything else are greatly appreciated.
Patches get absorbed pretty quickly.

 finalized documents could then be promoted to the official site as the
 maintainers see fit. not everybody has ready access to the development
 branch so i guess there will be people who will benefit in this
 effort.

Unfortunately we don't have a very good work flow in place for this
right now and JIRA is your best bet at the moment.

 ciao!
 
 On 11/8/05, Richard Allen [EMAIL PROTECTED] wrote:
  I second that one. My biggest stumbling block so far with adopting Maven
  has been lack of documentation. However, I do understand how difficult
  it can be to get the docs written.
 
  Richard
 
  Alexander Hars wrote:
 
   Hi,
  
   Two weeks ago I wrote a significantly expanded Guide to Creating
   Archetypes. It was immediately posted to CVS, but it is still not
   available on the website.
  
   Is there some reason why the Maven2 site is not updated regularly
   (last update was 10/21). Shouldn't it be very easy using Maven2?
   I am sure that lots of  improvements have been made to the
   documentation in the last weeks.
  
   The documentation is really essential for all us newbies to Maven2 and
   it would help very much if you could update the site.
  
   Thank you very much
   Alexander
  
  
   -
   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]
 
 
 
 
 --
 
 Programming, an artform that fights back
 
 Anuerin G. Diaz
 Registered Linux User #246176
 Friendly Linux Board @ http://mandrivausers.org/index.php
 http://capsule.ramfree17.org , when you absolutely have nothing else
 better to do
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

Three people can keep a secret provided two of them are dead.

 -- Unknown


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

Re: mvn site for parent does not create site info for children?

2005-11-08 Thread Jeff Jensen

What goal did you run?  Only site:deploy will do what you are looking for. 
Running site only does the site build.

The goals for each plugin are listed on the Maven plugin docs.  Here is the one
for site:
http://maven.apache.org/plugins/maven-site-plugin/


Quoting Dietrich Schulten [EMAIL PROTECTED]:

 Something seems to be wrong. I defined:

 distributionManagement
 site
 identer-easy/id
 urlfile://G:/entereasy/trunk/EnterEasyServer/target/mysite/url
 /site
 /distributionManagement

 but no folder mysite is created, rather everything goes to the
 respective target/site folders of each module.
 It seems that the site url is ignored. Or do I miss something?

 Regards,
 Dietrich

 Yann Le Du schrieb:
  Hi Dietrich,
 
  Calling mvn site on the parent also creates sites for modules (if you don't
  provide a site url for the module, it will be parentSiteUrl/module).
 
  Automatically creating links between parent and modules is due for 2.0.1 :
  http://jira.codehaus.org/browse/MNG-661
 
  Regards,
  Yann
 
  --- Dietrich Schulten [EMAIL PROTECTED] a écrit :
 
 
 Hi,
 
 does the site plugin only work for single projects or can I use it with
 a parent POM to create a site for the whole project tree?
 
 mvn site on the parent seems to create a site without any links to the
 submodules.
 
 Regards,
 Dietrich
 
 
 -
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
 
 
  ___
  Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
  Téléchargez cette version sur http://fr.messenger.yahoo.com
 
  -
  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: Issue tracking system

On Tue, 2005-11-08 at 14:57 +0100, Srepfler Srgjan wrote:
 Trac is a issue tracking system that's gaining popularity these days 
 http://www.edgewall.com/trac/ you can see an running instance here: 
 http://projects.edgewall.com/trac/
 It's a blend of wiki - issuetracker - subversion and is written in python.
 I just saw that there is a link for issue tracking  once I generated the 
 project site and I was wondering if I could use trac but I guess it's 
 not supported.

Sure you can use Trac. You are simply listing the URL to the issue
tracker right now, we don't really have any integration with issue
tracking systems right now per se but we're interested in making it
easier to work with issues tracking systems. One thing that is on the
horizon is a general API for interacting with issue tracking systems.

 Brett Porter wrote:
 
 Currently we have the following integration:
 - project info reports list the issue tracker (supports jira, bugzilla
 and scarab I believe)
 - changes plugin can retrieve changes from jira
 
 What type of support are you looking for?
 
 - Brett
 
 On 11/8/05, Srepfler Srgjan [EMAIL PROTECTED] wrote:
   
 
 Is there a way to integrate maven with an issue tracking system such as
 Trac?
 
 -
 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]
 
   
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

Simplex sigillum veri. (Simplicity is the seal of truth.)


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

RE: [m2] Guide to creating archetypes

On Tue, 2005-11-08 at 14:42 +, Tony Steele wrote:
 Please update website, 

The site is updated very frequently. We try to keep it current with the
changes made to the documentation.

 my biggest problem is finding out how to do
 things.

Anything in particular that's missing from the guides or introductory
material? Also check the JIRA components for documentation as I know
there are guides like the multi-project guide that are in demand and
it's noted in JIRA. You can also vote on issues which lets us know what
you guys want most which lets us focus our time better on writing what's
most desired.

 Tony
 -Original Message-
 From: Alexander Hars [mailto:[EMAIL PROTECTED] 
 Sent: 08 November 2005 12:53
 To: Maven Users List
 Subject: Guide to creating archetypes
 
 
 Hi,
 
 Two weeks ago I wrote a significantly expanded Guide to Creating 
 Archetypes. It was immediately posted to CVS, but it is still not 
 available on the website.
 
 Is there some reason why the Maven2 site is not updated regularly (last 
 update was 10/21). Shouldn't it be very easy using Maven2?
 I am sure that lots of  improvements have been made to the documentation
 
 in the last weeks.
 
 The documentation is really essential for all us newbies to Maven2 and 
 it would help very much if you could update the site.
 
 Thank you very much
  Alexander
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 http://www.bbc.co.uk/
 
 This e-mail (and any attachments) is confidential and may contain
 personal views which are not the views of the BBC unless specifically
 stated.
 If you have received it in error, please delete it from your system. 
 Do not use, copy or disclose the information in any way nor act in
 reliance on it and notify the sender immediately. Please note that the
 BBC monitors e-mails sent or received. 
 Further communication will signify your consent to this.
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

Re: [M2] How to add generation-only dependencies like junitdoclet

On Tue, 2005-11-08 at 16:07 +0100, Dietrich Schulten wrote:
 Hi,
 
 some dependencies are used as external tools for generation only, for
 instance junitdoclet. They are not needed in the distribution. The
 scopes compile, test, runtime do not suffice as it seems.
 
 What is best-practice to use such tools with Mvn?

You would make a plug-in for junitdoclet which you would then use in
your project and plug-in depenencies are fully separate from your
project.

The use of tools is encapsulated in plug-ins. Generating sources of any
kind would be handled by a plug-in. The closest example we have is this:

http://maven.apache.org/guides/mini/guide-generating-sources.html

Your junitdoclet plug-in would look very similar to that.

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

Jason van Zyl
jason at maven.org
http://maven.apache.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: [M2] single source tree - multiple artifacts - summary of options

On Tue, 2005-11-08 at 09:02 -0600, Ruel Loehr wrote:
 Guys,
 
 I was looking for a faq or doc that spelled out the options for those of
 us who have single source trees but need to produce multiple artifacts
 but can't find one.

What are the artifacts that you want to produce?

We do support secondary or attached artifacts and an example of that is
creating an ejb client JAR along with the full ejb jar.

We also generally recommend decomposing your build in separate builds if
you required multiple source trees. But I can't recommend anything
without knowing what you're trying to accomplish.

 I realize that my #1 option is to split the tree (this is in fact that
 path I will pursue), but I also want to be able to defend my position
 and state something like, 
 
 I split the source tree due to the fact that there are no workarounds
 in maven2 for producing multiple artifacts from a single source tree.

That's not entirely true. We frown up producing multiple primary
artifacts for example trying to build both the client, server and common
code from a single build.

 Is this in fact true?   I want to make sure before I pursue this route
 that it could not be accomplished by somehow creating multiple pom's in
 a single root dir or something.

The rule of thumb is one primary artifact per build. I've created JIRA
issues to request a mini guide be made on explaining secondary/attached
artifacts.

 
 
 Ruel Loehr
 JBoss QA
  
 -
 512-626-2782
 Yahoo: ruelloehr
 Skype: ruelloehr
 AOL: dokoruel
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



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

[M2] Problem using scm with cvs

2005-11-08 Thread Tony Steele

I am trying to use cvs as the scm with the cvs user name etc specified
in the local settings.xml. However the profile properties do not appear
to be substituted in the scm connection string. 

Anybody got any ideas?

I have the following:

Pom:
scm
  connection
 
scm:cvs:pserver:[EMAIL PROTECTED]:/data/cvsroot:applications/DIS
Repository/components/DISRepositoryManager
  /connection
/scm

Settings:

profiles
  profile
iddefault/id
  properties
cvs.userxx/cvs.user
cvs.serveramlnx04.tv.bbc.co.uk/cvs.server
  /properties
  /profile
/profiles
activeProfiles
  activeProfiledefault/activeProfile
/activeProfiles

Error:

[INFO] Generate changelog report.
[INFO] Generating changed sets xml to:
D:\Project\DISRepositoryManager\target\changelog.xml
[ERROR] Didn't find password for CVSROOT
':pserver:[EMAIL PROTECTED]:/data/cvsroot'.
[ERROR] Error processing command
org.netbeans.lib.cvsclient.connection.AuthenticationException: I/O error
while connecting to host ${cvs.server}.
at
org.netbeans.lib.cvsclient.connection.PServerConnection.openConnection(P
ServerConnection.java:237)
at
org.netbeans.lib.cvsclient.connection.PServerConnection.open(PServerConn
ection.java:298)

Tony

http://www.bbc.co.uk/

This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system. 
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received. 
Further communication will signify your consent to this.

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

Re: [m2] How dependency versions are resolved with transitivity?

On Tue, 2005-11-08 at 12:49 +, Mark Hobson wrote:
 Hi Fabrice,
 
 mvn currently mediates dependency versions using a nearest-wins
 strategy.  This means that the dependency version specified highest in
 the dependency tree (i.e. nearest to the project being built) is used.
 
 As a side note, I really need the highest-wins strategy - any pointers
 to open issues or code required?

It's slated for 2.1.

 Mark
 
 On 08/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 
 
 
 
  Hi,
 
  Does anyone know how Maven resolves a version for a specific depedency when
  this dependency comes with different versions due to transitivity?
 
  I have the following case: I'm developing a framework where I use
  commons-lang version 2.0, along with other libs that have commons-lang in
  their POM, but with a different version (1.0.1 most of the time). In my
  WAR, I end up with version 1.0.1 of commons-lang.
  I know that projects using my framework can handle that by using dependency
  management. However, I would expect that version 2.0 of commons-lang would
  be used as I specified it in the deps of the POM of my framework (shouldn't
  that override the version 1.0.1 given by transitivity of other libs ?).
 
  Thanks for you answer !
 
  Best Regards / Cordialement,
  Fabrice BELLINGARD
  DINQ/DSIN/INSI/EATE/IDVS/AIDV
  (+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]
 
 
  -
  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
jason at maven.org
http://maven.apache.org

Simplex sigillum veri. (Simplicity is the seal of truth.)


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

Re: [m2] Guide to creating archetypes

2005-11-08 Thread ir. ing. Jan Dockx



On 8 Nov 2005, at 15:42, Tony Steele wrote:


Please update website, my biggest problem is finding out how to do
things.

Tony



That's one for my sigs! :-)



[…]  my biggest problem is finding out how to do things.
(in a mail on the Maven Users List)

Re: Assembly dependency set includes

On Tue, 2005-11-08 at 10:24 +0100, Nitko2 wrote:
 Can I use wildcards in dependency set includes inside assembly descriptor?
 
 assembly
idmy-assembly/id
formats
  formatjar/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
fileSets
  fileSet
directorytarget/classes/directory
outputDirectory//outputDirectory
  /fileSet
/fileSets
dependencySets
  dependencySet
outputDirectory//outputDirectory
unpacktrue/unpack
scoperuntime/scope
includes
   includegroupId:artifactId/include
/includes
  /dependencySet
/dependencySets
 /assembly
 
 I would like to use something like includegroupId:*/include
 
 
 If not, is it planned?

Doesn't appear to be, can you create an JIRA issue:

http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=truemode=hidepid=10500sorter/order=DESCsorter/field=priorityresolution=-1component=11804


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

Jason van Zyl
jason at maven.org
http://maven.apache.org

the course of true love never did run smooth ...

 -- Shakespeare


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

Re: [m2] How dependency versions are resolved with transitivity?





Hi Mark,

Thank you for your answer! :)
Then I have another question: when 2 different dependency versions are at
the same level in the dependency tree, which one wins? Because in my case,
I have version 2.0 and version 1.0.1 of commons-lang at the same level, and
1.0.1 wins.

The highest-win strategy would be interesting, I agree.

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


   
 Mark Hobson   
 [EMAIL PROTECTED]  
 l.com   Pour
   Maven Users List
 08/11/2005 13:49  users@maven.apache.org
cc
   
 VeuillezObjet
répondre à Re: [m2] How dependency versions
 Maven Users List  are resolved with transitivity? 
 [EMAIL PROTECTED]  
 che.org  
   
   
   
   




Hi Fabrice,

mvn currently mediates dependency versions using a nearest-wins
strategy.  This means that the dependency version specified highest in
the dependency tree (i.e. nearest to the project being built) is used.

As a side note, I really need the highest-wins strategy - any pointers
to open issues or code required?

Mark

On 08/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:




 Hi,

 Does anyone know how Maven resolves a version for a specific depedency
when
 this dependency comes with different versions due to transitivity?

 I have the following case: I'm developing a framework where I use
 commons-lang version 2.0, along with other libs that have commons-lang in
 their POM, but with a different version (1.0.1 most of the time). In my
 WAR, I end up with version 1.0.1 of commons-lang.
 I know that projects using my framework can handle that by using
dependency
 management. However, I would expect that version 2.0 of commons-lang
would
 be used as I specified it in the deps of the POM of my framework
(shouldn't
 that override the version 1.0.1 given by transitivity of other libs ?).

 Thanks for you answer !

 Best Regards / Cordialement,
 Fabrice BELLINGARD
 DINQ/DSIN/INSI/EATE/IDVS/AIDV
 (+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


 -
 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]




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

RE: [M2] single source tree - multiple artifacts - summary ofoptions

2005-11-08 Thread Ruel Loehr


What are the artifacts that you want to produce?

The first use case is as follows.

I have a single source tree from which 5 jars are produced.

Jboss-common.jar-   primary source jar
Jboss-common-client.jar   - a subset of the primary source jar
Namespace.jar - some javax/xml/namespace classes  (this could easily be
split out into a sub project)
Testsuite-support.jar  - logging junk
Jboss-archive-browsing.jar - a tiny tiny subset of primary source jar

The actual source structure can be seen here (our anoncvs is pretty slow
though):


We do support secondary or attached artifacts and an example of that is
creating an ejb client JAR along with the full ejb jar.

Exactly this.  Is there a guide or an example?   I am currently looking
at a multi-project example I pulled from a jira issue located here:

http://jira.codehaus.org/browse/ARCHETYPE-8



We also generally recommend decomposing your build in separate builds
if
you required multiple source trees. But I can't recommend anything
without knowing what you're trying to accomplish.

Agreed.  And this is the path I will pursue when necessary, but if there
is a way of creating the client jars, I want to check it out as well.

In a multi-proj setup how do I get a class from a common tree into the
jar of another sub proj?


 I realize that my #1 option is to split the tree (this is in fact that
 path I will pursue), but I also want to be able to defend my position
 and state something like, 
 
 I split the source tree due to the fact that there are no workarounds
 in maven2 for producing multiple artifacts from a single source tree.

 That's not entirely true. We frown up producing multiple primary
 artifacts for example trying to build both the client, server and
common
 code from a single build.

Again, if you could point me to an example, or maybe an area of code to
look at, that would help.   I'm happy to record my findings in a
tutorial doc.



 
 
 Ruel Loehr
 JBoss QA
  
 -
 512-626-2782
 Yahoo: ruelloehr
 Skype: ruelloehr
 AOL: dokoruel
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



-
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: [M2] single source tree - multiple artifacts - summary ofoptions

2005-11-08 Thread Ruel Loehr

Whoops.  Hit send too fast

Existing source tree can be seen here:

http://anoncvs.forge.jboss.com:8080/viewrep/JBoss/jboss-common/src

Ruel Loehr
JBoss QA
 
-
512-626-2782
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel

-Original Message-
From: Ruel Loehr 
Sent: Tuesday, November 08, 2005 9:36 AM
To: 'Maven Users List'
Subject: RE: [M2] single source tree - multiple artifacts - summary
ofoptions


What are the artifacts that you want to produce?

The first use case is as follows.

I have a single source tree from which 5 jars are produced.

Jboss-common.jar-   primary source jar
Jboss-common-client.jar   - a subset of the primary source jar
Namespace.jar - some javax/xml/namespace classes  (this could easily be
split out into a sub project)
Testsuite-support.jar  - logging junk
Jboss-archive-browsing.jar - a tiny tiny subset of primary source jar

The actual source structure can be seen here (our anoncvs is pretty slow
though):


We do support secondary or attached artifacts and an example of that is
creating an ejb client JAR along with the full ejb jar.

Exactly this.  Is there a guide or an example?   I am currently looking
at a multi-project example I pulled from a jira issue located here:

http://jira.codehaus.org/browse/ARCHETYPE-8



We also generally recommend decomposing your build in separate builds
if
you required multiple source trees. But I can't recommend anything
without knowing what you're trying to accomplish.

Agreed.  And this is the path I will pursue when necessary, but if there
is a way of creating the client jars, I want to check it out as well.

In a multi-proj setup how do I get a class from a common tree into the
jar of another sub proj?


 I realize that my #1 option is to split the tree (this is in fact that
 path I will pursue), but I also want to be able to defend my position
 and state something like, 
 
 I split the source tree due to the fact that there are no workarounds
 in maven2 for producing multiple artifacts from a single source tree.

 That's not entirely true. We frown up producing multiple primary
 artifacts for example trying to build both the client, server and
common
 code from a single build.

Again, if you could point me to an example, or maybe an area of code to
look at, that would help.   I'm happy to record my findings in a
tutorial doc.



 
 
 Ruel Loehr
 JBoss QA
  
 -
 512-626-2782
 Yahoo: ruelloehr
 Skype: ruelloehr
 AOL: dokoruel
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



-
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: M2 Getting started guide

2005-11-08 Thread Mordo, Aviran (EXP N-NANNATEK)

I have just started to evaluate Maven  myself, and was looking for this
information of how to setup multiple projects.

Aviran
http://www.aviransplace.com

-Original Message-
From: Pete [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 7:23 AM
To: Maven Users List
Subject: M2 Getting started guide

The M2 getting starting guide used to go on to explain how to set up a
parent project and child projects with a simple example (parent etc) ,
this seems to have gone completely from the guide.

I have this working myself, but was pointing others in the this
direction for information.

The mini guides have nothing on multi project.

-
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: M2 Getting started guide

2005-11-08 Thread scowx


Hi All

I am also looking for this information and I cannot find any guidance on the
correct structure for multiple projects.  This would be an extremely useful
guide.

regards

Stephen

Quoting Mordo, Aviran (EXP N-NANNATEK) [EMAIL PROTECTED]:


I have just started to evaluate Maven  myself, and was looking for this
information of how to setup multiple projects.

Aviran
http://www.aviransplace.com

-Original Message-
From: Pete [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 08, 2005 7:23 AM
To: Maven Users List
Subject: M2 Getting started guide

The M2 getting starting guide used to go on to explain how to set up a
parent project and child projects with a simple example (parent etc) ,
this seems to have gone completely from the guide.

I have this working myself, but was pointing others in the this
direction for information.

The mini guides have nothing on multi project.

-
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]







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

RE: M2 Getting started guide

On Tue, 2005-11-08 at 08:51 -0700, [EMAIL PROTECTED] wrote:
 Hi All
 
 I am also looking for this information and I cannot find any guidance on the
 correct structure for multiple projects.  This would be an extremely useful
 guide.

It's in JIRA, you can vote on it:

http://jira.codehaus.org/browse/MNG-1366

It's pretty high on the list.

 regards
 
 Stephen
 
 Quoting Mordo, Aviran (EXP N-NANNATEK) [EMAIL PROTECTED]:
 
  I have just started to evaluate Maven  myself, and was looking for this
  information of how to setup multiple projects.
 
  Aviran
  http://www.aviransplace.com
 
  -Original Message-
  From: Pete [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, November 08, 2005 7:23 AM
  To: Maven Users List
  Subject: M2 Getting started guide
 
  The M2 getting starting guide used to go on to explain how to set up a
  parent project and child projects with a simple example (parent etc) ,
  this seems to have gone completely from the guide.
 
  I have this working myself, but was pointing others in the this
  direction for information.
 
  The mini guides have nothing on multi project.
 
  -
  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]
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.

  -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)


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

RE: [M2] single source tree - multiple artifacts - summary ofoptions

On Tue, 2005-11-08 at 09:36 -0600, Ruel Loehr wrote:
 Whoops.  Hit send too fast

I created a JIRA issue for an ejb client guide. I'll see if I can get to
it later on today.

 Existing source tree can be seen here:
 
 http://anoncvs.forge.jboss.com:8080/viewrep/JBoss/jboss-common/src
 
 Ruel Loehr
 JBoss QA
  
 -
 512-626-2782
 Yahoo: ruelloehr
 Skype: ruelloehr
 AOL: dokoruel
 
 -Original Message-
 From: Ruel Loehr 
 Sent: Tuesday, November 08, 2005 9:36 AM
 To: 'Maven Users List'
 Subject: RE: [M2] single source tree - multiple artifacts - summary
 ofoptions
 
 
 What are the artifacts that you want to produce?
 
 The first use case is as follows.
 
 I have a single source tree from which 5 jars are produced.
 
 Jboss-common.jar-   primary source jar
 Jboss-common-client.jar   - a subset of the primary source jar
 Namespace.jar - some javax/xml/namespace classes  (this could easily be
 split out into a sub project)
 Testsuite-support.jar  - logging junk
 Jboss-archive-browsing.jar - a tiny tiny subset of primary source jar
 
 The actual source structure can be seen here (our anoncvs is pretty slow
 though):
 
 
 We do support secondary or attached artifacts and an example of that is
 creating an ejb client JAR along with the full ejb jar.
 
 Exactly this.  Is there a guide or an example?   I am currently looking
 at a multi-project example I pulled from a jira issue located here:
 
 http://jira.codehaus.org/browse/ARCHETYPE-8
 
 
 
 We also generally recommend decomposing your build in separate builds
 if
 you required multiple source trees. But I can't recommend anything
 without knowing what you're trying to accomplish.
 
 Agreed.  And this is the path I will pursue when necessary, but if there
 is a way of creating the client jars, I want to check it out as well.
 
 In a multi-proj setup how do I get a class from a common tree into the
 jar of another sub proj?
 
 
  I realize that my #1 option is to split the tree (this is in fact that
  path I will pursue), but I also want to be able to defend my position
  and state something like, 
  
  I split the source tree due to the fact that there are no workarounds
  in maven2 for producing multiple artifacts from a single source tree.
 
  That's not entirely true. We frown up producing multiple primary
  artifacts for example trying to build both the client, server and
 common
  code from a single build.
 
 Again, if you could point me to an example, or maybe an area of code to
 look at, that would help.   I'm happy to record my findings in a
 tutorial doc.
 
 
 
  
  
  Ruel Loehr
  JBoss QA
   
  -
  512-626-2782
  Yahoo: ruelloehr
  Skype: ruelloehr
  AOL: dokoruel
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
  
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



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

Re: [m2] How dependency versions are resolved with transitivity?

On 08/11/05, Jason van Zyl [EMAIL PROTECTED] wrote:
  As a side note, I really need the highest-wins strategy - any pointers
  to open issues or code required?

 It's slated for 2.1.

Right thanks.  Just found the issue if anyone's interested:

http://jira.codehaus.org/browse/MNG-612

And the code appears to be:

http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/ArtifactCollector.java?rev=279720view=markup
http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactCollector.java?rev=330201view=markup

Looks like a bit of work to implement another strategy.

Mark

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

(first maven 2 day) unable to download artifact

2005-11-08 Thread ir. ing. Jan Dockx

Just started working with maven 2. I've installed the binary 
installation of maven 2, and I'm trying to run


maven eclipse:eclipse

on the freshly checked-out maven 2 main trunk.


I get


[INFO] Failed to resolve artifact.

GroupId: org.apache.maven
ArtifactId: maven-model
Version: 2.0.1-SNAPSHOT

Reason: Unable to download the artifact from any repository
  org.apache.maven:maven-model:2.0.1-SNAPSHOT:jar

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)



Is this a temporary problem in the repo, or do I have a problem?





Met vriendelijke groeten,

Jan Dockx

PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66

PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25

http://www.peopleware.be/
http://www.mobileware.be/

Error on first maven

2005-11-08 Thread Giuseppe Picone

When I run Maven for th 1-st  time (no repository)

Condirmvn archetype:create -DgroupId=com.mycompany.app -DartifactI
d=my-app -e

I get the following error:


+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking for up
dates from central
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.pom
1K downloaded
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin
-parent/2.0-beta-1/maven-plugin-parent-2.0-beta-1.pom
6K downloaded
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.jar
6K downloaded
[INFO] -
---
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:create] (aggregator-style)
[INFO] -
---
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-archetype-core
/1.0-alpha-3/maven-archetype-core-1.0-alpha-3.pom
1K downloaded
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-archetype/1.0-
alpha-3/maven-archetype-1.0-alpha-3.pom
661b downloaded
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/2.0-beta-1/mav
en-2.0-beta-1.pom
6K downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.3/plexus-util
s-1.0.3.pom
970b downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-root/1.0.3/plexus-root-
1.0.3.pom
6K downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-container-default/1.0-a
lpha-6/plexus-container-default-1.0-alpha-6.pom
916b downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-containers/1.0.2/plexus
-containers-1.0.2.pom
488b downloaded
Downloading: http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/c
lassworlds-1.1-alpha-2.pom
3K downloaded
Downloading: http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom
145b downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-util
s-1.0.2.pom
740b downloaded
Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0-beta
-1/maven-model-2.0-beta-1.pom
1K downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-velocity/1.0/plexus-vel
ocity-1.0.pom
943b downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-components/1.0/plexus-c
omponents-1.0.pom
1K downloaded
Downloading: http://repo1.maven.org/maven2/plexus/plexus-root/1.0/plexus-root-1.
0.pom
4K downloaded
Downloading: http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.2
/commons-logging-1.0.2.pom
745b downloaded
Downloading: http://repo1.maven.org/maven2/logkit/logkit/1.0.1/logkit-1.0.1.pom
147b downloaded
Downloading: http://repo1.maven.org/maven2/log4j/log4j/1.1.3/log4j-1.1.3.pom
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Error building POM (may not be this project's POM).


Project ID: log4j:log4j

Reason: Error getting POM for 'log4j:log4j' from the repository: Error transferr
ing file
  log4j:log4j:1.1.3:pom

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)



[INFO] -
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency
 information: Unable to read the metadata file for artifact 'log4j:log4j:jar': E
rror getting POM for 'log4j:log4j' from the repository: Error transferring file
  log4j:log4j:1.1.3:pom

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)

  log4j:log4j:1.1.3:jar

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)
Path to dependency:
1) org.apache.maven.plugins:maven-archetype-plugin:maven-plugin:1.0-alph
a-3
2) org.apache.maven:maven-archetype-core:jar:1.0-alpha-3
3) plexus:plexus-velocity:jar:1.0
4) commons-logging:commons-logging:jar:1.0.2


at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:536)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau

Re: [m2] How dependency versions are resolved with transitivity?

Hi Fabrice,

On 08/11/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
 Hi Mark,

 Thank you for your answer! :)

No probs.

 Then I have another question: when 2 different dependency versions are at
 the same level in the dependency tree, which one wins? Because in my case,
 I have version 2.0 and version 1.0.1 of commons-lang at the same level, and
 1.0.1 wins.

Not sure, I know I have had problems with this before.  I currently
fix these uncertainties with an overriding dependency version in my
top-level pom, but agree that's nasty.  Have a look through the
DefaultArtifactCollector code (see the link in my previous reply) and
see if you can deduce what it does.

 The highest-win strategy would be interesting, I agree.

I would like to look into implementing this before 2.1 if I can find
the time (probably not then ;).

Cheers,

Mark

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

Re: [m2] parent's relativePath





I understand that artifactId and groupId are still required. But when I try
using relativePath (and therefore removes the version element), Maven
tells me that the version element of parent element is missing... Is it the
default behaviour or I'm missing something?

Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


   
 Brett Porter  
 [EMAIL PROTECTED]  
 ail.com Pour
   Maven Users List
 07/11/2005 03:36  users@maven.apache.org
cc
   
 VeuillezObjet
répondre à Re: [m2] parent's relativePath
 Maven Users List  
 [EMAIL PROTECTED]  
 che.org  
   
   
   




The docs on relativePath are lacking, and it really makes it quite
deceptive. It is not extend from m1.

What it does is modifies the behaviour of dan's first point.
Basically, we have a concept of a universal source directory (more
generally, a workspace) that is partially implemented - it means that
even without the reactor or the local repository, Maven is able to
find the source code for a particular dependency/parent reference so
that you can more easily develop new versions.

The default location for the parent is ../pom.xml, relativePath allows
you to select a different location, for example when you structure is
flat, or deeper without an intermediate parent pom.

However, the group and artifact ID is still required as when the
parent is coming from the repository, it must look for the parent in
the repository, and so on. This feature is only for enhancing the
development in a local checkout of that project.

Hope that helps

On 11/7/05, Jeff Jensen [EMAIL PROTECTED] wrote:
 Brett,

 Based on your comment of MNG-624 on 11/6/05 7:56 pm, I'm either not using
 relativePath correctly, or can't/not supposed to at all.

 So is there a way to do what I tried below, or must the parent POM be in
the
 repo?  Does MNG-740 have any merit?

 Are there doc/clarification notes on relativePath and I just missed it?


 -Original Message-
 From: Jeff Jensen [mailto:[EMAIL PROTECTED]
 Sent: Sunday, November 06, 2005 8:08 AM
 To: 'Maven Users List'
 Subject: RE: [m2] parent's relativePath

 Thanks Dan,

 My problem seems similar/same as your MNG-740.  I too have the parent pom
 not in a dir directly above the other components, but in a dir at the
same
 level as the other components.

 In MNG-740, A doesn't build for me without the listed step 1: install
root
 POM.  The relativePath setting seems to have no effect.  I do not
receive
 an error message that the parent was not found either.

 I'll add my use case to the comments.  Thanks again Dan.


 -Original Message-
 From: dan tran [mailto:[EMAIL PROTECTED]
 Sent: Saturday, November 05, 2005 11:52 PM
 To: Maven Users List
 Subject: Re: [m2] parent's relativePath

 Normally, maven looks for parent pom with this order
   immeditate parent directory
  local repo
  remote repo
  So the parent pom.xml in parent dir, must have the groupID and artifacID
 found in child pom  But there is a bug that may be your problem too
 http://jira.codehaus.org/browse/MNG-740
  -D


  On 11/5/05, Jeff Jensen [EMAIL PROTECTED] wrote:
 
  Hi,
 
  In parent, how does one use relativePath? I can only get POM
  inheritance to work if I have done a mvn install on the parent
project.
  Then the component projects find it in the local private repo.
 
  I'm sure I just don't understand something yet. If there is docs on
  it, please give me an RTFM link! TIA


 -
 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]




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

[m2] Surefire report plugin exception

Hi,

after running mvn -U clean site:site site:deploy

I go the following error:


[INFO] Generate Maven Surefire Report report.
java.lang.NumberFormatException: For input string: 0,157
at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224)
at java.lang.Float.parseFloat(Float.java:394)
at org.codehaus.mojo.surefire.ReportTestSuite.startElement(
ReportTestSuite.java:78)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement
(AbstractSAXParser.java:533)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(
XMLDTDValidator.java:798)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement
(XMLDocumentFragmentScannerImpl.java:878)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook
(XMLDocumentScannerImpl.java:1157)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
(XMLDocumentFragmentScannerImpl.java:1794)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
(XMLDocumentFragmentScannerImpl.java:368)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
XML11Configuration.java:834)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java
:148)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
AbstractSAXParser.java:1242)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
at org.codehaus.mojo.surefire.ReportTestSuite.init(ReportTestSuite.java
:59)
at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(
SurefireReportParser.java:42)
at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
SurefireReportGenerator.java:44)
at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
SurefireReportMojo.java:77)
at org.apache.maven.reporting.AbstractMavenReport.generate(
AbstractMavenReport.java:117)
at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java
:802)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:399)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:452)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:301)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:137)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
java.lang.NullPointerException
at
org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection
(SurefireReportGenerator.java:344)
at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
SurefireReportGenerator.java:60)
at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
SurefireReportMojo.java:77)
at org.apache.maven.reporting.AbstractMavenReport.generate(
AbstractMavenReport.java:117)
at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java
:802)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:399)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:452)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:301)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
at

Re: Guide to creating archetypes

On 11/8/05, Jason van Zyl [EMAIL PROTECTED] wrote:
 On Tue, 2005-11-08 at 15:11 +0200, Anuerin Diaz wrote:
  maybe we can use http://wiki.apache.org/maven/ for a collaborative
  effort? there is no specific wiki site for maven2 but from what i can
  see that wiki is relatively unused by maven1.

 Anyone is welcome to use the wiki but we have a decent pattern started
 for the doco. People can help by adding to the FAQs, creating mini
 guides and creating introductory guides. If they are placed in JIRA they
 are usually processed pretty quickly. Full documents if they are new are
 preferred and patches for everything else are greatly appreciated.
 Patches get absorbed pretty quickly.

  finalized documents could then be promoted to the official site as the
  maintainers see fit. not everybody has ready access to the development
  branch so i guess there will be people who will benefit in this
  effort.

 Unfortunately we don't have a very good work flow in place for this
 right now and JIRA is your best bet at the moment.


the way i see it is we can use JIRA as the official promotion vehicle.
documentation could be refined in the wikis by user comments and
suggestions and if no more flaws are detected then it could be
submitted to JIRA for inclusion on the main site. the wiki can also be
a repository of bits and pieces that are not full-bodied enough to
warrant their own mini-guide (e.g. a listing of all properties that
could be accessed in maven) .

another advantage of this approach is that the the rough drafts can
aid users find their way. although the downside is if the draft is
very rough it could make learning something more difficult than it
seems.

just an idea. :)

ciao!


--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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

WAR

2005-11-08 Thread Rafael Silva

Hi,

First, thanks to Emmanuel Venisse, it's all right now with the CVS. Now 
I'd like to know if has any way to use the continuum in my tomcat. Usually I 
take the war files of the projects and put at my webapps. But about the 
continuum, I didn't find any war file and none document about this. May someone 
help me with this?!

Thanks in advance,

Rafael Silva
[EMAIL PROTECTED]
Bolsista PIBIC

RE: Error on first maven

2005-11-08 Thread Sean Hennessy

Your browser probably was not wide enough to display the other command
line parameters..
mvn -e archetype:create \
-DgroupId=com.mycompany.app \
-DartifactId=my-app \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-site

(don't forget to cd to my-app before attempting mvn site )

-Original Message-
From: Giuseppe Picone [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 7:41 AM
To: users@maven.apache.org
Subject: Error on first maven


When I run Maven for th 1-st  time (no repository)

Condirmvn archetype:create -DgroupId=com.mycompany.app -DartifactI
d=my-app -e

I get the following error:


+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'. [INFO]
org.apache.maven.plugins: checking for updates from central [INFO]
org.codehaus.mojo: checking for updates from central [INFO] artifact
org.apache.maven.plugins:maven-archetype-plugin: checking for up dates
from central
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin
-parent/2.0-beta-1/maven-plugin-parent-2.0-beta-1.pom
6K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
ype-plugin/1.0-alpha-3/maven-archetype-plugin-1.0-alpha-3.jar
6K downloaded
[INFO]

-
---
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:create] (aggregator-style)
[INFO]

-
---
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-archetype-core
/1.0-alpha-3/maven-archetype-core-1.0-alpha-3.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-archetype/1.0-
alpha-3/maven-archetype-1.0-alpha-3.pom
661b downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven/2.0-beta-1/mav
en-2.0-beta-1.pom
6K downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.3/plexus-util
s-1.0.3.pom
970b downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-root/1.0.3/plexus-root-
1.0.3.pom
6K downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-container-default/1.0-a
lpha-6/plexus-container-default-1.0-alpha-6.pom
916b downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-containers/1.0.2/plexus
-containers-1.0.2.pom
488b downloaded
Downloading:
http://repo1.maven.org/maven2/classworlds/classworlds/1.1-alpha-2/c
lassworlds-1.1-alpha-2.pom
3K downloaded
Downloading:
http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom
145b downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-utils/1.0.2/plexus-util
s-1.0.2.pom
740b downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0-beta
-1/maven-model-2.0-beta-1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-velocity/1.0/plexus-vel
ocity-1.0.pom
943b downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-components/1.0/plexus-c
omponents-1.0.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/plexus/plexus-root/1.0/plexus-root-1.
0.pom
4K downloaded
Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.2
/commons-logging-1.0.2.pom
745b downloaded
Downloading:
http://repo1.maven.org/maven2/logkit/logkit/1.0.1/logkit-1.0.1.pom
147b downloaded
Downloading:
http://repo1.maven.org/maven2/log4j/log4j/1.1.3/log4j-1.1.3.pom
[INFO]

-
---
[ERROR] BUILD ERROR
[INFO]

-
---
[INFO] Error building POM (may not be this project's POM).


Project ID: log4j:log4j

Reason: Error getting POM for 'log4j:log4j' from the repository: Error
transferr ing file
  log4j:log4j:1.1.3:pom

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)



[INFO]

-
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get
dependency
 information: Unable to read the metadata file for artifact
'log4j:log4j:jar': E rror getting POM for 'log4j:log4j' from the
repository: Error transferring file
  log4j:log4j:1.1.3:pom

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)

  log4j:log4j:1.1.3:jar

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  snapshots (http://snapshots.maven.codehaus.org/maven2)
Path to dependency:
1)

Re: (first maven 2 day) unable to download artifact

On Tue, 2005-11-08 at 16:57 +0100, ir. ing. Jan Dockx wrote:
 Just started working with maven 2. I've installed the binary 
 installation of maven 2, and I'm trying to run
 
 maven eclipse:eclipse
 
 on the freshly checked-out maven 2 main trunk.

If you are using trunk then you need to bootstrap. I recommend using the
standard distribution but if you want to live on the edge:

http://maven.apache.org/guides/development/guide-building-m2.html

 
 I get
 
 
 [INFO] Failed to resolve artifact.
 
 GroupId: org.apache.maven
 ArtifactId: maven-model
 Version: 2.0.1-SNAPSHOT
 
 Reason: Unable to download the artifact from any repository
org.apache.maven:maven-model:2.0.1-SNAPSHOT:jar
 
 from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
 
 
 
 Is this a temporary problem in the repo, or do I have a problem?
 
 
 
 
 
 Met vriendelijke groeten,
 
 Jan Dockx
 
 PeopleWare NV - Head Office
 Cdt.Weynsstraat 85
 B-2660 Hoboken
 Tel: +32 3 448.33.38
 Fax: +32 3 448.32.66
 
 PeopleWare NV - Branch Office Geel
 Kleinhoefstraat 5
 B-2440 Geel
 Tel: +32 14 57.00.90
 Fax: +32 14 58.13.25
 
 http://www.peopleware.be/
 http://www.mobileware.be/
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



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

Re: Guide to creating archetypes

2005/11/8, Jason van Zyl [EMAIL PROTECTED]:

 On Tue, 2005-11-08 at 13:53 +0100, Alexander Hars wrote:
  Hi,
 
  Two weeks ago I wrote a significantly expanded Guide to Creating
  Archetypes. It was immediately posted to CVS, but it is still not
  available on the website.

 http://maven.apache.org/guides/mini/guide-creating-archetypes.html

 Is that not it?


What I miss there is what archetype.xml contains in the META-INF directory.
That does not seem to get explained.

regards,

Wim

[m2] assembly:directory requires an install?

hi,

   does the assembly:directory goal really need the project's
sub-module artifacts to be installed in the local repository before it
will assemble them? i am a little confused becase a couple of days ago
i dont remember needing to install the sub-module artifacts prior to
calling the assembly:directory goal.

my project has a parent project that defines two sub-modules in
its modules element. module2 depends on module1. my assembly call now
fails when trying to package module2 because it couldn't  resolve
my.app:module1:1.0:jar. invoking mvn package does not produce any
problem. while mvn install assembly:directory will work, i am
putting this as a last resort because this might  have some
implication on our version management.

thanks.

ciao!

--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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

Re: (first maven 2 day) unable to download artifact

2005-11-08 Thread ir. ing. Jan Dockx


Thanks for the apt ( ;-) ) response.

I already got it built, that's not the issue. I then removed ~/.m2, did 
a clean install of the bin distro, and tried that installation on the 
clean trunk project.


This is just a request to get my facts straight (I'll be knee deep in 
here over the next few weeks):



Is it correct that this fails because:
there is actually no org.apache.maven:maven-model:2.0.1-SNAPSHOT:jar on 
any repository -- this artifact-version is only available when you 
build the trunk yourself?


So, as a consequence, you can cannot use the 2.0 bin distro on the 
current trunk itself?




On 8 Nov 2005, at 17:15, Jason van Zyl wrote:


On Tue, 2005-11-08 at 16:57 +0100, ir. ing. Jan Dockx wrote:

Just started working with maven 2. I've installed the binary
installation of maven 2, and I'm trying to run

maven eclipse:eclipse

on the freshly checked-out maven 2 main trunk.


If you are using trunk then you need to bootstrap. I recommend using 
the

standard distribution but if you want to live on the edge:

http://maven.apache.org/guides/development/guide-building-m2.html



I get


[INFO] Failed to resolve artifact.

GroupId: org.apache.maven
ArtifactId: maven-model
Version: 2.0.1-SNAPSHOT

Reason: Unable to download the artifact from any repository
   org.apache.maven:maven-model:2.0.1-SNAPSHOT:jar

from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   snapshots (http://snapshots.maven.codehaus.org/maven2)



Is this a temporary problem in the repo, or do I have a problem?





Met vriendelijke groeten,

Jan Dockx

PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66

PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25

http://www.peopleware.be/
http://www.mobileware.be/

--
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org



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



Met vriendelijke groeten,

Jan Dockx

PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66

PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25

http://www.peopleware.be/
http://www.mobileware.be/

Re: (first maven 2 day) unable to download artifact

On Tue, 2005-11-08 at 17:48 +0100, ir. ing. Jan Dockx wrote:
 Thanks for the apt ( ;-) ) response.
 
 I already got it built, that's not the issue. I then removed ~/.m2, did 
 a clean install of the bin distro, and tried that installation on the 
 clean trunk project.

Then you just wiped out the repository where the POMs were installed as
part of the bootstrap. Why did you remove ~/.m2 ?

If you are going to use trunk, you must bootstrap. That places the POMs
in your local repository.

Using the binary distro will use POMs we have released and are available
in the central repository.

 So, as a consequence, you can cannot use the 2.0 bin distro on the 
 current trunk itself?

Not generally recommended. I've never actually done it to be honest. I
usually bootstrap a couple times a day.

-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

  -- Ralph Johnson  Don Roberts, Patterns for Evolving Frameworks 


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

[m2] Adding goals to execution

2005-11-08 Thread David Jackman

Here's what I'd like to do:  For our product, we have a number of Maven
projects, most of which are simple Java jar projects, but others are
not.  For these jar projects, I'd like the javadoc:jar and source:jar
goals to execute as well.  I'd like this to be as automatic as possible
for projects (i.e. define this in one central place without requiring
individual projects to do anything explicit).
 
As far as I know, there are three ways to accomplish this.  First would
be to add the plugins to the pom.xml for each project.  This works, but
requires adding them to each project, defeating my goal to only define
it in one place.
 
The next way to do this would be to add the plugins to the parent
pom.xml.  I can put the information into the pluginManagement section of
the parent, but this still requires that each project's pom contain a
reference to the plugin, which I'd rather not do.  The other option is
to put the information in the parent's build-plugins.  This actually
does seem to work (the subproject picks it up automatically), but has a
an unpleasant side effect in that these goals are run for all of the
non-jar type projects as well as the jar type projects.  Looking a bit
closer, it seems the javadoc:javadoc and source:jar goals are saying
they won't execute because the project isn't the right type, but the
javadoc:jar goal runs anyway, creating a javadoc jar with no actual
javadocs in it.  Maybe this is just a bug and I should report/patch it.
 
The third way to do this would be to add the plugins to a profile and
have the build pick it up there.  I'm not as well-versed with profiles,
so I may be missing something here.  But from what I know, for this to
work I'd have to specify the profile whenever I build (unless it's the
default) and make sure all of the developers have the correct settings
for their profile definition (or I suppose I can put the profile
definition into the parent pom, but I'm not sure how that works).  I
don't think it actually buys me anything to list the plugins in a
profile, though (i.e. it doesn't work any better than listing the
plugins directly in the parent pom).
 
Anyway, is there a recommended methodology for doing this sort of thing?
Is there something I'm missing that I should be taking advantage of?
 
Thanks,
..David..

Re: [m2] Surefire report plugin exception

2005-11-08 Thread Eduardo Rocha

Hi Wim,

It is a known bug, it was already reported and fixed:

http://jira.codehaus.org/browse/MOJO-100?page=all

[]'s
Eduardo

2005/11/8, Wim Deblauwe [EMAIL PROTECTED]:
 Hi,

 after running mvn -U clean site:site site:deploy

 I go the following error:


 [INFO] Generate Maven Surefire Report report.
 java.lang.NumberFormatException: For input string: 0,157
 at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1224)
 at java.lang.Float.parseFloat(Float.java:394)
 at org.codehaus.mojo.surefire.ReportTestSuite.startElement(
 ReportTestSuite.java:78)
 at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement
 (AbstractSAXParser.java:533)
 at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(
 XMLDTDValidator.java:798)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement
 (XMLDocumentFragmentScannerImpl.java:878)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook
 (XMLDocumentScannerImpl.java:1157)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
 (XMLDocumentFragmentScannerImpl.java:1794)
 at
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
 (XMLDocumentFragmentScannerImpl.java:368)
 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
 XML11Configuration.java:834)
 at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
 XML11Configuration.java:764)
 at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java
 :148)
 at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
 AbstractSAXParser.java:1242)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
 at org.codehaus.mojo.surefire.ReportTestSuite.init(ReportTestSuite.java
 :59)
 at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(
 SurefireReportParser.java:42)
 at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
 SurefireReportGenerator.java:44)
 at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
 SurefireReportMojo.java:77)
 at org.apache.maven.reporting.AbstractMavenReport.generate(
 AbstractMavenReport.java:117)
 at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java
 :802)
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:399)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:519)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
 (DefaultLifecycleExecutor.java:482)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
 DefaultLifecycleExecutor.java:452)
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
 (DefaultLifecycleExecutor.java:301)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
 DefaultLifecycleExecutor.java:268)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
 DefaultLifecycleExecutor.java:137)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
 :39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 java.lang.NullPointerException
 at
 org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection
 (SurefireReportGenerator.java:344)
 at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
 SurefireReportGenerator.java:60)
 at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
 SurefireReportMojo.java:77)
 at org.apache.maven.reporting.AbstractMavenReport.generate(
 AbstractMavenReport.java:117)
 at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java
 :802)
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
 at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
 DefaultPluginManager.java:399)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
 DefaultLifecycleExecutor.java:519)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
 (DefaultLifecycleExecutor.java:482)
 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(

[m2] Surefire questions


Hey everyone,

I'm trying to move a maven 1 project to maven 2.  All the dependencies 
look like they're working fine now, and I'm able to build and run the 
tests. 

When running the tests, there is a quite a bit of output going to 
stdout, such as Hibernate query statements.  In maven 1 I used the 
properties


||maven.junit.fork=true
maven.junit.dir=${maven.build.dir}/test

to do a couple of things.  Forking the process would make the stdout go 
into the .txt reports.  Setting the directory it's run in would make it 
so any log files created during the test runs, such as the p6spy and the 
log4j logs, would be put in the test directory rather than the root 
project directory.  To make this work I also had to have a preGoal in my 
maven.xml file for test:prepare-filesystem to create that test directory 
before the tests were run.


I'm wondering how I can accomplish the same thing, or at least something 
similar, with m2.  Any ideas?


Thanks,
Rich

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

Re: [m2] Surefire questions


A couple of other questions about differences from m1.

In m2 it seems that the test message output is being buffered and not 
displayed until all tests have been run.  Is there a way to change that?


In m1 I could tell maven to only run tests matching a certain criteria 
with something like maven -Dtestmatch=Object* test:match.  Is this 
possible right now, and if not is it planned for the future?  If so, when?


Thanks again,
Rich

Richard Wallace wrote:

Hey everyone,

I'm trying to move a maven 1 project to maven 2.  All the dependencies 
look like they're working fine now, and I'm able to build and run the 
tests.
When running the tests, there is a quite a bit of output going to 
stdout, such as Hibernate query statements.  In maven 1 I used the 
properties


||maven.junit.fork=true
maven.junit.dir=${maven.build.dir}/test

to do a couple of things.  Forking the process would make the stdout 
go into the .txt reports.  Setting the directory it's run in would 
make it so any log files created during the test runs, such as the 
p6spy and the log4j logs, would be put in the test directory rather 
than the root project directory.  To make this work I also had to have 
a preGoal in my maven.xml file for test:prepare-filesystem to create 
that test directory before the tests were run.


I'm wondering how I can accomplish the same thing, or at least 
something similar, with m2.  Any ideas?


Thanks,
Rich

-
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: [m2] Adding goals to execution

On Tue, 2005-11-08 at 10:02 -0700, David Jackman wrote:
 Here's what I'd like to do:  For our product, we have a number of Maven
 projects, most of which are simple Java jar projects, but others are
 not.  For these jar projects, I'd like the javadoc:jar and source:jar
 goals to execute as well.  I'd like this to be as automatic as possible
 for projects (i.e. define this in one central place without requiring
 individual projects to do anything explicit).
  
 As far as I know, there are three ways to accomplish this.  First would
 be to add the plugins to the pom.xml for each project.  This works, but
 requires adding them to each project, defeating my goal to only define
 it in one place.
  
 The next way to do this would be to add the plugins to the parent
 pom.xml.  I can put the information into the pluginManagement section of
 the parent, but this still requires that each project's pom contain a
 reference to the plugin, which I'd rather not do.  The other option is
 to put the information in the parent's build-plugins.  This actually
 does seem to work (the subproject picks it up automatically), but has a
 an unpleasant side effect in that these goals are run for all of the
 non-jar type projects as well as the jar type projects.  Looking a bit
 closer, it seems the javadoc:javadoc and source:jar goals are saying
 they won't execute because the project isn't the right type, but the
 javadoc:jar goal runs anyway, creating a javadoc jar with no actual
 javadocs in it.  Maybe this is just a bug and I should report/patch it.
  
 The third way to do this would be to add the plugins to a profile and
 have the build pick it up there.  I'm not as well-versed with profiles,
 so I may be missing something here.  But from what I know, for this to
 work I'd have to specify the profile whenever I build (unless it's the
 default) and make sure all of the developers have the correct settings
 for their profile definition (or I suppose I can put the profile
 definition into the parent pom, but I'm not sure how that works).  I
 don't think it actually buys me anything to list the plugins in a
 profile, though (i.e. it doesn't work any better than listing the
 plugins directly in the parent pom).
  
 Anyway, is there a recommended methodology for doing this sort of thing?
 Is there something I'm missing that I should be taking advantage of?

I'm doing a bunch of stuff so I created a place holder:

http://jira.codehaus.org/browse/MNG-1463

Chris Berry had a post a while back, IIRC, which showed how he did it.

You might want to comment there for the time being. Starting next week
I'm going to try and tack that list of best practices by posting the
lists, adding material to the wiki and trying to get some closure.

 Thanks,
 ..David..
  
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


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

Re: [m2] Surefire questions

On Tue, 2005-11-08 at 10:25 -0700, Richard Wallace wrote:
 A couple of other questions about differences from m1.
 
 In m2 it seems that the test message output is being buffered and not 
 displayed until all tests have been run.  Is there a way to change that?
 
 In m1 I could tell maven to only run tests matching a certain criteria 
 with something like maven -Dtestmatch=Object* test:match.  Is this 
 possible right now, and if not is it planned for the future?  If so, when?

mvn -Dtest=*FooTest test

 Thanks again,
 Rich
 
 Richard Wallace wrote:
  Hey everyone,
 
  I'm trying to move a maven 1 project to maven 2.  All the dependencies 
  look like they're working fine now, and I'm able to build and run the 
  tests.
  When running the tests, there is a quite a bit of output going to 
  stdout, such as Hibernate query statements.  In maven 1 I used the 
  properties
 
  ||maven.junit.fork=true
  maven.junit.dir=${maven.build.dir}/test
 
  to do a couple of things.  Forking the process would make the stdout 
  go into the .txt reports.  Setting the directory it's run in would 
  make it so any log files created during the test runs, such as the 
  p6spy and the log4j logs, would be put in the test directory rather 
  than the root project directory.  To make this work I also had to have 
  a preGoal in my maven.xml file for test:prepare-filesystem to create 
  that test directory before the tests were run.
 
  I'm wondering how I can accomplish the same thing, or at least 
  something similar, with m2.  Any ideas?
 
  Thanks,
  Rich
 
  -
  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
jason at maven.org
http://maven.apache.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: WAR

2005-11-08 Thread Emmanuel Venisse


It isn't possible for the moment to use continuum as a war. We'll try to do it 
for 1.1

Emmanuel

Rafael Silva a écrit :

Hi,

First, thanks to Emmanuel Venisse, it's all right now with the CVS. Now I'd like 
to know if has any way to use the continuum in my tomcat. Usually I take the 
war files of the projects and put at my webapps. But about the continuum, I 
didn't find any war file and none document about this. May someone help me with this?!

Thanks in advance,

Rafael Silva
[EMAIL PROTECTED]
Bolsista PIBIC

Re: [m102] bad results when including custom.css

2005-11-08 Thread Lukas Theussl

Thomas,

I'm a bit confused by your message, you are describing exactly what I
wrote in my previous reply (custom.css - project.css), this is also
prominently documented on the xdoc plugin homepage [1]. Anyway, it seems
that you got it right now.

On a side note, you might be interested in
http://jira.codehaus.org/browse/MPXDOC-80
This has been implemented in the current 1.10-SNAPSHOT version of the
xdoc plugin, I suppose this is just what you originally expected.

Cheers,
Lukas

[1] http://maven.apache.org/maven-1.x/reference/plugins/xdoc/

[EMAIL PROTECTED] wrote:

hi Lukas,

Thank you for responding with help.

However, I was not able to get ${basedir}/xdocs/style/custom.css to work.

The rendered html did not use my css, and when I viewed the html source,
it was not importing custom.css

I put the file everywhere in my project. The xdoc plugin *did* copy it to
the output folders, but it was never used.

I finally google'd on maven.xdoc.theme.url and found a jira reference at
http://jira.codehaus.org/browse/MPXDOC-85 that mentioned just using
the name project.css for a custom stylesheets file.

That *does* work. ${basedir}/xdocs/style/project.css is picked up
by xdoc, the html imports it, and my stylesheet is used.

Maybe I was doing something else wrong, and maybe this works because
of some other change I made, but at least it works and I'm not touching
the project.

Thanks again for your help.

Tom

Lukas Theussl
[EMAIL PROTECTED]
org To
Maven Users List
11/04/2005 06:45 users@maven.apache.org
PM cc

Subject
Please respond to Re: [m102] bad results when
Maven Usersincluding custom.css
List
[EMAIL PROTECTED]
he.org

Hi Thomas,

The maven.xdoc.theme.url property only works as an absolute URL (the
documentation on this has recently been updated), what you want is a
project.css file in xdocs/style/, this will automatically be picked up.

HTH,
-Lukas

[EMAIL PROTECTED] wrote:

hello,

I put a custom.css file under xdocs/style and added

maven.xdoc.theme.url

=./style/custom.css
to project.properties

The m1 doc says ...a css file that can be used in addition to
maven-base.css

However, when the site is generated, the pages do not look like a

standard

maven
project page.

it looks like none of the standard maven css files are being used or

found.

Do I need to specify anything else to make all the maven css files
available?

Thanks
Tom

This message is intended for the recipient only and is not meant to be

forwarded or distributed in any other format. This communication is for
informational purposes only. It is not intended as an offer or
solicitation for the purchase or sale of any financial instrument, or
security, or as an official confirmation of any transaction. Putnam does
not accept purchase or redemptions of securities, instructions, or
authorizations that are sent via e-mail. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments)
and its subsidiaries and affiliates. If you are not the intended recipient
of this e-mail, please delete the e-mail.

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

This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any

Re: [m102] bad results when including custom.css

2005-11-08 Thread Thomas_Perry







Lukas, my fault, I did not read your response thoroughly.

You had the correction right.  It would have saved me some time
had I *carefully* read your response.

Thank you again for your help.  and a big  d'oh for me.

Tom



   
 Lukas Theussl 
 [EMAIL PROTECTED] 
 org   To 
   Maven Users List
 11/08/2005 12:45  users@maven.apache.org
 PM cc 
   
   Subject 
 Please respond to Re: [m102] bad results when 
   Maven Usersincluding custom.css
   List   
 [EMAIL PROTECTED] 
  he.org  
   
   
   




Thomas,

I'm a bit confused by your message, you are describing exactly what I
wrote in my previous reply (custom.css - project.css), this is also
prominently documented on the xdoc plugin homepage [1]. Anyway, it seems
that you got it right now.

On a side note, you might be interested in
http://jira.codehaus.org/browse/MPXDOC-80
This has been implemented in the current 1.10-SNAPSHOT version of the
xdoc plugin, I suppose this is just what you originally expected.

Cheers,
Lukas


[1] http://maven.apache.org/maven-1.x/reference/plugins/xdoc/



[EMAIL PROTECTED] wrote:





 hi Lukas,

 Thank you for responding with help.

 However, I was not able to get  ${basedir}/xdocs/style/custom.css to
work.

 The rendered html did not use my css, and when I viewed the html source,
 it was not importing custom.css

 I put the file everywhere in my project.  The xdoc plugin *did* copy it
to
 the output folders, but it was never used.

 I finally google'd on   maven.xdoc.theme.url  and found a jira reference
at
 http://jira.codehaus.org/browse/MPXDOC-85  that mentioned just using
 the name project.css for a custom stylesheets file.

 That *does* work.   ${basedir}/xdocs/style/project.css   is picked up
 by xdoc, the html imports it, and my stylesheet is used.

 Maybe I was doing something else wrong, and maybe this works because
 of some other change I made, but at least it works and I'm not touching
 the project.

 Thanks again for your help.

 Tom





  Lukas Theussl

  [EMAIL PROTECTED]

  org
To
Maven Users List

  11/04/2005 06:45  users@maven.apache.org

  PM
cc



Subject
  Please respond to Re: [m102] bad results when

Maven Usersincluding custom.css

List

  [EMAIL PROTECTED]

   he.org











 Hi Thomas,

 The maven.xdoc.theme.url property only works as an absolute URL (the
 documentation on this has recently been updated), what you want is a
 project.css file in xdocs/style/, this will automatically be picked up.

 HTH,
 -Lukas


 [EMAIL PROTECTED] wrote:




hello,

I put a custom.css file under xdocs/style  and added

 maven.xdoc.theme.url

=./style/custom.css
to project.properties

The m1 doc says ...a css file that can be used in addition to
maven-base.css

However, when the site is generated, the pages do not look like a

 standard

maven
project page.

it looks like none of the standard maven css files are being used or

 found.

Do I need to specify anything else to make all the maven css files
available?

Thanks
Tom




This message is intended for the recipient only and is not meant to be

 forwarded or distributed in any other format. This communication is for
 informational purposes only.  It is not intended as an offer or
 solicitation for the purchase or sale of any financial instrument, or
 security, or as an official confirmation of any transaction.  Putnam does
 not accept purchase or redemptions of securities, instructions, or
 authorizations that are sent via e-mail.   All market prices, data and
 other information are not warranted as to completeness or accuracy and
are
 subject to change without notice.  Any comments or statements made herein
 do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments)
 and its subsidiaries and affiliates.  If you are not the intended
recipient

SNAPSHOT replacement

2005-11-08 Thread Duane Homick

Is there a way to have SNAPSHOT just be replaced by the build number and not by 
the date-build number?  Can I control the formatting as well?  (ie. use _ 
instead of -)

Thanks
Duane Homick
Software Engineer
Sandvine Inc.

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

Re: [m2] Adding goals to execution

2005-11-08 Thread John Casey


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'd say that the javadoc:jar mojo needs to detect its environment just
as the javadoc:javadoc mojo does. That's a bug IMO.

FWIW,

john

David Jackman wrote:
| Here's what I'd like to do:  For our product, we have a number of Maven
| projects, most of which are simple Java jar projects, but others are
| not.  For these jar projects, I'd like the javadoc:jar and source:jar
| goals to execute as well.  I'd like this to be as automatic as possible
| for projects (i.e. define this in one central place without requiring
| individual projects to do anything explicit).
|
| As far as I know, there are three ways to accomplish this.  First would
| be to add the plugins to the pom.xml for each project.  This works, but
| requires adding them to each project, defeating my goal to only define
| it in one place.
|
| The next way to do this would be to add the plugins to the parent
| pom.xml.  I can put the information into the pluginManagement section of
| the parent, but this still requires that each project's pom contain a
| reference to the plugin, which I'd rather not do.  The other option is
| to put the information in the parent's build-plugins.  This actually
| does seem to work (the subproject picks it up automatically), but has a
| an unpleasant side effect in that these goals are run for all of the
| non-jar type projects as well as the jar type projects.  Looking a bit
| closer, it seems the javadoc:javadoc and source:jar goals are saying
| they won't execute because the project isn't the right type, but the
| javadoc:jar goal runs anyway, creating a javadoc jar with no actual
| javadocs in it.  Maybe this is just a bug and I should report/patch it.
|
| The third way to do this would be to add the plugins to a profile and
| have the build pick it up there.  I'm not as well-versed with profiles,
| so I may be missing something here.  But from what I know, for this to
| work I'd have to specify the profile whenever I build (unless it's the
| default) and make sure all of the developers have the correct settings
| for their profile definition (or I suppose I can put the profile
| definition into the parent pom, but I'm not sure how that works).  I
| don't think it actually buys me anything to list the plugins in a
| profile, though (i.e. it doesn't work any better than listing the
| plugins directly in the parent pom).
|
| Anyway, is there a recommended methodology for doing this sort of thing?
| Is there something I'm missing that I should be taking advantage of?
|
| Thanks,
| ..David..
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDcPN+K3h2CZwO/4URAjkaAJ49pVI9amanJB//7IuQRoiHX7+0pACfVC7T
jSirjtPNkQJoLeZzmwFX2c4=
=V93w
-END PGP SIGNATURE-

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

Re: [m2] Surefire report plugin exception

ah, ok. Hopefully a new version containing this fix will be released soon,
because now I can't generate any site using Maven 2. I would like to be able
to continue my conversion from M1 to M2 as soon as possible.

thanks,

Wim

2005/11/8, Eduardo Rocha [EMAIL PROTECTED]:

 Hi Wim,

 It is a known bug, it was already reported and fixed:

 http://jira.codehaus.org/browse/MOJO-100?page=all

 []'s
 Eduardo

 2005/11/8, Wim Deblauwe [EMAIL PROTECTED]:
  Hi,
 
  after running mvn -U clean site:site site:deploy
 
  I go the following error:
 
 
  [INFO] Generate Maven Surefire Report report.
  java.lang.NumberFormatException: For input string: 0,157
  at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java
 :1224)
  at java.lang.Float.parseFloat(Float.java:394)
  at org.codehaus.mojo.surefire.ReportTestSuite.startElement(
  ReportTestSuite.java:78)
  at
 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement
  (AbstractSAXParser.java:533)
  at
 com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(
  XMLDTDValidator.java:798)
  at
 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement
  (XMLDocumentFragmentScannerImpl.java:878)
  at
 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook
  (XMLDocumentScannerImpl.java:1157)
  at
 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
  (XMLDocumentFragmentScannerImpl.java:1794)
  at
 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
  (XMLDocumentFragmentScannerImpl.java:368)
  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
  XML11Configuration.java:834)
  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
  XML11Configuration.java:764)
  at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(
 XMLParser.java
  :148)
  at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
  AbstractSAXParser.java:1242)
  at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
  at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
  at org.codehaus.mojo.surefire.ReportTestSuite.init(
 ReportTestSuite.java
  :59)
  at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(
  SurefireReportParser.java:42)
  at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
  SurefireReportGenerator.java:44)
  at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
  SurefireReportMojo.java:77)
  at org.apache.maven.reporting.AbstractMavenReport.generate(
  AbstractMavenReport.java:117)
  at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
 SiteMojo.java
  :802)
  at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
  at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
  DefaultPluginManager.java:399)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
  DefaultLifecycleExecutor.java:519)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
  (DefaultLifecycleExecutor.java:482)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
  DefaultLifecycleExecutor.java:452)
  at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
  (DefaultLifecycleExecutor.java:301)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
  DefaultLifecycleExecutor.java:268)
  at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
  DefaultLifecycleExecutor.java:137)
  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(
 NativeMethodAccessorImpl.java
  :39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:585)
  at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
  at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
  at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
  at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
  java.lang.NullPointerException
  at
 
 org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection
  (SurefireReportGenerator.java:344)
  at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
  SurefireReportGenerator.java:60)
  at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
  SurefireReportMojo.java:77)
  at org.apache.maven.reporting.AbstractMavenReport.generate(
  AbstractMavenReport.java:117)
  at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
 SiteMojo.java
  :802)
  at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)

Re: [m2] Surefire report plugin exception

2005-11-08 Thread Eduardo Rocha

You can checkout HEAD on CVS and build Maven as indicated in site :)

2005/11/8, Wim Deblauwe [EMAIL PROTECTED]:
 ah, ok. Hopefully a new version containing this fix will be released soon,
 because now I can't generate any site using Maven 2. I would like to be able
 to continue my conversion from M1 to M2 as soon as possible.

 thanks,

 Wim

 2005/11/8, Eduardo Rocha [EMAIL PROTECTED]:
 
  Hi Wim,
 
  It is a known bug, it was already reported and fixed:
 
  http://jira.codehaus.org/browse/MOJO-100?page=all
 
  []'s
  Eduardo
 
  2005/11/8, Wim Deblauwe [EMAIL PROTECTED]:
   Hi,
  
   after running mvn -U clean site:site site:deploy
  
   I go the following error:
  
  
   [INFO] Generate Maven Surefire Report report.
   java.lang.NumberFormatException: For input string: 0,157
   at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java
  :1224)
   at java.lang.Float.parseFloat(Float.java:394)
   at org.codehaus.mojo.surefire.ReportTestSuite.startElement(
   ReportTestSuite.java:78)
   at
  com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement
   (AbstractSAXParser.java:533)
   at
  com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(
   XMLDTDValidator.java:798)
   at
  
  com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement
   (XMLDocumentFragmentScannerImpl.java:878)
   at
  
  com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook
   (XMLDocumentScannerImpl.java:1157)
   at
  
  com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
   (XMLDocumentFragmentScannerImpl.java:1794)
   at
  
  com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument
   (XMLDocumentFragmentScannerImpl.java:368)
   at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
   XML11Configuration.java:834)
   at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(
   XML11Configuration.java:764)
   at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(
  XMLParser.java
   :148)
   at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(
   AbstractSAXParser.java:1242)
   at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
   at javax.xml.parsers.SAXParser.parse(SAXParser.java:311)
   at org.codehaus.mojo.surefire.ReportTestSuite.init(
  ReportTestSuite.java
   :59)
   at org.codehaus.mojo.surefire.SurefireReportParser.parseXMLReportFiles(
   SurefireReportParser.java:42)
   at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
   SurefireReportGenerator.java:44)
   at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
   SurefireReportMojo.java:77)
   at org.apache.maven.reporting.AbstractMavenReport.generate(
   AbstractMavenReport.java:117)
   at org.apache.maven.plugins.site.SiteMojo.generateReportsPages(
  SiteMojo.java
   :802)
   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:301)
   at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
   DefaultPluginManager.java:399)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
   DefaultLifecycleExecutor.java:519)
   at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal
   (DefaultLifecycleExecutor.java:482)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
   DefaultLifecycleExecutor.java:452)
   at
  
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
   (DefaultLifecycleExecutor.java:301)
   at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
   DefaultLifecycleExecutor.java:268)
   at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
   DefaultLifecycleExecutor.java:137)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
  NativeMethodAccessorImpl.java
   :39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
   DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
   java.lang.NullPointerException
   at
  
  org.codehaus.mojo.surefire.SurefireReportGenerator.constructTestCasesSection
   (SurefireReportGenerator.java:344)
   at org.codehaus.mojo.surefire.SurefireReportGenerator.doGenerateReport(
   SurefireReportGenerator.java:60)
   at org.codehaus.mojo.surefire.SurefireReportMojo.executeReport(
   SurefireReportMojo.java:77)
   at

Set my own properties

Is there a way to set properties in the pom and the settings.xml that
are available during execution? Something like path_to_file_x = c:\. The
intent is to have some properties that are defined in profiles that can
change behaviors defined in my poms.

Re: [m2] Adding goals to execution

I added the mail in the comments. I still had it in my gmail. hope it helps.

regards,

Wim

2005/11/8, Jason van Zyl [EMAIL PROTECTED]:

 On Tue, 2005-11-08 at 10:02 -0700, David Jackman wrote:
  Here's what I'd like to do: For our product, we have a number of Maven
  projects, most of which are simple Java jar projects, but others are
  not. For these jar projects, I'd like the javadoc:jar and source:jar
  goals to execute as well. I'd like this to be as automatic as possible
  for projects (i.e. define this in one central place without requiring
  individual projects to do anything explicit).
 
  As far as I know, there are three ways to accomplish this. First would
  be to add the plugins to the pom.xml for each project. This works, but
  requires adding them to each project, defeating my goal to only define
  it in one place.
 
  The next way to do this would be to add the plugins to the parent
  pom.xml. I can put the information into the pluginManagement section of
  the parent, but this still requires that each project's pom contain a
  reference to the plugin, which I'd rather not do. The other option is
  to put the information in the parent's build-plugins. This actually
  does seem to work (the subproject picks it up automatically), but has a
  an unpleasant side effect in that these goals are run for all of the
  non-jar type projects as well as the jar type projects. Looking a bit
  closer, it seems the javadoc:javadoc and source:jar goals are saying
  they won't execute because the project isn't the right type, but the
  javadoc:jar goal runs anyway, creating a javadoc jar with no actual
  javadocs in it. Maybe this is just a bug and I should report/patch it.
 
  The third way to do this would be to add the plugins to a profile and
  have the build pick it up there. I'm not as well-versed with profiles,
  so I may be missing something here. But from what I know, for this to
  work I'd have to specify the profile whenever I build (unless it's the
  default) and make sure all of the developers have the correct settings
  for their profile definition (or I suppose I can put the profile
  definition into the parent pom, but I'm not sure how that works). I
  don't think it actually buys me anything to list the plugins in a
  profile, though (i.e. it doesn't work any better than listing the
  plugins directly in the parent pom).
 
  Anyway, is there a recommended methodology for doing this sort of thing?
  Is there something I'm missing that I should be taking advantage of?

 I'm doing a bunch of stuff so I created a place holder:

 http://jira.codehaus.org/browse/MNG-1463

 Chris Berry had a post a while back, IIRC, which showed how he did it.

 You might want to comment there for the time being. Starting next week
 I'm going to try and tack that list of best practices by posting the
 lists, adding material to the wiki and trying to get some closure.

  Thanks,
  ..David..
 
 --
 jvz.

 Jason van Zyl
 jason at maven.org http://maven.org
 http://maven.apache.org

 happiness is like a butterfly: the more you chase it, the more it will
 elude you, but if you turn your attention to other things, it will come
 and sit softly on your shoulder ...

 -- Thoreau


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

RE: Set my own properties

Found it here:
http://maven.apache.org/guides/introduction/introduction-to-profiles.htm
l
Duh. 

-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 2:15 PM
To: Maven Users List
Subject: Set my own properties

Is there a way to set properties in the pom and the settings.xml that
are available during execution? Something like path_to_file_x = c:\. The
intent is to have some properties that are defined in profiles that can
change behaviors defined in my poms.

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

Re: [M2] - maven-release-plugin cannot load SCM provider

2005-11-08 Thread Trent Rosenbaum

Brett thanks for taking the time to look into my issues with the
maven-release plugin.
I was able to deploy a release locally. I just thought that because
their was a jira issue with the tagBase property for the plugin I
should be putting the whole URL with the prexfix because the URL
specified int he developerConnection is being used to construct the
tag URL.

Trent

On 08/11/05, Brett Porter [EMAIL PROTECTED] wrote:
Ah, sorry for the confusion.

nulike the connections, tagBase is just the SVN URL (omit scm:svn) as
it is an SVN specific property.

- Brett

On 11/8/05, Trent Rosenbaum [EMAIL PROTECTED] wrote:
This is the feedback I got from running mvn release:prepare

[INFO] [release:prepare]
[INFO] What tag name should be used?
0.1.2
[INFO] Tagging release with the label 0.1.2.
Provider message:
The svn tag command failed.
Command output:
svn: Error resolving case of
'scm:svn:file:\d:\subversion-1.2.0_data\repositorie
s\my_repo\bug-control-model\tags\0.1.2'

[INFO]
-
---
[ERROR] BUILD ERROR
[INFO]
-
---
[INFO] An error is occurred in the tag process.

The URL for the tagBase is identical to the URL supplied within the
developerConnection element but tags replaces trunk.

Trent

On 08/11/05, Brett Porter [EMAIL PROTECTED] wrote:
The bug is for the default of ../tags when used instead of a tagbase
as you have, so it is different.

Above that exception, there should have been output from the svn
command. Does that reveal anything?

- Brett

On 11/8/05, Trent Rosenbaum [EMAIL PROTECTED] wrote:
I did not have this pom.xml checked into SVN and so it was trying to
work with the previous revision of my file and this did not have a SCM
URL defined. I have been able to get the plugin to prompt me for
input regarding the tags, but I am falling over in the tagging process
with the following exception:

Is this the same exception that has lead to the creation of the
following issue in jira?

http://jira.codehaus.org/browse/MNG-883

org.apache.maven.lifecycle.LifecycleExecutionException: An error is
occurred in
the tag process.

Caused by: org.apache.maven.plugin.MojoExecutionException: An error is
occurred
in the tag process.
at
org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(Prepar
eReleaseMojo.java:1414)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe
leaseMojo.java:246)

thanks for taking to time to look into this.
Trent

On 07/11/05, Brett Porter [EMAIL PROTECTED] wrote:
I thought I had used windows paths in the SCM URL before without
issues, but its worth trying:

scm|svn|file:///d:/subversion...

hth,
Brett

On 11/8/05, Trent Rosenbaum [EMAIL PROTECTED] wrote:
This is the SCM URL for the project:

scm
developerConnectionscm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/trunk/developerConnection
/scm

and the plugin is configured with the following tagbase element:

plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.0-beta-3/version
configuration
tagBasescm:svn:file:///D:/subversion-1.2.0_data/repositories/my_repo/bug-control-model/tags/tagBase
/configuration
/plugin

On 07/11/05, Brett Porter [EMAIL PROTECTED] wrote:
They both use the same library - so the release plugin is for
automating release related tasks, the scm plugin for development
related tasks.

Can you please repost the full SCM URL that gave you this error -
there is still something wrong with it.

- Brett

On 11/8/05, Trent Rosenbaum [EMAIL PROTECTED] wrote:
Thanks for the reply.
When I started to use the plugin I was prefixing the URLs with
scm:svn, but then I still had a problem so thought about
exploring
and that is why I asked about setting the scm provider in a
different
manner. I have again used these prefixes and I still get a
problem.
Maven gave me the follow stacktrace below. I am using
2.0-beta-3 of the plugin.

During my reading of the site I noticed that both the scm and
the
release plugin are similar. Is it right to think that the
maven-scm
plugin is planned to allow developers to aquire a project
without a
pom.xml and then to complete the every day version control
tasks?
With this in mind is it best to view the maven-release plugin
as a
component that

[M2] How to designate what classes go in the ejb client jar

2005-11-08 Thread Ballard, Ken

In M1.0.2, I put this:

maven.ejb.client.base.excludes=**/*EJB.class,**/*Bean.class,**/*CMP.class,**
/*Session.class,**/*LocalHome.class,**/*Local.class

in my project.properties. Does anyone know how to achieve this in M2?

Thanks,
Ken

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

Maven SVG Plugin

2005-11-08 Thread Martin van den Bemt


Hi everyone,

I have an SVG Plugin for maven 1 and I wonder if anyone is interested in using that plugin in maven2 
(the maven1 plugin was never released, but is in public cvs on mvdb.org). If there is any interest 
in a maven2 plugin, I will try to have a go at a rewrite this week and actually trying to release 
the thing :)


Mvgr,
Martin

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

[m2] Custom artifact types (and the handlers who love them)

2005-11-08 Thread David Jackman

I've created a Mojo that generates a Javadoc-like documentation set, and
my plugin does things similar to the javadoc plugin in that it archives
all of the docs into a jar file and attaches the artifact to the list.
In looking at the artifact code, however, it looks like it's trying to
find an artifact handler for my custom artifact type so it knows how to
work with it (specifically, I'm trying to dictate what the file
extension should be).  How do I create and register an artifact handler
for my artifact type?  I assuem that my plugin would take care of this
sort of thing?
 
..David..

RE: [m2] Adding goals to execution

2005-11-08 Thread David Jackman

I think so, too.  I filed a bug (MNG-1464) and included a patch.

-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 08, 2005 11:51 AM
To: Maven Users List
Subject: Re: [m2] Adding goals to execution

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'd say that the javadoc:jar mojo needs to detect its environment just
as the javadoc:javadoc mojo does. That's a bug IMO.

FWIW,

john

David Jackman wrote:
| Here's what I'd like to do:  For our product, we have a number of 
| Maven projects, most of which are simple Java jar projects, but others

| are not.  For these jar projects, I'd like the javadoc:jar and 
| source:jar goals to execute as well.  I'd like this to be as automatic

| as possible for projects (i.e. define this in one central place 
| without requiring individual projects to do anything explicit).
|
| As far as I know, there are three ways to accomplish this.  First 
| would be to add the plugins to the pom.xml for each project.  This 
| works, but requires adding them to each project, defeating my goal to 
| only define it in one place.
|
| The next way to do this would be to add the plugins to the parent 
| pom.xml.  I can put the information into the pluginManagement section 
| of the parent, but this still requires that each project's pom contain

| a reference to the plugin, which I'd rather not do.  The other option 
| is to put the information in the parent's build-plugins.  This 
| actually does seem to work (the subproject picks it up automatically),

| but has a an unpleasant side effect in that these goals are run for 
| all of the non-jar type projects as well as the jar type projects.  
| Looking a bit closer, it seems the javadoc:javadoc and source:jar 
| goals are saying they won't execute because the project isn't the 
| right type, but the javadoc:jar goal runs anyway, creating a javadoc 
| jar with no actual javadocs in it.  Maybe this is just a bug and I
should report/patch it.
|
| The third way to do this would be to add the plugins to a profile and 
| have the build pick it up there.  I'm not as well-versed with 
| profiles, so I may be missing something here.  But from what I know, 
| for this to work I'd have to specify the profile whenever I build 
| (unless it's the
| default) and make sure all of the developers have the correct settings

| for their profile definition (or I suppose I can put the profile 
| definition into the parent pom, but I'm not sure how that works).  I 
| don't think it actually buys me anything to list the plugins in a 
| profile, though (i.e. it doesn't work any better than listing the 
| plugins directly in the parent pom).
|
| Anyway, is there a recommended methodology for doing this sort of
thing?
| Is there something I'm missing that I should be taking advantage of?
|
| Thanks,
| ..David..
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDcPN+K3h2CZwO/4URAjkaAJ49pVI9amanJB//7IuQRoiHX7+0pACfVC7T
jSirjtPNkQJoLeZzmwFX2c4=
=V93w
-END PGP SIGNATURE-

-
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]

Profiles not working?

2005-11-08 Thread Mike Whittemore

We have all our source code in ClearCase on Unix, under the vobs directory,
but also mount it on Windows drive Z:. I want to be able to build on either
windows or unix using the same source code and Maven files, and need to
reference this root directory (as root.dir) in several plugin properties.
Unfortunatley, I cannot get it to work with this setup:

profiles

profile
idwindows/id
activation
os
familywindows/family
/os
/activation
properties
root.dirZ:\/root.dir
/properties
/profile

profile
idunix/id
activation
os
familyunix/family
/os
/activation
properties
root.dir/vobs/root.dir
/properties
/profile

/profiles

When I run mvn projecthelp:active-profiles I get There are no active
profiles. instead of either unix or windows. I've also tried the -P to
force activation to no avail.

Any assistance would be appreciated.

Thanks.


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

RE: Profiles not working?

Mvn -Pwindows should do it. 

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Mike Whittemore
Sent: Tuesday, November 08, 2005 3:48 PM
To: users@maven.apache.org
Subject: Profiles not working?

We have all our source code in ClearCase on Unix, under the vobs
directory, but also mount it on Windows drive Z:. I want to be able to
build on either windows or unix using the same source code and Maven
files, and need to reference this root directory (as root.dir) in
several plugin properties.
Unfortunatley, I cannot get it to work with this setup:

profiles

profile
idwindows/id
activation
os
familywindows/family
/os
/activation
properties
root.dirZ:\/root.dir
/properties
/profile

profile
idunix/id
activation
os
familyunix/family
/os
/activation
properties
root.dir/vobs/root.dir
/properties
/profile

/profiles

When I run mvn projecthelp:active-profiles I get There are no active
profiles. instead of either unix or windows. I've also tried the -P
to force activation to no avail.

Any assistance would be appreciated.

Thanks.

-
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]

Profile precedence?

I am trying to determine how maven processes profiles. I have defined a
property in 2 profiles like this:
profiles
  profile
idtest/id
activation
  property
nameenv/name
valuetest/value
  /property
/activation
 
properties
  appserver.home/path/to/test/appserver/appserver.home
/properties
  /profile
  profile
iddev/id
activation
 activeByDefaulttrue/activeByDefault
/activation
properties
  appserver.home/path/to/dev/appserver/appserver.home
/properties
  /profile
/profiles
 
When I echo the output and both profiles are active, it is always using
the test profile value. It doesn't seem to matter what the -P order is
nor does it matter what the order in the pom is. 
 
I'm trying to figure out what the deterministic behavior is so I can
make sure I structure my profiles correctly. I will have overlapping
profiles that define platform - dev/test/release and instance - my
desktop/my laptop etc. I will thus always need multiple profiles active
to define my platform instance (dev - laptop or test-nh for example).

[m2] How can I deploy the maven-tomcat-plugin to my local remote repository?

2005-11-08 Thread KC Baltz

I've pulled the Tomcat plugin from codehaus via svn and had good success 
installing and using it.  Now I'd like to deploy it to our internal remote 
repository.  I can run the deploy (not tomcat:deploy) goal and everything 
appears to work.  however, when I delete the maven-tomcat-plugin directory from 
my ~/.m2/repository tree, to force a new download, it doesn't work.  I get the 
following:
 
[INFO] A required plugin was not found: Plugin could not be found - check that 
the goal name is correct: Unable to download the artifact from any repository
  org.codehaus.mojo:tomcat-maven-plugin:1.0-SNAPSHOT:maven-plugin
 
from the specified remote repositories:
  central ( http://repo1.maven.org/maven2)
 
  org.codehaus.mojo:tomcat-maven-plugin:1.0-SNAPSHOT:maven-plugin
 
from the specified remote repositories:
  central ( http://repo1.maven.org/maven2)
 
If I do a 'find tomcat-maven-plugin' in ~/.m2/repository/org/codehaus/mojo, I 
get the following:
 
tomcat-maven-plugin
tomcat-maven-plugin/1.0-SNAPSHOT
tomcat-maven-plugin/1.0-SNAPSHOT/maven-metadata-CopartRelease.xml
tomcat-maven-plugin/1.0-SNAPSHOT/tomcat-maven-plugin-1.0-20051108.212942-4.pom
tomcat-maven-plugin/1.0-SNAPSHOT/tomcat-maven-plugin-1.0-SNAPSHOT.pom
 
In my pom.xml that's trying to use the plugin, I have the following:
 
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
version1.0-SNAPSHOT/version
configuration
servertomcatLocal/server
path/cpf/path
url${tomcat.manager.url}/url
/configuration
/plugin

Can anyone help?
 
K.C.

[m2] Deploying and using snapshot versions


Hello again,

I have several projects that I'm trying to convert to use maven 2.  
There are some that are dependent on others.  The projects that are 
depended on have versions like 0.2-SNAPSHOT.  With m1 this wasn't a big 
deal, everything was treated the same pretty much.  Now, when I do a 
'mvn deploy' the SNAPSHOT part on the pom and jar file are replaced with 
the date and build number.  That's fine, I don't mind that.  But, then 
in the dependent projects I have the version set as 0.2-SNAPSHOT.  When 
maven tries to download the pom it fails because it tries to get 
mylib-0.2-SNAPSHOT.pom rather than mylib-0.2-${last build date}-${last 
build number}.jar.  I tried switching to just using SNAPSHOT as the 
version and that didn't help at all either.  Any ideas what I'm doing 
wrong?  Or is this a bug?


Thanks,
Rich

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

Re: [m2] Deploying and using snapshot versions

Oh wait, nevermind.  It's a problem with my eyes.  The pom it's trying 
to download is for it's parent project which I haven't deployed yet.


Richard Wallace wrote:

Hello again,

I have several projects that I'm trying to convert to use maven 2.  
There are some that are dependent on others.  The projects that are 
depended on have versions like 0.2-SNAPSHOT.  With m1 this wasn't a 
big deal, everything was treated the same pretty much.  Now, when I do 
a 'mvn deploy' the SNAPSHOT part on the pom and jar file are replaced 
with the date and build number.  That's fine, I don't mind that.  But, 
then in the dependent projects I have the version set as 
0.2-SNAPSHOT.  When maven tries to download the pom it fails because 
it tries to get mylib-0.2-SNAPSHOT.pom rather than mylib-0.2-${last 
build date}-${last build number}.jar.  I tried switching to just using 
SNAPSHOT as the version and that didn't help at all either.  Any ideas 
what I'm doing wrong?  Or is this a bug?


Thanks,
Rich

-
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: War and Site plugins: final release soon?

2005-11-08 Thread Brett Porter

the corny when its done answer. You're right, we need to resolve the
outstanding issues (minor as they are in most cases) first.

- Brett

On 11/8/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:




 Hi guys,

 Maven 2.0 has been released for quite a while now, and I was wondering when
 the Maven Distributed Plugins of the Maven Plugin Matrix would all be
 released in their final versions. As for me, I'm looking forward to the
 site plugin and the war plugin (which has only 4 issues left, amongst which
 MNG-1038 is important to me).

 Thanks for your answer!

 Best Regards / Cordialement,
 Fabrice BELLINGARD
 DINQ/DSIN/INSI/EATE/IDVS/AIDV
 (+33) (01 61) 45 15 91  -  [EMAIL PROTECTED]


 -
 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: Profile precedence?