RE: Admin account locked

[MATHUS Baptiste]

Hi Wendy,

Thanks for your answer. As I don't know plexus  the archiva webapp structure I 
don't where to find db configuration.
It seems like (I'm using the default) it's using JavaDB. Where's is configured 
the jdbc url so I can just copy-paste it ?

Thanks again.
Cheers.

-Message d'origine-
De : Wendy Smoak [mailto:[EMAIL PROTECTED] 
Envoyé : mercredi 6 février 2008 19:29
À : archiva-users@maven.apache.org
Objet : Re: Admin account locked

On Feb 6, 2008 11:19 AM, MATHUS Baptiste [EMAIL PROTECTED] wrote:
 It seems I f#^$d up something with my archiva instance. I wasn't able to 
 remember my admin password, so I asked for a reset.
 I reset the account three or four times.

 Now, I'm locked, each time I try to log in, I've got the 
 http://mvnrepo:4000/archiva/index.action?infoMessage=Account+Locked url.

 What can I do ? Even server-side operation to unlock me would help :-).

Stop Archiva, then re-start it.  The admin account should unlock.

If that doesn't work, you can connect to the users database directly and modify 
it.

(You can safely ignore the NoSuchPropertyExceptions in the logs.)

--
Wendy

Access to commons group

[Niall Pemberton]

I have a continuum logon (niallp) - can I get admin rights to maintain
the Apache Commons builds please

http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22

Niall

Re: Access to commons group

[Brett Porter]

done - by the way these requests should go through the normal
infrastructure channels

On 07/02/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
 I have a continuum logon (niallp) - can I get admin rights to maintain
 the Apache Commons builds please

 http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22

 Niall



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Bug in Continuum 1.1-beta-3 ? - goals and profile seem to be locked together

[sebb]

Just tried updating one of the HttpComponents projects. I changed the
profile to Java 1.4 for one of the projects, and now they all seem to
be using 1.4.

Likewise changing the goals for one of the projects affects the other two.

However, changing the notifiers seems to only affect the current project.

Is this tied behaviour correct?

If so, how can we build some projects in the group using 1.4 and some
using Java 5?

Re: Access to commons group

[sebb]

In that case the registration confirmation e-mail from Continuum
should be adjusted accordingly ...

On 07/02/2008, Brett Porter [EMAIL PROTECTED] wrote:
 done - by the way these requests should go through the normal
 infrastructure channels

 On 07/02/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
  I have a continuum logon (niallp) - can I get admin rights to maintain
  the Apache Commons builds please
 
  http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22
 
  Niall
 


 --
 Brett Porter
 Blog: http://blogs.exist.com/bporter/

Re: Access to commons group

[Brett Porter]

yep - have recorded that as INFRA-1514, thanks

On 07/02/2008, sebb [EMAIL PROTECTED] wrote:
 In that case the registration confirmation e-mail from Continuum
 should be adjusted accordingly ...

 On 07/02/2008, Brett Porter [EMAIL PROTECTED] wrote:
  done - by the way these requests should go through the normal
  infrastructure channels
 
  On 07/02/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
   I have a continuum logon (niallp) - can I get admin rights to maintain
   the Apache Commons builds please
  
   http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22
  
   Niall
  
 
 
  --
  Brett Porter
  Blog: http://blogs.exist.com/bporter/
 



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: release from a specific tag

[Benoit Decherf]

But I don't want to create an official version every night.
In the nightly version, there still have the -SNAPSHOT versions. So I 
can't use release:perform to do it. I realy need to execute the 
release:prepare from the nightly tag.


All projects here ask for this feature. I think this is a very good 
feature to be able to release an unofficial  version that is entirely 
tested.
It seems strange that nobody has asked for this feature. All of you 
always create a version from the last commits files of the trunk 
(integration branch) ?


Is it possible to make an evolution of the release plugin to support this ?

Benoit


Nicole Lacoste wrote:

Hi Benoit,

Yes I think so.  Well I know you can release from a tag made with the
release prepare.  The command is

mvn release:perform -DconnectionUrl=scm:svn:file://your-url-here/tag-name

Look at page 224 of better builds with maven for more details

Nicole

On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:
  

Hi,

I think that we should be able to perform a release from an old nightly
tag rather than do it always from the trunk :

Every night functional tests run on a project A. On day d everything
works, but after, I decide to add a feature and I broke the trunk. I'd
like to be able to release the project in it's state of day d without
losing the work I done. This could be useful in some cases.
Is there already a way to do it ?

Benoit

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





  

Re: release from a specific tag

[Kalle Korhonen]

I don't understand what you are asking. release:perform doesn't do anything
else but runs deploy (and site-deploy) on the newly created tag; after
release:prepare, the release is already cut. If you want snapshots, why
don't you just deploy uniquely versioned snapshots nightly?

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:

 But I don't want to create an official version every night.
 In the nightly version, there still have the -SNAPSHOT versions. So I
 can't use release:perform to do it. I realy need to execute the
 release:prepare from the nightly tag.

 All projects here ask for this feature. I think this is a very good
 feature to be able to release an unofficial  version that is entirely
 tested.
 It seems strange that nobody has asked for this feature. All of you
 always create a version from the last commits files of the trunk
 (integration branch) ?

 Is it possible to make an evolution of the release plugin to support this
 ?

 Benoit


 Nicole Lacoste wrote:
  Hi Benoit,
 
  Yes I think so.  Well I know you can release from a tag made with the
  release prepare.  The command is
 
  mvn release:perform
 -DconnectionUrl=scm:svn:file://your-url-here/tag-name
 
  Look at page 224 of better builds with maven for more details
 
  Nicole
 
  On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:
 
  Hi,
 
  I think that we should be able to perform a release from an old nightly
  tag rather than do it always from the trunk :
 
  Every night functional tests run on a project A. On day d everything
  works, but after, I decide to add a feature and I broke the trunk. I'd
  like to be able to release the project in it's state of day d without
  losing the work I done. This could be useful in some cases.
  Is there already a way to do it ?
 
  Benoit
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 

Re: release from a specific tag

[Benoit Decherf]

Image that we are working on the trunk. Every night a nightly snapshot 
is created and deploy on a test servers and automatic tests are run 
(they can last 4hours for a project).

on date 04 feb. every tests passed.
on date 05 feb. some tests are broken.

But on 06 feb we want to make a release (to install in prod). The dev 
started on 05 feb are not finished, and so the nightly of 04 feb should 
be released.
To do so, I suppose that release:prepare should be executed from the 
nightly tag of 4 feb to remove all snapshots dependencies, tag the 
release with an official tag, etc... The release prepare should create a 
branch from this tag to do it ?


Benoit


Kalle Korhonen wrote:

I don't understand what you are asking. release:perform doesn't do anything
else but runs deploy (and site-deploy) on the newly created tag; after
release:prepare, the release is already cut. If you want snapshots, why
don't you just deploy uniquely versioned snapshots nightly?

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
  

But I don't want to create an official version every night.
In the nightly version, there still have the -SNAPSHOT versions. So I
can't use release:perform to do it. I realy need to execute the
release:prepare from the nightly tag.

All projects here ask for this feature. I think this is a very good
feature to be able to release an unofficial  version that is entirely
tested.
It seems strange that nobody has asked for this feature. All of you
always create a version from the last commits files of the trunk
(integration branch) ?

Is it possible to make an evolution of the release plugin to support this
?

Benoit


Nicole Lacoste wrote:


Hi Benoit,

Yes I think so.  Well I know you can release from a tag made with the
release prepare.  The command is

mvn release:perform
  

-DconnectionUrl=scm:svn:file://your-url-here/tag-name


Look at page 224 of better builds with maven for more details

Nicole

On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:

  

Hi,

I think that we should be able to perform a release from an old nightly
tag rather than do it always from the trunk :

Every night functional tests run on a project A. On day d everything
works, but after, I decide to add a feature and I broke the trunk. I'd
like to be able to release the project in it's state of day d without
losing the work I done. This could be useful in some cases.
Is there already a way to do it ?

Benoit

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




  



  

Re: release from a specific tag

[Kalle Korhonen]

Ah ok, I see what you mean, but I think it's specific to your process. I'd
assume that most projects operate so they require that the trunk/branch
builds cleanly, rather than releasing from a specific time
point/version/label. In your case, it'd mean reverting the trunk to 04 feb,
then doing the release. In the meantime 05 feb would continue in branch or
with local copies only. I believe it's also common practice to require the
trunk builds to succeed. In our development process, we try not to prevent
build failures but to minimize the time the build remains in broken state,
with whatever means necessary (in some cases, reverting to previous state).

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:

 Image that we are working on the trunk. Every night a nightly snapshot
 is created and deploy on a test servers and automatic tests are run
 (they can last 4hours for a project).
 on date 04 feb. every tests passed.
 on date 05 feb. some tests are broken.

 But on 06 feb we want to make a release (to install in prod). The dev
 started on 05 feb are not finished, and so the nightly of 04 feb should
 be released.
 To do so, I suppose that release:prepare should be executed from the
 nightly tag of 4 feb to remove all snapshots dependencies, tag the
 release with an official tag, etc... The release prepare should create a
 branch from this tag to do it ?

 Benoit


 Kalle Korhonen wrote:
  I don't understand what you are asking. release:perform doesn't do
 anything
  else but runs deploy (and site-deploy) on the newly created tag; after
  release:prepare, the release is already cut. If you want snapshots, why
  don't you just deploy uniquely versioned snapshots nightly?
 
  Kalle
 
 
  On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
 
  But I don't want to create an official version every night.
  In the nightly version, there still have the -SNAPSHOT versions. So I
  can't use release:perform to do it. I realy need to execute the
  release:prepare from the nightly tag.
 
  All projects here ask for this feature. I think this is a very good
  feature to be able to release an unofficial  version that is entirely
  tested.
  It seems strange that nobody has asked for this feature. All of you
  always create a version from the last commits files of the trunk
  (integration branch) ?
 
  Is it possible to make an evolution of the release plugin to support
 this
  ?
 
  Benoit
 
 
  Nicole Lacoste wrote:
 
  Hi Benoit,
 
  Yes I think so.  Well I know you can release from a tag made with the
  release prepare.  The command is
 
  mvn release:perform
 
  -DconnectionUrl=scm:svn:file://your-url-here/tag-name
 
  Look at page 224 of better builds with maven for more details
 
  Nicole
 
  On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:
 
 
  Hi,
 
  I think that we should be able to perform a release from an old
 nightly
  tag rather than do it always from the trunk :
 
  Every night functional tests run on a project A. On day d
 everything
  works, but after, I decide to add a feature and I broke the trunk.
 I'd
  like to be able to release the project in it's state of day d
 without
  losing the work I done. This could be useful in some cases.
  Is there already a way to do it ?
 
  Benoit
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
 
 

Re: release from a specific tag

[Benoit Decherf]

I'm not sure that this it's specific to our process (If this is the 
case, we should probably change it :) ).


I don't think that is possible to have always a clean trunk/branch.
Let me explain our process:
Each developer commit their changes on the trunk.
Each hour, continuum check for changes and package the components(and 
execute the unit test).
Each night project is tagged (nightly tag) and the packages are 
installed on a dev plateform and automatics tests are executed. This can 
last 3 hours.


So, I agree with you that if a unit test fails, the developer have to 
clean it (This shouldn't happen because tests should be executed before 
commit). But the integration tests that last 3 hours can't be executed 
on each commit, so something can be broken for several days because of a 
regression. This also occurs at maven.


Additionaly, when performing (prepare) a release, It should be great to 
be sure that the integration tests passed. So it can be useful to be 
able to prepare/perform a release from a nightly tag.


Benoit

Kalle Korhonen wrote:

Ah ok, I see what you mean, but I think it's specific to your process. I'd
assume that most projects operate so they require that the trunk/branch
builds cleanly, rather than releasing from a specific time
point/version/label. In your case, it'd mean reverting the trunk to 04 feb,
then doing the release. In the meantime 05 feb would continue in branch or
with local copies only. I believe it's also common practice to require the
trunk builds to succeed. In our development process, we try not to prevent
build failures but to minimize the time the build remains in broken state,
with whatever means necessary (in some cases, reverting to previous state).

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
  

Image that we are working on the trunk. Every night a nightly snapshot
is created and deploy on a test servers and automatic tests are run
(they can last 4hours for a project).
on date 04 feb. every tests passed.
on date 05 feb. some tests are broken.

But on 06 feb we want to make a release (to install in prod). The dev
started on 05 feb are not finished, and so the nightly of 04 feb should
be released.
To do so, I suppose that release:prepare should be executed from the
nightly tag of 4 feb to remove all snapshots dependencies, tag the
release with an official tag, etc... The release prepare should create a
branch from this tag to do it ?

Benoit


Kalle Korhonen wrote:


I don't understand what you are asking. release:perform doesn't do
  

anything


else but runs deploy (and site-deploy) on the newly created tag; after
release:prepare, the release is already cut. If you want snapshots, why
don't you just deploy uniquely versioned snapshots nightly?

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:

  

But I don't want to create an official version every night.
In the nightly version, there still have the -SNAPSHOT versions. So I
can't use release:perform to do it. I realy need to execute the
release:prepare from the nightly tag.

All projects here ask for this feature. I think this is a very good
feature to be able to release an unofficial  version that is entirely
tested.
It seems strange that nobody has asked for this feature. All of you
always create a version from the last commits files of the trunk
(integration branch) ?

Is it possible to make an evolution of the release plugin to support


this


?

Benoit


Nicole Lacoste wrote:



Hi Benoit,

Yes I think so.  Well I know you can release from a tag made with the
release prepare.  The command is

mvn release:perform

  

-DconnectionUrl=scm:svn:file://your-url-here/tag-name



Look at page 224 of better builds with maven for more details

Nicole

On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:


  

Hi,

I think that we should be able to perform a release from an old


nightly


tag rather than do it always from the trunk :

Every night functional tests run on a project A. On day d


everything


works, but after, I decide to add a feature and I broke the trunk.


I'd


like to be able to release the project in it's state of day d


without


losing the work I done. This could be useful in some cases.
Is there already a way to do it ?

Benoit

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





  



  

Re: release from a specific tag

[VUB Stefan Seidel]

Hi,

I have to support Benoit here, I think it is a very useful use case. We 
have never thought of going back when something fails but indirectly we 
work around it.
We too have continuum running every night, and if all goes well and the 
integration tests succeed, an application package is built containing 
all the necessary jar, war and ear files and it is deployed to a remote 
server using scp. Thus, we can always have a tested working binary 
version. But we too could not declare this as a release version, because 
we only have a binary.
A workaround would be to tag the sources every night, then check out the 
sources using the tag, then release it from there.


regards,
Stefan

Benoit Decherf wrote:
I'm not sure that this it's specific to our process (If this is the 
case, we should probably change it :) ).


I don't think that is possible to have always a clean trunk/branch.
Let me explain our process:
Each developer commit their changes on the trunk.
Each hour, continuum check for changes and package the components(and 
execute the unit test).
Each night project is tagged (nightly tag) and the packages are 
installed on a dev plateform and automatics tests are executed. This can 
last 3 hours.


So, I agree with you that if a unit test fails, the developer have to 
clean it (This shouldn't happen because tests should be executed before 
commit). But the integration tests that last 3 hours can't be executed 
on each commit, so something can be broken for several days because of a 
regression. This also occurs at maven.


Additionaly, when performing (prepare) a release, It should be great to 
be sure that the integration tests passed. So it can be useful to be 
able to prepare/perform a release from a nightly tag.


Benoit

Kalle Korhonen wrote:
Ah ok, I see what you mean, but I think it's specific to your process. 
I'd

assume that most projects operate so they require that the trunk/branch
builds cleanly, rather than releasing from a specific time
point/version/label. In your case, it'd mean reverting the trunk to 04 
feb,
then doing the release. In the meantime 05 feb would continue in 
branch or
with local copies only. I believe it's also common practice to require 
the
trunk builds to succeed. In our development process, we try not to 
prevent
build failures but to minimize the time the build remains in broken 
state,
with whatever means necessary (in some cases, reverting to previous 
state).


Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
 

Image that we are working on the trunk. Every night a nightly snapshot
is created and deploy on a test servers and automatic tests are run
(they can last 4hours for a project).
on date 04 feb. every tests passed.
on date 05 feb. some tests are broken.

But on 06 feb we want to make a release (to install in prod). The dev
started on 05 feb are not finished, and so the nightly of 04 feb should
be released.
To do so, I suppose that release:prepare should be executed from the
nightly tag of 4 feb to remove all snapshots dependencies, tag the
release with an official tag, etc... The release prepare should create a
branch from this tag to do it ?

Benoit


Kalle Korhonen wrote:
   

I don't understand what you are asking. release:perform doesn't do
  

anything
   

else but runs deploy (and site-deploy) on the newly created tag; after
release:prepare, the release is already cut. If you want snapshots, why
don't you just deploy uniquely versioned snapshots nightly?

Kalle


On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:

 

But I don't want to create an official version every night.
In the nightly version, there still have the -SNAPSHOT versions. So I
can't use release:perform to do it. I realy need to execute the
release:prepare from the nightly tag.

All projects here ask for this feature. I think this is a very good
feature to be able to release an unofficial  version that is 
entirely

tested.
It seems strange that nobody has asked for this feature. All of you
always create a version from the last commits files of the trunk
(integration branch) ?

Is it possible to make an evolution of the release plugin to support


this
   

?

Benoit


Nicole Lacoste wrote:

   

Hi Benoit,

Yes I think so.  Well I know you can release from a tag made with the
release prepare.  The command is

mvn release:perform

  

-DconnectionUrl=scm:svn:file://your-url-here/tag-name

   

Look at page 224 of better builds with maven for more details

Nicole

On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:


 

Hi,

I think that we should be able to perform a release from an old


nightly
   

tag rather than do it always from the trunk :

Every night functional tests run on a project A. On day d


everything
   

works, but after, I decide to add a feature and I broke the trunk.


I'd
   

like to be able to release the project in it's state of day d


without
   

Re: Attaching HTML pages to Maven panels using mvn site

[DCVer]

Still haven't found any hint :( Has anyone some idea?

DCVer wrote:
 
 Hello all!
 
 I am using docbkx-maven-plugin do create HTML pages from DocBook files and
 attach created HTML pages to site (using mvn site command - I define links
 to those pages using site.xml file). The only problem is, that all maven
 pages are plugged to nice panels (top panel and left-side panel), but when
 i click on the link to HTML page, created from DocBook it is opened in
 whole page (without those nice panels). Unfortunately I can't modify any
 of those HTML pages, because they are created dynamically, during mvn site
 command. Is there a possibility do attach some HTML pages to those nice
 panels? Can e.g. xdoc xml pages import new HTML pages? (Maven creates
 nice panels to all XHTML pages saved in xdocs directory). Thanks in
 advance for any suggestions or even better solutions :)
 

-- 
View this message in context: 
http://www.nabble.com/Attaching-HTML-pages-to-Maven-panels-using-%22mvn-site%22-tp15092490s177p15331846.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Strange problems with mvn release:perform when running javadoc:jar on Windows

[Stephen Connolly]

Found the solution...

he had his CLASSPATH environment variable set and it was pulling in
all sorts of junk from a previous version of the JDK

On Jan 18, 2008 12:36 PM, Stephen Connolly
[EMAIL PROTECTED] wrote:
 oh it gets stranger.

 we have no problems with javadoc:javadoc, only javadoc:jar



 On Jan 18, 2008 9:57 AM, Tom Huybrechts [EMAIL PROTECTED]  wrote:
  I've had my share of javadoc problems, but not this one. Did you try to
 run
  the javadoc command itself from the commandline ?
 
  Tom
 
  On Jan 18, 2008 10:48 AM, Stephen Connolly
 [EMAIL PROTECTED]
 
 
 
  wrote:
 
   Anyone??? or will i just file an issue
  
   On Jan 17, 2008 8:24 AM, Stephen Connolly
 [EMAIL PROTECTED]
   
   wrote:
  
Here is the stacktrace:
   
The exact same commands from my machine work with the exact same
   proxyHost
and proxyPort and JDK and Maven version
   
[INFO] [javadoc:jar]
[DEBUG] C:\Java\jdk1.6.0_04\jre\..\bin\javadoc.exe
-J-DproxyHost=.com -J-DproxyPort= @options @packages
Loading source files for package com....
Constructing Javadoc information...
Standard Doclet version 1.6.0_04
Building tree for all the packages and classes...
Generating
   
  
 C:/work/jsr-112-workmanager-impl/target/apidocs\com/___/___/___//\_.html...
[INFO]
   
 
[ERROR] BUILD ERROR
[INFO]
   
 
[INFO] Error while creating archive:Exit code: 1 -
java.lang.IllegalArgumentException
 at sun.net.www.ParseUtil.decode(ParseUtil.java:189)
 at sun.misc.URLClassPath$FileLoader .init(URLClassPath.java:953)
 at sun.misc.URLClassPath$3.run(URLClassPath.java:326)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.misc.URLClassPath.getLoader (URLClassPath.java:320)
 at sun.misc.URLClassPath.getLoader(URLClassPath.java:297)
 at sun.misc.URLClassPath.findResource(URLClassPath.java:144)
 at java.net.URLClassLoader$2.run(URLClassLoader.java :362)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findResource(URLClassLoader.java:359)
 at java.lang.ClassLoader.getResource(ClassLoader.java :977)
 at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1159)
 at javax.xml.parsers.SecuritySupport$4.run(SecuritySupport.java:96)
 at java.security.AccessController.doPrivileged (Native Method)
 at javax.xml.parsers.SecuritySupport.getResourceAsStream(
SecuritySupport.java:89)
 at javax.xml.parsers.FactoryFinder.findJarServiceProvider(
FactoryFinder.java :250)
 at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:223)
 at
 javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java
:128)
 at
   com.sun.tools.doclets.internal.toolkit.builders.LayoutParser.parseXML (
LayoutParser.java:72)
 at
 com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.build(
ClassBuilder.java:108)
 at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles (
HtmlDoclet.java:155)
 at
   
 com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles
   (
AbstractDoclet.java:164)
 at
   com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration (
AbstractDoclet.java:106)
 at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(
AbstractDoclet.java:64)
 at com.sun.tools.doclets.formats.html.HtmlDoclet.start
 (HtmlDoclet.java
:42)
 at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
 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 :597)
 at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:215)
 at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:91)
 at com.sun.tools.javadoc.Start.parseAndExecute (Start.java:340)
 at com.sun.tools.javadoc.Start.begin(Start.java:128)
 at com.sun.tools.javadoc.Main.execute(Main.java:41)
 at com.sun.tools.javadoc.Main.main(Main.java:31)
com.sun.tools.doclets.internal.toolkit.util.DocletAbortException
 at
   com.sun.tools.doclets.internal.toolkit.builders.LayoutParser.parseXML(
LayoutParser.java:79)
 at com.sun.tools.doclets.internal.toolkit.builders.ClassBuilder.build
 (
ClassBuilder.java:108)
 at com.sun.tools.doclets.formats.html.HtmlDoclet.generateClassFiles(
HtmlDoclet.java:155)
 at
   
 com.sun.tools.doclets.internal.toolkit.AbstractDoclet.generateClassFiles
   (
AbstractDoclet.java:164)
 at
   com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(

Re: Updating M2_HOME/conf/settings.xml

[Benoit Decherf]

Hi,

Maybe you should check for a deployment/configuration system like bcfg2 
or puppet.


Benoit

Matthew Tordoff wrote:

Hi all,

I just wondered if anyone has any best practises for updating the global 
settings.xml in Maven. I have considered checking the conf folder into SVN, or 
even potentially checking the whole maven install into SVN, then when changes 
are made send out an email and people can just do an SVN update to pick up the 
changes. The only disadvantage of this process is that it relies on people 
reading their mail and kicking off the update. I would preferably like a method 
of automatically publishing changes which would automatically update all 
developers machines.

Any thoughts around this would be greatly appreciated.

Regards,

Matt

P.S. I would also be interested on your views regarding checking in solely the 
settings.xml file into version control, vs checking in the whole install.

_
Free games, great prizes - get gaming at Gamesbox. 
http://www.searchgamesbox.com
  



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

Re: Bug in Continuum 1.1-beta-3 ? - goals and profile seem to be locked together

[Emmanuel Venisse]

If you want different configurations, you have few solutions:
- Define a profile that use the most recent jdk and configure source/target
parameters on the compiler plugin in each projects
- Remove the group build definition and add a new build definition on each
project linked with a specific profile.

Emmanuel

On Feb 7, 2008 1:17 PM, sebb [EMAIL PROTECTED] wrote:

 Just tried updating one of the HttpComponents projects. I changed the
 profile to Java 1.4 for one of the projects, and now they all seem to
 be using 1.4.

 Likewise changing the goals for one of the projects affects the other two.

 However, changing the notifiers seems to only affect the current project.

 Is this tied behaviour correct?

 If so, how can we build some projects in the group using 1.4 and some
 using Java 5?

Re: How to disable Test during build

[Arun P Johny]

Hi,

   Thanks Rahul

   Is there a way to pass the value through pom.xml file. Because I 
don't want to pass the value every time as a command line argument


Thank you

Rahul Thakur wrote:

pass property -Dmaven.test.skip=true

Rahul

Arun P Johny wrote:

Hi,

Can anybody tell me how to disable execution of test phase during 
maven2 build. I'm using maven 2.0.7


I don't want the test phase to execute when I gaves mvn 
release:prepare and mvn release:perform


Thank You,
Arun

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


__ Information from ESET NOD32 Antivirus, version of virus 
signature database 2854 (20080206) __


The message was checked by ESET NOD32 Antivirus.

http://www.eset.com






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

Re: Access to commons group

[Niall Pemberton]

On Feb 7, 2008 12:16 PM, Brett Porter [EMAIL PROTECTED] wrote:
 done - by the way these requests should go through the normal
 infrastructure channels

Thanks

Niall

 On 07/02/2008, Niall Pemberton [EMAIL PROTECTED] wrote:
  I have a continuum logon (niallp) - can I get admin rights to maintain
  the Apache Commons builds please
 
  http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=22
 
  Niall
 

Updating M2_HOME/conf/settings.xml

[Matthew Tordoff]

Hi all,

I just wondered if anyone has any best practises for updating the global 
settings.xml in Maven. I have considered checking the conf folder into SVN, or 
even potentially checking the whole maven install into SVN, then when changes 
are made send out an email and people can just do an SVN update to pick up the 
changes. The only disadvantage of this process is that it relies on people 
reading their mail and kicking off the update. I would preferably like a method 
of automatically publishing changes which would automatically update all 
developers machines.

Any thoughts around this would be greatly appreciated.

Regards,

Matt

P.S. I would also be interested on your views regarding checking in solely the 
settings.xml file into version control, vs checking in the whole install.

_
Free games, great prizes - get gaming at Gamesbox. 
http://www.searchgamesbox.com

Re: Updating M2_HOME/conf/settings.xml

[VUB Stefan Seidel]

Put maven-install-dir/conf/settings.xml on a shared drive, or replace 
it with a symlink to a shared drive.


Why do you need to change the settings.xml anyway? Could it not be done 
in a master pom that is the parent to all other poms? Then you can 
simply deploy the master pom and you're done.


Stefan

Matthew Tordoff wrote:

Hi all,

I just wondered if anyone has any best practises for updating the global 
settings.xml in Maven. I have considered checking the conf folder into SVN, or 
even potentially checking the whole maven install into SVN, then when changes 
are made send out an email and people can just do an SVN update to pick up the 
changes. The only disadvantage of this process is that it relies on people 
reading their mail and kicking off the update. I would preferably like a method 
of automatically publishing changes which would automatically update all 
developers machines.

Any thoughts around this would be greatly appreciated.

Regards,

Matt

P.S. I would also be interested on your views regarding checking in solely the 
settings.xml file into version control, vs checking in the whole install.

_
Free games, great prizes - get gaming at Gamesbox. 
http://www.searchgamesbox.com


--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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

Re: maven eclipse plugin workspace dependencies resolution

[Roland Asmann]

I happen to know a little bit about this (mainly because my colleague created 
these options ;-) ).

I believe that version of the plugin hasn't been released yet, although it 
could be that a SNAPSHOT-release has been made. If not, check out the latest 
sources and build it for yourself, it should work like a charm!


On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
 Hi All,

 I'm trying to find a better way of using maven and eclipse in my team
 (m2eclipse just creates to many problems with transient dependencies,
 even in 0.0.12).

 So .. while trying to use maven-eclipse-plugin, I came across the
 -Declipse.workspaceToConnect=${workspace_loc}  option
 in http://jira.codehaus.org/browse/MECLIPSE-344.

 I've tried to use it so that the project dependencies inside my eclipse
 would be resolved and added to my library path.
 However that is not working, it still resolves the artifact jar in my
 local repository.

 Has anyone been able to make this work?

 Regards,

 Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

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

RE: Maven Reporting - DashBoard-Maven-Plugin

[Nagesh, Srinivas (IS Consultant)]

Hi Stefan,

Thanks for your response.

As you mentioned I am looking for a common report.When I try using the 
dashboard-maven-plugin, I ran into the following problem

I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html

1. Placed the dashboard plugin at the very end of the reporting tag.
2. Ran Maven Site. This actually generated the report before the findbugs 
plugin is executed. Shouldnt it supposed to run it at the last when all the 
other plugins have finished generating their reports?
3. Also as mentioned in the site above, what does this mean? add the dashboard 
report item in the left menu.

Would you happen to have a working example of the dashboard-maven-plugin?

Thanks

Srinivas
x3126

-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 2:46 AM
To: Maven Users List
Subject: Re: Maven Reporting

Hi,

you may consolidate single reports for all modules (like Javadoc, JXR, 
...) using the aggregate feature of these reports. The question is, 
what do you really want to do? Your modules have different names for 
example, how do you consolidate that?

If you are looking for a common report on JUnit tests, Checkstyle, 
Findbugs etc. have a look at the dashboard-maven-plugin.

regards,

Stefan

Nagesh, Srinivas (IS Consultant) wrote:
 Hi All,
 
 I have a multi-project setup in maven
 
 -- Proj
 -- pom.xml -- Reporting
 -- Proj1
 -- pom.xml
 -- Proj2
 -- pom.xml
 
 When I specify reporting in the parent pom, the reports are generated in
 the respective children projects. I would like to know if there is a
 feature to create a consolidated report of the sub project (Proj1 
 Proj2)?
 
 Thanks
 
 Srini
 

-- 
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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

maven eclipse plugin workspace dependencies resolution

[da Costa Oliveira, Pedro Manuel]

Hi All,
 
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
 
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc}  option
in http://jira.codehaus.org/browse/MECLIPSE-344.
 
I've tried to use it so that the project dependencies inside my eclipse
would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
 
Has anyone been able to make this work?
 
Regards,

Pedro 

RE: Maven Reporting - DashBoard-Maven-Plugin

[dvicente]

Hi all,

as described in dashboard documentation :
http://mojo.codehaus.org/dashboard-maven-plugin/

you must add this in your pom.xml or settings.xml to use properly the
dashboard plugin:

pluginRepositories
pluginRepository
idCodehaus Snapshots/id
url http://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories

But even if this configuration is well done, Maven doesn't recognize the
mvn dashboard-report:dashboard command.

and to work fine, you must run mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command
instead of mvn dashboard-report:dashboard.

See :

http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html
or
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html
or
http://jira.codehaus.org/browse/MOJO-899

In the project's beginning, i decided to modify the goal prefix to
dashboard-report instead of the default's one by adding in the pom.xml of
the dashboard plugin :

...
build

plugins
plugin
  artifactIdmaven-plugin-plugin/artifactId
  configuration
  goalPrefixdashboard-report/goalPrefix
  /configuration
/plugin
...
/plugins
...
/build


I think it's The Maven resolution problem of dashboard-report.

Maven does not resolve properly the plugin prefix.

it's for that : mvn dashboard-report:dashboard doesn't work correctly.

For the next release , i will post a vote to users@maven.apache.org  and
[EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the
default's one which works fine.

After that, you will have to modify the goal prefix in your command line or
Continuum goals to use the dashboard report :

from dashboard-report:dashboard to dashboard:dashboard
or
from dashboard-report:persist to dashboard:persist

Best Regards

David Vicente

SrinivasN wrote:
 
 I did... the second command never worked... it complains that it cannot
 find the dashboard-report plugin. I even set up the repository as
 mentioned and it downloaded while generating site... but the second
 command doesn't work.
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 10:00 AM
 To: Maven Users List
 Subject: Re: Maven Reporting - DashBoard-Maven-Plugin
 
 Quote:
 To generate the site and the correct dashboard report, you must run the 
 dashboard report plugin in 2 passes :
 # mvn site
 # mvn dashboard-report:dashboard
 
 You should execute these two commands on the command line.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi Stefan,
 
 Thanks for your response.
 
 As you mentioned I am looking for a common report.When I try using the
 dashboard-maven-plugin, I ran into the following problem
 
 I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
 
 1. Placed the dashboard plugin at the very end of the reporting tag.
 2. Ran Maven Site. This actually generated the report before the findbugs
 plugin is executed. Shouldnt it supposed to run it at the last when all
 the other plugins have finished generating their reports?
 3. Also as mentioned in the site above, what does this mean? add the
 dashboard report item in the left menu.
 
 Would you happen to have a working example of the dashboard-maven-plugin?
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 2:46 AM
 To: Maven Users List
 Subject: Re: Maven Reporting
 
 Hi,
 
 you may consolidate single reports for all modules (like Javadoc, JXR, 
 ...) using the aggregate feature of these reports. The question is, 
 what do you really want to do? Your modules have different names for 
 example, how do you consolidate that?
 
 If you are looking for a common report on JUnit tests, Checkstyle, 
 Findbugs etc. have a look at the dashboard-maven-plugin.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi All,

 I have a multi-project setup in maven

 -- Proj
 -- pom.xml -- Reporting
 -- Proj1
 -- pom.xml
 -- Proj2
 -- pom.xml

 When I specify reporting in the parent pom, the reports are generated in
 the respective children projects. I would like to know if there is a
 feature to create a consolidated report of the sub project (Proj1 
 Proj2)?

 Thanks

 Srini

 
 
 -- 
 best regards,
 
 Stefan Seidel
 software developer
 
 VUB Printmedia GmbH
 Chopinstraße 4
 D-04103 Leipzig
 Germany
 tel.+49 (341) 9 60 50 07
 fax.+49 (341) 9 60 50 92
 mail.   [EMAIL PROTECTED]
 web.www.vub.de
 
 HRB Köln 24015
 UStID DE 122 649 251
 GF Dr. Achim Preuss Neudorf,
 Dr. Christian Preuss Neudorf
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

RE: Maven Reporting - DashBoard-Maven-Plugin

[dvicente]

Hi all,

as described in dashboard documentation :
http://mojo.codehaus.org/dashboard-maven-plugin/

you must add this in your pom.xml or settings.xml to use properly the
dashboard plugin:

pluginRepositories
pluginRepository
idCodehaus Snapshots/id
url http://snapshots.repository.codehaus.org//url
/pluginRepository
/pluginRepositories

But even if this configuration is well done, Maven doesn't recognize the
mvn dashboard-report:dashboard command.

and to work fine, you must run mvn
org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command
instead of mvn dashboard-report:dashboard.

See :

http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html
or
http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html
or
http://jira.codehaus.org/browse/MOJO-899

In the project's beginning, i decided to modify the goal prefix to
dashboard-report instead of the default's one by adding in the pom.xml of
the dashboard plugin :

...
build

plugins
plugin
  artifactIdmaven-plugin-plugin/artifactId
  configuration
  goalPrefixdashboard-report/goalPrefix
  /configuration
/plugin
...
/plugins
...
/build


I think it's The Maven resolution problem of dashboard-report.

Maven does not resolve properly the plugin prefix.

it's for that : mvn dashboard-report:dashboard doesn't work correctly.

For the next release , i will post a vote to users@maven.apache.org  and
[EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the
default's one which works fine.

After that, you will have to modify the goal prefix in your command line or
Continuum goals to use the dashboard report :

from dashboard-report:dashboard to dashboard:dashboard
or
from dashboard-report:persist to dashboard:persist

Best Regards

David Vicente

SrinivasN wrote:
 
 I did... the second command never worked... it complains that it cannot
 find the dashboard-report plugin. I even set up the repository as
 mentioned and it downloaded while generating site... but the second
 command doesn't work.
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 10:00 AM
 To: Maven Users List
 Subject: Re: Maven Reporting - DashBoard-Maven-Plugin
 
 Quote:
 To generate the site and the correct dashboard report, you must run the 
 dashboard report plugin in 2 passes :
 # mvn site
 # mvn dashboard-report:dashboard
 
 You should execute these two commands on the command line.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi Stefan,
 
 Thanks for your response.
 
 As you mentioned I am looking for a common report.When I try using the
 dashboard-maven-plugin, I ran into the following problem
 
 I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
 
 1. Placed the dashboard plugin at the very end of the reporting tag.
 2. Ran Maven Site. This actually generated the report before the findbugs
 plugin is executed. Shouldnt it supposed to run it at the last when all
 the other plugins have finished generating their reports?
 3. Also as mentioned in the site above, what does this mean? add the
 dashboard report item in the left menu.
 
 Would you happen to have a working example of the dashboard-maven-plugin?
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 2:46 AM
 To: Maven Users List
 Subject: Re: Maven Reporting
 
 Hi,
 
 you may consolidate single reports for all modules (like Javadoc, JXR, 
 ...) using the aggregate feature of these reports. The question is, 
 what do you really want to do? Your modules have different names for 
 example, how do you consolidate that?
 
 If you are looking for a common report on JUnit tests, Checkstyle, 
 Findbugs etc. have a look at the dashboard-maven-plugin.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi All,

 I have a multi-project setup in maven

 -- Proj
 -- pom.xml -- Reporting
 -- Proj1
 -- pom.xml
 -- Proj2
 -- pom.xml

 When I specify reporting in the parent pom, the reports are generated in
 the respective children projects. I would like to know if there is a
 feature to create a consolidated report of the sub project (Proj1 
 Proj2)?

 Thanks

 Srini

 
 
 -- 
 best regards,
 
 Stefan Seidel
 software developer
 
 VUB Printmedia GmbH
 Chopinstraße 4
 D-04103 Leipzig
 Germany
 tel.+49 (341) 9 60 50 07
 fax.+49 (341) 9 60 50 92
 mail.   [EMAIL PROTECTED]
 web.www.vub.de
 
 HRB Köln 24015
 UStID DE 122 649 251
 GF Dr. Achim Preuss Neudorf,
 Dr. Christian Preuss Neudorf
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

RE: Maven Reporting - DashBoard-Maven-Plugin

[nicklist]

Try:

mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard

or whatever version you're using.

With regards,

Nick Stolwijk



-Original Message-
From: Nagesh, Srinivas (IS Consultant) [mailto:[EMAIL PROTECTED]
Sent: Thu 2/7/2008 4:03 PM
To: Maven Users List
Subject: RE: Maven Reporting - DashBoard-Maven-Plugin
 
I did... the second command never worked... it complains that it cannot find 
the dashboard-report plugin. I even set up the repository as mentioned and it 
downloaded while generating site... but the second command doesn't work.

Thanks

Srinivas
x3126

-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 10:00 AM
To: Maven Users List
Subject: Re: Maven Reporting - DashBoard-Maven-Plugin

Quote:
To generate the site and the correct dashboard report, you must run the 
dashboard report plugin in 2 passes :
# mvn site
# mvn dashboard-report:dashboard

You should execute these two commands on the command line.

regards,

Stefan

Nagesh, Srinivas (IS Consultant) wrote:
 Hi Stefan,
 
 Thanks for your response.
 
 As you mentioned I am looking for a common report.When I try using the 
 dashboard-maven-plugin, I ran into the following problem
 
 I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
 
 1. Placed the dashboard plugin at the very end of the reporting tag.
 2. Ran Maven Site. This actually generated the report before the findbugs 
 plugin is executed. Shouldnt it supposed to run it at the last when all the 
 other plugins have finished generating their reports?
 3. Also as mentioned in the site above, what does this mean? add the 
 dashboard report item in the left menu.
 
 Would you happen to have a working example of the dashboard-maven-plugin?
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 2:46 AM
 To: Maven Users List
 Subject: Re: Maven Reporting
 
 Hi,
 
 you may consolidate single reports for all modules (like Javadoc, JXR, 
 ...) using the aggregate feature of these reports. The question is, 
 what do you really want to do? Your modules have different names for 
 example, how do you consolidate that?
 
 If you are looking for a common report on JUnit tests, Checkstyle, 
 Findbugs etc. have a look at the dashboard-maven-plugin.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi All,

 I have a multi-project setup in maven

 -- Proj
 -- pom.xml -- Reporting
 -- Proj1
 -- pom.xml
 -- Proj2
 -- pom.xml

 When I specify reporting in the parent pom, the reports are generated in
 the respective children projects. I would like to know if there is a
 feature to create a consolidated report of the sub project (Proj1 
 Proj2)?

 Thanks

 Srini

 

-- 
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

-
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: maven eclipse plugin workspace dependencies resolution

[da Costa Oliveira, Pedro Manuel]

Refreshes are configured.
I tried your suggestion, but .. No luck ;) 

-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED] 
Sent: jeudi, 7. février 2008 16:39
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution

It appears there are still some bugs. My colleague suggests adding the 
parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this 
will fix your problems...

He also suggests setting some (if not most) of these properties inside your 
POM instead of in the launch.

One point I have to add: make sure eclipse refreshes the projects after your 
build, that could cause this kind of behavior as well!

If nothing else works, you'd have to wait until the release, but I believe 
that will happen pretty soon.


On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
 Hi,

 I'm running it from inside eclipse.

 I've tried using
 org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
 eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
 -Declipse.workspaceToConnect=${workspace_loc}
 -Declipse.useProjectReferences=true
 -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

 org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
 -X eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
 -Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk 
 -Declipse.useProjectReferences=true
 -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

 And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
 doesn't add the workspace projects as project dependencies.

 For a lot of reasons, my projects are not set up as module projects (don't
 know if that makes any difference in this case). I just want that if my
 project - webservices - dependes on - common - and common is in the
 workspace, that it is added to the webservices project library as a project
 dependency (can debug easily any changes done to dependant projects) and
 not as an artifact dependency.

 Thanks a lot,
 Pedro

 -Original Message-
 From: Roland Asmann [mailto:[EMAIL PROTECTED]
 Sent: jeudi, 7. février 2008 16:06
 To: Maven Users List
 Subject: Re: maven eclipse plugin workspace dependencies resolution

 I asked my colleague, it could be that the parameter has changed. He
 suggests trying 'eclipse.workspace'.

 I presume you are running Maven from inside Eclipse, right? Or filling out
 the correct path instead of '${workspace_loc}', because that is an
 Eclipse-variable! (Forgot to mention that before, sorry!)

 On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
  I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
  Shouldn't it contain the latest code/fixes?
 
  -Original Message-
  From: Roland Asmann [mailto:[EMAIL PROTECTED]
  Sent: jeudi, 7. février 2008 15:58
  To: Maven Users List
  Subject: Re: maven eclipse plugin workspace dependencies resolution
 
  I happen to know a little bit about this (mainly because my colleague
  created these options ;-) ).
 
  I believe that version of the plugin hasn't been released yet, although
  it could be that a SNAPSHOT-release has been made. If not, check out the
  latest sources and build it for yourself, it should work like a charm!
 
  On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
   Hi All,
  
   I'm trying to find a better way of using maven and eclipse in my team
   (m2eclipse just creates to many problems with transient dependencies,
   even in 0.0.12).
  
   So .. while trying to use maven-eclipse-plugin, I came across the
   -Declipse.workspaceToConnect=${workspace_loc}  option
   in http://jira.codehaus.org/browse/MECLIPSE-344.
  
   I've tried to use it so that the project dependencies inside my eclipse
   would be resolved and added to my library path.
   However that is not working, it still resolves the artifact jar in my
   local repository.
  
   Has anyone been able to make this work?
  
   Regards,
  
   Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
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: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released

[Donnchadh Ó Donnabháin]

Good work Haroon, Thanks for the information.
In my case I'm getting the error on the command line.
My project has numerous subprojects and the error only occurs several
projects into the build so it will take some time to create a minimal
test case.

  Donnchadh

On 07/02/2008, Haroon Rafique [EMAIL PROTECTED] wrote:
 On Today at 3:30pm, DD=Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote:

 DD   Hi Dan,
 DD
 DD When I switch from surefire 2.4 to 2.4.1 I get the error below.
 DD /tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what
 DD might be causing this?
 DD

 Not knowing much about surefirebooter, I can at least tell you
 (paraphrasing here) that the /tmp/surefirebooter*.jar files are created at
 runtime and then deleted when the test is over. If you run with mvn -X,
 the /tmp/surefirebooter*.jar will be left in tact to aid in the debugging
 process.

 For me when the error about Failed to load Main-Class manifest attribute
 from /tmp/surefirebooter???.jar appeared, I re-ran the tests with mvn -X
 and then opened up the /tmp/surefirebooter???.jar file. It is a .jar file
 with only one entry META-INF/MANIFEST.MF. Inside the MANIFEST.MF there are
 2 entries. Class-Path and Main-Class. Sure enough, the file was in tact,
 yet surefirebooter would say it can't find the Main-Class. You can even
 try the actual java -jar /tmp/surebooter???.jar . command and it
 still failed.

 Looking a little bit more, I was able to extract the MANIFEST.MF file and
 change its format from dos to unix in vim and repackaged it back into
 a jar and sure enough the java -jar /tmp/surefirebooter???.jar .
 command was able to run.

 This is as far as I've gotten so far.

 Two other data points:

 1) Problems are fixed when dropping jdk to 1.5.0_14
 2) Problem only appears running inside cruisecontrol (not on the command
line)

 I would be tempted to file a jira but my project is pretty big and I'm
 finding it absolutely difficult to localize the issue so that I can
 present a minimal test case.

 So, with the information that I have provided to you so far, hopefully you
 can provide a minimal test case :-) (or at least, I can wish).

 Regards,
 --
 Haroon Rafique
 [EMAIL PROTECTED]




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

Couldn't find a version in [2.0.0] to match range [1.0,2.0)

[Martin Funk]

Hi,

I'm trying to build geronimos daytrader application.
http://svn.apache.org/repos/asf/geronimo/daytrader/trunk

As I run 'mvn install' this comes up:

Couldn't find a version in [2.0.0] to match range [1.0,2.0)
  org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
  codehaus-snapshots (http://snapshots.repository.codehaus.org),
  apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)


What is this message trying to tell me? I understand that in the
pom.xmlthere is a dependency given on the geronimo-jaxrpc module in
the range of [
1.0, 2.0)
What I don't understand is that maven is not finding any version within that
range, since there are such modules present in the repository?

Can someone please give me a hint?

Martin

Javadoc plugin issues again

[Alexander Sack]

Hi All:
I'm trying to wrap up our build process and I'm having again more trouble
with the javadoc plugin (v2.3).  I have a multi module project organized:

pom.xml
module1
  pom.xml
module2
  pom.xml
etc.

In module1 (first one compiled, etc.), I have a simple pom that specifies
some dependencies for a jar module.  I've added to it:

reporting
plugins
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
debugtrue/debug
verbosetrue/verbose
/configuration
  /plugin
/plugins
  /reporting

Note:  FAQ mentions debug, Usage mentions verbose, I included both

When I run mvn javadoc:javadoc, Velocity starts but NO javadoc is generated.
 Do I have to specify something in the configuration that translates to the
@packages that gets passed to javadoc commandline Maven executes?  Has
anyone seen this before (the build is completely SUCCESSFUL minus the
javadoc stage).

I faced this once before and had to use the site build phase to get it to
go but I really want to avoid it (it generates a lot of unnecessary files).

Thanks!

-aps

-- 
What lies behind us and what lies in front of us is of little concern to
what lies within us. -Ralph Waldo Emerson

Re: Couldn't find a version in [2.0.0] to match range [1.0,2.0)

[Wayne Fay]

I know they've been working on their applications lately as we've had another 
question or two recently on this list related to bugs in their code/samples.

Please ask them directly (Geronimo Dev) why its not working.

(Looking at the error message, it seems like there is a dependency on 2.0.0 
coming from somewhere, but this module specifies [1.0, 2.0) which means that 
2.0.0 is not acceptable.)

Wayne

On 2/7/08, Martin Funk [EMAIL PROTECTED] wrote:
 Hi,
 
 I'm trying to build geronimos daytrader application.
 http://svn.apache.org/repos/asf/geronimo/daytrader/trunk
 
 As I run 'mvn install' this comes up:
 
 Couldn't find a version in [2.0.0] to match range [1.0,2.0)
   org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
 
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
   apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository),
   codehaus-snapshots (http://snapshots.repository.codehaus.org),
   apache-incubator (http://people.apache.org/repo/m2-incubating-repository/)
 
 
 What is this message trying to tell me? I understand that in the
 pom.xmlthere is a dependency given on the geronimo-jaxrpc module in
 the range of [
 1.0, 2.0)
 What I don't understand is that maven is not finding any version within that
 range, since there are such modules present in the repository?
 
 Can someone please give me a hint?
 
 Martin
 

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

Re: surefire 2.4 + testng, changing TestSuite name

[Erez Nahir]

Created http://jira.codehaus.org/browse/SUREFIRE-452 and provided fix for it
as attachment.

Can someone from surefire team clarify when is the next minor release of
surefire-plugin planned?

Thanks,
Erez.

On Feb 6, 2008 11:37 PM, Erez Nahir [EMAIL PROTECTED] wrote:

 Hi,

 I'm looking for a way to change the default suite name generated by
 surefire from TestSuite to something else.
 Using this configuration:
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-surefire-plugin/artifactId
 version2.4.1/version
 configuration
 groupsfast/groups
 excludedgroupsbroken/excludedgroups
 properties
 property
 namesuitename/name
 value${groupId}-${artifactId}/value
 /property
 property
 nametestname/name
 value${artifactId}/value
 /property
 /properties
 /configuration
 /plugin

 The suitename is changed in testng reports, but in the default
 TEST-TestSuite.xml files, it is not.
 Any way to do it?

 Thanks,
 Erez.

Re: tests throw java.lang.NoClassDefFoundError for MVN, JUnit 4 but not eclipse

[JavaGeek]

Thank you so much Nicole.  
When you say:  
Nicole Lacoste wrote:
 
 One thing is that all classes are required to have
 public constructors with either no-arg or String name. There are probably
 also requirements on public methods.  

I think you're right.  How did you figure this out?  Also, did you mean the
classes tested or the unit tests themselves?

Thanks so much,
Steven



-- 
View this message in context: 
http://www.nabble.com/tests-throw-java.lang.NoClassDefFoundError-for-MVN%2C-JUnit-4-but-not-eclipse-tp15309895s177p15340368.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Couldn't find a version in [2.0.0] to match range [1.0,2.0)

[Martin Funk]

As I read it its not a dependecy coming form somewhere, but its a list of
available versions.
Maybe I'm wrong.
But following my assumption I find:
http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-jaxrpc_1.1_spec/maven-metadata.xml
which claims that there is only version 2.0.0 available, though there are
the other directories too.

So is that a bug or is it just a convention to 'deprecate' or 'delete'
versions in the repository?

Martin

2008/2/7, Wayne Fay [EMAIL PROTECTED]:

 I know they've been working on their applications lately as we've had
 another question or two recently on this list related to bugs in their
 code/samples.

 Please ask them directly (Geronimo Dev) why its not working.

 (Looking at the error message, it seems like there is a dependency on
 2.0.0 coming from somewhere, but this module specifies [1.0, 2.0) which
 means that 2.0.0 is not acceptable.)

 Wayne

 On 2/7/08, Martin Funk [EMAIL PROTECTED] wrote:
  Hi,
 
  I'm trying to build geronimos daytrader application.
  http://svn.apache.org/repos/asf/geronimo/daytrader/trunk
 
  As I run 'mvn install' this comes up:
 
  Couldn't find a version in [2.0.0] to match range [1.0,2.0)
org.apache.geronimo.specs:geronimo-jaxrpc_1.1_spec:jar:null
 
  from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository
 ),
apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository
 ),
codehaus-snapshots (http://snapshots.repository.codehaus.org),
apache-incubator (
 http://people.apache.org/repo/m2-incubating-repository/)
 
 
  What is this message trying to tell me? I understand that in the
  pom.xmlthere is a dependency given on the geronimo-jaxrpc module in
  the range of [
  1.0, 2.0)
  What I don't understand is that maven is not finding any version within
 that
  range, since there are such modules present in the repository?
 
  Can someone please give me a hint?
 
  Martin
 

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

Re: tests throw java.lang.NoClassDefFoundError for MVN, JUnit 4 but not eclipse

[Martin Gainty]

depends on the return value from the factory
Since the return type is a serializable bean If you want to look at
reference for Serializable Beans I encourage you to read
http://java.sun.com/docs/books/tutorial/javabeans/persistence/index.html

M-

- Original Message -
From: JavaGeek [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, February 07, 2008 1:42 PM
Subject: Re: tests throw java.lang.NoClassDefFoundError for MVN, JUnit 4 but
not eclipse



 Thank you so much Nicole.
 When you say:
 Nicole Lacoste wrote:
 
  One thing is that all classes are required to have
  public constructors with either no-arg or String name. There are
probably
  also requirements on public methods.

 I think you're right.  How did you figure this out?  Also, did you mean
the
 classes tested or the unit tests themselves?

 Thanks so much,
 Steven



 --
 View this message in context:
http://www.nabble.com/tests-throw-java.lang.NoClassDefFoundError-for-MVN%2C-
JUnit-4-but-not-eclipse-tp15309895s177p15340368.html
 Sent from the Maven - Users mailing list archive at Nabble.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: conditional dependencies

[Stephen Connolly]

The problem I see with conditional dependencies is that they define the
dependencies that Maven needs in order to build/test the artifact.

So if I do a build on java6, my conditional dependencies will exclude
javax.activation...

I assume the Release/deploy plugins will upload the effective pom for my
build environment, which does not include javax.activation...

Now you come along and depend on my artifact, but are building with java5...
so you do not receive the conditional dependency.

On the other hand if the release/deploy plugins upload the pom and it's
profile definitions, Maven is going to have to re-detect the profile
activation to determine the transitive dependencies (Which I don't thinkk it
does)

-Stephen

On Feb 5, 2008 8:20 AM, SlinnHawkins, Jon (ELS-CAM) 
[EMAIL PROTECTED] wrote:

 Hi Jorg

 Yeah just set up profiles for Java5 and java6 each specifying the unique
 dependencies for the jdk.

 Jon

 -Original Message-
 From: Joerg Hohwiller [mailto:[EMAIL PROTECTED]
 Sent: 04 February 2008 21:13
 To: Maven Users List
 Subject: conditional dependencies

 Hi there,

 I am using conditional dependencies in the form that I use variables in
 the dependencies and profiles to set these variables.

 Now I currently wonder what to do if a dependency is only required under
 specific situations. E.g. stax or jsr250 is included in java6 while you
 need dependencies on external artifacts for java5.
 Has someone experience with that?
 Is it best to use a variable for the scope and set it to provided for
 java6?
 Or is it possible to add a dependency into the profile section?

 Thanks
   Jörg

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



 This email is from Elsevier Limited, a company registered in England and
 Wales with company number 1982084,
 whose registered office is The Boulevard, Langford Lane, Kidlington,
 Oxford, OX5 1GB, United Kingdom.


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

Maven ... Eclipse ... Antrun Plugin

[Hoying, Ken]

I have a antrun plugin set up in my POM file which does not specify a
goal as I want to run it on demand only.  When executing from the
command line everything works as expected.  However, if I attempt to run
any goals on the POM from within Eclipse using an External Builder to
initiate the command line execution, I get the following error:

[INFO] Failed to construct build plan for:
com.premierinc:scaEar:ear:1.0-SNAPSHOT (  task-segment: [package] ).
Reason: 

No lifecycle phase binding can be found for goal: run,
specified as a part of the execution: defaultin plugin:
org.apache.maven.plugins:maven-antrun-plugin

This plugin was resolved successfully.
However, the mojo metadata it contains does not specify a default
lifecycle phase binding.

Please provide a valid phase/ specification for execution: default
in plugin: org.apache.maven.plugins:maven-antrun-plugin


Has anyone seen this before or have a resolution to the issue?  I am not
sure why this would occur.  It seems that Eclipse is juts initiating the
same thing that I am from the command line.  So why would maven behave
differently?

Thanks in advance,
Ken Hoying





-
***Note:The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify the Sender
immediately by replying to the message and deleting it from your
computer. Thank you. Premier Inc.  

Missing 'scm' element in the POM.

[Jan Nielsen]

In Continuum 1.1, installed as a WAR in GlassFish 9.1ur1 on Windows, I
have a multi-module Maven 2 POM being uploaded with a POM Url:

  file:///c:/dev/myproj/trunk/pom.xml

with appropriate username, password, Defined by POM project group,
and a checked load only root as recursive build and the default
build definition template (Default). I have enabled file scheme;
svn.exe is part of the %PATH%; and the pom.xml has the following scm
element (sub-modules do not have an SCM element):

  scm
connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection

developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection
urlhttp://xxx.xxx.xxx/view/myproj/trunk//url
  /scm

The build from CLI with Maven 2.0.8 works fine, including the site
goal which uses the scm element data successfully in the StatScm
plugin; and this POM is successfully executed by Continuum 1.0.3 on
Tomcat 6.0 instance to build everything including the site goal which
includes the StatScm plugin.

I found a few relevant other posts like:

  http://www.nabble.com/trouble-adding-Maven-2.0-pom-td13778433.html#a13778433

but in myproj is, in fact, in Subversion and the SCM URLs appear to
be correct.

Any ideas?


Thanks,

-Jan

Re: ClearCase UCM baseline release before bumping version

[janee]

I have found a way to use maven to create both a release baseline
(non-SNAPSHOT) and a new development baseline.  It isn't pretty and I'd
still like to know if there's a simpler way.

Here are the steps I followed to release version and 1.0.1 and start work on
1.0.2-SNAPSHOT:

1) Create a ClearCase UCM activity in an up to date development view with no
checkouts.
 
2) Run mvn release:prepare specifying the same release version number for
both release and new development (1.0.1). The second round of commits will
fail, but that's okay.
 
3) Undo checkouts, deliver release POMs and baseline (do NOT run
release:clean).
 
4) Run mvn release:rollback to restore the original development version
(1.0.1-SNAPSHOT).
 
5) Run mvn release:prepare specifying the release version (1.0.1) and the
desired new development version (1.0.2-SNAPSHOT). Be sure to select a new
tag label.
 
6) Deliver new development POMs, baseline and recommend the baseline for new
development.

It seems to me that scm:tag should be able to deliver and baseline the
ClearCase project when using ClearCase UCM. Perhaps this could be an option.


janee wrote:
 
 Is there a way to configure release:prepare to deliver and baseline the
 release POMs after it commits and tags them and before it bumps the POMs
 to the new development version and commits them? I am using ClearCase LT
 UCM on Windows. 
 

-- 
View this message in context: 
http://www.nabble.com/ClearCase-UCM-baseline-release-before-bumping-version-tp15312730s177p15338144.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

RE: maven eclipse plugin workspace dependencies resolution

[da Costa Oliveira, Pedro Manuel]

Hi,

I'm running it from inside eclipse.

I've tried using 
org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true 
-Declipse.workspaceToConnect=${workspace_loc} 
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
-X eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true 
-Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk  
-Declipse.useProjectReferences=true
-Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

And replacing eclipse.workspaceToConnect with eclipse.workspace. It still 
doesn't add the workspace projects as project dependencies.

For a lot of reasons, my projects are not set up as module projects (don't know 
if that makes any difference in this case).
I just want that if my project - webservices - dependes on - common - and 
common is in the workspace, 
that it is added to the webservices project library as a project dependency 
(can debug easily any changes done to dependant projects) and not as an 
artifact dependency.

Thanks a lot,
Pedro

-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED] 
Sent: jeudi, 7. février 2008 16:06
To: Maven Users List
Subject: Re: maven eclipse plugin workspace dependencies resolution

I asked my colleague, it could be that the parameter has changed. He suggests 
trying 'eclipse.workspace'.

I presume you are running Maven from inside Eclipse, right? Or filling out the 
correct path instead of '${workspace_loc}', because that is an 
Eclipse-variable! (Forgot to mention that before, sorry!)


On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
 I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
 Shouldn't it contain the latest code/fixes?

 -Original Message-
 From: Roland Asmann [mailto:[EMAIL PROTECTED]
 Sent: jeudi, 7. février 2008 15:58
 To: Maven Users List
 Subject: Re: maven eclipse plugin workspace dependencies resolution

 I happen to know a little bit about this (mainly because my colleague
 created these options ;-) ).

 I believe that version of the plugin hasn't been released yet, although it
 could be that a SNAPSHOT-release has been made. If not, check out the
 latest sources and build it for yourself, it should work like a charm!

 On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
  Hi All,
 
  I'm trying to find a better way of using maven and eclipse in my team
  (m2eclipse just creates to many problems with transient dependencies,
  even in 0.0.12).
 
  So .. while trying to use maven-eclipse-plugin, I came across the
  -Declipse.workspaceToConnect=${workspace_loc}  option
  in http://jira.codehaus.org/browse/MECLIPSE-344.
 
  I've tried to use it so that the project dependencies inside my eclipse
  would be resolved and added to my library path.
  However that is not working, it still resolves the artifact jar in my
  local repository.
 
  Has anyone been able to make this work?
 
  Regards,
 
  Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

-
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: maven eclipse plugin workspace dependencies resolution

[Roland Asmann]

It appears there are still some bugs. My colleague suggests adding the 
parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this 
will fix your problems...

He also suggests setting some (if not most) of these properties inside your 
POM instead of in the launch.

One point I have to add: make sure eclipse refreshes the projects after your 
build, that could cause this kind of behavior as well!

If nothing else works, you'd have to wait until the release, but I believe 
that will happen pretty soon.


On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
 Hi,

 I'm running it from inside eclipse.

 I've tried using
 org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
 eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
 -Declipse.workspaceToConnect=${workspace_loc}
 -Declipse.useProjectReferences=true
 -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

 org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
 -X eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
 -Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk 
 -Declipse.useProjectReferences=true
 -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml

 And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
 doesn't add the workspace projects as project dependencies.

 For a lot of reasons, my projects are not set up as module projects (don't
 know if that makes any difference in this case). I just want that if my
 project - webservices - dependes on - common - and common is in the
 workspace, that it is added to the webservices project library as a project
 dependency (can debug easily any changes done to dependant projects) and
 not as an artifact dependency.

 Thanks a lot,
 Pedro

 -Original Message-
 From: Roland Asmann [mailto:[EMAIL PROTECTED]
 Sent: jeudi, 7. février 2008 16:06
 To: Maven Users List
 Subject: Re: maven eclipse plugin workspace dependencies resolution

 I asked my colleague, it could be that the parameter has changed. He
 suggests trying 'eclipse.workspace'.

 I presume you are running Maven from inside Eclipse, right? Or filling out
 the correct path instead of '${workspace_loc}', because that is an
 Eclipse-variable! (Forgot to mention that before, sorry!)

 On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
  I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
  Shouldn't it contain the latest code/fixes?
 
  -Original Message-
  From: Roland Asmann [mailto:[EMAIL PROTECTED]
  Sent: jeudi, 7. février 2008 15:58
  To: Maven Users List
  Subject: Re: maven eclipse plugin workspace dependencies resolution
 
  I happen to know a little bit about this (mainly because my colleague
  created these options ;-) ).
 
  I believe that version of the plugin hasn't been released yet, although
  it could be that a SNAPSHOT-release has been made. If not, check out the
  latest sources and build it for yourself, it should work like a charm!
 
  On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
   Hi All,
  
   I'm trying to find a better way of using maven and eclipse in my team
   (m2eclipse just creates to many problems with transient dependencies,
   even in 0.0.12).
  
   So .. while trying to use maven-eclipse-plugin, I came across the
   -Declipse.workspaceToConnect=${workspace_loc}  option
   in http://jira.codehaus.org/browse/MECLIPSE-344.
  
   I've tried to use it so that the project dependencies inside my eclipse
   would be resolved and added to my library path.
   However that is not working, it still resolves the artifact jar in my
   local repository.
  
   Has anyone been able to make this work?
  
   Regards,
  
   Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

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

Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released

[Haroon Rafique]

On Today at 3:30pm, DD=Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote:

DD   Hi Dan,
DD 
DD When I switch from surefire 2.4 to 2.4.1 I get the error below.
DD /tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what
DD might be causing this?
DD 
DD   Thanks
DD 
DD Donnchadh
DD 

Funny that you mention that. It happens for me too on jdk 1.6.0_04 but 
only when running under cruisecontrol. I'm on maven 2.0.8, surefire 2.4.

Later,
--
Haroon Rafique
[EMAIL PROTECTED]

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

Re: Updating M2_HOME/conf/settings.xml

[Matthew Tordoff]

Hi Stefan,

The reason that we don't have one master POM as a parent to all other POMs is 
that we have multiple different products, all under independant source control. 
These products may want to have differing master POMs. Also, we will be 
overriding the central repository location in the global settings.xml. Without 
the repository you won't be able to retrieve the master POM.

The solution we have decided upon is to use a software distribution management 
tool from Symantec (LiveState) which can be used to automatically push the 
latest configuration for Maven directly onto developers machines (even upgrade 
Maven itself if necessary). This requires no manual work to be done from the 
developers point of view.

Matt

-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Sent: 07 February 2008 13:42
To: Maven Users List
Subject: Re: Updating M2_HOME/conf/settings.xml

Put maven-install-dir/conf/settings.xml on a shared drive, or replace it with 
a symlink to a shared drive.

Why do you need to change the settings.xml anyway? Could it not be done in a 
master pom that is the parent to all other poms? Then you can simply deploy the 
master pom and you're done.

Stefan

Matthew Tordoff wrote:
 Hi all,
 
 I just wondered if anyone has any best practises for updating the global 
 settings.xml in Maven. I have considered checking the conf folder into SVN, 
 or even potentially checking the whole maven install into SVN, then when 
 changes are made send out an email and people can just do an SVN update to 
 pick up the changes. The only disadvantage of this process is that it relies 
 on people reading their mail and kicking off the update. I would preferably 
 like a method of automatically publishing changes which would automatically 
 update all developers machines.
 
 Any thoughts around this would be greatly appreciated.
 
 Regards,
 
 Matt
 
 P.S. I would also be interested on your views regarding checking in solely 
 the settings.xml file into version control, vs checking in the whole install.
 
 _
 Free games, great prizes - get gaming at Gamesbox. 
 http://www.searchgamesbox.com

--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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



_
Share what Santa brought you
https://www.mycooluncool.com

RE: Maven Reporting - DashBoard-Maven-Plugin

[Nagesh, Srinivas (IS Consultant)]

I did... the second command never worked... it complains that it cannot find 
the dashboard-report plugin. I even set up the repository as mentioned and it 
downloaded while generating site... but the second command doesn't work.

Thanks

Srinivas
x3126

-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 10:00 AM
To: Maven Users List
Subject: Re: Maven Reporting - DashBoard-Maven-Plugin

Quote:
To generate the site and the correct dashboard report, you must run the 
dashboard report plugin in 2 passes :
# mvn site
# mvn dashboard-report:dashboard

You should execute these two commands on the command line.

regards,

Stefan

Nagesh, Srinivas (IS Consultant) wrote:
 Hi Stefan,
 
 Thanks for your response.
 
 As you mentioned I am looking for a common report.When I try using the 
 dashboard-maven-plugin, I ran into the following problem
 
 I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html
 
 1. Placed the dashboard plugin at the very end of the reporting tag.
 2. Ran Maven Site. This actually generated the report before the findbugs 
 plugin is executed. Shouldnt it supposed to run it at the last when all the 
 other plugins have finished generating their reports?
 3. Also as mentioned in the site above, what does this mean? add the 
 dashboard report item in the left menu.
 
 Would you happen to have a working example of the dashboard-maven-plugin?
 
 Thanks
 
 Srinivas
 x3126
 
 -Original Message-
 From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 07, 2008 2:46 AM
 To: Maven Users List
 Subject: Re: Maven Reporting
 
 Hi,
 
 you may consolidate single reports for all modules (like Javadoc, JXR, 
 ...) using the aggregate feature of these reports. The question is, 
 what do you really want to do? Your modules have different names for 
 example, how do you consolidate that?
 
 If you are looking for a common report on JUnit tests, Checkstyle, 
 Findbugs etc. have a look at the dashboard-maven-plugin.
 
 regards,
 
 Stefan
 
 Nagesh, Srinivas (IS Consultant) wrote:
 Hi All,

 I have a multi-project setup in maven

 -- Proj
 -- pom.xml -- Reporting
 -- Proj1
 -- pom.xml
 -- Proj2
 -- pom.xml

 When I specify reporting in the parent pom, the reports are generated in
 the respective children projects. I would like to know if there is a
 feature to create a consolidated report of the sub project (Proj1 
 Proj2)?

 Thanks

 Srini

 

-- 
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

-
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: maven eclipse plugin workspace dependencies resolution

[Roland Asmann]

I asked my colleague, it could be that the parameter has changed. He suggests 
trying 'eclipse.workspace'.

I presume you are running Maven from inside Eclipse, right? Or filling out the 
correct path instead of '${workspace_loc}', because that is an 
Eclipse-variable! (Forgot to mention that before, sorry!)


On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
 I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
 Shouldn't it contain the latest code/fixes?

 -Original Message-
 From: Roland Asmann [mailto:[EMAIL PROTECTED]
 Sent: jeudi, 7. février 2008 15:58
 To: Maven Users List
 Subject: Re: maven eclipse plugin workspace dependencies resolution

 I happen to know a little bit about this (mainly because my colleague
 created these options ;-) ).

 I believe that version of the plugin hasn't been released yet, although it
 could be that a SNAPSHOT-release has been made. If not, check out the
 latest sources and build it for yourself, it should work like a charm!

 On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel wrote:
  Hi All,
 
  I'm trying to find a better way of using maven and eclipse in my team
  (m2eclipse just creates to many problems with transient dependencies,
  even in 0.0.12).
 
  So .. while trying to use maven-eclipse-plugin, I came across the
  -Declipse.workspaceToConnect=${workspace_loc}  option
  in http://jira.codehaus.org/browse/MECLIPSE-344.
 
  I've tried to use it so that the project dependencies inside my eclipse
  would be resolved and added to my library path.
  However that is not working, it still resolves the artifact jar in my
  local repository.
 
  Has anyone been able to make this work?
 
  Regards,
 
  Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

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

Re: Maven Reporting - DashBoard-Maven-Plugin

[VUB Stefan Seidel]

Quote:
To generate the site and the correct dashboard report, you must run the 
dashboard report plugin in 2 passes :

# mvn site
# mvn dashboard-report:dashboard

You should execute these two commands on the command line.

regards,

Stefan

Nagesh, Srinivas (IS Consultant) wrote:

Hi Stefan,

Thanks for your response.

As you mentioned I am looking for a common report.When I try using the 
dashboard-maven-plugin, I ran into the following problem

I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html

1. Placed the dashboard plugin at the very end of the reporting tag.
2. Ran Maven Site. This actually generated the report before the findbugs 
plugin is executed. Shouldnt it supposed to run it at the last when all the 
other plugins have finished generating their reports?
3. Also as mentioned in the site above, what does this mean? add the dashboard 
report item in the left menu.

Would you happen to have a working example of the dashboard-maven-plugin?

Thanks

Srinivas
x3126

-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 2:46 AM

To: Maven Users List
Subject: Re: Maven Reporting

Hi,

you may consolidate single reports for all modules (like Javadoc, JXR, 
...) using the aggregate feature of these reports. The question is, 
what do you really want to do? Your modules have different names for 
example, how do you consolidate that?


If you are looking for a common report on JUnit tests, Checkstyle, 
Findbugs etc. have a look at the dashboard-maven-plugin.


regards,

Stefan

Nagesh, Srinivas (IS Consultant) wrote:

Hi All,

I have a multi-project setup in maven

-- Proj
-- pom.xml -- Reporting
-- Proj1
-- pom.xml
-- Proj2
-- pom.xml

When I specify reporting in the parent pom, the reports are generated in
the respective children projects. I would like to know if there is a
feature to create a consolidated report of the sub project (Proj1 
Proj2)?

Thanks

Srini





--
best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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

Re: Installing Native DLL's into local repository

[VUB Stefan Seidel]

Hi,

Adamson, Eric (DIT) wrote:

I'm working with the JACOB (Java-COM Bridge) library, and would like to
install its artifacts -- JACOB.JAR and JACOB.DLL -- into my local
repository.  Installing the JAR was easy, but I'm unclear on how to
handle the native library.  How does one manage this correctly?


If you can install a JAR, why not a DLL? What exactly doesn't work?



Also, how best to search the list archives?  I'm only finding posts
archived by month ( at
http://mail-archives.apache.org/mod_mbox/maven-users/ ) but no broad
search facility.

http://www.nabble.com/Maven---Users-f178.html

best regards,

Stefan Seidel
software developer

VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.+49 (341) 9 60 50 07
fax.+49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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

Re: Bug in Continuum 1.1-beta-3 ? - goals and profile seem to be locked together

[sebb]

On 07/02/2008, Emmanuel Venisse [EMAIL PROTECTED] wrote:
 If you want different configurations, you have few solutions:
 - Define a profile that use the most recent jdk and configure source/target
 parameters on the compiler plugin in each projects
 - Remove the group build definition and add a new build definition on each
 project linked with a specific profile.

Does not seem possible to remove the group build definition.

However if one adds a new build definition, one can make that the
default for the project.
One can then delete the original group build from the project.

 Emmanuel

 On Feb 7, 2008 1:17 PM, sebb [EMAIL PROTECTED] wrote:

  Just tried updating one of the HttpComponents projects. I changed the
  profile to Java 1.4 for one of the projects, and now they all seem to
  be using 1.4.
 
  Likewise changing the goals for one of the projects affects the other two.
 
  However, changing the notifiers seems to only affect the current project.
 
  Is this tied behaviour correct?
 
  If so, how can we build some projects in the group using 1.4 and some
  using Java 5?
 

How to make Continuum ignore the failed junit tests and continue with the build?

[Tawfik, Sameh E]

1. Even though the build was not complete because of the failed junit
tests in on of the sub modules, Continuum sent an email indicating the
build is successful as follow: 


[continuum] BUILD SUCCESSFUL: MB1C 1.0 - Build Def: default maven2
buildDefinition


In the build output results, the following is displayed:

Results :

Tests in error: 

Tests run: 502, Failures: 0, Errors: 2, Skipped: 0

[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] There are test failures.

Please refer to
C:\Auto_Builds\working-directory\81\mb1c-dataaccess\target\surefire-repo
rts for the individual test results.
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 9 minutes 48 seconds
[INFO] Finished at: Thu Feb 07 12:35:57 PST 2008
[INFO] Final Memory: 18M/48M
[INFO]


2. My project has a parent pom.xml and multiple sub modules, and the
build stops when one of the junit tests fails, so is there is a way
where I can instruct Continuum to ignore the tests results and continue
with the build?

We need to know about all the failed tests from all the modules from a
complete run, instead one at a time.

 Thanks,

Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.

Re: maven eclipse plugin workspace dependencies resolution

[Roland Asmann]

Sorry to hear that. I guess there's nothing left but wait for the next 
release. Although, I could ask my colleague if we have a working copy of that 
plugin and send it to you. You'll have to wait a bit though, 'cause he 
already left. ;-)


On Thursday 07 February 2008 17:33, da Costa Oliveira, Pedro Manuel wrote:
 Refreshes are configured.
 I tried your suggestion, but .. No luck ;)

 -Original Message-
 From: Roland Asmann [mailto:[EMAIL PROTECTED]
 Sent: jeudi, 7. février 2008 16:39
 To: Maven Users List
 Subject: Re: maven eclipse plugin workspace dependencies resolution

 It appears there are still some bugs. My colleague suggests adding the
 parameter 'eclipse.projectDir=${basedir}', although he isn't 100% sure this
 will fix your problems...

 He also suggests setting some (if not most) of these properties inside your
 POM instead of in the launch.

 One point I have to add: make sure eclipse refreshes the projects after
 your build, that could cause this kind of behavior as well!

 If nothing else works, you'd have to wait until the release, but I believe
 that will happen pretty soon.

 On Thursday 07 February 2008 16:25, da Costa Oliveira, Pedro Manuel wrote:
  Hi,
 
  I'm running it from inside eclipse.
 
  I've tried using
  org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
  eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
  -Declipse.workspaceToConnect=${workspace_loc}
  -Declipse.useProjectReferences=true
  -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
 
  org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
  -X eclipse:clean eclipse:eclipse  -Dmaven.test.skip.exec=true
  -Declipse.workspaceToConnect=d:\eclipse_home\workspace\trunk
  -Declipse.useProjectReferences=true
  -Dorg.apache.maven.global-settings=V:\Group\IT\\maven\settings.xml
 
  And replacing eclipse.workspaceToConnect with eclipse.workspace. It still
  doesn't add the workspace projects as project dependencies.
 
  For a lot of reasons, my projects are not set up as module projects
  (don't know if that makes any difference in this case). I just want that
  if my project - webservices - dependes on - common - and common is in the
  workspace, that it is added to the webservices project library as a
  project dependency (can debug easily any changes done to dependant
  projects) and not as an artifact dependency.
 
  Thanks a lot,
  Pedro
 
  -Original Message-
  From: Roland Asmann [mailto:[EMAIL PROTECTED]
  Sent: jeudi, 7. février 2008 16:06
  To: Maven Users List
  Subject: Re: maven eclipse plugin workspace dependencies resolution
 
  I asked my colleague, it could be that the parameter has changed. He
  suggests trying 'eclipse.workspace'.
 
  I presume you are running Maven from inside Eclipse, right? Or filling
  out the correct path instead of '${workspace_loc}', because that is an
  Eclipse-variable! (Forgot to mention that before, sorry!)
 
  On Thursday 07 February 2008 16:00, da Costa Oliveira, Pedro Manuel wrote:
   I'm using maven-eclipse-plugin 2.5-SNAPSHOT.
   Shouldn't it contain the latest code/fixes?
  
   -Original Message-
   From: Roland Asmann [mailto:[EMAIL PROTECTED]
   Sent: jeudi, 7. février 2008 15:58
   To: Maven Users List
   Subject: Re: maven eclipse plugin workspace dependencies resolution
  
   I happen to know a little bit about this (mainly because my colleague
   created these options ;-) ).
  
   I believe that version of the plugin hasn't been released yet, although
   it could be that a SNAPSHOT-release has been made. If not, check out
   the latest sources and build it for yourself, it should work like a
   charm!
  
   On Thursday 07 February 2008 15:49, da Costa Oliveira, Pedro Manuel 
wrote:
Hi All,
   
I'm trying to find a better way of using maven and eclipse in my team
(m2eclipse just creates to many problems with transient dependencies,
even in 0.0.12).
   
So .. while trying to use maven-eclipse-plugin, I came across the
-Declipse.workspaceToConnect=${workspace_loc}  option
in http://jira.codehaus.org/browse/MECLIPSE-344.
   
I've tried to use it so that the project dependencies inside my
eclipse would be resolved and added to my library path.
However that is not working, it still resolves the artifact jar in my
local repository.
   
Has anyone been able to make this work?
   
Regards,
   
Pedro

-- 
Roland Asmann

CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien

Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at

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

Re: jasperreports-maven-plugin chokes on xml

[David C. Hicks]

Good thought, but I was already using 2.0.3.  I did change it to 1.2.5, 
which is what the original Ant build was using, but that didn't make any 
difference, either.


Dan Tran wrote:

this plugin uses 1.2.2 jasperreport, this may be the cause of your
issue.  But you can overide it thou. see doc for details

-D

On Feb 7, 2008 1:54 PM, David C. Hicks [EMAIL PROTECTED] wrote:
  

I'm converting an existing Ant build to Maven, and I've encountered a
sticking point with respect to my Jasper reports.

Though it's not the preferred method for doing headers and footers, our
reports use some imported xml to provide the report header and footer
definitions.  The xml is imported by way of ENTITY tags in the .jrxml
header.  When running one of these guys through the
jasperreports-maven-plugin, I get an error that doesn't really tell me
much.  Here is an example:

Error compiling report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
: headerParms.xml

Using the -e parameter does yield some stack trace indicating an error
in JasperReportsMojo.compile().  I'll include that trace at the end of
the message.  I hope someone has an idea.  Otherwise, I'm stuck with
either re-working all of my reports to use subreports for the headers
and footers or trying to run an Ant build from within my Maven build
(the more likely scenario since time is not on my side).

Thanks in advance for any advice,
Dave

Promised Stack Trace:

org.apache.maven.BuildFailureException: Error compiling report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
   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:324)
   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)
Caused by: org.apache.maven.plugin.MojoFailureException: Error compiling
report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
   at
org.codehaus.mojo.jasperreports.JasperReportsMojo.compile(JasperReportsMojo.java:236)
   at
org.codehaus.mojo.jasperreports.JasperReportsMojo.execute(JasperReportsMojo.java:191)
   at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
   ... 16 more


-
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: How to make Continuum ignore the failed junit tests and continue with the build?

[L. J.]

-Dmaven.tests.ignore.failure=true

On Feb 7, 2008 1:00 PM, Tawfik, Sameh E [EMAIL PROTECTED] wrote:




 1. Even though the build was not complete because of the failed junit
 tests in on of the sub modules, Continuum sent an email indicating the
 build is successful as follow:


 [continuum] BUILD SUCCESSFUL: MB1C 1.0 - Build Def: default maven2
 buildDefinition


 In the build output results, the following is displayed:

 Results :

 Tests in error:

 Tests run: 502, Failures: 0, Errors: 2, Skipped: 0

 [INFO]
 
 [ERROR] BUILD FAILURE
 [INFO]
 
 [INFO] There are test failures.

 Please refer to
 C:\Auto_Builds\working-directory\81\mb1c-dataaccess\target\surefire-repo
 rts for the individual test results.
 [INFO]
 
 [INFO] For more information, run Maven with the -e switch
 [INFO]
 
 [INFO] Total time: 9 minutes 48 seconds
 [INFO] Finished at: Thu Feb 07 12:35:57 PST 2008
 [INFO] Final Memory: 18M/48M
 [INFO]
 

 2. My project has a parent pom.xml and multiple sub modules, and the
 build stops when one of the junit tests fails, so is there is a way
 where I can instruct Continuum to ignore the tests results and continue
 with the build?

 We need to know about all the failed tests from all the modules from a
 complete run, instead one at a time.

  Thanks,

Sameh
 This email and any files transmitted with it are confidential, proprietary
 and intended solely for the individual or entity to whom they are
 addressed.
 If you have received this email in error please delete it immediately.

Re: jasperreports-maven-plugin chokes on xml

[Dan Tran]

this plugin uses 1.2.2 jasperreport, this may be the cause of your
issue.  But you can overide it thou. see doc for details

-D

On Feb 7, 2008 1:54 PM, David C. Hicks [EMAIL PROTECTED] wrote:
 I'm converting an existing Ant build to Maven, and I've encountered a
 sticking point with respect to my Jasper reports.

 Though it's not the preferred method for doing headers and footers, our
 reports use some imported xml to provide the report header and footer
 definitions.  The xml is imported by way of ENTITY tags in the .jrxml
 header.  When running one of these guys through the
 jasperreports-maven-plugin, I get an error that doesn't really tell me
 much.  Here is an example:

 Error compiling report design :
 /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
 : headerParms.xml

 Using the -e parameter does yield some stack trace indicating an error
 in JasperReportsMojo.compile().  I'll include that trace at the end of
 the message.  I hope someone has an idea.  Otherwise, I'm stuck with
 either re-working all of my reports to use subreports for the headers
 and footers or trying to run an Ant build from within my Maven build
 (the more likely scenario since time is not on my side).

 Thanks in advance for any advice,
 Dave

 Promised Stack Trace:

 org.apache.maven.BuildFailureException: Error compiling report design :
 /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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:324)
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)
 Caused by: org.apache.maven.plugin.MojoFailureException: Error compiling
 report design :
 /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
at
 org.codehaus.mojo.jasperreports.JasperReportsMojo.compile(JasperReportsMojo.java:236)
at
 org.codehaus.mojo.jasperreports.JasperReportsMojo.execute(JasperReportsMojo.java:191)
at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more


 -
 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: Error getting POM for 'org.apache.maven.plugins:maven-resources-plugin' from the repository

[nicklist]

My first suggestion would be to version all the plugins you use, maybe in a 
parent pom. Otherwise, builds that work now, will fail in the future, even your 
tags, because of updated plugins. Been there, done that, got the T-shirt.

Hth,

Nick Stolwijk

-Original Message-
From: Joshua Pollak [mailto:[EMAIL PROTECTED]
Sent: Thu 2/7/2008 5:06 PM
To: users@maven.apache.org
Subject: Error getting POM for 
'org.apache.maven.plugins:maven-resources-plugin' from the repository
 
Hello,

Over the last few days this problem has been plaguing my development  
team. At first I thought it was a problem with a specific projects use  
of snapshot plugins and our internal repository cache (Artifactory),  
but I just discovered it is happening on an internal project which is  
not configured to use Artifactory.

--

Project ID: org.apache.maven.plugins:maven-resources-plugin

Reason: Error getting POM for 'org.apache.maven.plugins:maven- 
resources-plugin' from the repository: Failed to resolve artifact,  
possibly due to a repository list that is not appropriately equipped  
for this artifact's metadata.
   org.apache.maven.plugins:maven-resources-plugin:pom:2.3-SNAPSHOT

from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
  for project org.apache.maven.plugins:maven-resources-plugin

--

I've only found two ways to make this problem go away:

1) Everyday, clear both the users ~/.m2/repository directory, and the  
Artifactory cache of plugin snapshots
2) Explicitly set the maven-resources-plugin version to 2.2.

I don't particularly like either option, but we are going with #2 for  
now. Does anyone have any suggestions?

Thanks,

Josh

-- 
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970

Error getting POM for 'org.apache.maven.plugins:maven-resources-plugin' from the repository

[Joshua Pollak]

Hello,

Over the last few days this problem has been plaguing my development  
team. At first I thought it was a problem with a specific projects use  
of snapshot plugins and our internal repository cache (Artifactory),  
but I just discovered it is happening on an internal project which is  
not configured to use Artifactory.


--

Project ID: org.apache.maven.plugins:maven-resources-plugin

Reason: Error getting POM for 'org.apache.maven.plugins:maven- 
resources-plugin' from the repository: Failed to resolve artifact,  
possibly due to a repository list that is not appropriately equipped  
for this artifact's metadata.

  org.apache.maven.plugins:maven-resources-plugin:pom:2.3-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
 for project org.apache.maven.plugins:maven-resources-plugin

--

I've only found two ways to make this problem go away:

1) Everyday, clear both the users ~/.m2/repository directory, and the  
Artifactory cache of plugin snapshots

2) Explicitly set the maven-resources-plugin version to 2.2.

I don't particularly like either option, but we are going with #2 for  
now. Does anyone have any suggestions?


Thanks,

Josh

--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970

XML-RPC Sample Client

[jimmy]

I am trying to run the Sample Client, not familiar with Maven or Java for that 
matter I am having some difficulties. I am able to 'mvn clean install' the 
entire continuum application from the root and then invoke the webapp and that 
all runs fine.

But how would one invoke the Sample Client for XML-RPC? When trying to run in 
with java on the command line I get the following NoClassDefFoundError. Any 
information would be greatly appreciated. Thank you for your help so far.

Jimmy

[EMAIL 
PROTECTED]:~/projects/continuum/continuum-xmlrpc/continuum-xmlrpc-client/target/classes/org/apache/maven/continuum/xmlrpc/client$
 java SampleClient
Exception in thread main java.lang.NoClassDefFoundError: SampleClient (wrong 
name: org/apache/maven/continuum/xmlrpc/client/SampleClient)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)

Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released

[Haroon Rafique]

On Today at 3:30pm, DD=Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote:

DD   Hi Dan,
DD 
DD When I switch from surefire 2.4 to 2.4.1 I get the error below. 
DD /tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what 
DD might be causing this?
DD 

Not knowing much about surefirebooter, I can at least tell you 
(paraphrasing here) that the /tmp/surefirebooter*.jar files are created at 
runtime and then deleted when the test is over. If you run with mvn -X, 
the /tmp/surefirebooter*.jar will be left in tact to aid in the debugging 
process.

For me when the error about Failed to load Main-Class manifest attribute 
from /tmp/surefirebooter???.jar appeared, I re-ran the tests with mvn -X 
and then opened up the /tmp/surefirebooter???.jar file. It is a .jar file 
with only one entry META-INF/MANIFEST.MF. Inside the MANIFEST.MF there are 
2 entries. Class-Path and Main-Class. Sure enough, the file was in tact, 
yet surefirebooter would say it can't find the Main-Class. You can even 
try the actual java -jar /tmp/surebooter???.jar . command and it 
still failed.

Looking a little bit more, I was able to extract the MANIFEST.MF file and 
change its format from dos to unix in vim and repackaged it back into 
a jar and sure enough the java -jar /tmp/surefirebooter???.jar . 
command was able to run.

This is as far as I've gotten so far.

Two other data points:

1) Problems are fixed when dropping jdk to 1.5.0_14
2) Problem only appears running inside cruisecontrol (not on the command 
   line)

I would be tempted to file a jira but my project is pretty big and I'm 
finding it absolutely difficult to localize the issue so that I can 
present a minimal test case.

So, with the information that I have provided to you so far, hopefully you 
can provide a minimal test case :-) (or at least, I can wish).

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

Re: Maven Concepts

[John Casey]

You've got it exactly right.

Maven builds are usually oriented around the concept of a lifecycle,  
which consists of phases in a specific order. Each phase has zero or  
more mojos (usually called goals) bound to it. Each phase in the  
lifecycle implies all of the phases that come before it. This allows  
users to bind (or configure) different goals to different phases of  
the build, then the standard phase names to run the build. The  
default goals for a given type of project are also bound to the  
lifecycle in this way, but behind the scenes, such that the user can  
supplement these default goals using configurations in the pom.xml.


So, if you have a jar project (packagingjar/packaging), you might  
have something like this:


Phase Goals
 ---

validate(none)
initialize   (none)
...
compileorg.apache.maven.plugins:maven-compiler- 
plugin:compile

...
testorg.apache.maven.plugins:maven-surefire- 
plugin:test

...
package  org.apache.maven.plugins:maven-jar-plugin:jar
...
install   org.apache.maven.plugins:maven-install- 
plugin:install

...
etc.

Now, if you just want to compile your project, you simply call the  
'compile' phase, like this:


mvn compile

If you want to run the unit tests, call this:

mvn test

Note that in order to run unit tests, you must have compiled your  
project's main sources. That's handled here, since the test phase is  
later in the lifecycle than the compile phase...'test' implies  
'compile' and all the other phases (in order) that come before 'test'.


On the other hand, Maven also supports certain one-off goals that are  
usually meant to help manage the project build in certain special  
cases, or give information about the build. One such example gives  
you a glimpse of the POM after all inheritance and profile injection  
has been completed:


mvn help:effective-pom

which is shorthand for:

mvn org.apache.maven.plugins:maven-help-plugin:effective-pom


Hope that helps,

-john

On Feb 7, 2008, at 4:50 PM, Dhruva Reddy wrote:


I know this seems like a silly thing to post on here, but...

What exactly is a goal and what is a phase?  I can't find a good  
answer in the documentation and there's a lot of seemingly  
conflicting information out there.


My current understanding is that a phase is a part of a lifecycle  
(process-resources, compile, etc).  A goal is somewhat analogous to  
an ANT-task, but with a focus on what should happen, rather than  
how it is done.


Can someone clear this up for me, giving examples?

Thanks,
Dhruva


---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john

Unable to send emails

[Jakub Kozisek]

Hello,

I want to get sending emails working, but when I'm trying to send validation
emails or notifications, I'm getting this exception:


INFO   | jvm 1| 2008/02/07 15:16:31 |
org.codehaus.plexus.mailsender.MailSenderException: Error while sending the
message.
INFO   | jvm 1| 2008/02/07 15:16:31 |   at
org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(
AbstractJavamailMailSender.java:221)
INFO   | jvm 1| 2008/02/07 15:16:31 |   at
org.codehaus.plexus.redback.xwork.mail.Mailer.sendMessage(Mailer.java:145)
INFO   | jvm 1| 2008/02/07 15:16:31 |   at
org.codehaus.plexus.redback.xwork.mail.Mailer.sendAccountValidationEmail(
Mailer.java:70)
INFO   | jvm 1| 2008/02/07 15:16:31 |   at
org.codehaus.plexus.redback.xwork.action.RegisterAction.resendRegistrationEmail
(RegisterAction.java:207)
...
INFO   | jvm 1| 2008/02/07 15:16:31 |   at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
INFO   | jvm 1| 2008/02/07 15:16:31 | Caused by:
com.sun.mail.smtp.SMTPSendFailedException: 553 5.5.4 [EMAIL PROTECTED]...
Real domain name required for sen
der address
INFO   | jvm 1| 2008/02/07 15:29:39 |   at
com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
INFO   | jvm 1| 2008/02/07 15:29:39 |   at
com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
INFO   | jvm 1| 2008/02/07 15:29:39 |   at
com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
INFO   | jvm 1| 2008/02/07 15:29:39 |   at
org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(
AbstractJavamailMailSender.java:214)
INFO   | jvm 1| 2008/02/07 15:29:39 |   ... 71 more


Any idea how can I set a domain name so Continuum will use it? The OS itself
knows about machine's domain name.

Thank you!

Regards,

Jakub

How to override POM properties from CLI

[Igor Romanov]

Hello,

I have properties in a POM file I need to be able to override with
command line –D option,
to run  build in a different environments. How can I do this? Simple
example below doesn't work
as I expect it should, i.e. test.txt will contain FALSE after running

c:\temp\module mvn -Dtest.result=PASS process-test-resources

What am I doing in a wrong way?

Sample project:
--

module/pom.xml

?xml version=1.0 encoding=UTF-8?
project
  modelVersion4.0.0/modelVersion
  groupIdcom.test/groupId
  artifactIdtest/artifactId
  version1.0/version
  packagingjar/packaging

  properties
  test.resultFAIL/test.result
  /properties

build
testResources
   testResource
   directory${basedir}/src/test/resources/directory
   filteringtrue/filtering
   includes
   include*.txt/include
   /includes
   /testResource
   /testResources
   /build
/project

module/src/test/resources/test.txt

This test ${test.result}

-- 
Igor.

Maven Concepts

[Dhruva Reddy]

I know this seems like a silly thing to post on here, but...

What exactly is a goal and what is a phase?  I can't find a good answer in the 
documentation and there's a lot of seemingly conflicting information out there.

My current understanding is that a phase is a part of a lifecycle 
(process-resources, compile, etc).  A goal is somewhat analogous to an 
ANT-task, but with a focus on what should happen, rather than how it is done.

Can someone clear this up for me, giving examples?

Thanks,
Dhruva

Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released

[Donnchadh Ó Donnabháin]

  Hi Dan,

When I switch from surefire 2.4 to 2.4.1 I get the error below.
/tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what
might be causing this?

  Thanks

Donnchadh


[INFO] Surefire report directory: /home/donnchadh/projects/ ...
/target/surefire-reports
Failed to load Main-Class manifest attribute from
/tmp/surefirebooter22682.jar
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to /home/donnchadh/projects/ ... /target/surefire-reports
for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to /home/donnchadh/projects/ ... /target/surefire-reports
for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:597)
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)
Caused by: org.apache.maven.plugin.MojoFailureException: There are
test failures.

Please refer to /home/donnchadh/projects/ ... /target/surefire-reports
for the individual test results.
at 
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:530)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more

[EMAIL PROTECTED] myproject]$ mvn -version
Maven version: 2.0.8
Java version: 1.6.0_04
OS name: linux version: 2.6.23.14-107.fc8 arch: i386 Family: unix


On 06/02/2008, Dan Fabulich [EMAIL PROTECTED] wrote:

 The Maven team is pleased to announce the release of the Maven Surefire
 Plugin, version 2.4.1

 http://maven.apache.org/plugins/maven-surefire-plugin/

 You can run mvn -up to get the latest version of the plugin, or specify
 the version in your project's plugin configuration:

 plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-surefire-plugin/artifactId
   version2.4.1/version
 /plugin


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

RE: How to make Continuum ignore the failed junit tests and continue with the build?

[Tawfik, Sameh E]

Thanks,

-Original Message-
From: L. J. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 1:11 PM
To: [EMAIL PROTECTED]
Subject: Re: How to make Continuum ignore the failed junit tests and
continue with the build?

-Dmaven.tests.ignore.failure=true

On Feb 7, 2008 1:00 PM, Tawfik, Sameh E [EMAIL PROTECTED]
wrote:




 1. Even though the build was not complete because of the failed junit
 tests in on of the sub modules, Continuum sent an email indicating the
 build is successful as follow:


 [continuum] BUILD SUCCESSFUL: MB1C 1.0 - Build Def: default maven2
 buildDefinition


 In the build output results, the following is displayed:

 Results :

 Tests in error:

 Tests run: 502, Failures: 0, Errors: 2, Skipped: 0

 [INFO]


 [ERROR] BUILD FAILURE
 [INFO]


 [INFO] There are test failures.

 Please refer to

C:\Auto_Builds\working-directory\81\mb1c-dataaccess\target\surefire-repo
 rts for the individual test results.
 [INFO]


 [INFO] For more information, run Maven with the -e switch
 [INFO]


 [INFO] Total time: 9 minutes 48 seconds
 [INFO] Finished at: Thu Feb 07 12:35:57 PST 2008
 [INFO] Final Memory: 18M/48M
 [INFO]



 2. My project has a parent pom.xml and multiple sub modules, and the
 build stops when one of the junit tests fails, so is there is a way
 where I can instruct Continuum to ignore the tests results and
continue
 with the build?

 We need to know about all the failed tests from all the modules from a
 complete run, instead one at a time.

  Thanks,

Sameh
 This email and any files transmitted with it are confidential,
proprietary
 and intended solely for the individual or entity to whom they are
 addressed.
 If you have received this email in error please delete it immediately.


This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.

Re: mvn clean site-deploy doesnt clean the remote site

[Dennis Lundberg]

There is already an issue for this in JIRA:
  http://jira.codehaus.org/browse/MSITE-250

If you want to increase the possibility of it being solved, you should 
vote for that issue.


Rahul Thakur wrote:
I don't think Maven can do this. You will need to delete the site 
manually from the remote machine.


I think this is a common use-case and might be an idea opening a JIRA 
issue for this feature.


Rahul

Savita_p_m wrote:

Hi

mvn clean site-deploy doesn't delete the site on the remote machine 
before

deploying the latest one.
Is there anyway I can do this? Any setting or property would help me to
clean the target folder at remote machine before deploying the new site?

I want to delete the folder before deploying the new one.
Regards
Savita
  


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





--
Dennis Lundberg

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

How does one find out what the SCHEDULES are?

[sebb]

There does not seem to be a way for the ordinary Continuum user to
find out what the schedules are - which makes it difficult to know
which one to pick.

Is this intentional, or is this a bug?

Re: Maven Concepts

[Graham Leggett]

Dhruva Reddy wrote:


What exactly is a goal and what is a phase?


In maven 1, there were only goals, and goals were specific targets that 
were embedded in specific maven plugins, a bit like an ant target.


So the jar plugin would have the jar goal which when run, would jar up 
some classes.


It soon became apparent that this leaves too much up to the end user: 
what if the artifact you are producing isn't a jar, but an ear instead? 
Or a war file? Why should the user have to know or care that they must 
run the ear:ear goal instead of the jar:jar goal?


Enter the phases of the lifecycle in maven 2.

Plugins attach various goals to the various phases in the lifecycles, 
and depending on which phase of the lifecycle you've asked maven to 
complete, all the relevant goals attached to that lifecycle will be run 
up to that phase.


So if you run mvn install (or run all goals in all phases up until 
the 'install' phase), maven figures out for itself that the 
compile:compile goal must run, and the ear:ear goal (because the 
artifact is an ear file), the user no longer needs to care.


So to sum up:

The lifecycle contains a list of phases, and each phase has a goal or 
goals attached to that phase. So running a phase is a convenient way of 
saying run all goals I need to run to make this artifact up to this 
phase, and don't tell me what those goals are, I don't care.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

Deploying a collection of Java class files

[zzzz8]

Maven seems to have support in deploying single file artifacts like jars,
ears, wars, etc.  However, my project requires me to deploy (via FTP) to a
particular directory on a machine all (or a selection) of my Java class
files - i.e. in an exploded form (not jarred).  My project is not a war or
an ear - just regular Java class files.  How can I do this with Maven?  I
can't seem to find any plugin that does this - it seems the deploy plugin
doesn't do this.  There may be an explode plugin, but I don't want the
Manifest file there either - and the explode plugin is only Maven 1.0
compatible...
-- 
View this message in context: 
http://www.nabble.com/Deploying-a-collection-of-Java-class-files-tp15346181s177p15346181.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Missing 'scm' element in the POM.

[Emmanuel Venisse]

do you have scm element defined in the pom stored in your svn?

Emmanuel

On Feb 7, 2008 9:25 PM, Jan Nielsen [EMAIL PROTECTED] wrote:

 In Continuum 1.1, installed as a WAR in GlassFish 9.1ur1 on Windows, I
 have a multi-module Maven 2 POM being uploaded with a POM Url:

  file:///c:/dev/myproj/trunk/pom.xml

 with appropriate username, password, Defined by POM project group,
 and a checked load only root as recursive build and the default
 build definition template (Default). I have enabled file scheme;
 svn.exe is part of the %PATH%; and the pom.xml has the following scm
 element (sub-modules do not have an SCM element):

  scm
connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection

  
 developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection
urlhttp://xxx.xxx.xxx/view/myproj/trunk//url
  /scm

 The build from CLI with Maven 2.0.8 works fine, including the site
 goal which uses the scm element data successfully in the StatScm
 plugin; and this POM is successfully executed by Continuum 1.0.3 on
 Tomcat 6.0 instance to build everything including the site goal which
 includes the StatScm plugin.

 I found a few relevant other posts like:


 http://www.nabble.com/trouble-adding-Maven-2.0-pom-td13778433.html#a13778433

 but in myproj is, in fact, in Subversion and the SCM URLs appear to
 be correct.

 Any ideas?


 Thanks,

 -Jan

Re: Recursive maven projects

[Jules Gosnell]

Patrick Shea patrick at ps1.net writes:

 
 When using a recursive maven project continuum does the right thing by
creating a project for each pom but it
 also means that the checkout will also be repeated for each project even if
it's not needed (ie: pom
 projects usually only contain one file, pom.xml)
 
 So in my case:
 
 pom1.xml
 +pom2.xml
 ++pom3.xml
 
 Continuum will create 3 projects but in my build areas projects 1 and 2 will
also checkout everything from
 project 3.
 
 I can't see an option to limit the checkout to be non recursive for project 1
and 2.
 
 Is there a way?
 
 Patrick
 
 


I have the same problem, but the show-stopper for me is that if I make
a change to a submodule. I find that this causes not only this
submodule and its upstream dependencies to be rebuilt (not just
refreshed), but also the top-level project and it's upstream
dependencies (i.e. all the submodules all over again).

I have only just set up our project in Continuum (1.1) and have been
very pleased with it so far, but this is a problem as our build time
is getting out of hand and I am trying to reduce the time taken
between the submission of a change and notification of
success/failure.

The double build, coupled with the time to update all the unused
submodules in the top-level modules CVS tree (on a slow CVS server) is
killing this aspiration :-(

I could probably move the top-level pom into a directory that is a
sibling to the other submodules, in the hope that it is the cvs update
spotting a change in a submodule which is causing the top-level pom's
project to be rebuilt - then the tlp would no longer physically
contain its submodules - but I would rather come up with less drastic
solution.

Perhaps a list of directories to somehow exclude from the cvs
checkout/update, which could be generated by looking at the modules
list ?

thanks for your time,

Jules

Re: Unable to send emails

[Emmanuel Venisse]

You must set the FROM address in
WEB-INF/classes/META-INF/plexus/application.xml

Emmanuel

On Feb 7, 2008 8:51 PM, Jakub Kozisek [EMAIL PROTECTED] wrote:

 Hello,

 I want to get sending emails working, but when I'm trying to send
 validation
 emails or notifications, I'm getting this exception:

 
 INFO   | jvm 1| 2008/02/07 15:16:31 |
 org.codehaus.plexus.mailsender.MailSenderException: Error while sending
 the
 message.
 INFO   | jvm 1| 2008/02/07 15:16:31 |   at
 org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(
 AbstractJavamailMailSender.java:221)
 INFO   | jvm 1| 2008/02/07 15:16:31 |   at
 org.codehaus.plexus.redback.xwork.mail.Mailer.sendMessage(Mailer.java:145)
 INFO   | jvm 1| 2008/02/07 15:16:31 |   at
 org.codehaus.plexus.redback.xwork.mail.Mailer.sendAccountValidationEmail(
 Mailer.java:70)
 INFO   | jvm 1| 2008/02/07 15:16:31 |   at

 org.codehaus.plexus.redback.xwork.action.RegisterAction.resendRegistrationEmail
 (RegisterAction.java:207)
 ...
 INFO   | jvm 1| 2008/02/07 15:16:31 |   at
 org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
 INFO   | jvm 1| 2008/02/07 15:16:31 | Caused by:
 com.sun.mail.smtp.SMTPSendFailedException: 553 5.5.4 [EMAIL PROTECTED]...
 Real domain name required for sen
 der address
 INFO   | jvm 1| 2008/02/07 15:29:39 |   at
 com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1388)
 INFO   | jvm 1| 2008/02/07 15:29:39 |   at
 com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:959)
 INFO   | jvm 1| 2008/02/07 15:29:39 |   at
 com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:583)
 INFO   | jvm 1| 2008/02/07 15:29:39 |   at
 org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send(
 AbstractJavamailMailSender.java:214)
 INFO   | jvm 1| 2008/02/07 15:29:39 |   ... 71 more
 

 Any idea how can I set a domain name so Continuum will use it? The OS
 itself
 knows about machine's domain name.

 Thank you!

 Regards,

 Jakub

RE: Deploying a collection of Java class files

[William Ferguson]

You can almost certainly do this using the assembly-plugin 

 -Original Message-
 From: 8 [mailto:[EMAIL PROTECTED] 
 Sent: Friday, 8 February 2008 9:30 AM
 To: users@maven.apache.org
 Subject: [***POSSIBLE SPAM***] - Deploying a collection of 
 Java class files - Sender is forged (SPF Fail)
 
 
 Maven seems to have support in deploying single file 
 artifacts like jars, ears, wars, etc.  However, my project 
 requires me to deploy (via FTP) to a particular directory on 
 a machine all (or a selection) of my Java class files - i.e. 
 in an exploded form (not jarred).  My project is not a war or 
 an ear - just regular Java class files.  How can I do this 
 with Maven?  I can't seem to find any plugin that does this - 
 it seems the deploy plugin doesn't do this.  There may be an 
 explode plugin, but I don't want the Manifest file there 
 either - and the explode plugin is only Maven 1.0 compatible...
 --
 View this message in context: 
 http://www.nabble.com/Deploying-a-collection-of-Java-class-fil
 es-tp15346181s177p15346181.html
 Sent from the Maven - Users mailing list archive at Nabble.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: How to override POM properties from CLI

[Wayne Fay]

You should put the properties in different profiles, and then specify
which profile using -Penv1 when running Maven.

Wayne

On 2/7/08, Igor Romanov [EMAIL PROTECTED] wrote:
 Hello,

 I have properties in a POM file I need to be able to override with
 command line –D option,
 to run  build in a different environments. How can I do this? Simple
 example below doesn't work
 as I expect it should, i.e. test.txt will contain FALSE after running

 c:\temp\module mvn -Dtest.result=PASS process-test-resources

 What am I doing in a wrong way?

 Sample project:
 --

 module/pom.xml

 ?xml version=1.0 encoding=UTF-8?
 project
   modelVersion4.0.0/modelVersion
   groupIdcom.test/groupId
   artifactIdtest/artifactId
   version1.0/version
   packagingjar/packaging

   properties
   test.resultFAIL/test.result
   /properties

 build
 testResources
testResource
directory${basedir}/src/test/resources/directory
filteringtrue/filtering
includes
include*.txt/include
/includes
/testResource
/testResources
/build
 /project

 module/src/test/resources/test.txt

 This test ${test.result}

 --
 Igor.


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

Re: Missing 'scm' element in the POM.

[Jan Nielsen]

I do; the pom.xml is identical to my workstation pom.xml. And the same
pom.xml works in Continuum 1.0.3.

On Feb 7, 2008 3:03 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote:
 do you have scm element defined in the pom stored in your svn?

 Emmanuel


 On Feb 7, 2008 9:25 PM, Jan Nielsen [EMAIL PROTECTED] wrote:

  In Continuum 1.1, installed as a WAR in GlassFish 9.1ur1 on Windows, I
  have a multi-module Maven 2 POM being uploaded with a POM Url:
 
   file:///c:/dev/myproj/trunk/pom.xml
 
  with appropriate username, password, Defined by POM project group,
  and a checked load only root as recursive build and the default
  build definition template (Default). I have enabled file scheme;
  svn.exe is part of the %PATH%; and the pom.xml has the following scm
  element (sub-modules do not have an SCM element):
 
   scm
 connectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/connection
 
   
  developerConnectionscm:svn:svn://xxx.xxx.xxx.xxx/myproj/trunk/developerConnection
 urlhttp://xxx.xxx.xxx/view/myproj/trunk//url
   /scm
 
  The build from CLI with Maven 2.0.8 works fine, including the site
  goal which uses the scm element data successfully in the StatScm
  plugin; and this POM is successfully executed by Continuum 1.0.3 on
  Tomcat 6.0 instance to build everything including the site goal which
  includes the StatScm plugin.
 
  I found a few relevant other posts like:
 
 
  http://www.nabble.com/trouble-adding-Maven-2.0-pom-td13778433.html#a13778433
 
  but in myproj is, in fact, in Subversion and the SCM URLs appear to
  be correct.
 
  Any ideas?
 
 
  Thanks,
 
  -Jan
 

Re: jasperreports-maven-plugin chokes on xml

[Dan Tran]

file a jira with a producable jrxml, i will give it a try

thanks

On Feb 7, 2008 2:37 PM, David C. Hicks [EMAIL PROTECTED] wrote:
 Good thought, but I was already using 2.0.3.  I did change it to 1.2.5,
 which is what the original Ant build was using, but that didn't make any
 difference, either.


 Dan Tran wrote:
  this plugin uses 1.2.2 jasperreport, this may be the cause of your
  issue.  But you can overide it thou. see doc for details
 
  -D
 
  On Feb 7, 2008 1:54 PM, David C. Hicks [EMAIL PROTECTED] wrote:
 
  I'm converting an existing Ant build to Maven, and I've encountered a
  sticking point with respect to my Jasper reports.
 
  Though it's not the preferred method for doing headers and footers, our
  reports use some imported xml to provide the report header and footer
  definitions.  The xml is imported by way of ENTITY tags in the .jrxml
  header.  When running one of these guys through the
  jasperreports-maven-plugin, I get an error that doesn't really tell me
  much.  Here is an example:
 
  Error compiling report design :
  /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
  : headerParms.xml
 
  Using the -e parameter does yield some stack trace indicating an error
  in JasperReportsMojo.compile().  I'll include that trace at the end of
  the message.  I hope someone has an idea.  Otherwise, I'm stuck with
  either re-working all of my reports to use subreports for the headers
  and footers or trying to run an Ant build from within my Maven build
  (the more likely scenario since time is not on my side).
 
  Thanks in advance for any advice,
  Dave
 
  Promised Stack Trace:
 
  org.apache.maven.BuildFailureException: Error compiling report design :
  /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
 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:324)
 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)
  Caused by: org.apache.maven.plugin.MojoFailureException: Error compiling
  report design :
  /home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
 at
  org.codehaus.mojo.jasperreports.JasperReportsMojo.compile(JasperReportsMojo.java:236)
 at
  org.codehaus.mojo.jasperreports.JasperReportsMojo.execute(JasperReportsMojo.java:191)
 at
  org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
 at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
 ... 16 more
 
 
  -
  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]



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

RE: How to make Continuum ignore the failed junit tests and continue with the build?

[Tawfik, Sameh E]

Unfortunately, the -Dmaven.tests.ignore.failure=true parameter does
not seem to have any effect on the build!

So, is there is something I need to define in pom.xml to activate this
feature, or something else?

I'm using:

Maven version: 2.0.7
Java version: 1.6.0_01
Os name: Windows 2003 version 5.2 arch: x86

I tried both -Dmaven.tests.ignore.failure=true and
-Dmaven.test.ignore.failure=true -- No S after test.

But, neither one made any difference. I run a test from the command line
as follow: 

mvn -Dmaven.tests.ignore.failure=true install
Also, I run:
mvn -Dmaven.test.ignore.failure=true install

In both cases the output as follow:
Tests in error:
  testRegExport(com.fairisaac.mb.adcds.engine.model.export.TestPMML)

Tests run: 184, Failures: 0, Errors: 15, Skipped: 0

[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] There are test failures.

Please refer to
C:\Auto_Builds\working-directory\81\mbpa-adcds\target\surefire-reports
for the individual test results.
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 56 seconds
[INFO] Finished at: Thu Feb 07 16:27:51 PST 2008
[INFO] Final Memory: 9M/17M
[INFO]


   Sameh

-Original Message-
From: Tawfik, Sameh E [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 1:32 PM
To: [EMAIL PROTECTED]
Subject: RE: How to make Continuum ignore the failed junit tests and
continue with the build?


Thanks,

-Original Message-
From: L. J. [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 07, 2008 1:11 PM
To: [EMAIL PROTECTED]
Subject: Re: How to make Continuum ignore the failed junit tests and
continue with the build?

-Dmaven.tests.ignore.failure=true

On Feb 7, 2008 1:00 PM, Tawfik, Sameh E [EMAIL PROTECTED]
wrote:




 1. Even though the build was not complete because of the failed junit
 tests in on of the sub modules, Continuum sent an email indicating the
 build is successful as follow:


 [continuum] BUILD SUCCESSFUL: MB1C 1.0 - Build Def: default maven2
 buildDefinition


 In the build output results, the following is displayed:

 Results :

 Tests in error:

 Tests run: 502, Failures: 0, Errors: 2, Skipped: 0

 [INFO]


 [ERROR] BUILD FAILURE
 [INFO]


 [INFO] There are test failures.

 Please refer to

C:\Auto_Builds\working-directory\81\mb1c-dataaccess\target\surefire-repo
 rts for the individual test results.
 [INFO]


 [INFO] For more information, run Maven with the -e switch
 [INFO]


 [INFO] Total time: 9 minutes 48 seconds
 [INFO] Finished at: Thu Feb 07 12:35:57 PST 2008
 [INFO] Final Memory: 18M/48M
 [INFO]



 2. My project has a parent pom.xml and multiple sub modules, and the
 build stops when one of the junit tests fails, so is there is a way
 where I can instruct Continuum to ignore the tests results and
continue
 with the build?

 We need to know about all the failed tests from all the modules from a
 complete run, instead one at a time.

  Thanks,

Sameh
 This email and any files transmitted with it are confidential,
proprietary
 and intended solely for the individual or entity to whom they are
 addressed.
 If you have received this email in error please delete it immediately.


This email and any files transmitted with it are confidential,
proprietary
and intended solely for the individual or entity to whom they are
addressed.
If you have received this email in error please delete it immediately.


This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.

Re: How to override POM properties from CLI

[Igor Romanov]

Thank you for reply.
Are you saying that properties specified in POM can not be overridden with
-D option?

Igor 


Wayne Fay wrote:
 
 You should put the properties in different profiles, and then specify
 which profile using -Penv1 when running Maven.
 
 Wayne
 

-- 
View this message in context: 
http://www.nabble.com/How-to-override-POM-properties-from-CLI-tp15344487s177p15347745.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released

[Dan Fabulich]

Haroon Rafique wrote:


For me when the error about Failed to load Main-Class manifest attribute
from /tmp/surefirebooter???.jar appeared, I re-ran the tests with mvn -X
and then opened up the /tmp/surefirebooter???.jar file. It is a .jar file
with only one entry META-INF/MANIFEST.MF. Inside the MANIFEST.MF there are
2 entries. Class-Path and Main-Class. Sure enough, the file was in tact,
yet surefirebooter would say it can't find the Main-Class. You can even
try the actual java -jar /tmp/surebooter???.jar . command and it
still failed.

Looking a little bit more, I was able to extract the MANIFEST.MF file and
change its format from dos to unix in vim and repackaged it back into
a jar and sure enough the java -jar /tmp/surefirebooter???.jar .
command was able to run.


Ah, hearing that makes me strongly suspect that this is SUREFIRE-445 and 
SUREFIRE-451.


http://jira.codehaus.org/browse/SUREFIRE-445
http://jira.codehaus.org/browse/SUREFIRE-451

Thanks for doing this research; I've moved these bugs into the upcoming 
2.4.2 release.


-Dan

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

Re: release from a specific tag

[Kalle Korhonen]

Well, maybe you have a valid use case, but I don't think there's any support
for it. How do you create a nightly tag then? Couldn't you just run
release:prepare nightly, then run integration tests on the newly created
tag, and if succeeds, perform the release, otherwise abandon the tag. I
don't see a difference between a nightly tag and an official tag - you
could just use minor/micro version numbers to differentiate between
official releases and nightlies. Alternatively, if you use svn, you should
in principle be able to use revision number for this, but I don't think
there's any way to instruct Maven to checkout specific revision for
release:prepare rather than always using the head.

Kalle


On Feb 7, 2008 2:40 AM, Benoit Decherf [EMAIL PROTECTED] wrote:

 I'm not sure that this it's specific to our process (If this is the
 case, we should probably change it :) ).

 I don't think that is possible to have always a clean trunk/branch.
 Let me explain our process:
 Each developer commit their changes on the trunk.
 Each hour, continuum check for changes and package the components(and
 execute the unit test).
 Each night project is tagged (nightly tag) and the packages are
 installed on a dev plateform and automatics tests are executed. This can
 last 3 hours.

 So, I agree with you that if a unit test fails, the developer have to
 clean it (This shouldn't happen because tests should be executed before
 commit). But the integration tests that last 3 hours can't be executed
 on each commit, so something can be broken for several days because of a
 regression. This also occurs at maven.

 Additionaly, when performing (prepare) a release, It should be great to
 be sure that the integration tests passed. So it can be useful to be
 able to prepare/perform a release from a nightly tag.

 Benoit

 Kalle Korhonen wrote:
  Ah ok, I see what you mean, but I think it's specific to your process.
 I'd
  assume that most projects operate so they require that the trunk/branch
  builds cleanly, rather than releasing from a specific time
  point/version/label. In your case, it'd mean reverting the trunk to 04
 feb,
  then doing the release. In the meantime 05 feb would continue in branch
 or
  with local copies only. I believe it's also common practice to require
 the
  trunk builds to succeed. In our development process, we try not to
 prevent
  build failures but to minimize the time the build remains in broken
 state,
  with whatever means necessary (in some cases, reverting to previous
 state).
 
  Kalle
 
 
  On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
 
  Image that we are working on the trunk. Every night a nightly snapshot
  is created and deploy on a test servers and automatic tests are run
  (they can last 4hours for a project).
  on date 04 feb. every tests passed.
  on date 05 feb. some tests are broken.
 
  But on 06 feb we want to make a release (to install in prod). The dev
  started on 05 feb are not finished, and so the nightly of 04 feb should
  be released.
  To do so, I suppose that release:prepare should be executed from the
  nightly tag of 4 feb to remove all snapshots dependencies, tag the
  release with an official tag, etc... The release prepare should create
 a
  branch from this tag to do it ?
 
  Benoit
 
 
  Kalle Korhonen wrote:
 
  I don't understand what you are asking. release:perform doesn't do
 
  anything
 
  else but runs deploy (and site-deploy) on the newly created tag; after
  release:prepare, the release is already cut. If you want snapshots,
 why
  don't you just deploy uniquely versioned snapshots nightly?
 
  Kalle
 
 
  On 2/7/08, Benoit Decherf [EMAIL PROTECTED] wrote:
 
 
  But I don't want to create an official version every night.
  In the nightly version, there still have the -SNAPSHOT versions. So I
  can't use release:perform to do it. I realy need to execute the
  release:prepare from the nightly tag.
 
  All projects here ask for this feature. I think this is a very good
  feature to be able to release an unofficial  version that is
 entirely
  tested.
  It seems strange that nobody has asked for this feature. All of you
  always create a version from the last commits files of the trunk
  (integration branch) ?
 
  Is it possible to make an evolution of the release plugin to support
 
  this
 
  ?
 
  Benoit
 
 
  Nicole Lacoste wrote:
 
 
  Hi Benoit,
 
  Yes I think so.  Well I know you can release from a tag made with
 the
  release prepare.  The command is
 
  mvn release:perform
 
 
  -DconnectionUrl=scm:svn:file://your-url-here/tag-name
 
 
  Look at page 224 of better builds with maven for more details
 
  Nicole
 
  On 06/02/2008, Benoit Decherf [EMAIL PROTECTED] wrote:
 
 
 
  Hi,
 
  I think that we should be able to perform a release from an old
 
  nightly
 
  tag rather than do it always from the trunk :
 
  Every night functional tests run on a project A. On day d
 
  everything
 
  works, but after, I decide to add a feature and I broke the trunk.

Re: surefire 2.4 + testng, changing TestSuite name

[Dan Fabulich]

Erez Nahir wrote:


Created http://jira.codehaus.org/browse/SUREFIRE-452 and provided fix for it
as attachment.


I saw your bug; it seems to fail some of the integration tests, so I'm not 
applying it right now.



Can someone from surefire team clarify when is the next minor release of
surefire-plugin planned?


I don't think we have any schedules/plans, but you're in luck, because 
there's a handful of bugs that we found right around the time that 2.4.1 
shipped. [Maybe people were waiting for the first service pack ;-)]


If you can get me a patch that passes the tests in the next couple of 
days, I'll probably submit it.


-Dan

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

Re: How to disable Test during build

[Arun P Johny]

Hi all,

Thanks for the help.

I added maven.test.skiptrue/maven.test.skip to my 
.m2/conf/settings.xml active profile.


It is working fine now

Thank again for all your help


Arun P Johny wrote:

Hi,

Can anybody tell me how to disable execution of test phase during 
maven2 build. I'm using maven 2.0.7


I don't want the test phase to execute when I gaves mvn 
release:prepare and mvn release:perform


Thank You,
Arun

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


__ Information from ESET NOD32 Antivirus, version of virus 
signature database 2854 (20080206) __


The message was checked by ESET NOD32 Antivirus.

http://www.eset.com






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

Re: How to disable Test during build

[David C. Hicks]

Arun, you can also define the property on the command line that you 
execute Maven from:  mvn -Dmaven.test.skip=true release




Arun P Johny wrote:

Hi all,

Thanks for the help.

I added maven.test.skiptrue/maven.test.skip to my 
.m2/conf/settings.xml active profile.


It is working fine now

Thank again for all your help


Arun P Johny wrote:

Hi,

Can anybody tell me how to disable execution of test phase during 
maven2 build. I'm using maven 2.0.7


I don't want the test phase to execute when I gaves mvn 
release:prepare and mvn release:perform


Thank You,
Arun

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


__ Information from ESET NOD32 Antivirus, version of virus 
signature database 2854 (20080206) __


The message was checked by ESET NOD32 Antivirus.

http://www.eset.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: jasperreports-maven-plugin chokes on xml

[David C. Hicks]

Thanks, Dan.  I've filed a report and attached a cut-down version of the 
project and files.  I hope it's helpful.

Dave

Dan Tran wrote:

file a jira with a producable jrxml, i will give it a try

thanks

On Feb 7, 2008 2:37 PM, David C. Hicks [EMAIL PROTECTED] wrote:
  

Good thought, but I was already using 2.0.3.  I did change it to 1.2.5,
which is what the original Ant build was using, but that didn't make any
difference, either.


Dan Tran wrote:


this plugin uses 1.2.2 jasperreport, this may be the cause of your
issue.  But you can overide it thou. see doc for details

-D

On Feb 7, 2008 1:54 PM, David C. Hicks [EMAIL PROTECTED] wrote:

  

I'm converting an existing Ant build to Maven, and I've encountered a
sticking point with respect to my Jasper reports.

Though it's not the preferred method for doing headers and footers, our
reports use some imported xml to provide the report header and footer
definitions.  The xml is imported by way of ENTITY tags in the .jrxml
header.  When running one of these guys through the
jasperreports-maven-plugin, I get an error that doesn't really tell me
much.  Here is an example:

Error compiling report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
: headerParms.xml

Using the -e parameter does yield some stack trace indicating an error
in JasperReportsMojo.compile().  I'll include that trace at the end of
the message.  I hope someone has an idea.  Otherwise, I'm stuck with
either re-working all of my reports to use subreports for the headers
and footers or trying to run an Ant build from within my Maven build
(the more likely scenario since time is not on my side).

Thanks in advance for any advice,
Dave

Promised Stack Trace:

org.apache.maven.BuildFailureException: Error compiling report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
   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:324)
   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)
Caused by: org.apache.maven.plugin.MojoFailureException: Error compiling
report design :
/home/dhicks/workspace/com.enttek.concessions.backoffice/reports/src/main/jasperreports/transfer.jrxml
   at
org.codehaus.mojo.jasperreports.JasperReportsMojo.compile(JasperReportsMojo.java:236)
   at
org.codehaus.mojo.jasperreports.JasperReportsMojo.execute(JasperReportsMojo.java:191)
   at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
   at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
   ... 16 more


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





-
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: Maven Concepts

[amit kumar]

Continuing on this thread I would also like to put a doubt(misconception)-
Until yesterday I used to think that if I have an artifact on local
repository + remote repository with same groupId-artifactId-version. The
maven will take the one which is built at a later time or some system
property attached to it which maven uses to differentiate.

The origin for this assumption was no matter if the artifact is present in
my local repository maven shows

Downloading \\remoteRepository\org\apache\x\x-1.0.pom
Downloading http:\\repo1.maven.org\org\apache\x\x-1.0.pom
.
.
.
.
.
What I assumed of this was that it compares where the latest of the artifact
is available even with same groupId+artifactId+version.

But yesterday when I cross checked even at the remote repository had a
artifact newly deployed (though with same groupId+artifactId+versionId) what
I was seeing in the classpath was the one from local repository.

Am I right in what I am concluding? Or again missing somewhere.

If what I have concluded upon is right, is there a way to make maven pick up
the one from remote repository(in case it is build and deployed later? )


Thanks and regards,
Amit


On Feb 8, 2008 4:55 AM, Graham Leggett [EMAIL PROTECTED] wrote:

 Dhruva Reddy wrote:

  What exactly is a goal and what is a phase?

 In maven 1, there were only goals, and goals were specific targets that
 were embedded in specific maven plugins, a bit like an ant target.

 So the jar plugin would have the jar goal which when run, would jar up
 some classes.

 It soon became apparent that this leaves too much up to the end user:
 what if the artifact you are producing isn't a jar, but an ear instead?
 Or a war file? Why should the user have to know or care that they must
 run the ear:ear goal instead of the jar:jar goal?

 Enter the phases of the lifecycle in maven 2.

 Plugins attach various goals to the various phases in the lifecycles,
 and depending on which phase of the lifecycle you've asked maven to
 complete, all the relevant goals attached to that lifecycle will be run
 up to that phase.

 So if you run mvn install (or run all goals in all phases up until
 the 'install' phase), maven figures out for itself that the
 compile:compile goal must run, and the ear:ear goal (because the
 artifact is an ear file), the user no longer needs to care.

 So to sum up:

 The lifecycle contains a list of phases, and each phase has a goal or
 goals attached to that phase. So running a phase is a convenient way of
 saying run all goals I need to run to make this artifact up to this
 phase, and don't tell me what those goals are, I don't care.

 Regards,
 Graham
 --

Re: Maven Concepts

[Sahoo]

I am no maven expert. AFAIK, only if it is SNAPSHOT (the one that ends 
with -SNAPSHOT) version then maven checks the timestamp etc. against the 
remote repository. Otherwise Maven always prefers the one in the local 
repository if one is available there. In your case, the artifact version 
looks to be 1.0 which means once the artifact is available in your local 
repo, maven won't go to remote repo for that one. Question why did the 
owner of the artifact chose to update the artifact, but did not bother 
to change the version number?


Someone can correct me if need be.

Thanks,
Sahoo
amit kumar wrote:

Continuing on this thread I would also like to put a doubt(misconception)-
Until yesterday I used to think that if I have an artifact on local
repository + remote repository with same groupId-artifactId-version. The
maven will take the one which is built at a later time or some system
property attached to it which maven uses to differentiate.

The origin for this assumption was no matter if the artifact is present in
my local repository maven shows

Downloading \\remoteRepository\org\apache\x\x-1.0.pom
Downloading http:\\repo1.maven.org\org\apache\x\x-1.0.pom
.
.
.
.
.
What I assumed of this was that it compares where the latest of the artifact
is available even with same groupId+artifactId+version.

But yesterday when I cross checked even at the remote repository had a
artifact newly deployed (though with same groupId+artifactId+versionId) what
I was seeing in the classpath was the one from local repository.

Am I right in what I am concluding? Or again missing somewhere.

If what I have concluded upon is right, is there a way to make maven pick up
the one from remote repository(in case it is build and deployed later? )


Thanks and regards,
Amit


On Feb 8, 2008 4:55 AM, Graham Leggett [EMAIL PROTECTED] wrote:

  

Dhruva Reddy wrote:



What exactly is a goal and what is a phase?
  

In maven 1, there were only goals, and goals were specific targets that
were embedded in specific maven plugins, a bit like an ant target.

So the jar plugin would have the jar goal which when run, would jar up
some classes.

It soon became apparent that this leaves too much up to the end user:
what if the artifact you are producing isn't a jar, but an ear instead?
Or a war file? Why should the user have to know or care that they must
run the ear:ear goal instead of the jar:jar goal?

Enter the phases of the lifecycle in maven 2.

Plugins attach various goals to the various phases in the lifecycles,
and depending on which phase of the lifecycle you've asked maven to
complete, all the relevant goals attached to that lifecycle will be run
up to that phase.

So if you run mvn install (or run all goals in all phases up until
the 'install' phase), maven figures out for itself that the
compile:compile goal must run, and the ear:ear goal (because the
artifact is an ear file), the user no longer needs to care.

So to sum up:

The lifecycle contains a list of phases, and each phase has a goal or
goals attached to that phase. So running a phase is a convenient way of
saying run all goals I need to run to make this artifact up to this
phase, and don't tell me what those goals are, I don't care.

Regards,
Graham
--




  


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