date:20060207

"Nearer" means closer in the tree, not newer. It used to be newer, and
I really should have kept it that way.

Making that configurable is a feature planned for 2.1. You can exclude
commons-collections from the hibernate dependency, or you can include
it with a forced version.

- Brett

On 2/8/06, Matt Raible <[EMAIL PROTECTED]> wrote:
> It seems logical to me that commons-collections 3.1 should be chosen
> over commons-collections 2.1.  Unfortunately, it looks like Hibernate
> overrides HtmlUnit.  Any idea why?  I'm using the 2.0.2 Ant Tasks.

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

Re: maven kodo plugin


[EMAIL PROTECTED] wrote:


Dear Henry,
  I have got  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT.

 However, I can't get  com.solarmetric:kodo-jdo:jar:3.0


 

I don't think it's in the repositories. Have you tried their website --> 
http://www.solarmetric.com/


Henry

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

[m2 ant] Why is commons-collections 2.1 chosen over 3.1

2006-02-07 Thread Matt Raible

It seems logical to me that commons-collections 3.1 should be chosen
over commons-collections 2.1.  Unfortunately, it looks like Hibernate
overrides HtmlUnit.  Any idea why?  I'm using the 2.0.2 Ant Tasks.

  org.hibernate:hibernate:jar:3.1 (selected)
dom4j:dom4j:jar:1.6 (selected)
ehcache:ehcache:jar:1.1 (selected)
cglib:cglib:jar:2.1_3 (selected)
  asm:asm:jar:1.5.3 (selected)
commons-collections:commons-collections:jar:2.1.1 (selected)
asm:asm:jar:1.5.3 (selected)
antlr:antlr:jar:2.7.6rc1 (selected)
  geronimo-spec:geronimo-spec-jta:jar:1.0.1B-rc4 (selected)
  displaytag:displaytag:jar:1.0 (selected)
javax.servlet:jstl:jar:1.0.2 (selected)
log4j:log4j:jar:1.2.8 (selected)
taglibs:standard:jar:1.0.4 (selected)
commons-lang:commons-lang:jar:2.0 (selected)
itext:itext:jar:0.99 (selected)
commons-beanutils:commons-beanutils:jar:1.6.1 (selected)
  commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4)
  commons-collections:commons-collections:jar:2.0 (removed - nearer found: 2
.1.1)
  uk.ltd.getahead:dwr:jar:1.0 (selected)
  org.springframework:spring:jar:1.2.6 (selected)
  commons-lang:commons-lang:jar:2.0 (selected)
  opensymphony:sitemesh:jar:2.2.1 (selected)
  org.codehaus.cargo:cargo-ant:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-orion:jar:0.7 (selected)
  org.codehaus.cargo:cargo-core-api-container:jar:0.7 (selected)
ant:ant:jar:1.5.4 (selected)
org.codehaus.cargo:cargo-core-api-module:jar:0.7 (selected)
  org.codehaus.cargo:cargo-core-api-util:jar:0.7 (selected)
  xerces:xercesImpl:jar:2.6.2 (selected)
geronimo-spec:geronimo-spec-j2ee-deployment:jar:1.1-rc4 (selected)
org.codehaus.cargo:cargo-core-api-generic:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-tomcat:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-jboss:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-weblogic:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-resin:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-jetty:jar:0.7 (selected)
org.codehaus.cargo:cargo-core-container-jo:jar:0.7 (selected)
  javax.servlet:jstl:jar:1.0.2 (removed - nearer found: 1.1.2)
  javax.servlet:jstl:jar:1.1.2 (selected)
  com.canoo:webtest:jar:1168 (selected)
htmlunit:htmlunit:jar:1.8-SNAPSHOT (selected)
  commons-jelly:commons-jelly-tags-log:jar:1.0 (selected)
  commons-codec:commons-codec:jar:1.3 (selected)
  commons-jelly:commons-jelly:jar:1.0 (selected)
commons-logging:commons-logging:jar:1.0.3 (removed - nearer found: 1.0.4
)
javax.servlet:servlet-api:jar:2.3 (removed - nearer found: 2.4)
commons-collections:commons-collections:jar:2.1 (removed - nearer found:
 2.1.1)
dom4j:dom4j:jar:1.5.2 (removed - nearer found: 1.6)
forehead:forehead:jar:1.0-beta-5 (selected)
javax.servlet:jstl:jar:1.0.6 (removed - nearer found: 1.1.2)
xerces:xerces:jar:2.2.1 (selected)
jaxen:jaxen:jar:1.1-beta-4 (selected)
  jaxen:jaxen:jar:1.1-beta-4 (removed - causes a cycle in the graph)
  dom4j:dom4j:jar:1.5.2 (removed - nearer found: 1.6)
  jdom:jdom:jar:b10 (selected)
  xom:xom:jar:1.0b3 (selected)
xerces:xmlParserAPIs:jar:2.6.1 (selected)
org.ccil.cowan.tagsoup:tagsoup:jar:0.9.7 (selected)
xerces:xercesImpl:jar:2.2.1 (removed - nearer found: 2.6.2)
xalan:xalan:jar:2.6.0 (selected)
com.ibm.icu:icu4j:jar:2.6.1 (selected)
  xerces:xmlParserAPIs:jar:2.6.1 (removed - nearer found: 2.6.2)
  xerces:xmlParserAPIs:jar:2.6.2 (selected)
commons-cli:commons-cli:jar:1.0 (selected)
  commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4
)
  commons-lang:commons-lang:jar:1.0 (removed - nearer found: 2.0)
commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6
.1)
commons-discovery:commons-discovery:jar:20030211.213356 (selected)
  junit:junit:jar:3.7 (removed - nearer found: 3.8.1)
  commons-logging:commons-logging:jar:1.0.3 (removed - nearer found: 1.0
.4)
commons-jexl:commons-jexl:jar:1.0 (selected)
  gsbase:gsbase:jar:2.0.1 (selected)
junitperf:junitperf:jar:1.8 (selected)
  junitperf:junitperf:jar:1.8 (selected)
  commons-httpclient:commons-httpclient:jar:3.0 (selected)
commons-logging:commons-logging:jar:1.0.3 (removed - nearer found: 1.0.4
)
commons-codec:commons-codec:jar:1.2 (removed - nearer found: 1.3)
  rhino:js:jar:1.6R2 (selected)
  commons-beanutils:commons-beanutils:jar:1.7.0 (removed - nearer found: 1.6
.1)
  jaxen:jaxen:jar:1.1-beta-4 (removed - nearer found: 1.1-beta-8)
  jaxen:jaxen:jar:1.1-beta-8 (selected)
jaxen:jaxen:jar:1.1-beta-6 (removed - causes a cycle in the graph)
dom4j:dom4j:jar:1.6.1 (removed - n

Re: maven kodo plugin

2006-02-07 Thread clark . rao

Dear Henry,
   I have got  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT.

  However, I can't get  com.solarmetric:kodo-jdo:jar:3.0

thanks.
Tel: (020)36315358-328 Fax: (020)36315170

  "Henry S. Isidro" 

  <[EMAIL PROTECTED]To:   Maven Users List 

  m>   cc:  

   Subject:  Re: maven kodo plugin  

  08/02/2006 14:00  

  Please respond to 

  "Maven Users  

  List" 

[EMAIL PROTECTED] wrote:

>Dear all,
>
>
>
>
>When I build maven kodo plugin, it failed. can you help?
>GroupId: org.codehaus.mojo
>ArtifactId: mojo-sandbox
>Version: 2-SNAPSHOT
>
>Reason: Unable to download the artifact from any repository
>
>  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT
>
>from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  central-1 (file:///d:/m2localrepo/)
>
>
>[INFO]
>

>[DEBUG] Trace
>org.apache.maven.reactor.MavenExecutionException: POM
>'org.codehaus.mojo:mojo-sandbox' not found in repository: Unable t
>o download the artifact from any repository
>
>  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT
>
>from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  central-1 (file:///d:/m2localrepo/)
>
>
You're using a sandbox plugin. Read this for more info:
http://mojo.codehaus.org/using-sandbox-plugins.html

HTH,
Henry

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

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__

2006 sees Hactl's 30 years of commitment to Hong Kong and our customers.
On this occasion we extend our thanks to all of you for your loyalty and
trust.
You have contributed to our success.

Visit us at our website at www.hactl.com

DISCLAIMER :-
The information contained in this message, including any attachment, is
confidential and may also be privileged. The information is intended only
for the person or entity to which it is addressed. Any review,
re-transmission, copying, storage, distribution or other use or disclosure
of this information by persons or entities other than the intended
recipient is prohibited. If you are not the intended recipient, please
contact the sender immediately by return email and delete this message from
your system. Thank you.

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

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

Re: maven kodo plugin

2006-02-07 Thread clark . rao

Dear Henry,
  thanks a lot

thanks.
Tel: (020)36315358-328 Fax: (020)36315170

  "Henry S. Isidro" 

  <[EMAIL PROTECTED]To:   Maven Users List 

  m>   cc:  

   Subject:  Re: maven kodo plugin  

  08/02/2006 14:00  

  Please respond to 

  "Maven Users  

  List" 

[EMAIL PROTECTED] wrote:

>Dear all,
>
>
>
>
>When I build maven kodo plugin, it failed. can you help?
>GroupId: org.codehaus.mojo
>ArtifactId: mojo-sandbox
>Version: 2-SNAPSHOT
>
>Reason: Unable to download the artifact from any repository
>
>  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT
>
>from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  central-1 (file:///d:/m2localrepo/)
>
>
>[INFO]
>

>[DEBUG] Trace
>org.apache.maven.reactor.MavenExecutionException: POM
>'org.codehaus.mojo:mojo-sandbox' not found in repository: Unable t
>o download the artifact from any repository
>
>  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT
>
>from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  central-1 (file:///d:/m2localrepo/)
>
>
You're using a sandbox plugin. Read this for more info:
http://mojo.codehaus.org/using-sandbox-plugins.html

HTH,
Henry

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

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__

2006 sees Hactl's 30 years of commitment to Hong Kong and our customers.
On this occasion we extend our thanks to all of you for your loyalty and
trust.
You have contributed to our success.

Visit us at our website at www.hactl.com

DISCLAIMER :-
The information contained in this message, including any attachment, is
confidential and may also be privileged. The information is intended only
for the person or entity to which it is addressed. Any review,
re-transmission, copying, storage, distribution or other use or disclosure
of this information by persons or entities other than the intended
recipient is prohibited. If you are not the intended recipient, please
contact the sender immediately by return email and delete this message from
your system. Thank you.

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

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

Re: maven kodo plugin


[EMAIL PROTECTED] wrote:


Dear all,




   When I build maven kodo plugin, it failed. can you help?
GroupId: org.codehaus.mojo
ArtifactId: mojo-sandbox
Version: 2-SNAPSHOT

Reason: Unable to download the artifact from any repository

 org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 central-1 (file:///d:/m2localrepo/)


[INFO]

[DEBUG] Trace
org.apache.maven.reactor.MavenExecutionException: POM
'org.codehaus.mojo:mojo-sandbox' not found in repository: Unable t
o download the artifact from any repository

 org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 central-1 (file:///d:/m2localrepo/)
 

You're using a sandbox plugin. Read this for more info: 
http://mojo.codehaus.org/using-sandbox-plugins.html


HTH,
Henry

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

maven kodo plugin

2006-02-07 Thread clark . rao

Dear all,




When I build maven kodo plugin, it failed. can you help?
GroupId: org.codehaus.mojo
ArtifactId: mojo-sandbox
Version: 2-SNAPSHOT

Reason: Unable to download the artifact from any repository

  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  central-1 (file:///d:/m2localrepo/)


[INFO]

[DEBUG] Trace
org.apache.maven.reactor.MavenExecutionException: POM
'org.codehaus.mojo:mojo-sandbox' not found in repository: Unable t
o download the artifact from any repository

  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  central-1 (file:///d:/m2localrepo/)

at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.ProjectBuildingException: POM
'org.codehaus.mojo:mojo-sandbox' not found in reposito
ry: Unable to download the artifact from any repository

  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  central-1 (file:///d:/m2localrepo/)

at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:4
20)
at
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:969)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:583)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:295)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:273)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 11 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any reposi
tory

  org.codehaus.mojo:mojo-sandbox:pom:2-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  central-1 (file:///d:/m2localrepo/)

at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:136)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:3
77)
... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
download the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:260)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124)
... 20 more
[INFO]

[INFO] Total time: < 1 second
[INFO] Finished at: Wed Feb 08 13:20:01 CST 2006
[INFO] Final Memory: 1M/4M
[INFO]









thanks.
Tel: (020)36315358-328 Fax: (020)36315170







thanks.
Tel: (020)36315358-328 Fax: (020)36315170

___
2006 sees Hactl's 30 years of commitment to Hong Kong and our customers.
On this occasion we extend our thanks to all of you for your loyalty and
trust.
You have contributed to our success.

Visit us at our website at www.hactl.com

DISCLAIMER :-
The information contained in this message, including any attachment, is
confidential and may also be privileged. The information is intended only
for the person or entity to which it is addressed. Any review,
re-transmission, copying, storage, distribution or other use or disclosure
of this information by persons or entities other than the intended
recipient is prohibited.

[m1] Jalopy plugin problems

2006-02-07 Thread Wendy Smoak

Twice now, on two different machines (same codebase, though,) the
Jalopy plugin was working fine and then suddenly stopped working with
the error below.

Full output of maven jalopy -X is here:
   http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Jalopy

The only thing that changed was Jalopy's config file.  Reverting those
changes to a known good state didn't help.  Other developers on the
project aren't having any trouble.  Obviously I've done *something* to
it (twice!) but I have no idea what.

Does anyone see anything that looks suspicious?

-Wendy

/svn/struts/current/action
$ maven jalopy
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

java.lang.ClassCastException: java.lang.String
at de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24
19)
at de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24
45)
at de.hunsicker.jalopy.storage.Convention.(Convention.java:211)
at de.hunsicker.jalopy.plugin.ant.AntPlugin.(AntPlugin.java:60)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.ja
va:490)
at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:231)

at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:162)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185)
...
build:start:

jalopy:taskdef:

java:prepare-filesystem:

java:compile:
[echo] Compiling to c:\svn\struts\current\action/target/classes

BUILD FAILED
File.. c:\java\m1-repository\cache\maven-jalopy-plugin-1.3.1\plugin.jelly
Element... ant:jalopy
Line.. 64
Column 46
java.lang.NoClassDefFoundError
Total time: 2 seconds
Finished at: Tue Feb 07 22:20:09 GMT-07:00 2006

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

Re: [m102] overriding goal


Laird Nelson wrote:


On 2/7/06, Henry S. Isidro <[EMAIL PROTECTED]> wrote:
 


I'm not exactly sure what you mean but have you tried ?
   




To be fair, no, I haven't, but that would involve an infinite loop:


 
   
 


What I'd like to be able to do is:


 
   
 


But as is becoming more and more clear to me each day this is impossible.
Oh well; moving on.

Best,
Laird

 


I guess you're right, this might not be possible.

Regards,
Henry

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

Re: [m102] overriding goal

2006-02-07 Thread Laird Nelson

On 2/7/06, Henry S. Isidro <[EMAIL PROTECTED]> wrote:
>
> I'm not exactly sure what you mean but have you tried  "goalname" />?

To be fair, no, I haven't, but that would involve an infinite loop:

What I'd like to be able to do is:

But as is becoming more and more clear to me each day this is impossible.
Oh well; moving on.

Best,
Laird

Re: [m2] - Installing new archetypes

2006-02-07 Thread Trent Rosenbaum

Thanks for the help John, I have reinstalled the j2ee archetype after making
sure all the files were deleted.
I have gone back to the file maven-metadata-central.xml and this still has
the same information inside it.

The archetype plugin can now use this archetype without any issues, so what
have I updated if it is not this file?

Trent

On 08/02/06, John Casey <[EMAIL PROTECTED]> wrote:
>
> try re-installing it with the following command line option:
>
> -DupdateReleaseInfo=true
>
> That will update the RELEASE metadata. It would seem that there should
> be a way to specify the archetype-artifact's version, though...
>
> -john
>
>

Re: [m2] - Installing new archetypes


try re-installing it with the following command line option:

-DupdateReleaseInfo=true

That will update the RELEASE metadata. It would seem that there should 
be a way to specify the archetype-artifact's version, though...


-john

Trent Rosenbaum wrote:

Hi there,

Can anyone offer any thoughts on the following.  I have downloaded
maven-archetype-j2ee module and have packaged + installed the Jar artifact.
When I go to inspect my local repo I find the following:

org\apache\maven\archetypes\maven-archetype-j2ee

under this directory I find the following files:

maven-metadata-local.xml, (this contains info about my archetype jar file)
maven-metadata-central.xml, (this contains the data example below)



 - <#>  
  org.apache.maven.archetypes
  maven-archetype-j2ee
 RELEASE


when I go to use the archetype I get the following problem

---
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.archetypes
ArtifactId: maven-archetype-j2ee
Version: RELEASE

Reason: Unable to determine the release version

  org.apache.maven.archetypes:maven-archetype-j2ee:jar:RELEASE
---

If I specify the archetypeVersion on the command line the archetype plugin
is able to locate and use the correct version of the j2ee archetype.
Am I right in thinking this issue is caused by the
maven-metadata-central.xml file?
When I look under other archetypes for example maven-archetype-quickstart,
the maven-metadata-central.xml file contains data
appropriate to the version installed locally.  Does maven or the archetype
plugin contain a flag to update the data so I do not have use specify the
version on the command line?


Trent



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

[m2] - Installing new archetypes

2006-02-07 Thread Trent Rosenbaum

Hi there,

Can anyone offer any thoughts on the following.  I have downloaded
maven-archetype-j2ee module and have packaged + installed the Jar artifact.
When I go to inspect my local repo I find the following:

org\apache\maven\archetypes\maven-archetype-j2ee

under this directory I find the following files:

maven-metadata-local.xml, (this contains info about my archetype jar file)
maven-metadata-central.xml, (this contains the data example below)



 - <#>  
  org.apache.maven.archetypes
  maven-archetype-j2ee
 RELEASE


when I go to use the archetype I get the following problem

---
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.archetypes
ArtifactId: maven-archetype-j2ee
Version: RELEASE

Reason: Unable to determine the release version

  org.apache.maven.archetypes:maven-archetype-j2ee:jar:RELEASE
---

If I specify the archetypeVersion on the command line the archetype plugin
is able to locate and use the correct version of the j2ee archetype.
Am I right in thinking this issue is caused by the
maven-metadata-central.xml file?
When I look under other archetypes for example maven-archetype-quickstart,
the maven-metadata-central.xml file contains data
appropriate to the version installed locally.  Does maven or the archetype
plugin contain a flag to update the data so I do not have use specify the
version on the command line?


Trent

Re: [m102] overriding goal


Laird Nelson wrote:


Yes, thank you; you have, of course, defined a new goal that governs whether
the old one is executed, which is a perfectly valid approach.  I was hoping
for a wee bit more, namely the ability to not only override a goal but to
gain access to the overridden goal from the overriding goal.

Thanks,
Laird

On 2/7/06, Henry S. Isidro <[EMAIL PROTECTED]> wrote:
 


Laird Nelson wrote:

   


I see.  So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set.  How would I do
 


this?
   


I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing.  On the other hand, if that
property is set, then I would like to run the plugin goal.


From where I sit this seems to be impossible.



 


This is just from the top of my head so I haven't tried it but I think
this will work:



 

**

If the property evil.dictator is set to "true" then the world is
destroyed when the goal is run.

HTH,
Henry
   

I'm not exactly sure what you mean but have you tried "goalname" />?


Regards,
Henry

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

Re: [m102] overriding goal

2006-02-07 Thread Laird Nelson

Yes, thank you; you have, of course, defined a new goal that governs whether
the old one is executed, which is a perfectly valid approach.  I was hoping
for a wee bit more, namely the ability to not only override a goal but to
gain access to the overridden goal from the overriding goal.

Thanks,
Laird

On 2/7/06, Henry S. Isidro <[EMAIL PROTECTED]> wrote:
>
> Laird Nelson wrote:
>
> >I see.  So suppose there is a plugin goal named world:destroy and I only
> >want to run it if the property evil.dictator is set.  How would I do
> this?
> >I don't want it to be an error if someone tries to run it without said
> >property; I just want to silently do nothing.  On the other hand, if that
> >property is set, then I would like to run the plugin goal.
> >
> >>From where I sit this seems to be impossible.
> >
> >
> This is just from the top of my head so I haven't tried it but I think
> this will work:
>
> 
>  
>   
>  
> **
>
> If the property evil.dictator is set to "true" then the world is
> destroyed when the goal is run.
>
> HTH,
> Henry
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

RE: [m1.1b2] Javadoc plugin 1.8 warnings report is empty

2006-02-07 Thread Jeff Jensen

Hi Arnaud, thanks for the info.  Are there any particular plugins I can back
down a rev on so that it works?
 

-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 5:07 PM
To: Maven Users List
Subject: Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty

It's a problem of conflict between different plugins which uses two
incopatible releases of commons-collections.
It'll be fixed in maven 1.1 beta 3 because we unified all the dependencies.

Arnaud

On 2/7/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> Hello Lukas!  Thank you for the prompt reply and interest to help  :-)
>
> Yes, you did!  I know it worked for awhile, I am not sure when/how it 
> broke again.  I only know it has been broken for awhile.
>
> This is a different problem this time, and it exists across all 4 of 
> our projects (the small and large).
>
> I will gladly create that JIRA next...
> I will first create it with all the details I can, then try to make a 
> small test case.
>
>
> Quoting Lukas Theussl <[EMAIL PROTECTED]>:
>
> > Hi Jeff,
> >
> > I thought we had resolved all your problems with javadoc warnings ;)
> >
> > Would you mind opening another issue with more detailed information, 
> > ie the exact versions of javadoc, xdoc and site plugin that you are 
> > using, and the files that are generated in target/javadoc? Or even 
> > better, a small, reproducible test case? It's weird though that it 
> > works with xdoc but not with site.
> >
> > Thanks,
> > Lukas
> >
> >
> > Jeff Jensen wrote:
> > > Hi,
> > >
> > > Our Javadoc Warnings Report run with maven site has failed for along
time.
> > I
> > > finally have time to (hopefully!) resolve the problem.
> > >
> > > The report will state the number of files, number of errors=0, and 
> > > an empty Files section.
> > >
> > > Running it with maven.javadoc.debug=true, the following info is in 
> > > the log
> > (the
> > > first error message):
> > >
> > > Read 276 line(s) from input file
> > > Building map from 276 input line(s)
> > > Parsing line   [javadoc]
> > >
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
AWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in 
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > > *** WARNING: exception parsing line '  [javadoc]
> > >
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccount
AWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> va/util/Set;
> > > java.lang.NoSuchMethodError:
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Lja
> va/util/Set;
> > > at
> > >
> >
> org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarn
> ingsTextToXml.java:295)
> > >
> > >
> > > This failure repeats many times, I think for every warning in the
file.
> > >
> > >
> > > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> > >
> > > Nothing is obvious to me at this point - I keep reviewing the 
> > > jelly file
> > hoping
> > > to find something.  Does it to anyone else?
> > >
> > >
> > > --
> > > --- 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: project specific local repos


it's possible, if a little involved. ;)

First, you need a local repository that contains only the plugin 
artifacts needed for your build plus your project's dependencies. This 
means setting up a settings.xml that points to this isolated local 
repository (probably the settings.xml *and* the local repository will 
live in your project directory, but I'd expect that the local repository 
would *not* be checked into SCM...ignored, I mean). Then, to use this 
settings.xml, you'd have to use:


mvn --offline --settings /path/to/your/settings.xml 

to run the build (offline, so it won't muck around with trying to access 
a remote repository). To keep this consistent, you may want to create a 
shell script or batch file in your project directory that would wrap the 
'mvn' command line invocation, and inject these two options. This would 
be the entry point for your users to build your project. Now, if you're 
looking to locate this project directory on a CD, you must make sure 
that you're able to park your compiled classes somewhere writable, maybe 
in /tmp or something. You'd need:



${java.io.tmpdir}/${artifactId}-${version}


in your pom.xml, to redirect from /target to this new working directory.

I *think* that would do the trick for you, but you'd have to check me on 
that. Also note that it's possible that the outputDirectory redirection 
has some bugs in it, as it relies on each plugin correctly referencing 
${project.build.outputDirectory} in its output path construction, rather 
than simply ${basedir}/target or somesuch.


Good luck, and let me know how it goes! :-)

-john


Stefan Podkowinski wrote:

The plugin looks interesting but its not quite what I need. Although
the assemble plugin allows to create custom source distributions with
gathered libs I dont get why I should do this since my project *is*
actually the source ;)

What I like to do is to ship my maven project as it is including a
repository with all dependencies (which includes non-public jars or
patched jars). So even when the sky is falling and the last public
repo is gone, I can be sure my project compiles fine and I'm further
able to distribute it to others. Is there any standard way how this
could be done with maven? I'm aware that this possibly goes against
the whole 'no binaries in cvs' idea but I really wonder why I have to
setup my own remote repo and - even worse - why everyone else who
likes to work on the sources will have as well, just to keep some
control over artifacts.

On 2/7/06, John Casey <[EMAIL PROTECTED]> wrote:

This is probably going to be *a lot* easier for you:

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

Cheers,

John

Stefan Podkowinski wrote:

Hello

Whats the best way to distribute your project if you need to provide
all artifacts incl. dependencies with your release? E.g. if you want
to ship everything on CD, or just have a lot of artifacts that are not
available on public repos.

I wonder if it would be possible to create a project specific local
repo that is refered to from pom.xml? But as far as I could tell
theres only a config option for remote repos and I didnt have much
success with it.. Am I missing something or how would I do this?

Regards,
Stefan

-
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: Multiproject support in Maven 2

2006-02-07 Thread Cristiano V. Gavião


Hi,

Im studing m2 and something is not yet clear in my mind

How can I "merge" the contents of the common-war project module with a 
common-resources project. This resource project has only tlds, css and 
other web stuffs...


I want this merge be done before the war file be generated... I want 
every resource project being merged in only one war


Can you helpme please...

thanks

Cristiano Gavião

Mick Knutson escreveu:


   
   common-jar
   common-war
   common-managers
   sequence-generator
   properties-configuration
   


 


Thanks
Mick Knutson

http://www.BASELogic.com
http://www.MickKnutson.com

MSN Messenger: [EMAIL PROTECTED]

 



- Original Message - From: 
<[EMAIL PROTECTED]>

To: 
Sent: Tuesday, January 24, 2006 1:52 PM
Subject: Multiproject support in Maven 2



Hi,
Anybody knows if multiproject or equivalent plug-in is
supported in Maven 2?
Thanks,
AJ

-
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: [m102] overriding goal


Laird Nelson wrote:


I see.  So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set.  How would I do this?
I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing.  On the other hand, if that
property is set, then I would like to run the plugin goal.


From where I sit this seems to be impossible.
 

This is just from the top of my head so I haven't tried it but I think 
this will work:




 

**

If the property evil.dictator is set to "true" then the world is 
destroyed when the goal is run.


HTH,
Henry

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

Re: properties files


Try:


  

  ${build.sourceDirectory}
  
**/*.properties
  

  


...and if you wanted to do the same thing for test-resources, you'd have 
an additional section of the form 
[]+ in your build section.


-john

Kevin Galligan wrote:
I know that we should use the resources directory to store properties 
files, but to ease our platform build changes, I'd like to leave 
properties files in the java source directory.  It looks like the jar 
plugin moves xml files over.  Is there a way to force properties files 
as well?


Thanks,
-Kevin

-
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: Generating a jboss wsr file

Check out the "introduction to the build lifecycle" in the
documentation. This contains most of the information needed. There are
also plenty of mails on this in the archives.

- Brett

On 2/8/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
> Brett,
>
> Thanks!
>
> I guess along with thiscan someone give me some advice for how to
> publish an archive whose extension is not presently supported? If
> this means producing a new type of archive, let me know, perhaps I
> can contribute this. If there are any good links to information on
> how to do this, please post them -- I'd love to check out the
> possibility of doing this if there presently isn't a better way.
>
> Cheers,
>
> Brad
>
> On Feb 7, 2006, at 4:11 PM, Brett Porter wrote:
>
> > I don't think there is anything specific. You might like to checkout
> > the jboss plugin at mojo.codehaus.org.
> >
> > - Brett
> >
> > On 2/8/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
> >> I hadn't heard from anyone on this, but just a yeah or nay on whether
> >> WSR files are supported would be helpful. Is anyone else out there
> >> using JBoss, and building wsr's (web service archives)? As with all
> >> of these JBossian archives, they are just JAR files with different
> >> extensions. Does anyone have a suggestion on the best way to build
> >> and publish what essentially is a jar but with a different extension
> >> (wsr instead of jar)?
> >>
> >> Thanks for your help.
> >>
> >> Brad
> >>
> >>
> >> On Feb 6, 2006, at 6:41 PM, Brad O'Hearne wrote:
> >>
> >>> Is there a way to generate a jboss wsr file using maven?
> >>>
> >>> Brad
> >>>
> >>> 
> >>> -
> >>> 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: Generating a jboss wsr file

2006-02-07 Thread Brad O'Hearne


Brett,

Thanks!

I guess along with thiscan someone give me some advice for how to  
publish an archive whose extension is not presently supported? If  
this means producing a new type of archive, let me know, perhaps I  
can contribute this. If there are any good links to information on  
how to do this, please post them -- I'd love to check out the  
possibility of doing this if there presently isn't a better way.


Cheers,

Brad

On Feb 7, 2006, at 4:11 PM, Brett Porter wrote:


I don't think there is anything specific. You might like to checkout
the jboss plugin at mojo.codehaus.org.

- Brett

On 2/8/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:

I hadn't heard from anyone on this, but just a yeah or nay on whether
WSR files are supported would be helpful. Is anyone else out there
using JBoss, and building wsr's (web service archives)? As with all
of these JBossian archives, they are just JAR files with different
extensions. Does anyone have a suggestion on the best way to build
and publish what essentially is a jar but with a different extension
(wsr instead of jar)?

Thanks for your help.

Brad


On Feb 6, 2006, at 6:41 PM, Brad O'Hearne wrote:


Is there a way to generate a jboss wsr file using maven?

Brad

 
-

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: Generating a jboss wsr file

I don't think there is anything specific. You might like to checkout
the jboss plugin at mojo.codehaus.org.

- Brett

On 2/8/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
> I hadn't heard from anyone on this, but just a yeah or nay on whether
> WSR files are supported would be helpful. Is anyone else out there
> using JBoss, and building wsr's (web service archives)? As with all
> of these JBossian archives, they are just JAR files with different
> extensions. Does anyone have a suggestion on the best way to build
> and publish what essentially is a jar but with a different extension
> (wsr instead of jar)?
>
> Thanks for your help.
>
> Brad
>
>
> On Feb 6, 2006, at 6:41 PM, Brad O'Hearne wrote:
>
> > Is there a way to generate a jboss wsr file using maven?
> >
> > Brad
> >
> > -
> > 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: [m1.1b2] Javadoc plugin 1.8 warnings report is empty

2006-02-07 Thread Arnaud HERITIER

It's a problem of conflict between different plugins which uses two
incopatible releases of commons-collections.
It'll be fixed in maven 1.1 beta 3 because we unified all the dependencies.

Arnaud

On 2/7/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> Hello Lukas!  Thank you for the prompt reply and interest to help  :-)
>
> Yes, you did!  I know it worked for awhile, I am not sure when/how it broke
> again.  I only know it has been broken for awhile.
>
> This is a different problem this time, and it exists across all 4 of our
> projects (the small and large).
>
> I will gladly create that JIRA next...
> I will first create it with all the details I can, then try to make a small 
> test
> case.
>
>
> Quoting Lukas Theussl <[EMAIL PROTECTED]>:
>
> > Hi Jeff,
> >
> > I thought we had resolved all your problems with javadoc warnings ;)
> >
> > Would you mind opening another issue with more detailed information, ie
> > the exact versions of javadoc, xdoc and site plugin that you are using,
> > and the files that are generated in target/javadoc? Or even better, a
> > small, reproducible test case? It's weird though that it works with xdoc
> > but not with site.
> >
> > Thanks,
> > Lukas
> >
> >
> > Jeff Jensen wrote:
> > > Hi,
> > >
> > > Our Javadoc Warnings Report run with maven site has failed for along time.
> > I
> > > finally have time to (hopefully!) resolve the problem.
> > >
> > > The report will state the number of files, number of errors=0, and an 
> > > empty
> > > Files section.
> > >
> > > Running it with maven.javadoc.debug=true, the following info is in the log
> > (the
> > > first error message):
> > >
> > > Read 276 line(s) from input file
> > > Building map from 276 input line(s)
> > > Parsing line   [javadoc]
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > > *** WARNING: exception parsing line '  [javadoc]
> > >
> >
> C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > > java.lang.NoSuchMethodError:
> > >
> >
> org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > > at
> > >
> >
> org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
> > >
> > >
> > > This failure repeats many times, I think for every warning in the file.
> > >
> > >
> > > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> > >
> > > Nothing is obvious to me at this point - I keep reviewing the jelly file
> > hoping
> > > to find something.  Does it to anyone else?
> > >
> > >
> > > -
> > > 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]

properties files

2006-02-07 Thread Kevin Galligan

I know that we should use the resources directory to store properties 
files, but to ease our platform build changes, I'd like to leave 
properties files in the java source directory.  It looks like the jar 
plugin moves xml files over.  Is there a way to force properties files 
as well?


Thanks,
-Kevin

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

Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty

2006-02-07 Thread Jeff Jensen

Hello Lukas!  Thank you for the prompt reply and interest to help  :-)

Yes, you did!  I know it worked for awhile, I am not sure when/how it broke
again.  I only know it has been broken for awhile.

This is a different problem this time, and it exists across all 4 of our
projects (the small and large).

I will gladly create that JIRA next...
I will first create it with all the details I can, then try to make a small test
case.


Quoting Lukas Theussl <[EMAIL PROTECTED]>:

> Hi Jeff,
>
> I thought we had resolved all your problems with javadoc warnings ;)
>
> Would you mind opening another issue with more detailed information, ie
> the exact versions of javadoc, xdoc and site plugin that you are using,
> and the files that are generated in target/javadoc? Or even better, a
> small, reproducible test case? It's weird though that it works with xdoc
> but not with site.
>
> Thanks,
> Lukas
>
>
> Jeff Jensen wrote:
> > Hi,
> >
> > Our Javadoc Warnings Report run with maven site has failed for along time.
> I
> > finally have time to (hopefully!) resolve the problem.
> >
> > The report will state the number of files, number of errors=0, and an empty
> > Files section.
> >
> > Running it with maven.javadoc.debug=true, the following info is in the log
> (the
> > first error message):
> >
> > Read 276 line(s) from input file
> > Building map from 276 input line(s)
> > Parsing line   [javadoc]
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > us.state.vantage.hm.ar.entity.AccountAWPContainer
> > *** WARNING: exception parsing line '  [javadoc]
> >
>
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
> > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
> > us.state.vantage.hm.ar.entity.AccountAWPContainer':
> >
>
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > java.lang.NoSuchMethodError:
> >
>
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
> > at
> >
>
org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)
> >
> >
> > This failure repeats many times, I think for every warning in the file.
> >
> >
> > But, if I run "maven javadoc xdoc" only, the file parses correctly.
> >
> > Nothing is obvious to me at this point - I keep reviewing the jelly file
> hoping
> > to find something.  Does it to anyone else?
> >
> >
> > -
> > 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]

where to define custom compiler?

2006-02-07 Thread Marc Dugger

 
Instead of JavacCompiler, I'd like to try my own implementation
(Javac13Compiler) that attempts to shorten the command line arguments. 
Where do I define the which implementation to use so it's picked up by
M2?  Thanks.

Marc Dugger
[EMAIL PROTECTED]


6% real estate sales commission? Not likely.
Learn why at http://tinyurl.com/dvkbu






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

Re: [m2] Docs of "fileset" elements

2006-02-07 Thread dan tran

   
   
  tools
   
   jmlib/**
   
   


On 2/7/06, Rollo, Dan <[EMAIL PROTECTED]> wrote:
>
> I can't seem to find documentation about exactly which sub elements are
> valid in a Fileset.
>
> I have an assembly descriptor in which I'd like to include files from a
> location under the basedir, but I don't want all the parent dirs
> included in the path in the final output zip. I thought specifying the
> "dir" of the fileset should do what I need, but I can't get it to work.
>
> Example project tree:
> appname
>tools
>jmlib
>otherlib
>src
>main
>assembly->  bin.xml
>
>
> For example, in the assembly descriptor:
> "bin.xml"
>
> 
>bin
>
>zip
>
>
> 
>
>tools/jmlib/**
>
>
>
> 
>
> The assembly descriptor above includes the desired files, but the paths
> in the jar are like below:
> appname-1.0-SNAPSHOT/tools/jmllib
>
> What I really want is (no "tools" dir in the path inside the jar):
> appname-1.0-SNAPSHOT/jmllib
>
> Thanks,
> Dan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

[m2] Docs of "fileset" elements

2006-02-07 Thread Rollo, Dan

I can't seem to find documentation about exactly which sub elements are
valid in a Fileset.

I have an assembly descriptor in which I'd like to include files from a
location under the basedir, but I don't want all the parent dirs
included in the path in the final output zip. I thought specifying the
"dir" of the fileset should do what I need, but I can't get it to work.

Example project tree:
appname
tools
jmlib
otherlib
src
main
assembly->  bin.xml


For example, in the assembly descriptor:
"bin.xml"


bin

zip


 

tools/jmlib/**





The assembly descriptor above includes the desired files, but the paths
in the jar are like below:
appname-1.0-SNAPSHOT/tools/jmllib

What I really want is (no "tools" dir in the path inside the jar):
appname-1.0-SNAPSHOT/jmllib

Thanks,
Dan

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

Re: [m1.1b2] Javadoc plugin 1.8 warnings report is empty

2006-02-07 Thread Lukas Theussl


Hi Jeff,

I thought we had resolved all your problems with javadoc warnings ;)

Would you mind opening another issue with more detailed information, ie 
the exact versions of javadoc, xdoc and site plugin that you are using, 
and the files that are generated in target/javadoc? Or even better, a 
small, reproducible test case? It's weird though that it works with xdoc 
but not with site.


Thanks,
Lukas


Jeff Jensen wrote:

Hi,

Our Javadoc Warnings Report run with maven site has failed for along time.  I
finally have time to (hopefully!) resolve the problem.

The report will state the number of files, number of errors=0, and an empty
Files section.

Running it with maven.javadoc.debug=true, the following info is in the log (the
first error message):

Read 276 line(s) from input file
Building map from 276 input line(s)
Parsing line   [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer
*** WARNING: exception parsing line '  [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer':
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
java.lang.NoSuchMethodError:
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
at
org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)


This failure repeats many times, I think for every warning in the file.


But, if I run "maven javadoc xdoc" only, the file parses correctly.

Nothing is obvious to me at this point - I keep reviewing the jelly file hoping
to find something.  Does it to anyone else?


-
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: AW: AW: m2 and perforce ???

Maven is actually composed of about a million little versioned jars.  I'm 
referring to the Maven SCM subsystem, whose latest release is 1.0-beta-2.  You 
would need to check out the maven scm source code and build it to get the 
latest binaries and then update the release and scm plugins to use those 
binaries by updating their POMs in your repository.  Realistically it's not for 
the faint-hearted or a Maven newbie.  I wish I had a better answer for you but 
I don't.  :-(

Yes, you have the release process right - prepare then perform.  If you look at 
the earliest error message, it seems to indicate that your SCM URL is malformed.

mike 

-Original Message-
From: Esteban Chavez [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 2:24 PM
To: Maven Users List
Subject: AW: AW: AW: m2 and perforce ???

Mike,

do you mean maven 2.0.1 as the latest publically available build ?

If it helps, I will upgrade...

An other question :
After a (successful) "maven scm:update", I was trying to create a release of my 
project.
I executed "maven -X release:update" but got the error below.

After "release:update" I suppose I have to run "maven -X release:perform".
For my understanding, am I on the right way ?
Where will I have to specify the release number (e.G '1.0.0') for the release ?

Mike, if these things are described in the maven documentation somewhere, then 
please don't care.
I'm looking for it...

Esteban.



+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und 
Einstellungen\Tevan\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'd:\tools\maven-2.0.1\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository 
central [DEBUG] Retrieving parent-POM from the repository for project:
null:maven-release-plugin:maven-plugin:2.0-beta-3
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] -
---
[DEBUG] ecb:ecb-presentation-tiles:war:1.0-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-api:jar:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-utils:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-manager-plexus:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-managers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for
runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-svn:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2
(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-project:jar:2.0
[DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache

[m1.1b2] Javadoc plugin 1.8 warnings report is empty

2006-02-07 Thread Jeff Jensen

Hi,

Our Javadoc Warnings Report run with maven site has failed for along time.  I
finally have time to (hopefully!) resolve the problem.

The report will state the number of files, number of errors=0, and an empty
Files section.

Running it with maven.javadoc.debug=true, the following info is in the log (the
first error message):

Read 276 line(s) from input file
Building map from 276 input line(s)
Parsing line   [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer
*** WARNING: exception parsing line '  [javadoc]
C:devrootperforcehealthmatchcommonmainsrcjavausstatevantagehmarentityAccountAWPContainer.java:66:
warning - Tag @see: can't find setAutomaticWithdrawalPlan. in
us.state.vantage.hm.ar.entity.AccountAWPContainer':
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
java.lang.NoSuchMethodError:
org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set;
at
org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295)


This failure repeats many times, I think for every warning in the file.


But, if I run "maven javadoc xdoc" only, the file parses correctly.

Nothing is obvious to me at this point - I keep reviewing the jelly file hoping
to find something.  Does it to anyone else?


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

Re: project specific local repos

2006-02-07 Thread Stefan Podkowinski

The plugin looks interesting but its not quite what I need. Although
the assemble plugin allows to create custom source distributions with
gathered libs I dont get why I should do this since my project *is*
actually the source ;)

What I like to do is to ship my maven project as it is including a
repository with all dependencies (which includes non-public jars or
patched jars). So even when the sky is falling and the last public
repo is gone, I can be sure my project compiles fine and I'm further
able to distribute it to others. Is there any standard way how this
could be done with maven? I'm aware that this possibly goes against
the whole 'no binaries in cvs' idea but I really wonder why I have to
setup my own remote repo and - even worse - why everyone else who
likes to work on the sources will have as well, just to keep some
control over artifacts.

On 2/7/06, John Casey <[EMAIL PROTECTED]> wrote:
> This is probably going to be *a lot* easier for you:
>
> http://maven.apache.org/guides/mini/guide-assemblies.html
>
> Cheers,
>
> John
>
> Stefan Podkowinski wrote:
> > Hello
> >
> > Whats the best way to distribute your project if you need to provide
> > all artifacts incl. dependencies with your release? E.g. if you want
> > to ship everything on CD, or just have a lot of artifacts that are not
> > available on public repos.
> >
> > I wonder if it would be possible to create a project specific local
> > repo that is refered to from pom.xml? But as far as I could tell
> > theres only a config option for remote repos and I didnt have much
> > success with it.. Am I missing something or how would I do this?
> >
> > Regards,
> > Stefan
> >
> > -
> > 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: multiproject/module site ETA

2006-02-07 Thread Kristof Vanbecelaere


On Feb 7, 2006, at 0:35, Brett Porter wrote:

Yes, you just need to install the skins first with - 
DupdateReleaseInfo=true set.


Sorry, I don't have a clue. Can you elaborate?

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

Re: Generating a jboss wsr file

2006-02-07 Thread Brad O'Hearne

I hadn't heard from anyone on this, but just a yeah or nay on whether  
WSR files are supported would be helpful. Is anyone else out there  
using JBoss, and building wsr's (web service archives)? As with all  
of these JBossian archives, they are just JAR files with different  
extensions. Does anyone have a suggestion on the best way to build  
and publish what essentially is a jar but with a different extension  
(wsr instead of jar)?


Thanks for your help.

Brad


On Feb 6, 2006, at 6:41 PM, Brad O'Hearne wrote:


Is there a way to generate a jboss wsr file using maven?

Brad

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

AW: AW: AW: m2 and perforce ???

Mike,

do you mean maven 2.0.1 as the latest publically available build ?

If it helps, I will upgrade...

An other question :
After a (successful) "maven scm:update", I was trying to create a release of
my project.
I executed "maven -X release:update" but got the error below.

After "release:update" I suppose I have to run "maven -X release:perform".
For my understanding, am I on the right way ?
Where will I have to specify the release number (e.G '1.0.0') for the
release ?

Mike, if these things are described in the maven documentation somewhere,
then please don't care.
I'm looking for it...

Esteban.



+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und
Einstellungen\Tevan\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'd:\tools\maven-2.0.1\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-release-plugin:maven-plugin:2.0-beta-3
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] -
---
[DEBUG] ecb:ecb-presentation-tiles:war:1.0-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-api:jar:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-utils:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-manager-plexus:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-managers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for
runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-svn:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2
(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-project:jar:2.0
[DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-profile:jar:2.0
[DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-cvs:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-alpha-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-core:jar:2.0
[DEBUG]   org.apache.maven:maven-core:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-plugin-parameter-documen

classpath/manifest file in jar

2006-02-07 Thread Kristof Vanbecelaere


Hi,

when using 2.1-SNAPSHOT of maven-jar-plugin, is there a way of  
getting a custom manifest file in a jar? Or getting classpath entries  
in the generated manifest? And which would that be?


Is the info in http://maven.apache.org/guides/mini/guide- 
manifest.html still applicable to 2.1-SNAPSHOT (my impression is it  
isn't)?


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

RE: AW: AW: m2 and perforce ???

You are running the latest publically available build.  I know there was a 
problem with sync'ing with your version which was fixed soon after the beta-2 
release so I suspect you are seeing that bug.  The latest SNAPSHOT version is 
pretty stable (has not changed in 2-3 weeks or so with no known issues) so you 
might consider trying that if you continue to see sync issues.

mike

-Original Message-
From: Esteban Chavez [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 1:27 PM
To: Maven Users List
Subject: AW: AW: AW: m2 and perforce ???

Mike,

thanks for the help !

I ran maven -X scm:update --> it was now successful (see trace below) !
I don't understand what happened :o(
Could you please give some explanations about the log ?
Did I run it with a newer plug-in version ?

Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -X scm:update
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und 
Einstellungen\Tevan\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'd:\tools\maven-2.0.1\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[DEBUG] maven-scm-plugin: resolved to version 1.0-beta-2 from repository 
central [DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)
[INFO] -
---
[DEBUG] org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-settings:jar:2.0
[DEBUG]   org.apache.maven:maven-settings:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG]   junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-cvs:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-api:jar:1.0-beta-2
[DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0-beta-2 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-local:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-local:jar:1.0-beta-2
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-starteam:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-manager-plexus:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-managers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-utils:jar:1.0.1
[DEBUG]   plexus:plexus-utils:jar:1.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-clearcase:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-perforce:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-2
(selected for runt

Re: Using


You should probably look into turning the websphere_tasks project into a
plugin with multiple mojos, as described in:

http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html

This will make those Ant scriptlets reusable, without clogging up your
POM inheritance hierarchy.

Cheers,

John

Dixit, Sandeep (ProSource Solutions) wrote:

Hi John,


From the websphere_tasks project (a pom-only project that is using an

antrun plugin. There is no jar.) I am inheriting the WebSphere admin
functionality (WebSphere deploy, install, uninstall, etc.) in EAR module
only. 


From the parent distributionProject pom, I am inheriting the common

dependencies.

Thanks,
Sandeep

-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 10:48 AM

To: Maven Users List
Subject: Re: Using 

In general, Maven follows the Java-ish single-inheritance model. What 
you're trying to do is multiple inheritance of POMs, which we don't

support.

What specifically is in your websphere tasks project that you want 
inherited here? Maybe there is another approach that will solve your 
problem, but I cannot tell from this little information...


-john

Dixit, Sandeep (ProSource Solutions) wrote:

Here is my project structure:

- websphere tasks project (deployed in the rep)
- distributionProject
- EJB module : pom inherits distributionProject pom
- WEB module : pom inherits distributionProject pom
- EAR module : pom inherits distributionProject pom; I ALSO WANT
inherit websphere tasks here. However my websphere project is non-jar,
POM only project.

Could you please provide me some pointers on how to achieve this? I

was

thinking of using  to achieve this...

Thanks,
Sandeep



-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 06, 2006 4:53 PM

To: Maven Users List
Subject: Re: Using 

Not sure what the end goal is here, but I assume you're saying you're 
trying to do something like:



   
 
   some.group.id
   some-artifact
   1.1.1.1
   pom
 
   


Other than playing the trick of having that POM's dependencies all 
included in the core classloader of Maven, I'm not sure what this
would 

acoomplish. BTW, it's entirely possible that the  element isn't


allowed here, I don't remember for sure. It would seem to make some 
amount of sense not to allow this, though...


-john

Dixit, Sandeep (ProSource Solutions) wrote:

Is there a way to extend a POM only project using
... tag?

I am not able to do so as by default extension is looking for JAR

type

project. And mine is POM. Extension tag is not allowing defining of
 tag.

Thanks,
Sandeep






---

***National City made the following annotations




---

This communication is a confidential and proprietary business

communication.  It is intended solely for the use of the designated
recipient(s).  If this communication is received in error, please
contact the sender and delete this communication.




===

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





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

AW: AW: AW: m2 and perforce ???

Mike,

thanks for the help !

I ran maven -X scm:update --> it was now successful (see trace below) !
I don't understand what happened :o(
Could you please give some explanations about the log ?
Did I run it with a newer plug-in version ?

Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -X scm:update
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und
Einstellungen\Tevan\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'd:\tools\maven-2.0.1\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[DEBUG] maven-scm-plugin: resolved to version 1.0-beta-2 from repository
central
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)
[INFO] -
---
[DEBUG] org.apache.maven.plugins:maven-scm-plugin:maven-plugin:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-settings:jar:2.0
[DEBUG]   org.apache.maven:maven-settings:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(selected for runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG]   junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-cvs:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-api:jar:1.0-beta-2
[DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0-beta-2 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-local:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-local:jar:1.0-beta-2
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-starteam:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-manager-plexus:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-managers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-utils:jar:1.0.1
[DEBUG]   plexus:plexus-utils:jar:1.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-clearcase:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-perforce:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-2
(selected for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:maven-plugin-api:jar:2.0
[DEBUG]   org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-provider-svn:jar:1.0-beta-2
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-scm-providers:pom:1.0-beta-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-beta-2
(selected for runtime)
[DEBUG] Configuring mo

Failure to inject ScmManager, bug in maven-embedder?

2006-02-07 Thread Michael Böckling


Hello List!

In a custom mojo, I have a plexus component field like this:

 /**
  * @component
  */
 private ScmManager scmManager;


Using the Plug-In on the commandline works, but when I try to execute 
the Mojo using the maven-embedder, I get an IllegalArgumentException. 
Could this be a bug in the embedder, or why isn't this working?

Partial stack:

...
   ... 13 more
Caused by: 
org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException: 
Error composing component
   at 
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
   at 
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
   at 
org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)

   ... 16 more
Caused by: 
org.codehaus.plexus.component.composition.CompositionException: 
Composition failed for the field scmManager in object of type 
com.giniality.TransferMojo
   at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:144)
   at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
   at 
org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
   at 
org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
   at 
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)

   ... 18 more
Caused by: java.lang.IllegalArgumentException
   at sun.reflect.UnsafeObjectFieldAccessorImpl.set(Unknown Source)
   at java.lang.reflect.Field.set(Unknown Source)
   at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:137)

   ... 22 more

Is there a reason? Should I file a Jira?

Regards,
   Michael

--
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69
[EMAIL PROTECTED]; http://www.giniality.com/



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

RE: [m2] parent pom

2006-02-07 Thread Frank Russo

I don't think you have to. I don't have it in mine, and it works fine.

Maybe she included it as an example... 

Frank Russo
Senior Developer
FX Alliance, LLC

-Original Message-
From: Mang Jun Lau [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 10:33 AM
To: Maven Users List
Subject: Re: [m2] parent pom

Thanks for that sample.  It helps out a lot.  I was wondering why we
have to depend on maven-model?  What is that for?

Thanks.

_Mang

Maria Odea Ching <[EMAIL PROTECTED]>
01/30/2006 10:17 PM
Please respond to
"Maven Users List" 

To
Maven Users List 
cc

Subject
Re: [m2] parent pom

Hi Fredy,

The concept of parent poms can be applied to multi-module projects 
wherein it provides you the priviledge of building your modules 
individually or as a whole (project).
You need to define your parent pom in your project's root directory (ex.

C:\Project\pom.xml ) and the children pom in each module's root 
directory (ex. C:\Project\module-1\pom.xml).

Please take a look below at the sample parent and child poms.

Parent POM:

  4.0.0
  sample.project
  sample
  pom
  Sample Project
  1.0-SNAPSHOT
  This is a sample project

module-1
module-2
module-3

  junit
  junit
  3.8.1
  test

org.apache.maven
maven-model
2.0

Module-1 Child POM:
http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

sample.project
sample
1.0-SNAPSHOT

  4.0.0
  module-1
  Sample Project Module 1

  org.apache.maven
  maven-model

Thanks,
Odea

Fredy wrote:

>hi,
>i've read something about the parent pom at multiple places, but have
not 
found an explanation about it.
>Is there a doc about parent pom's? Where to define it, how to extend
it?? 
Do it mean a pom in a multi module project like mojo-sandbox?
>
>Fredy
>
>-
>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: [ANN] Maven Dashboard Plugin 1.9 for Maven 1.x released

2006-02-07 Thread Lukas Theussl

Sorry, this is somewhat hidden in the properties:

http://maven.apache.org/maven-1.x/reference/plugins/dashboard/properties.html

Look for the maven.dashboard.sort and maven.dashboard.sort.property
properties. The latter defaults to 'name', but can be any element
defined in your pom, eg 'developers.developer.name'.

-Lukas

Wim Deblauwe wrote:

Thank you for still supporting Maven 1.x!

How does the sorting work. I could not find any clue in the jira issue?

regards,

Wim

2006/2/6, [EMAIL PROTECTED] < [EMAIL PROTECTED]>:

We are pleased to announce the Maven Dashboard Plugin 1.9 release!

http://maven.apache.org/maven-1.x/reference/plugins/dashboard/

Generate a dashboard containing global statistics about other maven
reports

===

Changes in this version include:

New Features:

o Allow sorting of dashboard items (requires Maven 1.1). Fixes
MPDASHBOARD-28.
o Add message on status of finding dashboard-single.xml. Fixes
MPDASHBOARD-30. Thanks to Jeff Jensen.
o Add new aggregators jiraopenand jirascheduled.
o Added Cobertura aggregator. Fixes MPDASHBOARD-31.

Fixed bugs:

o Fix count of changelog-entries with maven-changelog-plugin-1.9. Fixes
MPDASHBOARD-35. Thanks to Christoph Jerolimov.
o Incorrect links with multiproject independent navigation. Fixes
MPDASHBOARD-24. Thanks to Wim Deblauwe.
o maven.dashboard.report.showemptyproperty not honored. Fixes
MPDASHBOARD-32.
Thanks to Wim Deblauwe.
o Cobertura aggregator doesn't support offline mode. Fixes MPDASHBOARD-34.

Thanks to Philippe Kernevez.
o Properties maven.dashboard.basedir, maven.dashboard.includes,
maven.dashboard.excludesand maven.dashboard.ignoreFailureswere ignored
and
were always defaulting to their multiproject plugin counterpart. Fixes
MPDASHBOARD-27.
o The JUnit pass rate aggregator was no longer showing values in the
dashboard. Fixes MPDASHBOARD-26. Thanks to Wim Deblauwe.

Changes:

o Update the default checkstyle report location to make it compatible with

Checkstyle plugin 3.0+ (MPCHECKSTYLE-40). Fixes MPDASHBOARD-33. Thanks
to
[EMAIL PROTECTED]

===

To automatically install the plugin, type the following on a single line:

maven plugin:download

-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/

-DgroupId=maven
-DartifactId=maven-dashboard-plugin
-Dversion=1.9

For a manual installation, you can download the plugin here:

http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.9.jar

Have fun!
-The Maven Dashboard Plugin development team

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

RE: m2 and perforce ???

2006-02-07 Thread Helck, Christopher

Hi Esteban,

Somehow you need to find out the exact command that maven2 is trying to 
execute. In maven1 the -X usaully did this, but in Maven2 it doesn't seem to. 
If you want I'll give it a try. Please send me the snippet of XML you use to 
setup Perforce in pom.xml.

Regards,
C. Helck

-Original Message-
From: Esteban Chavez [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 4:58 AM
To: Maven Users List
Subject: AW: m2 and perforce ???


Hi Emmanuel,

This is what I get when running the update goal. ('maven' is my own alias for 
'mvn') Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'. [INFO] 
-
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)
[INFO] -
---
[INFO] [scm:update]
[ERROR] Provider message:
[ERROR] Unable to sync
[ERROR] Command output:
[ERROR]
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Command failed.
[INFO] -
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:555)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
faultLifecycleExecutor.java:485)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:455)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:303)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:216)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
at 
org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java
:252)
at
org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:432)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:530)
... 16 more
[INFO] -
---
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Feb 07 10:55:07 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] -
---




-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 10:44
An: Maven Users List
Betreff: Re: m2 and perforce ???


Do you have an error or something?

Emmanuel

Esteban Chavez a écrit :
> Hi,
>
> is there someone who got already m2 and perforce running together ? 
> I'm unable to make a source update (mvn -e scm:update)
>
> mvn -e scm:status --> is ok
> mvn -e scm:validate --> is ok
>
> "p4 sync -f" --> is ok
>
> Thank you very much !
>
> Esteban.
>
>
> Esteban Chávez Baroni
> banking objects
>
> Moorweg 8
> 22453 Hamburg
> Phone: +49 -(0)40 - 57006757
> Mobile: +49 -(0)163 -5813639
> Mail: [EMAIL PROTECTED]
> Web: www.banking-objects.de
>
>
>
>
> --
> --
>
> -
> 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: AW: AW: m2 and perforce ???

"Unable to sync" usually indicates the user is not logged in.  Obviously that 
sounds like that is not the case here.

Esteban, turn on debugging with -X and send me the relevant output directly in 
email please.

mike


-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 10:50 AM
To: Maven Users List
Subject: Re: AW: AW: m2 and perforce ???

I don't know, i never used Perforce.

Mike, any idea?

Emmanuel

Esteban Chavez a écrit :
> I suppose, I'm logged in.
> Otherwise 'p4 sync -f" would produce an error, isn't it ?
> Is there a command to test if the used user is logged in ?
> 
> Further, I ran the following goal
> 
> maven -e scm:update -Dusername=ecb -Dpassword=MY_PASSWD --> NOK
> 
> 
> "p4 info" returned :
> 
> D:\p4client\components\ecb-presentation-tiles>p4 info User name: ecb 
> Client name: ECB Client host: ECB Client root: D:\p4client\components 
> Current directory: d:\p4client\components\ecb-presentation-tiles
> Client address: 127.0.0.1:3730
> Server address: localhost:1666
> Server root: C:\Programme\Perforce
> Server date: 2006/02/07 12:10:03 +0100 Westeuropõische Normalzeit 
> Server version: P4D/NTX86/2003.2/62096 (2004/06/08) Server license: 
> none
> 
> Is it possible that the problem is caused by my perforce version ? I 
> don't have any license, it's a single user installation (for free).
> 
> Thanks, Emmanuel !
> 
> Esteban.
> 
> 
> -Ursprüngliche Nachricht-
> Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 7. Februar 2006 11:31
> An: Maven Users List
> Betreff: Re: AW: m2 and perforce ???
> 
> 
> Are you logged in to Perforce?
> 
> I think perforce provider requires that you're logged in.
> 
> Emmanuel
> 
> Esteban Chavez a écrit :
> 
>>Hi Emmanuel,
>>
>>This is what I get when running the update goal. ('maven' is my own 
>>alias for 'mvn') Esteban.
>>
>>
>>D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
>>+ Error stacktraces are turned on.
>>[INFO] Scanning for projects...
>>[INFO] Searching repository for plugin with prefix: 'scm'.
>>
> 
> [INFO] 
> -
> 
>>---
>>[INFO] Building Maven Webapp Archetype
>>[INFO]task-segment: [scm:update] (aggregator-style)
>>
> 
> [INFO] 
> -
> 
>>---
>>[INFO] [scm:update]
>>[ERROR] Provider message:
>>[ERROR] Unable to sync
>>[ERROR] Command output:
>>[ERROR]
>>
> 
> [INFO] 
> -
> 
>>---
>>[ERROR] BUILD ERROR
>>
> 
> [INFO] 
> -
> 
>>---
>>[INFO] Command failed.
>>
> 
> [INFO] 
> -
> 
>>---
>>[INFO] Trace
>>org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau
> ltLife
> 
>>cycleExecutor.java:555)
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG
> oal(De
> 
>>faultLifecycleExecutor.java:485)
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defaul
> tLifec
> 
>>ycleExecutor.java:455)
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> leFail
> 
>>ures(DefaultLifecycleExecutor.java:303)
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(Defa
> 
>>ultLifecycleExecutor.java:216)
>>at
>>
> 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ecycle
> 
>>Executor.java:139)
>>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>>at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at
>>
> 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39
> 
>>)
>>at
>>
> 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl
> 
>>.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:585)
>>at
>>org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>at
>>org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
>>at
>>
> 
> org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMoj
> o.java
> 
>>:252)
>>at
>>org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
>>at
>>
> 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultP

Re: Compile with 1.5

2006-02-07 Thread Alejandro Sarco

John, thanks for the answer. Yes, I did read these. But the problem is 
I'm not explicitly calling the compiler plugin from my poms because I'm 
using all the defaults.
Unless... are you suggesting to add an otherwise empty  entry 
with only these two parameters in my master pom?.

I will try it now trying... it works!!

Thank you very much!
Alex.


John Casey wrote:

You should read these:

* http://maven.apache.org/guides/mini/guide-configuring-plugins.html
* http://maven.apache.org/plugins/maven-compiler-plugin/howto.html

That last one contains something like this:


  

  maven-compiler-plugin
  
1.5
1.5
  

  


-john

Alejandro Sarco wrote:

Hello,

How can I tell the compiler plugin to compile for 1.5, if I'm using 
all the defaults and my poms don't name the maven-compiler-plugin at 
all?

Is there a central configuration for plugins?
Adding 1.5 as a property in the 
profiles doesn't helps.


Thanks,
Alex.

-
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: AW: AW: m2 and perforce ???


I don't know, i never used Perforce.

Mike, any idea?

Emmanuel

Esteban Chavez a écrit :

I suppose, I'm logged in.
Otherwise 'p4 sync -f" would produce an error, isn't it ?
Is there a command to test if the used user is logged in ?

Further, I ran the following goal

maven -e scm:update -Dusername=ecb -Dpassword=MY_PASSWD --> NOK


"p4 info" returned :

D:\p4client\components\ecb-presentation-tiles>p4 info
User name: ecb
Client name: ECB
Client host: ECB
Client root: D:\p4client\components
Current directory: d:\p4client\components\ecb-presentation-tiles
Client address: 127.0.0.1:3730
Server address: localhost:1666
Server root: C:\Programme\Perforce
Server date: 2006/02/07 12:10:03 +0100 Westeuropõische Normalzeit
Server version: P4D/NTX86/2003.2/62096 (2004/06/08)
Server license: none

Is it possible that the problem is caused by my perforce version ? I don't
have any license, it's a single user installation (for free).

Thanks, Emmanuel !

Esteban.


-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 11:31
An: Maven Users List
Betreff: Re: AW: m2 and perforce ???


Are you logged in to Perforce?

I think perforce provider requires that you're logged in.

Emmanuel

Esteban Chavez a écrit :


Hi Emmanuel,

This is what I get when running the update goal. ('maven' is my own alias
for 'mvn')
Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.



[INFO] -


---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)



[INFO] -


---
[INFO] [scm:update]
[ERROR] Provider message:
[ERROR] Unable to sync
[ERROR] Command output:
[ERROR]



[INFO] -


---
[ERROR] BUILD ERROR



[INFO] -


---
[INFO] Command failed.



[INFO] -


---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife


cycleExecutor.java:555)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De


faultLifecycleExecutor.java:485)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec


ycleExecutor.java:455)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail


ures(DefaultLifecycleExecutor.java:303)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa


ultLifecycleExecutor.java:216)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle


Executor.java:139)
   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at



sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39


)
   at



sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl


.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
   at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
   at



org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java


:252)
   at
org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
   at



org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage


r.java:432)
   at



org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife


cycleExecutor.java:530)
   ... 16 more



[INFO] -


---
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Feb 07 10:55:07 CET 2006
[INFO] Final Memory: 3M/6M



[INFO] -


---




-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 10:44
An: Maven Users List
Betreff: Re: m2 and perforce ???


Do you have an error or something?

Emmanuel

Esteban Chavez a écrit :



Hi,

is there someone who got already m2 and perforce runni

Re: How to install sources

2006-02-07 Thread Erick Dovale


Hi Darryl,
I mean the project's source jar not the dependencies and by install i 
mean to install them in the local repo.
I could use the install plugin to do this but I was wondering if there 
was a way of doing it all together in a single step..


thanks..

erick.

Darryl L. Pierce wrote:


Erick Dovale wrote:

 


Hi there,
can any one tell how can I install the sources jar of the artifacts in
the local repository??
   



Do you mean the source files for your dependencies or the source files for
what you're producing?

 



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

RE: Automating release:prepare

I don't think the release plugin is designed to do what you want.
Releases are supposed to be feature complete, developer-approved
artifacts designed to be used externally.  Automation is impossible with
that definition.

I assume you want numbered releases so you have an exact manifest of
what your system is running in each daily build?  Sounds like you need a
mix of snapshots and releases, something like numbered snapshots.
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 9:37 AM
To: Maven Users List
Subject: Automating release:prepare

I would like to execute a release:prepare and release:perform from 
continuum nightly.   The release:prepare step prompts for tag name, next

version name, etc.   Looking at 
 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
it appears there may be a way to do this without prompting, but I'm
uncertain what the best way to do this is.

Lets say my version number is 1.0.0.0-SNAPSHOT.Every night, I want
to 
run a release:prepare and release:perform and bump the last digit by 1.

So, I'd want release:prepare to change the version number to 1.0.0.0,
tag it with a label (1.0.0.0) and then bump the version to
1.0.0.1-SNAPSHOT and then commit that.

What approach would I take to do this?   I was thinking about setting 
params in continuum such as, but I dont have access to the version
number 
from there.Should you configure the plugin within the pom to 
accomplish this?If so, what's the best approach for bumping the 
version number?I think the pluginVersionManager may be of use, but
I'm 
not sure.

Any help/direction on this would be greatly appreciated.

Thanks,
Brian Yoffe

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of any
financial instrument or as an official confirmation of any transaction.
All market prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice. Any
comments or statements made herein do not necessarily reflect those of
JPMorgan Chase & Co., its subsidiaries and affiliates



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

RE: Using

2006-02-07 Thread Dixit, Sandeep (ProSource Solutions)

Hi John,

>From the websphere_tasks project (a pom-only project that is using an
antrun plugin. There is no jar.) I am inheriting the WebSphere admin
functionality (WebSphere deploy, install, uninstall, etc.) in EAR module
only. 

>From the parent distributionProject pom, I am inheriting the common
dependencies.

Thanks,
Sandeep

-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 10:48 AM
To: Maven Users List
Subject: Re: Using 

In general, Maven follows the Java-ish single-inheritance model. What 
you're trying to do is multiple inheritance of POMs, which we don't
support.

What specifically is in your websphere tasks project that you want 
inherited here? Maybe there is another approach that will solve your 
problem, but I cannot tell from this little information...

-john

Dixit, Sandeep (ProSource Solutions) wrote:
> Here is my project structure:
> 
> - websphere tasks project (deployed in the rep)
> - distributionProject
>   - EJB module : pom inherits distributionProject pom
>   - WEB module : pom inherits distributionProject pom
>   - EAR module : pom inherits distributionProject pom; I ALSO WANT
> inherit websphere tasks here. However my websphere project is non-jar,
> POM only project.
> 
> Could you please provide me some pointers on how to achieve this? I
was
> thinking of using  to achieve this...
> 
> Thanks,
> Sandeep
> 
> 
> 
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED] 
> Sent: Monday, February 06, 2006 4:53 PM
> To: Maven Users List
> Subject: Re: Using 
> 
> Not sure what the end goal is here, but I assume you're saying you're 
> trying to do something like:
> 
> 
>
>  
>some.group.id
>some-artifact
>1.1.1.1
>pom
>  
>
> 
> 
> Other than playing the trick of having that POM's dependencies all 
> included in the core classloader of Maven, I'm not sure what this
would 
> acoomplish. BTW, it's entirely possible that the  element isn't

> allowed here, I don't remember for sure. It would seem to make some 
> amount of sense not to allow this, though...
> 
> -john
> 
> Dixit, Sandeep (ProSource Solutions) wrote:
>> Is there a way to extend a POM only project using
>> ... tag?
>>
>> I am not able to do so as by default extension is looking for JAR
type
>> project. And mine is POM. Extension tag is not allowing defining of
>>  tag.
>>
>> Thanks,
>> Sandeep
>>
>>
>>
>

> ---
>> ***National City made the following annotations
>>
>

> ---
>> This communication is a confidential and proprietary business
> communication.  It is intended solely for the use of the designated
> recipient(s).  If this communication is received in error, please
> contact the sender and delete this communication.
>

> ===
>> -
>> 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: Automating release:prepare


you'll must remove release.properties after each run.

Emmanuel

John Casey a écrit :
You can run maven in batch mode (-B), which is non-interactive. From 
that point, you'd have to specify a few command-line system properties 
to push in the answers to the questions it asks...I think it'd bump the 
version in the manner you're asking for, but it's going to need some 
testing. :)


The call would probably look something like this:

mvn -B \
  -DtagBase=https://svn.somewhere.com/path/to/repo/tags \
  release:prepare \
  release:perform

I *think* that would do it, but it may take some fine-tuning to get it 
right...for instance, you may need username/password parameters on the 
command-line too, but checking in to the SCM.


Good luck, and let me know if it works!

-john

[EMAIL PROTECTED] wrote:

I would like to execute a release:prepare and release:perform from 
continuum nightly.   The release:prepare step prompts for tag name, 
next version name, etc.   Looking at 
 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html 
it appears there may be a way to do this without prompting, but I'm 
uncertain what the best way to do this is.


Lets say my version number is 1.0.0.0-SNAPSHOT.Every night, I want 
to run a release:prepare and release:perform and bump the last digit 
by 1.  So, I'd want release:prepare to change the version number to 
1.0.0.0, tag it with a label (1.0.0.0) and then bump the version to 
1.0.0.1-SNAPSHOT and then commit that.


What approach would I take to do this?   I was thinking about setting 
params in continuum such as, but I dont have access to the version 
number from there.Should you configure the plugin within the pom 
to accomplish this?If so, what's the best approach for bumping the 
version number?I think the pluginVersionManager may be of use, but 
I'm not sure.


Any help/direction on this would be greatly appreciated.

Thanks,
Brian Yoffe

This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All 
market prices,
data and other information are not warranted as to completeness or 
accuracy and
are subject to change without notice. Any comments or statements made 
herein do not necessarily reflect those of JPMorgan Chase & Co., its 
subsidiaries and affiliates





-
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: Compile with 1.5


You should read these:

* http://maven.apache.org/guides/mini/guide-configuring-plugins.html
* http://maven.apache.org/plugins/maven-compiler-plugin/howto.html

That last one contains something like this:


  

  maven-compiler-plugin
  
1.5
1.5
  

  


-john

Alejandro Sarco wrote:

Hello,

How can I tell the compiler plugin to compile for 1.5, if I'm using all 
the defaults and my poms don't name the maven-compiler-plugin at all?

Is there a central configuration for plugins?
Adding 1.5 as a property in the 
profiles doesn't helps.


Thanks,
Alex.

-
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: Automating release:prepare

You can run maven in batch mode (-B), which is non-interactive. From 
that point, you'd have to specify a few command-line system properties 
to push in the answers to the questions it asks...I think it'd bump the 
version in the manner you're asking for, but it's going to need some 
testing. :)


The call would probably look something like this:

mvn -B \
  -DtagBase=https://svn.somewhere.com/path/to/repo/tags \
  release:prepare \
  release:perform

I *think* that would do it, but it may take some fine-tuning to get it 
right...for instance, you may need username/password parameters on the 
command-line too, but checking in to the SCM.


Good luck, and let me know if it works!

-john

[EMAIL PROTECTED] wrote:
I would like to execute a release:prepare and release:perform from 
continuum nightly.   The release:prepare step prompts for tag name, next 
version name, etc.   Looking at 
 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html it 
appears there may be a way to do this without prompting, but I'm uncertain 
what the best way to do this is.


Lets say my version number is 1.0.0.0-SNAPSHOT.Every night, I want to 
run a release:prepare and release:perform and bump the last digit by 1.  
So, I'd want release:prepare to change the version number to 1.0.0.0, tag 
it with a label (1.0.0.0) and then bump the version to 1.0.0.1-SNAPSHOT 
and then commit that.


What approach would I take to do this?   I was thinking about setting 
params in continuum such as, but I dont have access to the version number 
from there.Should you configure the plugin within the pom to 
accomplish this?If so, what's the best approach for bumping the 
version number?I think the pluginVersionManager may be of use, but I'm 
not sure.


Any help/direction on this would be greatly appreciated.

Thanks,
Brian Yoffe

This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein 
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries 
and affiliates





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

Re: [m102] overriding goal

2006-02-07 Thread Laird Nelson

I see.  So suppose there is a plugin goal named world:destroy and I only
want to run it if the property evil.dictator is set.  How would I do this?
I don't want it to be an error if someone tries to run it without said
property; I just want to silently do nothing.  On the other hand, if that
property is set, then I would like to run the plugin goal.

>From where I sit this seems to be impossible.

Thanks,
Laird

On 2/7/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>
> Hi Laird,
>
> Laird Nelson wrote on Tuesday, February 07, 2006 5:23 AM:
>
> > Leaping in: if you can override a plugin goal, can you call "super"?
> > That is, I'd like my goal override to prevent execution of the "real"
> > goal in some circumstances.  What's the best way to go about this?
>
> No. In that case you have to add your functionality to preGoal/postGoal.
>
> - Jörg
>
> >
> > Thanks,
> > Laird
> >
> > On 1/13/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> >>
> >> Kristof Vanbecelaere wrote on Friday, January 13, 2006 2:27 PM:
> >>
> >>> Hi,
> >>>
> >>> is it correct that in 1.0.2 one can only override project goals but
> >>> not plugin goals?
> >>
> >> No, you can also override plugin goals.
> >>
> >> - Jörg
> >>
> >>
> > -
> >> 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: Does maven 2 really support dependencies of type "war"?


can you post a copy of your POM?

Jason Chaffee wrote:

If I try to add a dependency of type war to my pom, I get the following

Error (note: I can remove war and it doesn’t fail):

 


[ERROR] FATAL ERROR

[INFO]



-

---

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

 

 


Project ID: webaoo:webapp

POM Location: C:\workspace\webapp\pom.xml

Validation Messages:

 


[0]  'dependencies.dependency.version' is missing for

common-assets:common-assets

 

 


Reason: Failed to validate POM

 

 


[INFO]



-

---

[INFO] Trace

org.apache.maven.reactor.MavenExecutionException: Failed to validate POM

at

org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)

at

org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:39)

at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at

org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

at

org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

 


at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Caused by: org.apache.maven.project.InvalidProjectModelException: Failed

to vali

date POM

at

org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog

ic(DefaultMavenProjectBuilder.java:781)

at

org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave

nProjectBuilder.java:631)

at

org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi

le(DefaultMavenProjectBuilder.java:303)

at

org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave

nProjectBuilder.java:274)

at

org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)

at

org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)

at

org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)

... 11 more

 

 


**Jason Chaffee **

**Software Architect/Server Team Manager **

TVWorks

[EMAIL PROTECTED] 

Tel : 415.380.6316

Cell: 415.637.8061

 

 



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

Compile with 1.5

2006-02-07 Thread Alejandro Sarco


Hello,

How can I tell the compiler plugin to compile for 1.5, if I'm using all 
the defaults and my poms don't name the maven-compiler-plugin at all?

Is there a central configuration for plugins?
Adding 1.5 as a property in the 
profiles doesn't helps.


Thanks,
Alex.

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

Re: project specific local repos


This is probably going to be *a lot* easier for you:

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

Cheers,

John

Stefan Podkowinski wrote:

Hello

Whats the best way to distribute your project if you need to provide
all artifacts incl. dependencies with your release? E.g. if you want
to ship everything on CD, or just have a lot of artifacts that are not
available on public repos.

I wonder if it would be possible to create a project specific local
repo that is refered to from pom.xml? But as far as I could tell
theres only a config option for remote repos and I didnt have much
success with it.. Am I missing something or how would I do this?

Regards,
Stefan

-
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: Using

In general, Maven follows the Java-ish single-inheritance model. What 
you're trying to do is multiple inheritance of POMs, which we don't support.


What specifically is in your websphere tasks project that you want 
inherited here? Maybe there is another approach that will solve your 
problem, but I cannot tell from this little information...


-john

Dixit, Sandeep (ProSource Solutions) wrote:

Here is my project structure:

- websphere tasks project (deployed in the rep)
- distributionProject
- EJB module : pom inherits distributionProject pom
- WEB module : pom inherits distributionProject pom
- EAR module : pom inherits distributionProject pom; I ALSO WANT
inherit websphere tasks here. However my websphere project is non-jar,
POM only project.

Could you please provide me some pointers on how to achieve this? I was
thinking of using  to achieve this...

Thanks,
Sandeep



-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 06, 2006 4:53 PM

To: Maven Users List
Subject: Re: Using 

Not sure what the end goal is here, but I assume you're saying you're 
trying to do something like:



   
 
   some.group.id
   some-artifact
   1.1.1.1
   pom
 
   


Other than playing the trick of having that POM's dependencies all 
included in the core classloader of Maven, I'm not sure what this would 
acoomplish. BTW, it's entirely possible that the  element isn't 
allowed here, I don't remember for sure. It would seem to make some 
amount of sense not to allow this, though...


-john

Dixit, Sandeep (ProSource Solutions) wrote:

Is there a way to extend a POM only project using
... tag?

I am not able to do so as by default extension is looking for JAR type
project. And mine is POM. Extension tag is not allowing defining of
 tag.

Thanks,
Sandeep





---

***National City made the following annotations



---

This communication is a confidential and proprietary business

communication.  It is intended solely for the use of the designated
recipient(s).  If this communication is received in error, please
contact the sender and delete this communication.

===

-
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: A local repository acting as a remote one

When designing Maven 2, we found a need for metadata beyond the POM. 
This metadata has to be merged from multiple repositories, so the build 
can take the appropriate actions as if there were only one repository. 
This leads to a difference between the notion of a local repository 
(which really is now much more like a local-only cache) and a remote 
repository (which represents only a fragment of all knowledge available 
to a build).


In short, it was a design decision to make these two separate. We 
considered the case where users would want to reuse a local repository 
as a remote repository, and decided it wasn't a common enough use case 
to override these other design considerations.


What I'd suggest is creating a plugin that will traverse your local 
repository and perform some sort of artifact-deployment to a separate 
remote repository (you can follow the maven-deploy-plugin as a guide for 
this). I know that this will lead to some duplication between your local 
repository and the remote repository used by your devs, but consider 
this: do you really want your developers to pickup *everything* that 
lands in your local repository? Even the things that are still in 
progress, and not ready for general consumption? Wouldn't it be a better 
model to be a bit more deliberate in publishing to their repository? 
Just a thought.


Anyway, sorry for any inconvenience.

-john

Fabrice BELLINGARD wrote:

Hi Maveners,

My case is the following: with Maven 2, I want to have an intermediate
repository for my dev team, so that the developers don't download Jars from
Ibiblio but only from this very repository. This is a common use case lots
of people know.
The difference in my case is that I want to have it on my computer, and I
want my local repository to be this intermediate repository. So to sum up:
my local repository would be the remote repository of my teams. Why ?
Because of 2 main reasons that seem important to me:
- I want to control which components they use (so I don't want a Maven proxy
that would allow them to download any Jars they would want)
- I don't want to have twice the same Jars (once in the intermediate
repository and once in my local repository), because it would take twice the
required space on my hard drive
Theses are the reasons why I want to make my local repository accessible via
HTTP as a remote repository.

However, I made some tests and it seems that there are problems due to the
metadata files: when one of my dev's Maven connects to my local repository
to download a Jar, it can't find the maven metadata file and so my local
repository is blacklisted. It seems that local metadata is different from
remote metadata, which is a pain in my case...


So my questions are: is this the normal behaviour? did I miss something? is
there a workaround for that?
--> Maven developers: shouldn't it be possible to copy-paste a repository
and using it either ways as a remote or a local repository?

Thank you so much in advance for your answers, and please CC me when
answering, I'm not on the list for the moment.

Best regards,
Stephen Fabemn.



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

Automating release:prepare

2006-02-07 Thread brian . a . yoffe

I would like to execute a release:prepare and release:perform from 
continuum nightly.   The release:prepare step prompts for tag name, next 
version name, etc.   Looking at 
 http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html it 
appears there may be a way to do this without prompting, but I'm uncertain 
what the best way to do this is.

Lets say my version number is 1.0.0.0-SNAPSHOT.Every night, I want to 
run a release:prepare and release:perform and bump the last digit by 1.  
So, I'd want release:prepare to change the version number to 1.0.0.0, tag 
it with a label (1.0.0.0) and then bump the version to 1.0.0.1-SNAPSHOT 
and then commit that.

What approach would I take to do this?   I was thinking about setting 
params in continuum such as, but I dont have access to the version number 
from there.Should you configure the plugin within the pom to 
accomplish this?If so, what's the best approach for bumping the 
version number?I think the pluginVersionManager may be of use, but I'm 
not sure.

Any help/direction on this would be greatly appreciated.

Thanks,
Brian Yoffe

This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein 
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries 
and affiliates

Re: [m2] parent pom

2006-02-07 Thread Mang Jun Lau

Thanks for that sample.  It helps out a lot.  I was wondering why we have 
to depend on maven-model?  What is that for?

Thanks.

_Mang

Maria Odea Ching <[EMAIL PROTECTED]> 
01/30/2006 10:17 PM
Please respond to
"Maven Users List" 

To
Maven Users List 
cc

Subject
Re: [m2] parent pom

Hi Fredy,

The concept of parent poms can be applied to multi-module projects 
wherein it provides you the priviledge of building your modules 
individually or as a whole (project).
You need to define your parent pom in your project's root directory (ex. 
C:\Project\pom.xml ) and the children pom in each module's root 
directory (ex. C:\Project\module-1\pom.xml).

Please take a look below at the sample parent and child poms.

Parent POM:

  4.0.0
  sample.project
  sample
  pom
  Sample Project
  1.0-SNAPSHOT
  This is a sample project

module-1
module-2
module-3

  junit
  junit
  3.8.1
  test

org.apache.maven
maven-model
2.0

Module-1 Child POM:
http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

sample.project
sample
1.0-SNAPSHOT

  4.0.0
  module-1
  Sample Project Module 1

  org.apache.maven
  maven-model

Thanks,
Odea

Fredy wrote:

>hi,
>i've read something about the parent pom at multiple places, but have not 
found an explanation about it.
>Is there a doc about parent pom's? Where to define it, how to extend it?? 
Do it mean a pom in a multi module project like mojo-sandbox?
>
>Fredy
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
> 
>

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

Re: [M2] Ant-Script for simple Web-Project


Unfortunately, there seems to be an open TODO in the code for that.

Off the top of my head, I can't imagine how you'd adjust it to work with 
the packaging of the project...at least, not easily. If you'd like to 
take a look at the source, it's here:


http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ant-plugin

If you like, you can add an issue for this in jira at:

http://jira.codehaus.org/browse/MANT

Cheers,

John

Christian Schlaefcke wrote:

Hi Folks,

I need to create a ant build script for a simple web project.

When I run "mvn install" it runs fine and creates a war file. When I run
"mvn ant:ant" and execute the resulting script it just produces a jar
file. How can I tell the ant plugin to create web specific build script?

Regards,

Christian

My pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  de.tonline.app.forum
  WebProj
  war
  1.0-SNAPSHOT
  My Little Webproject
  http://www.mysite.net
  
  
  
APForum
target
WebRoot/WEB-INF/classes
src

  

  maven-war-plugin
  
WebRoot
  

  

  



-
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: Application.xml


You could probably use the appxml attribute, like this:


  ...
  

  maven-ear-plugin
  
/path/to/META-INF/application.xml
  

...
  


-john

[EMAIL PROTECTED] wrote:

Hi ,

I'm getting the following warning  when creating the ear file , 
application.xml is not getting included in the final Ear file.(maven1.x)
 
" selected ear files include a META-INF/application.xml which will be 
ignored (please use appxml attribute to ear task"


Can any one pls help me in figuring out the problem.


Regards
Saravana


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

Re: m2: developing ant plugin - problems passing maven.compile.classpath

2006-02-07 Thread Martin van der Plas


Hi All,

I've the same problem here. How to convert the 
${project.testClassPathElements} into an ant  classpath reference?


Any help  is appreciated.
Thanks.

Martin

[EMAIL PROTECTED] wrote:


I have created an ant plugin with the following mojo:

gateway.mojos.xml



   
  
 generate-transform
 
 generate-xquery
 this target generates the transform driven from
pathMappings.xml
   



Here is the corresponding target within my build script:


 
 
 


I need to pass in the ${maven.compile.classpath} so I can pick up the
saxonsa dependency configured in my plugins pom, so included the xml below
into the gateway.mojos.xml

 
   
  mavenCompileClasspath
  mavenCompileClasspath
  true
  ${maven.compile.classpath}
  java.lang.String
  maven compile classpath.
   
 

Unfortunately, this does not work. Does anyone know how i can pass the
maven.compile.classpath into my build script at runtime?

Thanks,
John



This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein 
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries 
and affiliates



-
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: Scheduling Error

2006-02-07 Thread Gerard Garrigan

Nail on the head,

Thanks very much,

Ger

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] 
Sent: 07 February 2006 14:50
To: continuum-users@maven.apache.org
Subject: Re: Scheduling Error

It's a known issue that will be fix in 1.0.3 
(http://jira.codehaus.org/browse/CONTINUUM-577)

I think it's because you have a schedule without any attached projects. Remove 
this unused schedule 
or attach to it a project.

Emmanuel

Gerard Garrigan a écrit :
>  Hello,
> 
>  I'm using Continuum with a Maven 2 project. It builds fine when you
> force the build but the following error arises when the build is
> scheduled:
> 
>  jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run
> 
>  jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled
> Exception:
> 
>  jvm 1| java.lang.NullPointerException
> 
>  jvm 1|  at
> org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
> um.java:368)
> 
>  jvm 1|  at
> org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
> BuildJob.java:66)
> 
>  jvm 1|  at
> org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> 
>  jvm 1|  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
> :516)
> 
>  jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger
> schedulerError
> 
>  jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception.
> 
>  jvm 1| org.quartz.SchedulerException: Job threw an unhandled
> exception. [See nested exception: java.lang.NullPointerException]
> 
>  jvm 1|  at
> org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> 
>  jvm 1|  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
> :516)
> 
>  jvm 1| * Nested Exception (Underlying Cause) ---
> 
>  jvm 1| java.lang.NullPointerException
> 
>  jvm 1|  at
> org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
> um.java:368)
> 
>  jvm 1|  at
> org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
> BuildJob.java:66)
> 
>  jvm 1|  at
> org.quartz.core.JobRunShell.run(JobRunShell.java:191)
> 
>  jvm 1|  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
> :516)
> 
>  I have replaced continuum-core-1.0.2.jar with
> continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I
> only have one project to build in Continuum. I'm running Continuum in
> Windows. 
> 
>  Any help will be greatly appreciated,
> 
>  Thanks very much
> 
>  
> 
> Ger 
> 
>  
> 
>

Re: release:prepare + cvs : password is required


If you want the fix, you should checkout the release plugin and install it.

Bedin, Stephane (GE Healthcare) a écrit :

How can I update my plugin version of maven-scp to get the correction ?

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: mar. 7 février 2006 15:15
To: Maven Users List
Subject: Re: release:prepare + cvs : password is required


Ok, The released version of release plugin use an old version of maven-scm.

This problem is fixed in svn, if you want to try it.
Other solution is to put your password on scm url but it isn't secure.

Emmanuel

Bedin, Stephane (GE Healthcare) a écrit :


Yes I'm using CVSNT (as part of WinCVS).
(Note: I had also tried : mvn scm:update to get the latest scm plugins)

Here are the traces of 'mvn -Dpassword=your_password release:prepare':

+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and 
Settings\rivieje\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program 
Files\maven-2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository 
central
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-release-plugin:maven-plugin:2.0-beta-3
[INFO] 

[INFO] Building DICOM Objects Checker
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 

[DEBUG] com.gehealthcare:doc:jar:1.2-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]   com.gehealthcare:dicomdatamodel:jar:1.5 (selected for compile)
[DEBUG]   commons-logging:commons-logging:jar:1.0.4 (selected for compile)
[DEBUG]   log4j:log4j:jar:1.2.12 (selected for compile)
[DEBUG]   xml-apis:xml-apis:jar:1.0.b2 (selected for compile)
[DEBUG]   merge:mcw:jar:mc3java265ib3w32 (selected for compile)
[DEBUG]   xalan:xalan:jar:2.7.0 (selected for compile)
[DEBUG] While downloading xml-apis:xml-apis:2.0.2
 This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


[DEBUG]   xerces:xercesImpl:jar:2.7.1 (selected for compile)
[DEBUG]   com.gehealthcare:mergeinstaller:jar:1.2 (selected for compile)
[DEBUG]   com.gehealthcare:dicomservice:jar:1.12 (selected for compile)
[DEBUG] org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for 
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected 
for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-api:jar:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for 
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-utils:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-manager-plexus:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-managers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for 
runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-provider-svn:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2 (selected 
for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-project:jar:2.0
[DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0

RE: release:prepare + cvs : password is required

2006-02-07 Thread Bedin, Stephane \(GE Healthcare\)

How can I update my plugin version of maven-scp to get the correction ?

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: mar. 7 février 2006 15:15
To: Maven Users List
Subject: Re: release:prepare + cvs : password is required


Ok, The released version of release plugin use an old version of maven-scm.

This problem is fixed in svn, if you want to try it.
Other solution is to put your password on scm url but it isn't secure.

Emmanuel

Bedin, Stephane (GE Healthcare) a écrit :
> Yes I'm using CVSNT (as part of WinCVS).
> (Note: I had also tried : mvn scm:update to get the latest scm plugins)
> 
> Here are the traces of 'mvn -Dpassword=your_password release:prepare':
> 
> + Error stacktraces are turned on.
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and 
> Settings\rivieje\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program 
> Files\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository 
> central
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-release-plugin:maven-plugin:2.0-beta-3
> [INFO] 
> 
> [INFO] Building DICOM Objects Checker
> [INFO]task-segment: [release:prepare] (aggregator-style)
> [INFO] 
> 
> [DEBUG] com.gehealthcare:doc:jar:1.2-SNAPSHOT (selected for null)
> [DEBUG]   junit:junit:jar:3.8.1 (selected for test)
> [DEBUG]   com.gehealthcare:dicomdatamodel:jar:1.5 (selected for compile)
> [DEBUG]   commons-logging:commons-logging:jar:1.0.4 (selected for compile)
> [DEBUG]   log4j:log4j:jar:1.2.12 (selected for compile)
> [DEBUG]   xml-apis:xml-apis:jar:1.0.b2 (selected for compile)
> [DEBUG]   merge:mcw:jar:mc3java265ib3w32 (selected for compile)
> [DEBUG]   xalan:xalan:jar:2.7.0 (selected for compile)
> [DEBUG] While downloading xml-apis:xml-apis:2.0.2
>   This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
> 
> 
> [DEBUG]   xerces:xercesImpl:jar:2.7.1 (selected for compile)
> [DEBUG]   com.gehealthcare:mergeinstaller:jar:1.2 (selected for compile)
> [DEBUG]   com.gehealthcare:dicomservice:jar:1.12 (selected for compile)
> [DEBUG] org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3 
> (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> org.apache.maven:maven-artifact-manager:jar:2.0
> [DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for 
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> org.apache.maven:maven-artifact:jar:2.0
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> org.apache.maven:maven-repository-metadata:jar:2.0
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for 
> runtime)
> [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 
> (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-scm-api:jar:1.0-alpha-2
> [DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for 
> runtime)
> [DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> plexus:plexus-utils:jar:1.0.3
> [DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-scm-manager-plexus:jar:1.0-alpha-2
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-scm-managers:pom:1.0-alpha-2
> [DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2 
> (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> plexus:plexus-container-default:jar:1.0-alpha-5
> [DEBUG] Retrieving parent-POM from the repository for project: 
> plexus:plexus-containers:pom:1.0
> [DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for 
> runtime)
> [DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-scm-provider-svn:jar:1.0-alpha-2
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-scm-providers:pom:1.0-alpha-2
> [DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2 
> (selected for runtime)
> [DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: 
> null:maven-project:jar:2.0
> [DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
> [DEBUG] org

Re: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released

2006-02-07 Thread Arnaud HERITIER

I don't know (I don't have the code here) but it must be transparent
do you use maven 1.0.2 also ?

Can you open an issue for these problems of parsers please.

Arnaud

On 2/7/06, Durfee, Bernard <[EMAIL PROTECTED]> wrote:
> I get the following after I upgraded from 2.5 to 3.0...
>
> BUILD FAILED
> File.. \home\.maven\cache\maven-checkstyle-plugin-3.0\plugin.jelly
> Element... style
> Line.. 238
> Column 59
> java.lang.ClassCastException:
> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser
>
> ...I have the Xerces libraries in the JRE's "lib/endorsed" directory,
> but I have the Oracle XML parser specified as the TransformerFactory.
> Does this mean that CheckStyle is now dependant on having Xerces be the
> "active" XML parser?
>
> Bernie
>
>
>
> > -Original Message-
> > From: Eric Rose [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 07, 2006 12:09 AM
> > To: Maven Users List
> > Subject: Re: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released
> >
> >
> > On Tuesday 07 February 2006 06:18, [EMAIL PROTECTED] wrote:
> > > We are pleased to announce the Maven Checkstyle Plugin 3.0 release!
> > >
> > > http://maven.apache.org/maven-1.x/reference/plugins/checkstyle/
> >
> > Hi,
> >
> > I'm using Maven 1.0.2 and had been running with no errors
> > using the Checkstyle
> > Plugin 2.5, but am getting the following after upgrading to
> > version 3.0:
> >
> > checkstyle:init:
> >
> > checkstyle:report:
> > checkstyle:run:
> > [echo] Using
> > file:/usr/local/forge/ForgeLibs/BuildTools/etc/checkstyle.xml
> > for checkstyle ...
> > [echo] LocaleCountry : en
> > [checkstyle] Running Checkstyle 4.1 on 1396 files
> >
> > checkstyle:report-internal:
> > [style]
> > Processing
> > /home/ericr/workspace/mapIntelligence/tmp/checkstyle/checkstyl
> > e-raw-report.xml
> > to
> > /home/ericr/workspace/mapIntelligence/tmp/checkstyle/checkstyl
> > e-summary-report.xml
> > [style] Loading
> > stylesheet
> > /usr/local/mavenPluginRepository/cache/maven-checkstyle-plugin
> > -3.0/plugin-resources/checkstyle-summary.xsl
> >
> > BUILD FAILED
> > File..
> > /usr/local/mavenPluginRepository/cache/maven-checkstyle-plugin
> > -3.0/plugin.jelly
> > Element... style
> > Line.. 238
> > Column 59
> > Provider for javax.xml.transform.TransformerFactory cannot be found
> > Total time: 36 seconds
> > Finished at: Tue Feb 07 15:58:56 EST 2006
> >
> >
> >
> > I presume that I'll have to add
> > -Djavax.xml.transform.TransformerFactory=org.apache.xalan.proc
> > essor.TransformerFactoryImpl
> > somewhere, but I'm not sure where best to put it or of
> > there's a better
> > solution. Any clues?
> >
> > Eric
> >
> > --
> > Eric Rose  | "Sed quis custodiet ipsos custodes?"
> > [EMAIL PROTECTED]   | Juvenal (Satires, VI.347-8)
> >
> > **
> > *
> > This message contains privileged and confidential information intended
> > only for the use of the addressee named above.  If you are not the
> > intended recipient of this message you must not disseminate, copy or
> > take any action in reliance on it.  If you have received this message
> > in error please notify the sender immediately.  Any views expressed in
> > this message are those of the individual sender, except where the
> > sender specifically states them to be the views of another (including
> > a Body Corporate).
> >
> > If you wish to opt out from future messages, send an email to
> > [EMAIL PROTECTED] with the subject UNSUBSCRIBE
> > **
> > **
> >
> >
>
> -
> 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: Ear projects

2006-02-07 Thread Tim Morrow

On 2/7/06, Max Cooper <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-02-06 at 15:40 -0700, Brad O'Hearne wrote:
> > I'm trying to convert an existing project to a maven ear project and I'm
> > having some difficulty. I have several questions:
> >
> > 1) Is there any solid documentation surrounding EAR projects? There
> > doesn't seem to be much of anything in any depth discussing EARs or
> > structuring ear projects.

I found this link to be invaluable: http://jira.codehaus.org/browse/ARCHETYPE-8

I didn't use the attached archetype, instead unzipped the sample
project.  It is a multi-module build which includes jars, a war, ejbs
and an ear project.  It worked great for me.

Tim

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

Re: Scheduling Error


It's a known issue that will be fix in 1.0.3 
(http://jira.codehaus.org/browse/CONTINUUM-577)

I think it's because you have a schedule without any attached projects. Remove this unused schedule 
or attach to it a project.


Emmanuel

Gerard Garrigan a écrit :

 Hello,

 I'm using Continuum with a Maven 2 project. It builds fine when you
force the build but the following error arises when the build is
scheduled:

 jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run

 jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled
Exception:

 jvm 1| java.lang.NullPointerException

 jvm 1|  at
org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
um.java:368)

 jvm 1|  at
org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
BuildJob.java:66)

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger
schedulerError

 jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception.

 jvm 1| org.quartz.SchedulerException: Job threw an unhandled
exception. [See nested exception: java.lang.NullPointerException]

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:202)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 jvm 1| * Nested Exception (Underlying Cause) ---

 jvm 1| java.lang.NullPointerException

 jvm 1|  at
org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
um.java:368)

 jvm 1|  at
org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
BuildJob.java:66)

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 I have replaced continuum-core-1.0.2.jar with
continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I
only have one project to build in Continuum. I'm running Continuum in
Windows. 


 Any help will be greatly appreciated,

 Thanks very much

 

Ger

RE: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released

2006-02-07 Thread Durfee, Bernard

I get the following after I upgraded from 2.5 to 3.0...

BUILD FAILED
File.. \home\.maven\cache\maven-checkstyle-plugin-3.0\plugin.jelly
Element... style
Line.. 238
Column 59
java.lang.ClassCastException:
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser

...I have the Xerces libraries in the JRE's "lib/endorsed" directory,
but I have the Oracle XML parser specified as the TransformerFactory.
Does this mean that CheckStyle is now dependant on having Xerces be the
"active" XML parser?

Bernie



> -Original Message-
> From: Eric Rose [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, February 07, 2006 12:09 AM
> To: Maven Users List
> Subject: Re: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released
> 
> 
> On Tuesday 07 February 2006 06:18, [EMAIL PROTECTED] wrote:
> > We are pleased to announce the Maven Checkstyle Plugin 3.0 release!
> >
> > http://maven.apache.org/maven-1.x/reference/plugins/checkstyle/
> 
> Hi,
> 
> I'm using Maven 1.0.2 and had been running with no errors 
> using the Checkstyle 
> Plugin 2.5, but am getting the following after upgrading to 
> version 3.0:
> 
> checkstyle:init:
> 
> checkstyle:report:
> checkstyle:run:
> [echo] Using 
> file:/usr/local/forge/ForgeLibs/BuildTools/etc/checkstyle.xml 
> for checkstyle ...
> [echo] LocaleCountry : en
> [checkstyle] Running Checkstyle 4.1 on 1396 files
> 
> checkstyle:report-internal:
> [style] 
> Processing 
> /home/ericr/workspace/mapIntelligence/tmp/checkstyle/checkstyl
> e-raw-report.xml 
> to 
> /home/ericr/workspace/mapIntelligence/tmp/checkstyle/checkstyl
> e-summary-report.xml
> [style] Loading 
> stylesheet 
> /usr/local/mavenPluginRepository/cache/maven-checkstyle-plugin
> -3.0/plugin-resources/checkstyle-summary.xsl
> 
> BUILD FAILED
> File.. 
> /usr/local/mavenPluginRepository/cache/maven-checkstyle-plugin
> -3.0/plugin.jelly
> Element... style
> Line.. 238
> Column 59
> Provider for javax.xml.transform.TransformerFactory cannot be found
> Total time: 36 seconds
> Finished at: Tue Feb 07 15:58:56 EST 2006
> 
> 
> 
> I presume that I'll have to add 
> -Djavax.xml.transform.TransformerFactory=org.apache.xalan.proc
> essor.TransformerFactoryImpl 
> somewhere, but I'm not sure where best to put it or of 
> there's a better 
> solution. Any clues?
> 
> Eric
> 
> -- 
> Eric Rose  | "Sed quis custodiet ipsos custodes?"
> [EMAIL PROTECTED]   | Juvenal (Satires, VI.347-8)
> 
> **
> *
> This message contains privileged and confidential information intended
> only for the use of the addressee named above.  If you are not the
> intended recipient of this message you must not disseminate, copy or
> take any action in reliance on it.  If you have received this message
> in error please notify the sender immediately.  Any views expressed in
> this message are those of the individual sender, except where the
> sender specifically states them to be the views of another (including
> a Body Corporate).
> 
> If you wish to opt out from future messages, send an email to
> [EMAIL PROTECTED] with the subject UNSUBSCRIBE
> **
> **
> 
> 

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

Site-deploy or wagon hanging (Maven 2.0.2, Red Hat and SuSe)

2006-02-07 Thread Johnson, Jonathan

Hi all,

Is anyone aware that the following command

mvn clean install deploy site-deploy

will hang when site-deploy executes the following rm command 

command: cd /home/builder/454/deploy/site/common/.; unzip -o 
> wagon47499.zip; rm -f wagon47499.zip 

I'm using Maven 2.0.2, Red Hat 4.  
Arnaud Bally reported the same using Maven 2.0.2, SuSe 9.2.

The threads below are from our discussions in the Continuum group.  We 
determined this is NOT a Continuum problem, rather is appears to be 
consistently stemming from the site-deploy plugin.



-Original Message-
From: Michael Böckling [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 07, 2006 5:05 AM
To: continuum-users@maven.apache.org
Subject: Re: Continuum and site-deploy or wagon hanging

Nope, I experienced the exact same problem. Here it happens on a SuSe 
9.2 with Maven 2.0.2 (and also in Continuum, of course). I had the 
impression that this does not affect small sites, but only large ones 
with many reports and all.
It seems the site *does* get deployed correctly, but it hangs at very 
same line (wagon47499.zip; rm -f wagon47499.zip) when trying to delete 
the temporary upload file.
Can't be a problem with permissions, since it only happens now and then. 
Defining a timeout is really essential, since it hangs forever once it 
gets stuck.

Regards,
Michael


> Hmm, all problems were fixed in wagon for maven 2.0.2.
>
> If you have pb with this version, send a message to maven user list.
>
> Emmanuel
>
> Arnaud Bailly a écrit :
>
>> Hi,
>> We are experiencing same problem : wagon hangs on ssh deploy and
>> site-deploy in a random way. Sometimes it works, sometimes it doesn't.
>> This has nothing to do with continuum as the problem occurs in maven
>> direct invocations. Solutions are of course welcomed, I was not able 
>> to trace the cause of
>> this problem (files permissions ok, ssh auth ok).
>
-- 
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69
[EMAIL PROTECTED]; http://www.giniality.com/



Good question, thanks.  Yes when run from the command line 

mvn clean install deploy site-deploy

it Maven hangs in the sample place.  The M2 site-deploy plugin is hanging on 
the unzip command.  

I will send my findings to the site-deploy plugin mailing list and let you know 
when there is a resolution.

Although this is unrelated to Continuum, Continuum should handle this 
gracefully.  The only way to work around the problem is to restart the 
Continuum server (and not use the site-deploy command for the moment). Perhaps 
adding some sort of daemon that detects a hung condition would strengthen its 
fault tolerance.


-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 3:52 PM
To: continuum-users@maven.apache.org
Subject: Re: Continuum and site-deploy or wagon hanging

Do you have the same problem when you call site-deploy directly for maven on 
your continuum machine?
When a goal is called, it's an external maven process that run it and not 
Continuum.

Emmanuel

Johnson, Jonathan a écrit :
> Anyone having problems with Continuum or site-deploy or wagon hanging?
> 
> Using Continuum 1.0.2, Maven 2.0.2.
> 
> I recently added deploy and deploy-site to my Continuum build and have 
> found Continuum will hang waiting for the build to finish.  If I 
> restart Continuum and force the build again it will sometimes work, 
> sometimes it hangs again.
> 
> It always hangs at the same place, just after calling unzip on the 
> site zip file expansion.  The site does get expanded so it seems to 
> hang just after completing the expansion.
> 
> Tail of build report.  
> 
> ...
> [INFO] ResourceManager : found templates/package-frame.vm with loader 
> org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
> [INFO] Generate "Maven Surefire Report" report.
> [INFO] Generate "Tag List" report.
> [INFO] Generate an index file for the English version.
> [INFO] [site:deploy]
> scp://hober/home/builder/454/deploy/site/common - Session: Opened 
> Executing command: mkdir -p /home/builder/454/deploy/site/common/.
> Executing command: mkdir -p /home/builder/454/deploy/site/common/.
> Executing command: scp -t
> /home/builder/454/deploy/site/common/./wagon47499.zip
> Uploading: ./wagon47499.zip to
> scp://hober/home/builder/454/deploy/site/common
> 
> ###[...for email, bunch of pounds omitted...]#! 
> ###[...omitted...]##
> 
> Transfer finished. 6317094 bytes copied in 3.269 seconds Executing
> command: cd /home/builder/454/deploy/site/common/.; unzip -o 
> wagon47499.zip; rm -f wagon47499.zip  Hung here 



LEGAL NOTICE:
Unless expressly stated otherwise, this message is confidential and may be 
privileged. It is intended for the addressee(s) only. Access to this e-mail by 
anyone else is unauthorized. If you are not an addressee, any disclosure or 
copying of the contents or any action taken (or not take

Re: Using Maven 2 from Eclipse/RAD 6.0

2006-02-07 Thread kaneda-java


Check for version probleme. RAD might be eclipse 3.0.2 whiche need a specific
Meven IDE version.
I think

Quoting Mang Jun Lau <[EMAIL PROTECTED]>:


I've tried installing this plugin into RAD 6 but it doesn't work.



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

Scheduling Error

2006-02-07 Thread Gerard Garrigan

 Hello,

 I'm using Continuum with a Maven 2 project. It builds fine when you
force the build but the following error arises when the build is
scheduled:

 jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.JobRunShell run

 jvm 1| SEVERE: Job DEFAULT.itraxspring threw an unhandled
Exception:

 jvm 1| java.lang.NullPointerException

 jvm 1|  at
org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
um.java:368)

 jvm 1|  at
org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
BuildJob.java:66)

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 jvm 1| 02-Feb-2006 14:21:00 org.quartz.core.ErrorLogger
schedulerError

 jvm 1| SEVERE: Job (DEFAULT.itraxspring threw an exception.

 jvm 1| org.quartz.SchedulerException: Job threw an unhandled
exception. [See nested exception: java.lang.NullPointerException]

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:202)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 jvm 1| * Nested Exception (Underlying Cause) ---

 jvm 1| java.lang.NullPointerException

 jvm 1|  at
org.apache.maven.continuum.DefaultContinuum.buildProjects(DefaultContinu
um.java:368)

 jvm 1|  at
org.apache.maven.continuum.scheduler.ContinuumBuildJob.execute(Continuum
BuildJob.java:66)

 jvm 1|  at
org.quartz.core.JobRunShell.run(JobRunShell.java:191)

 jvm 1|  at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java
:516)

 I have replaced continuum-core-1.0.2.jar with
continuum-core-1.1-SNAPSHOT.jar and the problem was not fixed. Also I
only have one project to build in Continuum. I'm running Continuum in
Windows. 

 Any help will be greatly appreciated,

 Thanks very much

 

Ger

Re: release:prepare + cvs : password is required


Ok, The released version of release plugin use an old version of maven-scm.

This problem is fixed in svn, if you want to try it.
Other solution is to put your password on scm url but it isn't secure.

Emmanuel

Bedin, Stephane (GE Healthcare) a écrit :

Yes I'm using CVSNT (as part of WinCVS).
(Note: I had also tried : mvn scm:update to get the latest scm plugins)

Here are the traces of 'mvn -Dpassword=your_password release:prepare':

+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and 
Settings\rivieje\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program 
Files\maven-2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository 
central
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-release-plugin:maven-plugin:2.0-beta-3
[INFO] 

[INFO] Building DICOM Objects Checker
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 

[DEBUG] com.gehealthcare:doc:jar:1.2-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]   com.gehealthcare:dicomdatamodel:jar:1.5 (selected for compile)
[DEBUG]   commons-logging:commons-logging:jar:1.0.4 (selected for compile)
[DEBUG]   log4j:log4j:jar:1.2.12 (selected for compile)
[DEBUG]   xml-apis:xml-apis:jar:1.0.b2 (selected for compile)
[DEBUG]   merge:mcw:jar:mc3java265ib3w32 (selected for compile)
[DEBUG]   xalan:xalan:jar:2.7.0 (selected for compile)
[DEBUG] While downloading xml-apis:xml-apis:2.0.2
  This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


[DEBUG]   xerces:xercesImpl:jar:2.7.1 (selected for compile)
[DEBUG]   com.gehealthcare:mergeinstaller:jar:1.2 (selected for compile)
[DEBUG]   com.gehealthcare:dicomservice:jar:1.12 (selected for compile)
[DEBUG] org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for 
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected 
for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-api:jar:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for 
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-utils:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-manager-plexus:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-managers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for 
runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-provider-svn:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2 (selected 
for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-project:jar:2.0
[DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-profile:jar:2.0
[DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime)
[DEBUG] Ret

RE: release:prepare + cvs : password is required

2006-02-07 Thread Bedin, Stephane \(GE Healthcare\)

Yes I'm using CVSNT (as part of WinCVS).
(Note: I had also tried : mvn scm:update to get the latest scm plugins)

Here are the traces of 'mvn -Dpassword=your_password release:prepare':

+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and 
Settings\rivieje\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program 
Files\maven-2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[DEBUG] maven-release-plugin: resolved to version 2.0-beta-3 from repository 
central
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-release-plugin:maven-plugin:2.0-beta-3
[INFO] 

[INFO] Building DICOM Objects Checker
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 

[DEBUG] com.gehealthcare:doc:jar:1.2-SNAPSHOT (selected for null)
[DEBUG]   junit:junit:jar:3.8.1 (selected for test)
[DEBUG]   com.gehealthcare:dicomdatamodel:jar:1.5 (selected for compile)
[DEBUG]   commons-logging:commons-logging:jar:1.0.4 (selected for compile)
[DEBUG]   log4j:log4j:jar:1.2.12 (selected for compile)
[DEBUG]   xml-apis:xml-apis:jar:1.0.b2 (selected for compile)
[DEBUG]   merge:mcw:jar:mc3java265ib3w32 (selected for compile)
[DEBUG]   xalan:xalan:jar:2.7.0 (selected for compile)
[DEBUG] While downloading xml-apis:xml-apis:2.0.2
  This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


[DEBUG]   xerces:xercesImpl:jar:2.7.1 (selected for compile)
[DEBUG]   com.gehealthcare:mergeinstaller:jar:1.2 (selected for compile)
[DEBUG]   com.gehealthcare:dicomservice:jar:1.12 (selected for compile)
[DEBUG] org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-3 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG]   org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for 
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected 
for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-api:jar:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-api:jar:1.0-alpha-2 (selected for 
runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-utils:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-manager-plexus:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-managers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-alpha-2 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-container-default:jar:1.0-alpha-5
[DEBUG] Retrieving parent-POM from the repository for project: 
plexus:plexus-containers:pom:1.0
[DEBUG] plexus:plexus-container-default:jar:1.0-alpha-5 (selected for 
runtime)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-provider-svn:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-alpha-2 (selected 
for runtime)
[DEBUG] regexp:regexp:jar:1.3 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-project:jar:2.0
[DEBUG]   org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 
(selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
org.apache.maven:maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-profile:jar:2.0
[DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-provider-cvs:jar:1.0-alpha-2
[DEBUG] Retrieving parent-POM from the repository for project: 
null:maven-scm-providers:pom:1.0-alpha-2
[DEBUG]   org.apache.maven.scm:maven-scm-provider-cvs:

Re: [m2] Bug? Maven2 Classloader doesn't URLEncoding

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

I'm not sure if this is a bug, and I suspect it is in classworlds if
it is, but we can track it there.

- Brett

On 2/8/06, Roland Kofler <[EMAIL PROTECTED]> wrote:
> Can I contact a developer to file the bug?
>
>
> Roland Kofler schrieb:
> > When I'm executing an
> >
> > getClass().getClassLoader().getResource(s);
> >
> > it gives back an URL encoded string in eclipse while Maven2 gives me
> > blanks in my URL:
> >
> > eclipse
> > file:/C:/Dokumente%20und%20Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg
> >
> >
> > maven2
> > file:/C:/Dokumente und
> > Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg
> >
> > Maybe there is a special system setting swiched on in Maven, to evoke
> > this error?
> >
> > Thanks,
> > Roland
> >
> > -
> > 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: Using

2006-02-07 Thread Dixit, Sandeep (ProSource Solutions)

Here is my project structure:

- websphere tasks project (deployed in the rep)
- distributionProject
- EJB module : pom inherits distributionProject pom
- WEB module : pom inherits distributionProject pom
- EAR module : pom inherits distributionProject pom; I ALSO WANT
inherit websphere tasks here. However my websphere project is non-jar,
POM only project.

Could you please provide me some pointers on how to achieve this? I was
thinking of using  to achieve this...

Thanks,
Sandeep



-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 06, 2006 4:53 PM
To: Maven Users List
Subject: Re: Using 

Not sure what the end goal is here, but I assume you're saying you're 
trying to do something like:


   
 
   some.group.id
   some-artifact
   1.1.1.1
   pom
 
   


Other than playing the trick of having that POM's dependencies all 
included in the core classloader of Maven, I'm not sure what this would 
acoomplish. BTW, it's entirely possible that the  element isn't 
allowed here, I don't remember for sure. It would seem to make some 
amount of sense not to allow this, though...

-john

Dixit, Sandeep (ProSource Solutions) wrote:
> Is there a way to extend a POM only project using
> ... tag?
> 
> I am not able to do so as by default extension is looking for JAR type
> project. And mine is POM. Extension tag is not allowing defining of
>  tag.
> 
> Thanks,
> Sandeep
> 
> 
>

---
> ***National City made the following annotations
>

---
> This communication is a confidential and proprietary business
communication.  It is intended solely for the use of the designated
recipient(s).  If this communication is received in error, please
contact the sender and delete this communication.
>

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

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




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

Re: [m2] Bug? Maven2 Classloader doesn't URLEncoding

2006-02-07 Thread Roland Kofler


Can I contact a developer to file the bug?


Roland Kofler schrieb:

When I'm executing an

getClass().getClassLoader().getResource(s);

it gives back an URL encoded string in eclipse while Maven2 gives me 
blanks in my URL:


eclipse
file:/C:/Dokumente%20und%20Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg 



maven2
file:/C:/Dokumente und 
Einstellungen/roland.kofler/systemone/core/target/test-classes/fsm.jpg


Maybe there is a special system setting swiched on in Maven, to evoke 
this error?


Thanks,
Roland

-
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: release:prepare + cvs : password is required


Can you post 'mvn release:prepare' traces in debug mode (-X parameter)? It will 
be more helpful.

I'd guess you use CVSNT, right?

try this: mvn -Dpassword=your_password release:prepare

Emmanuel


Bedin, Stephane (GE Healthcare) a écrit :

Hi all,
I'm trying to use the release:prepare plugin... without success.
I'm using maven 2.0.2,
My pom.xml contains:
  
scm:cvs:pserver:[EMAIL 
PROTECTED]:/cvsroot/doc:doc
scm:cvs:pserver:[EMAIL 
PROTECTED]:/cvsroot/doc:doc
  

Whien I launch 'mvn release:prepare', I got an error :
D:\cvs\doc>mvn release:prepare
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 
-
---
[INFO] Building DICOM Objects Checker
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 
-
---
[INFO] [release:prepare]
[INFO] What tag name should be used?
RELEASE_1_0
[INFO] Verifying there are no local modifications ...
[INFO] 
-
---
[ERROR] BUILD ERROR
[INFO] 
-
---
[INFO] An error is occurred in the status process.

Embedded error: Exception while executing SCM command.
password is required
[INFO] 
-
---
[INFO] For more information, run Maven with the -e switch
[INFO] 
-
---
[INFO] Total time: 11 seconds
[INFO] Finished at: Tue Feb 07 11:50:22 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] 
-
---

I tryed 'cvs login' with success, and then 'mvn release:prepare', but I have 
always the same error.

I parsed the mailing list and many forum, but without any clear response.
Any idea ?

Stéphane

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

release:prepare + cvs : password is required

2006-02-07 Thread Bedin, Stephane \(GE Healthcare\)

Hi all,
I'm trying to use the release:prepare plugin... without success.
I'm using maven 2.0.2,
My pom.xml contains:
  
scm:cvs:pserver:[EMAIL 
PROTECTED]:/cvsroot/doc:doc
scm:cvs:pserver:[EMAIL 
PROTECTED]:/cvsroot/doc:doc
  

Whien I launch 'mvn release:prepare', I got an error :
D:\cvs\doc>mvn release:prepare
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO] 
-
---
[INFO] Building DICOM Objects Checker
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO] 
-
---
[INFO] [release:prepare]
[INFO] What tag name should be used?
RELEASE_1_0
[INFO] Verifying there are no local modifications ...
[INFO] 
-
---
[ERROR] BUILD ERROR
[INFO] 
-
---
[INFO] An error is occurred in the status process.

Embedded error: Exception while executing SCM command.
password is required
[INFO] 
-
---
[INFO] For more information, run Maven with the -e switch
[INFO] 
-
---
[INFO] Total time: 11 seconds
[INFO] Finished at: Tue Feb 07 11:50:22 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] 
-
---

I tryed 'cvs login' with success, and then 'mvn release:prepare', but I have 
always the same error.

I parsed the mailing list and many forum, but without any clear response.
Any idea ?

Stéphane

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

AW: AW: m2 and perforce ???

I suppose, I'm logged in.
Otherwise 'p4 sync -f" would produce an error, isn't it ?
Is there a command to test if the used user is logged in ?

Further, I ran the following goal

maven -e scm:update -Dusername=ecb -Dpassword=MY_PASSWD --> NOK


"p4 info" returned :

D:\p4client\components\ecb-presentation-tiles>p4 info
User name: ecb
Client name: ECB
Client host: ECB
Client root: D:\p4client\components
Current directory: d:\p4client\components\ecb-presentation-tiles
Client address: 127.0.0.1:3730
Server address: localhost:1666
Server root: C:\Programme\Perforce
Server date: 2006/02/07 12:10:03 +0100 Westeuropõische Normalzeit
Server version: P4D/NTX86/2003.2/62096 (2004/06/08)
Server license: none

Is it possible that the problem is caused by my perforce version ? I don't
have any license, it's a single user installation (for free).

Thanks, Emmanuel !

Esteban.


-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 11:31
An: Maven Users List
Betreff: Re: AW: m2 and perforce ???


Are you logged in to Perforce?

I think perforce provider requires that you're logged in.

Emmanuel

Esteban Chavez a écrit :
> Hi Emmanuel,
>
> This is what I get when running the update goal. ('maven' is my own alias
> for 'mvn')
> Esteban.
>
>
> D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
>
[INFO] -
> ---
> [INFO] Building Maven Webapp Archetype
> [INFO]task-segment: [scm:update] (aggregator-style)
>
[INFO] -
> ---
> [INFO] [scm:update]
> [ERROR] Provider message:
> [ERROR] Unable to sync
> [ERROR] Command output:
> [ERROR]
>
[INFO] -
> ---
> [ERROR] BUILD ERROR
>
[INFO] -
> ---
> [INFO] Command failed.
>
[INFO] -
> ---
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
> cycleExecutor.java:555)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
> faultLifecycleExecutor.java:485)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
> ycleExecutor.java:455)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
> ures(DefaultLifecycleExecutor.java:303)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
> ultLifecycleExecutor.java:216)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
> Executor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
> at
>
org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java
> :252)
> at
> org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
> at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
> r.java:432)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
> cycleExecutor.java:530)
> ... 16 more
>
[INFO] -
> ---
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Tue Feb 07 10:55:07 CET 2006
> [INFO] Final Memory: 3M/6M
>
[INFO] -
> ---
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 7. Februar 2006 10:44
> An: Maven Users List
> Betreff: Re: m2 and perforce ???
>
>
> Do you have an error or something?
>
> Emmanuel
>
> Esteban Chavez a écrit :
>
>>Hi,
>>
>>is there someone

Re: AW: m2 and perforce ???


Are you logged in to Perforce?

I think perforce provider requires that you're logged in.

Emmanuel

Esteban Chavez a écrit :

Hi Emmanuel,

This is what I get when running the update goal. ('maven' is my own alias
for 'mvn')
Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)
[INFO] -
---
[INFO] [scm:update]
[ERROR] Provider message:
[ERROR] Unable to sync
[ERROR] Command output:
[ERROR]
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Command failed.
[INFO] -
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:555)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
faultLifecycleExecutor.java:485)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:455)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:216)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
at
org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java
:252)
at
org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:432)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:530)
... 16 more
[INFO] -
---
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Feb 07 10:55:07 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] -
---




-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 10:44
An: Maven Users List
Betreff: Re: m2 and perforce ???


Do you have an error or something?

Emmanuel

Esteban Chavez a écrit :


Hi,

is there someone who got already m2 and perforce running together ?
I'm unable to make a source update (mvn -e scm:update)

mvn -e scm:status --> is ok
mvn -e scm:validate --> is ok

"p4 sync -f" --> is ok

Thank you very much !

Esteban.


Esteban Chávez Baroni
banking objects

Moorweg 8
22453 Hamburg
Phone: +49 -(0)40 - 57006757
Mobile: +49 -(0)163 -5813639
Mail: [EMAIL PROTECTED]
Web: www.banking-objects.de






-
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 2.0: accents and entities with xdoc

2006-02-07 Thread Herve Quiroz

On Tue, Feb 07, 2006 at 11:19:42AM +0100, Herve Quiroz wrote:
> Now I definitively need entities to work (or some mechanism to include a
> file into another)...

BTW, XInclude does not work either.

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

Re: Maven 2.0: accents and entities with xdoc

2006-02-07 Thread Herve Quiroz

Thanks for your help.

On Tue, Feb 07, 2006 at 10:10:22AM +0100, Peschier J. (Jeroen) wrote:
> - Make sure your DTD matches the root element name of your docbook file.
> If memory serves me, it should be 'document' for xdoc. So it should read
>
> ]>

Changing the doctype to 'document' did not change anything. I even tried
to specify an absolute path to be sure I was not mistaken with my
relative one.

After some research on the web, it seems like Maven 2 may not support
entities at all...

> - You say your XML file is encoded ISO-8859-1. Did you also specify the
> encoding like  on the first line in your
> XML file? If not, the XML parser will assume UTF-8 like the XML spec
> mandates.

Yes, my file was already tagged with  on
the first line.

Anyway, I found out the source of the problem. The outputEncoding is
also set to ISO-8859-1, and the resulting file contains:

  content="text/html; charset=ISO-8859-1"

Anyway, accents from the page are encoded in UTF-8. I edited the page to
change its encoding to UTF-8 and the page was displaying accents
correctly in my browser. So maybe it is a bug afterall.

However, I changed the outputEncoding setting to UTF-8 in pom.xml and
the resulting page correctly displays accents so I will use this
workaround for now.

Now I definitively need entities to work (or some mechanism to include a
file into another)...

Herve

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

Re: A local repository acting as a remote one

2006-02-07 Thread Max Cooper

On Mon, 2006-02-06 at 22:31 +0100, Fabrice BELLINGARD wrote:
> Hi Maveners,
> 
> My case is the following: with Maven 2, I want to have an intermediate
> repository for my dev team, so that the developers don't download Jars from
> Ibiblio but only from this very repository. This is a common use case lots
> of people know.
> The difference in my case is that I want to have it on my computer, and I
> want my local repository to be this intermediate repository. So to sum up:
> my local repository would be the remote repository of my teams. Why ?
> Because of 2 main reasons that seem important to me:
> - I want to control which components they use (so I don't want a Maven proxy
> that would allow them to download any Jars they would want)

You can setup maven-proxy so that it ONLY uses the files you add to it.
I am not sure if that solves your entire problem, but it is possible by
changing the maven.repo.list property in the maven-proxy.properties
file.

Sharing a local repository is somewhat dangerous, since it is used
during a build for inter-dependencies between your modules. It might be
best to have a separate shared repository from your local repository for
this reason.

-Max

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

Re: Continuum and site-deploy or wagon hanging

2006-02-07 Thread Michael Böckling

Nope, I experienced the exact same problem. Here it happens on a SuSe 
9.2 with Maven 2.0.2 (and also in Continuum, of course). I had the 
impression that this does not affect small sites, but only large ones 
with many reports and all.
It seems the site *does* get deployed correctly, but it hangs at very 
same line (wagon47499.zip; rm -f wagon47499.zip) when trying to delete 
the temporary upload file.
Can't be a problem with permissions, since it only happens now and then. 
Defining a timeout is really essential, since it hangs forever once it 
gets stuck.


Regards,
Michael



Hmm, all problems were fixed in wagon for maven 2.0.2.

If you have pb with this version, send a message to maven user list.

Emmanuel

Arnaud Bailly a écrit :


Hi,
We are experiencing same problem : wagon hangs on ssh deploy and
site-deploy in a random way. Sometimes it works, sometimes it doesn't.
This has nothing to do with continuum as the problem occurs in maven
direct invocations. Solutions are of course welcomed, I was not able 
to trace the cause of

this problem (files permissions ok, ssh auth ok).



--
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69
[EMAIL PROTECTED]; http://www.giniality.com/

Re: Ear projects

2006-02-07 Thread Max Cooper

On Mon, 2006-02-06 at 15:40 -0700, Brad O'Hearne wrote:
> I'm trying to convert an existing project to a maven ear project and I'm 
> having some difficulty. I have several questions:
> 
> 1) Is there any solid documentation surrounding EAR projects? There 
> doesn't seem to be much of anything in any depth discussing EARs or 
> structuring ear projects.
> 
> 2) How do I create an EAR project? The command line in the brief 
> documentation returns errors.
> 
> 3) I have an existing Java project with Java source and I tried to build 
> it as an EAR project. It doesn't seem to compile java source code. Is 
> there some rule that states an EAR can't have java source code?

Ear files are assemblies of other archives (EJB jars, wars, etc.), so it
doesn't make sense to have Java source code directly associated with an
ear project. Create a jar project for your Java code, and then make your
ear project depend on it. However, even that won't be very useful unless
you have a war (webapp) or EJB jar that uses the code.

-Max

> 
> Thanks for your help
> 
> Brad
> 
> -
> 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]

AW: m2 and perforce ???

Hi Emmanuel,

This is what I get when running the update goal. ('maven' is my own alias
for 'mvn')
Esteban.


D:\p4client\components\ecb-presentation-tiles>maven -e scm:update
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] -
---
[INFO] Building Maven Webapp Archetype
[INFO]task-segment: [scm:update] (aggregator-style)
[INFO] -
---
[INFO] [scm:update]
[ERROR] Provider message:
[ERROR] Unable to sync
[ERROR] Command output:
[ERROR]
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Command failed.
[INFO] -
---
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Command failed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:555)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(De
faultLifecycleExecutor.java:485)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
ycleExecutor.java:455)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
ures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
ultLifecycleExecutor.java:216)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Executor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Command failed.
at
org.apache.maven.scm.plugin.AbstractScmMojo.checkResult(AbstractScmMojo.java
:252)
at
org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:70)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
r.java:432)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
cycleExecutor.java:530)
... 16 more
[INFO] -
---
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Feb 07 10:55:07 CET 2006
[INFO] Final Memory: 3M/6M
[INFO] -
---




-Ursprüngliche Nachricht-
Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 7. Februar 2006 10:44
An: Maven Users List
Betreff: Re: m2 and perforce ???


Do you have an error or something?

Emmanuel

Esteban Chavez a écrit :
> Hi,
>
> is there someone who got already m2 and perforce running together ?
> I'm unable to make a source update (mvn -e scm:update)
>
> mvn -e scm:status --> is ok
> mvn -e scm:validate --> is ok
>
> "p4 sync -f" --> is ok
>
> Thank you very much !
>
> Esteban.
>
>
> Esteban Chávez Baroni
> banking objects
>
> Moorweg 8
> 22453 Hamburg
> Phone: +49 -(0)40 - 57006757
> Mobile: +49 -(0)163 -5813639
> Mail: [EMAIL PROTECTED]
> Web: www.banking-objects.de
>
>
>
>
> 
>
> -
> 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: Application.xml

2006-02-07 Thread Max Cooper

Maven 2 generates the application.xml file for you:
http://maven.apache.org/plugins/maven-ear-plugin/howto.html

-Max

On Tue, 2006-02-07 at 13:35 +0530, [EMAIL PROTECTED] wrote:
> Hi ,
> 
> I'm getting the following warning  when creating the ear file , 
> application.xml is not getting included in the final Ear file.(maven1.x)
>  
> " selected ear files include a META-INF/application.xml which will be 
> ignored (please use appxml attribute to ear task"
> 
> Can any one pls help me in figuring out the problem.
> 
> 
> Regards
> Saravana


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

Re: m2 and perforce ???


Do you have an error or something?

Emmanuel

Esteban Chavez a écrit :

Hi,

is there someone who got already m2 and perforce running together ?
I'm unable to make a source update (mvn -e scm:update)

mvn -e scm:status --> is ok
mvn -e scm:validate --> is ok

"p4 sync -f" --> is ok

Thank you very much !

Esteban.


Esteban Chávez Baroni
banking objects

Moorweg 8
22453 Hamburg
Phone: +49 -(0)40 - 57006757
Mobile: +49 -(0)163 -5813639
Mail: [EMAIL PROTECTED]
Web: www.banking-objects.de






-
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 Dashboard Plugin 1.9 for Maven 1.x released

2006-02-07 Thread Wim Deblauwe

Thank you for still supporting Maven 1.x!

How does the sorting work. I could not find any clue in the jira issue?

regards,

Wim

2006/2/6, [EMAIL PROTECTED] < [EMAIL PROTECTED]>:
>
> We are pleased to announce the Maven Dashboard Plugin 1.9 release!
>
> http://maven.apache.org/maven-1.x/reference/plugins/dashboard/
>
> Generate a dashboard containing global statistics about other maven
> reports
>
>
> ===
>
> Changes in this version include:
>
>   New Features:
>
> o Allow sorting of dashboard items (requires Maven 1.1). Fixes
>   MPDASHBOARD-28.
> o Add message on status of finding dashboard-single.xml. Fixes
>   MPDASHBOARD-30. Thanks to Jeff Jensen.
> o Add new aggregators jiraopenand jirascheduled.
> o Added Cobertura aggregator. Fixes MPDASHBOARD-31.
>
>   Fixed bugs:
>
> o Fix count of changelog-entries with maven-changelog-plugin-1.9. Fixes
>   MPDASHBOARD-35. Thanks to Christoph Jerolimov.
> o Incorrect links with multiproject independent navigation. Fixes
>   MPDASHBOARD-24. Thanks to Wim Deblauwe.
> o maven.dashboard.report.showemptyproperty not honored. Fixes
> MPDASHBOARD-32.
>   Thanks to Wim Deblauwe.
> o Cobertura aggregator doesn't support offline mode. Fixes MPDASHBOARD-34.
>
>   Thanks to Philippe Kernevez.
> o Properties maven.dashboard.basedir, maven.dashboard.includes,
>   maven.dashboard.excludesand maven.dashboard.ignoreFailureswere ignored
> and
>   were always defaulting to their multiproject plugin counterpart. Fixes
>   MPDASHBOARD-27.
> o The JUnit pass rate aggregator was no longer showing values in the
>   dashboard. Fixes MPDASHBOARD-26. Thanks to Wim Deblauwe.
>
>   Changes:
>
> o Update the default checkstyle report location to make it compatible with
>
>   Checkstyle plugin 3.0+ (MPCHECKSTYLE-40). Fixes MPDASHBOARD-33. Thanks
> to
>   [EMAIL PROTECTED]
>
> ===
>
>
>
> To automatically install the plugin, type the following on a single line:
>
> maven plugin:download
>   
> -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
>
>   -DgroupId=maven
>   -DartifactId=maven-dashboard-plugin
>   -Dversion=1.9
>
> For a manual installation, you can download the plugin here:
>
> http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-dashboard-plugin-1.9.jar
>
>
> Have fun!
> -The Maven Dashboard Plugin development team
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Continuum and site-deploy or wagon hanging

2006-02-07 Thread Arnaud Bailly

Hi,
We are experiencing same problem : wagon hangs on ssh deploy and
site-deploy in a random way. Sometimes it works, sometimes it doesn't.
This has nothing to do with continuum as the problem occurs in maven
direct invocations. 
Solutions are of course welcomed, I was not able to trace the cause of
this problem (files permissions ok, ssh auth ok).

Regards,

-- 
Arnaud Bailly, Dr. - Ingénieur de Recherche 
NORSYS 
1, rue de la Cense des Raines
ZAC du Moulin
59710 ENNEVELIN
Tel : (33) 3 28 76 56 76
Mob : (33) 6 17 12 19 78
Fax : (33) 3 28 76 57 00
Web : http://www.norsys.fr

m2 and perforce ???