date:20080227

Can we see your code?

Emmanuel

On Wed, Feb 27, 2008 at 1:01 AM, kroe [EMAIL PROTECTED] wrote:


 I am tinkering with the ContinuumXmlRpcClient and think I found a bug.
  When
 calling addMavenTwoProject and specifying the project group id I get an
 exception.  Am I doing something wrong, or is this method broken?

 Thanks,
 -Ken

 INFO   | jvm 1| 2008/02/26 18:05:53 |
 org.apache.xmlrpc.XmlRpcException:
 Failed to invoke method addMavenTwoProject in class
 org.apache.maven.continuum.x
 mlrpc.server.ContinuumServiceImpl: null
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at

 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.invoke
 (ContinuumXmlRpcMetaDataHand
 ler.java:164)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at

 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.execute
 (ContinuumXmlRpcMetaDataHan
 dler.java:133)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.xmlrpc.server.XmlRpcServerWorker.execute(
 XmlRpcServerWorker.java:43)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:83)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.xmlrpc.server.XmlRpcStreamServer.execute(
 XmlRpcStreamServer.java:182)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(
 XmlRpcServletServer.java:103)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcServlet.doPost(
 ContinuumXmlRpcServlet.java:193)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
 WebApplicationHandler.java:830)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(
 FilterDispatcher.java:189)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
 WebApplicationHandler.java:821)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
 PageFilter.java:118)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
 PageFilter.java:52)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
 WebApplicationHandler.java:821)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(
 ActionContextCleanUp.java:88)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
 WebApplicationHandler.java:821)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(
 WebApplicationHandler.java:471)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.jetty.servlet.WebApplicationContext.handle(
 WebApplicationContext.java:633)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpServer.service(HttpServer.java:909)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
 INFO   | jvm 1| 2008/02/26 18:05:53 | Caused by:
 INFO   | jvm 1| 2008/02/26 18:05:53 | java.lang.StackOverflowError
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at
 org.apache.maven.continuum.xmlrpc.server.ContinuumServiceImpl.getPGSummary
 (ContinuumServiceImpl.java:231)
 INFO   | jvm 1| 2008/02/26 18:05:53 |   at

losing pom.xml

2008-02-27 Thread BDM


hello,
I am using continuum 1.1 and get this error when forcing a build : it 
checkout correctly the only file of this project but then generate an 
error but the pom.xml is removed ... but who was removing this file 

When I try manually with the commands given in this log, all is OK.

775722963 [SocketListener0-6] INFO  
org.apache.maven.continuum.Continuum:default  - Enqueuing 
'myCompMavenProject' with build definition 'default maven2 
buildDefinition' - id=11).
775722965 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Initializing build
775722976 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Starting build of myCompMavenProject
775723014 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Updating working dir
775723014 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action check-working-directory
775723016 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action update-working-directory-from-scm
775723073 [pool-1-thread-1] INFO  
org.apache.maven.continuum.scm.ContinuumScm:default  - Updating project: 
id: '30', name 'myCompMavenProject'.
775723195 [pool-1-thread-1] INFO  
org.apache.maven.scm.manager.ScmManager:default  - Executing: /bin/sh -c 
cd 
/opt/java/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/30 
 svn --username svn_user --non-interactive update
775723195 [pool-1-thread-1] INFO  
org.apache.maven.scm.manager.ScmManager:default  - Working directory: 
/opt/java/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/30
775724255 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Merging SCM results
775724314 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
AlwaysBuild configured, building
775724314 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action update-project-from-working-directory
775724321 [pool-1-thread-1] INFO  
org.codehaus.plexus.action.Action:update-project-from-working-directory  
- Updating project 'myCompMavenProject' from checkout.
775724649 [pool-1-thread-1] ERROR 
org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper:default  
- Cannot build maven project from 
/opt/java/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/30/pom.xml 
(The POM expression: ${pom.scm.url} could not be evaluated. Reason: 
Expression value '${pom.scm.url}' references itself in 
'net.myComp:myCompMavenProject:pom:smup-trunk-1.0-SNAPSHOT'.).


775724676 [pool-1-thread-1] ERROR 
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Error executing action update-project-from-working-directory '
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error 
executing action 'update-project-from-working-directory'
   at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:434)
   at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:139)
   at 
org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50)
   at 
org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
   at 
edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
   at 
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
   at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
   at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)

   at java.lang.Thread.run(Thread.java:619)
Caused by: 
org.apache.maven.continuum.execution.ContinuumBuildExecutorException: 
Error while mapping metadata:add.project.project.building.error

add.project.unknown.error

   at 
org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:157)
   at 
org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:75)
   at 
org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:408)

   ... 8 more
775724676 [pool-1-thread-1] INFO  
org.apache.maven.continuum.buildcontroller.BuildController:default  - 
Performing action execute-builder
775724886 [pool-1-thread-1] INFO  
org.apache.maven.continuum.utils.shell.ShellCommandHelper:default  - 
Executing: /bin/sh -c cd

Build blocked

2008-02-27 Thread Nicolas Loison

Hello,

I've got a problem with a build in Continuum. My Continuum version is
1.0.3and I using Maven 2.

My build runs a jmeter script who is bad. Even if I restart Continuum, the
build is always blocked at the same place and it's impossible to suppress it
!!

Please, can you help me ?

Thanks

Nico

PS: Sorry for my English I'm french user

Re: maven-eclipse-plugin 2.4 versioned projects

I've been pouring through maven-eclipse-plugin 2.4 code and realized that 
there is potentially a problem with 
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter class 
(line 125), IMHO:


   writer.addAttribute( ATTR_DEPLOY_NAME, 
config.getProject().getArtifactId() );


It seems like the code above assumes deploy-name cannot contain version 
numbers, project name templates etc. It would be great if the code could 
follow similar structured approach for setting/getting the project name as 
in org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter (line 169), 
which generates .project file:


   writer.writeText( config.getEclipseProjectName() );

Here the project name is set during configuration/dependancy resolution 
phase by org.apache.maven.plugin.eclipse.EclipsePlugin and later used by the 
EclipseProjectWriter class.


So I'm curious if this issue could be resolved by simply using 
getEclipseProjectName() method in 
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter class:


   writer.addAttribute( ATTR_DEPLOY_NAME, config.getEclipseProjectName() );

Please advise..

--
Salman Moghal

- Original Message - 
From: Salman Moghal [EMAIL PROTECTED]

To: users@maven.apache.org
Sent: Tuesday, February 26, 2008 3:38 PM
Subject: maven-eclipse-plugin 2.4  versioned projects



Hello:

I'm using maven-eclipse-plugin v2.4 to generate WTP 1.5 resource for 
Eclipse 3.2.x / RAD v6.x environment.  The goal of this exercise is to 
take advantage of Eclipse 3.2 /  RAD v6.x
integrated development, debugging, and hot code deployment features.  The 
runtime environment is WebSphere Application Server v6.1.  Eclipse / RAD 
also have M2Eclipse plugin installed for dependency management, etc. 
There is one slight issue that has me scratching my head for a few days. 
It has to do with generated WTP v1.5 files.


Essentially, maven eclipse plugin goal eclipse:m2eclipse generates all 
WTP 1.5 files correctly.  However, once 
addVersionToProjectNametrue/addVersionToProjectName is added to plugin 
config,  .settings/org.eclipse.wst.common.component contains an incorrect 
entry.  The goal generates the .project WTP file properly with a project 
name containing the POM version number, but the corresponding 
.settings/org.eclipse.wst.common.component contains an incorrect value for 
wb-module deploy-name=..  The value of deploy-name=  does not 
contain a POM version number along with the project name.


The reason why having a version number in wb-module deploy-name= entry is 
important is because if the EAR / WAR module is deployed to WebSphere 
runtime in loose configuration mode, the runtime complains about not 
being able to locate corresponding modules.  Loose configuration allows 
the class files to reside in Eclipse / RAD workspace and speeds up the EAR 
deployment process many folds since no real EAR is generated and installed 
into WebSphere.  Eclipse / RAD loose config file is located under 
WORKSPACE/.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR 
NAME/looseconfig.xmi.


Note that if I manually make the change to the generated 
.settings/org.eclipse.wst.common.component file by adding version number 
along with the project name, the runtime doesn't complain and everything 
works well in loose configuration mode.


May be I'm missing something in maven-eclipse-plugin configuration. Here's 
what I have:


!-- maven-eclipse-plugin config for generating WTP 1.5 resources for WAR 
and EARs --

plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId

  configuration
manifest
  ${basedir}/src/main/resources/META-INF/MANIFEST.MF
/manifest

addVersionToProjectNametrue/addVersionToProjectName
useProjectReferencesfalse/useProjectReferences

wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
wtpversion1.5/wtpversion

additionalBuildcommands

buildcommandcom.ibm.etools.common.migration.MigrationBuilder/buildcommand
buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand

buildcommandorg.eclipse.wst.common.project.facet.core.builder/buildcommand

buildcommandorg.eclipse.wst.validation.validationbuilder/buildcommand
/additionalBuildcommands
additionalProjectnatures

projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
projectnatureorg.eclipse.jdt.core.javanature/projectnature

projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature

projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
/additionalProjectnatures
classpathContainers

classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
/classpathContainers
  /configuration

/plugin
!-- maven-eclipse-plugin --


Is there any way to manipulate or affect entries in 
.settings/org.eclipse.wst.common.component via maven-eclipse-plugin 
configuration?  to If you guys have any clues / pointers /

scm plugin and fille permission

2008-02-27 Thread Benoit Decherf


It seems that mvn scm:checkout doesn't respect the file permissions.

In cvs I have a file with exec permission (-rwxrwxr-x).
If I checkout the project using mvn scm:checkout, I get:
-rw-rw-r-- 1 decherfb decherfb 394 2007-08-21 12:01 
/tmp/migrate/searchFeeder/clean.sh


Using directly the cvs command executed by scm :
cvs -z3 -f -q checkout -r searchFeeder_1-1-x -d searchFeeder searchFeeder
I get:
-rwxrwxr-x 1 decherfb decherfb   394 2007-08-21 12:01 clean.sh


I think there is a bug here ?

Benoit

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

Re: Compilation Failure Still Build Successful message

If you use maven 2.0.7, the fix is explain in the Continuum FAQs

Emmanuel

On Wed, Feb 27, 2008 at 6:58 AM, Hemant Malik [EMAIL PROTECTED]
wrote:

 Hi,abh
 In one of my submodules project, one of the sub module is having a
 compilation error, but the email subject in the notification is still
 Build
 Successful. Is there any setting I am missing or some other problem?

 Regards,
 Hemant Malik

Re: scm plugin and fille permission

Maybe an issue in the java cvs lib used by maven-scm. If you have cvs
command line installed, you can use the native cvs:
http://maven.apache.org/scm/cvs.html

Emmanuel

 It seems that mvn scm:checkout doesn't respect the file permissions.

 In cvs I have a file with exec permission (-rwxrwxr-x).
 If I checkout the project using mvn scm:checkout, I get:
 -rw-rw-r-- 1 decherfb decherfb 394 2007-08-21 12:01
 /tmp/migrate/searchFeeder/clean.sh

 Using directly the cvs command executed by scm :
 cvs -z3 -f -q checkout -r searchFeeder_1-1-x -d searchFeeder searchFeeder
 I get:
 -rwxrwxr-x 1 decherfb decherfb   394 2007-08-21 12:01 clean.sh


 I think there is a bug here ?

 Benoit

 -
 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: Cargo: custom ctx path for deployment

Clifton,

I remember I had problems with the context property of Cargo: it didn't work
at all but I can't remember which container was involved.

Regards
Jeff MAURY

On Wed, Feb 27, 2008 at 4:38 AM, Clifton [EMAIL PROTECTED] wrote:

I have what seems like a simple task but is getting out hand. We deploy
servlet war webapps from a multi-module Maven2 build to a central Tomcat
5.x
server. I want to customize the deployment of webapps to a central server
for each developer. Right now I have two profiles setup, dev and staging.
These set properties to send the cargo deployment to either our developer
machine or a staging machine for QA. With 5-6 devs potentially working on
the project I want to customize deployments to the dev machine so that
each
war deploys under a custom ctx path with the developers initials. For Eg.
right now all dev profile deploys go out like:

http://devserver:8080/webapp1
http://devserver:8080/webapp2
http://devserver:8080/webapp3

I'd like to set a dev profile called dev-ccc and have it deploy the war
files like so:

http://devserver:8080/ccc-webapp1
http://devserver:8080/ccc-webapp2
http://devserver:8080/ccc-webapp3

So far I have a property set in the default profile of the project root
pom
(parent to each webapp pom) called webapp.root.ctx and it is set to /.
The
project root pom inherits from a parent pom which details the all the
other
profiles that I want to override the default profile. So if I do a deploy
with the regular dev profile the default profile is also activated which
assumes the ctx path of /. I created a profile dev-ccc in the root
project's parent pom that sets the ctx path to /ccc-. If I deploy the
servlets with profile dev-ccc the project's super pom webapp.root.ctx is
still set to /. I verify this using help:effective-pom. It's as if the
properties in the super pom are shadowed by the properties in the project
root pom. I thought it would be the other way around. To further clarify
this is a rough example of my poms:

Team-wide super pom:
project
!-- other stuff --
properties
webapp.root.ctx/ccc-/webapp.root.ctx
/properties
/project

Project root pom
project
!-- other stuff --
properties
webapp.root.ctx//webapp.root.ctx
/properties
/project

Webapp1 pom:
project
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
configuration
deployer
deployables
deployable
groupIdcom.mycomp.web/groupId
artifactIdwebapp1/artifactId
typewar/type
properties

context${webapp.root.ctx}webapp1/context
/properties
/deployable
/deployables
/deployer
/configuration
executions
execution
phasedeploy/phase
/execution
/executions
/plugin
/project

Could somebody lend a hand? Thanx a bunch in advance!

-Cliff
--
View this message in context:
http://www.nabble.com/Cargo%3A-custom-ctx-path-for-deployment-tp15705398s177p15705398.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Re: scm plugin and fille permission

2008-02-27 Thread Benoit Decherf


You are right. thanks.

Benoit.

Emmanuel Venisse wrote:

Maybe an issue in the java cvs lib used by maven-scm. If you have cvs
command line installed, you can use the native cvs:
http://maven.apache.org/scm/cvs.html

Emmanuel

  

It seems that mvn scm:checkout doesn't respect the file permissions.

In cvs I have a file with exec permission (-rwxrwxr-x).
If I checkout the project using mvn scm:checkout, I get:
-rw-rw-r-- 1 decherfb decherfb 394 2007-08-21 12:01
/tmp/migrate/searchFeeder/clean.sh

Using directly the cvs command executed by scm :
cvs -z3 -f -q checkout -r searchFeeder_1-1-x -d searchFeeder searchFeeder
I get:
-rwxrwxr-x 1 decherfb decherfb   394 2007-08-21 12:01 clean.sh


I think there is a bug here ?

Benoit

-
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: Problem with snapshots

This is because the file name with the timestamp is something internal to
the repository. When the dependency is resolved to your WAR, the original
file name is restored based on the artifactId and the version you mention in
your POM.
Maybe if you put Maven in debug mode, you could see that the file retrieved
from your local repository is the one with the timestamp.

Regards
Jeff MAURY

On Wed, Feb 27, 2008 at 10:53 AM, Papapara Tudu [EMAIL PROTECTED]
wrote:


 Hello,
 maybe I misunderstand something about snapshots, but I have the following
 problem:
 1. I have a non-Maven project which I export into a jar file and then
 install as a snapshot onto my local repository running on Archiva with
 this
 command:

 mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
 -DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
 -DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
 -DrepositoryId=archiva.default

 2. The very first version of that jar that was deployed onto the
 repository
 is saved as project-2.2-SNAPSHOT.jar.

 3. As expected, any further jars that I deploy onto the local repository
 get
 saved as e.g. project-2.2-20080226.143100-1.jar

 4.  The problem is that when I reference that jar in any other project,
 when
 I build the other project, only the project-2.2-SNAPSHOT.jar version (the
 very first one that was installed) is picked up in the output war and ear
 files.

 5. I can see that the actual snapshots, e.g.
 project-2.2-20080226.143100-1.jar do get downloaded from the internal
 repository and installed onto my local repository, but they're never used
 by
 referencing projects.

 6. I'm using the Maven Plugin for Eclipse and what is strange is that in
 the
 Maven Dependencies tree in all referencing projects, I see the
 project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
 see this:
 project: resolved to version project-2.2-20080226.143100-1 from repository
 myRepository


 7. I reference this jar in other projects as:
 dependency
  groupIdcom.company.project/groupId
  artifactIdproject/artifactId
  version[2,)/version
 /dependency

  (I also tried this configuration:
 dependency
  groupIdcom.company.project/groupId
  artifactIdproject/artifactId
  version2.2-SNAPSHOT/version
 /dependency
 but it had exactly the same results)

 8. My pom.xml config is:

distributionManagement
snapshotRepository
idmyRepository/id
url

  dav:http://[someip]/archiva/repository/myRepository/
/url
/snapshotRepository
/distributionManagement

pluginRepositories
pluginRepository
idmyRepository/id
url

  dav:http://[someip]/archiva/repository/myRepository/
/url
/pluginRepository
/pluginRepositories

repositories
repository
idmyRepository/id
namemyRepository/name

  urlhttp://[someip]/archiva/repository/myRepository/url
releases
enabledtrue/enabled
/releases
snapshots
enabledtrue/enabled
/snapshots
/repository
/repositories


 I wonder what I am doing wrong.

 Thanks in advance for the help.

 Papapara Tudu
 --
 View this message in context:
 http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15709789.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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




-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Re: maven-eclipse-plugin 2.4 versioned project

2008-02-27 Thread Siarhei Dudzin

I've done quite some troubleshooting around RAD6+maven. I would advise to
override the finalName for the artifact so it doesn't have version at the
end.
It's even better if those match the project directory names.

maven-eclipse-plugin 2.5-SNAPSHOT has quite a lot of improvements in RAD6/7
support. It is currently only 1 jira issue away from being released.

Siarhei

On Wed, Feb 27, 2008 at 9:04 AM, Salman Moghal [EMAIL PROTECTED] wrote:

 I've been pouring through maven-eclipse-plugin 2.4 code and realized that
 there is potentially a problem with
 org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass
 (line 125), IMHO:

writer.addAttribute( ATTR_DEPLOY_NAME,
 config.getProject().getArtifactId() );

 It seems like the code above assumes deploy-name cannot contain version
 numbers, project name templates etc. It would be great if the code could
 follow similar structured approach for setting/getting the project name as
 in org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter (line
 169),
 which generates .project file:

writer.writeText( config.getEclipseProjectName() );

 Here the project name is set during configuration/dependancy resolution
 phase by org.apache.maven.plugin.eclipse.EclipsePlugin and later used by
 the
 EclipseProjectWriter class.

 So I'm curious if this issue could be resolved by simply using
 getEclipseProjectName() method in
 org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass:

writer.addAttribute( ATTR_DEPLOY_NAME, config.getEclipseProjectName()
 );

 Please advise..

 --
 Salman Moghal

 - Original Message -
 From: Salman Moghal [EMAIL PROTECTED]
 To: users@maven.apache.org
 Sent: Tuesday, February 26, 2008 3:38 PM
 Subject: maven-eclipse-plugin 2.4  versioned projects


  Hello:
 
  I'm using maven-eclipse-plugin v2.4 to generate WTP 1.5 resource for
  Eclipse 3.2.x / RAD v6.x environment.  The goal of this exercise is to
  take advantage of Eclipse 3.2 /  RAD v6.x
  integrated development, debugging, and hot code deployment features.
  The
  runtime environment is WebSphere Application Server v6.1.  Eclipse / RAD
  also have M2Eclipse plugin installed for dependency management, etc.
  There is one slight issue that has me scratching my head for a few days.
  It has to do with generated WTP v1.5 files.
 
  Essentially, maven eclipse plugin goal eclipse:m2eclipse generates all
  WTP 1.5 files correctly.  However, once
  addVersionToProjectNametrue/addVersionToProjectName is added to
 plugin
  config,  .settings/org.eclipse.wst.common.component contains an
 incorrect
  entry.  The goal generates the .project WTP file properly with a project
  name containing the POM version number, but the corresponding
  .settings/org.eclipse.wst.common.component contains an incorrect value
 for
  wb-module deploy-name=..  The value of deploy-name=  does not
  contain a POM version number along with the project name.
 
  The reason why having a version number in wb-module deploy-name= entry
 is
  important is because if the EAR / WAR module is deployed to WebSphere
  runtime in loose configuration mode, the runtime complains about not
  being able to locate corresponding modules.  Loose configuration allows
  the class files to reside in Eclipse / RAD workspace and speeds up the
 EAR
  deployment process many folds since no real EAR is generated and
 installed
  into WebSphere.  Eclipse / RAD loose config file is located under
 
 WORKSPACE/.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR
  NAME/looseconfig.xmi.
 
  Note that if I manually make the change to the generated
  .settings/org.eclipse.wst.common.component file by adding version number
  along with the project name, the runtime doesn't complain and everything
  works well in loose configuration mode.
 
  May be I'm missing something in maven-eclipse-plugin configuration.
 Here's
  what I have:
 
  !-- maven-eclipse-plugin config for generating WTP 1.5 resources for
 WAR
  and EARs --
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
 
configuration
  manifest
${basedir}/src/main/resources/META-INF/MANIFEST.MF
  /manifest
 
  addVersionToProjectNametrue/addVersionToProjectName
  useProjectReferencesfalse/useProjectReferences
 
  wtpmanifesttrue/wtpmanifest
  wtpapplicationxmltrue/wtpapplicationxml
  wtpversion1.5/wtpversion
 
  additionalBuildcommands
 
  buildcommandcom.ibm.etools.common.migration.MigrationBuilder
 /buildcommand
  buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand
 
  buildcommandorg.eclipse.wst.common.project.facet.core.builder
 /buildcommand
 
  buildcommandorg.eclipse.wst.validation.validationbuilder
 /buildcommand
  /additionalBuildcommands
  additionalProjectnatures
 
  projectnatureorg.eclipse.wst.common.project.facet.core.nature
 /projectnature

Problem with snapshots

2008-02-27 Thread Papapara Tudu


Hello,
maybe I misunderstand something about snapshots, but I have the following
problem:
1. I have a non-Maven project which I export into a jar file and then
install as a snapshot onto my local repository running on Archiva with this
command:

mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
-DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
-DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
-DrepositoryId=archiva.default

2. The very first version of that jar that was deployed onto the repository
is saved as project-2.2-SNAPSHOT.jar. 

3. As expected, any further jars that I deploy onto the local repository get
saved as e.g. project-2.2-20080226.143100-1.jar

4.  The problem is that when I reference that jar in any other project, when
I build the other project, only the project-2.2-SNAPSHOT.jar version (the
very first one that was installed) is picked up in the output war and ear
files.

5. I can see that the actual snapshots, e.g.
project-2.2-20080226.143100-1.jar do get downloaded from the internal
repository and installed onto my local repository, but they're never used by
referencing projects.

6. I'm using the Maven Plugin for Eclipse and what is strange is that in the
Maven Dependencies tree in all referencing projects, I see the
project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
see this:
project: resolved to version project-2.2-20080226.143100-1 from repository
myRepository


7. I reference this jar in other projects as:
dependency
  groupIdcom.company.project/groupId 
  artifactIdproject/artifactId 
  version[2,)/version 
/dependency

 (I also tried this configuration:
dependency
  groupIdcom.company.project/groupId 
  artifactIdproject/artifactId 
  version2.2-SNAPSHOT/version 
/dependency
but it had exactly the same results)

8. My pom.xml config is:

distributionManagement
snapshotRepository
idmyRepository/id
url

dav:http://[someip]/archiva/repository/myRepository/
/url
/snapshotRepository
/distributionManagement

pluginRepositories
pluginRepository
idmyRepository/id
url

dav:http://[someip]/archiva/repository/myRepository/
/url  
/pluginRepository
/pluginRepositories

repositories
repository
idmyRepository/id
namemyRepository/name

urlhttp://[someip]/archiva/repository/myRepository/url
releases
enabledtrue/enabled
/releases
snapshots
enabledtrue/enabled
/snapshots
/repository
/repositories


I wonder what I am doing wrong.

Thanks in advance for the help.

Papapara Tudu
-- 
View this message in context: 
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15709789.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Problem with snapshots

2008-02-27 Thread [EMAIL PROTECTED]

Hi,

The problem is that maven assumes that the -SNAPSHOT is the newest, not
the oldest version available.

You obviously have projects that declare dependencies on just -SNAPSHOT,
but want the latest *dated* version to be used. So I suggest you delete
the original -SNAPSHOT version, or rename it to have an appropriate date
suffix.

Regards,
Simon

Papapara Tudu schrieb:
 Hello,
 maybe I misunderstand something about snapshots, but I have the following
 problem:
 1. I have a non-Maven project which I export into a jar file and then
 install as a snapshot onto my local repository running on Archiva with this
 command:

 mvn deploy:deploy-file -Dfile=Project.jar -DgroupId=com.company.project
 -DartifactId=project -Dversion=2.2-SNAPSHOT -Dpackaging=jar
 -DgeneratePom=true -Durl=http://[someip]/archiva/repository/myRepository
 -DrepositoryId=archiva.default

 2. The very first version of that jar that was deployed onto the repository
 is saved as project-2.2-SNAPSHOT.jar. 

 3. As expected, any further jars that I deploy onto the local repository get
 saved as e.g. project-2.2-20080226.143100-1.jar

 4.  The problem is that when I reference that jar in any other project, when
 I build the other project, only the project-2.2-SNAPSHOT.jar version (the
 very first one that was installed) is picked up in the output war and ear
 files.

 5. I can see that the actual snapshots, e.g.
 project-2.2-20080226.143100-1.jar do get downloaded from the internal
 repository and installed onto my local repository, but they're never used by
 referencing projects.

 6. I'm using the Maven Plugin for Eclipse and what is strange is that in the
 Maven Dependencies tree in all referencing projects, I see the
 project-2.2-SNAPSHOT.jar file, but in the plugin logs on the Console I can
 see this:
 project: resolved to version project-2.2-20080226.143100-1 from repository
 myRepository


 7. I reference this jar in other projects as:
 dependency
   groupIdcom.company.project/groupId 
   artifactIdproject/artifactId 
   version[2,)/version 
 /dependency

  (I also tried this configuration:
 dependency
   groupIdcom.company.project/groupId 
   artifactIdproject/artifactId 
   version2.2-SNAPSHOT/version 
 /dependency
 but it had exactly the same results)

 8. My pom.xml config is:

   distributionManagement
   snapshotRepository
   idmyRepository/id
   url
   
 dav:http://[someip]/archiva/repository/myRepository/
   /url
   /snapshotRepository
   /distributionManagement

   pluginRepositories
   pluginRepository
   idmyRepository/id
   url
   
 dav:http://[someip]/archiva/repository/myRepository/
   /url  
   /pluginRepository
   /pluginRepositories

   repositories
   repository
   idmyRepository/id
   namemyRepository/name
   
 urlhttp://[someip]/archiva/repository/myRepository/url
   releases
   enabledtrue/enabled
   /releases
   snapshots
   enabledtrue/enabled
   /snapshots
   /repository
   /repositories


 I wonder what I am doing wrong.

 Thanks in advance for the help.

 Papapara Tudu
   


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

Re: Multi-Module Hierarchy : Eclipse vs Maven Plugins

2008-02-27 Thread Siarhei Dudzin

Just FYI, Eclipse 3.3 does support hierarchical project layout.

Siarhei

On Mon, Feb 25, 2008 at 7:52 AM, Andrew Hughes [EMAIL PROTECTED] wrote:

 Thanks Graham!

 I works this out just as I got your email :)

 To explain this to others... taking a multi module maven project either
 out
 of svn/cvs (Q: outside eclipse only?) or creating one from scratch leaves
 you with a skeleton Maven project. With no eclipse
 .project/.classpath/.whatever files in the project, it can then be made
 eclipse complient with the mvn eclipse:eclipse command on the project
 parent.  From this point onwards, the project source now contains all the
 Maven Information, Eclipse Information, and possibly svn/cvs.

 Now that you have content to import, you can Import Existing Projects -
 Maven Project into Eclipse. With it will come the Maven, Eclipse and
 possibly svn/cvs information. The parent appears in the project list, as
 do
 the modules.

 I only have these closing questions/clarification...

 Performing checkout's outside the IDE, then running mvn eclipse:eclipse,
 then  importing is a bit of a pain to get around this would people
 (arguably no doubt) checkin the mvn eclipse:eclipse configuration into
 svn/cvs once generated? Or is it possible to checkout a parent, then run
 eclipse:eclipse within the IDE?


 Thanks again,
 Andrew


 On Mon, Feb 25, 2008 at 9:52 AM, Graham Leggett [EMAIL PROTECTED] wrote:

  Andrew Hughes wrote:
 
   The bottom line is that eclipse can't cope with specifically with the
   parent and heirarchy strucutre. You must checkout the whole parent
  with
   command line (or a different IDE) and mvn install the parent to the
  local
   repo..
 
  Yep, not too far beyond most developers at this point...
 
   then work on each module individually checked out in isolation.
 
  Why?
 
  Just run mvn eclipse:eclipse in the root of your multimodule project,
  and then tell eclipse to import existing projects starting at the root
  of the multi module project.
 
  Eclipse will import all projects regardless of any weird directory
  structure you (or maven) might have imposed, and you can switch between
  the projects at will, and have all of them loaded at once.
 
  Maven sets up all the eclipse projects in a multimodule build so that
  each project depends directly on each other project in eclipse (as
  opposed to modules depending on the final jar of another module). This
  removes the need to run mvn install on one module before changes to it
  are visible to other modules in the multimodule project.
 
  Yes, the original checkout will need to be done outside of eclipse using
  a normal scm tool, but that's not beyond the skills of a developer is
 it?
 
  Regards,
  Graham
  --

Re: Adding a Project using XML-RPC - Broken?

2008-02-27 Thread Olivier Lamy

looks related to CONTINUUM-1590 ?

--
Olivier

2008/2/27, Emmanuel Venisse [EMAIL PROTECTED]:
 Can we see your code?


  Emmanuel


  On Wed, Feb 27, 2008 at 1:01 AM, kroe [EMAIL PROTECTED] wrote:

  
   I am tinkering with the ContinuumXmlRpcClient and think I found a bug.
When
   calling addMavenTwoProject and specifying the project group id I get an
   exception.  Am I doing something wrong, or is this method broken?
  
   Thanks,
   -Ken
  
   INFO   | jvm 1| 2008/02/26 18:05:53 |
   org.apache.xmlrpc.XmlRpcException:
   Failed to invoke method addMavenTwoProject in class
   org.apache.maven.continuum.x
   mlrpc.server.ContinuumServiceImpl: null
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
   
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.invoke
   (ContinuumXmlRpcMetaDataHand
   ler.java:164)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
   
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.execute
   (ContinuumXmlRpcMetaDataHan
   dler.java:133)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcServerWorker.execute(
   XmlRpcServerWorker.java:43)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:83)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcStreamServer.execute(
   XmlRpcStreamServer.java:182)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(
   XmlRpcServletServer.java:103)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcServlet.doPost(
   ContinuumXmlRpcServlet.java:193)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:830)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(
   FilterDispatcher.java:189)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
   PageFilter.java:118)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
   PageFilter.java:52)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(
   ActionContextCleanUp.java:88)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(
   WebApplicationHandler.java:471)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationContext.handle(
   WebApplicationContext.java:633)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpServer.service(HttpServer.java:909)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
   INFO   | jvm 1| 2008/02/26 18:05:53 | Caused by:
   INFO   | jvm 1| 2008/02/26 18:05:53 |

Re: Newbie... Help!!!!!!!

2008-02-27 Thread [EMAIL PROTECTED]

Keenan schrieb:
 Can anyone provide a complete settings.xml file with proxy settings, mirrors,
 repositories etc for maven 2.0.5
 Pls.. its urgent
   
See the references section of the Myfaces documentation page:
  http://maven.apache.org/guides/index.html

Regards,
Simon


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

Newbie... Help!!!!!!!

2008-02-27 Thread Keenan


Can anyone provide a complete settings.xml file with proxy settings, mirrors,
repositories etc for maven 2.0.5
Pls.. its urgent


TIA

-- 
View this message in context: 
http://www.nabble.com/Newbie...-Help%21%21%21%21%21%21%21-tp15710307s177p15710307.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Release plugin (prepare) doesn't update more than one dependencies in multi modules project

2008-02-27 Thread Zucchi Alessandro

Hi all,
I found the time to upload a simple example that reproduce the problem.
http://www.nabble.com/file/p15710300/test.zip test.zip

Step to follow:
1- install project in your repository (updating your SSC url (svn/ cvs ..)
2- run: mvn -DpreparationGoals=clean,install -DautoVersionSubmodules=true
release:clean release:prepare on framework project
3- run:mvn -DpreparationGoals=clean,install -DautoVersionSubmodules=true
release:clean release:prepare on au project end resolve all the
SNAPSHOT dependencies prompted (framework business framework sistema)
4- Look at the au root pom.xml. You will see something of similar

dependency
groupIdtest.zucchetti.qweb.framework/groupId
artifactIdsistema/artifactId
version03.00.05-SNAPSHOT/version
/dependency
dependency
groupIdtest.zucchetti.qweb.framework/groupId
artifactIdbusiness/artifactId
version03.00.04-SNAPSHOT/version
/dependency

Only one SNAPSHOT dependency has been correctly updated.
For me this is a bug the I tryed to resolve with this patch:

http://jira.codehaus.org/secure/attachment/32414/patch.txt
http://jira.codehaus.org/secure/attachment/32414/patch.txt

Any help is appreciated
Alex

Zucchi Alessandro wrote:

Hi Paul,
thank you for your answer.

I created a new issue in JIRA with a patch that resolve the problem (or
what I think to be a problem)
http://jira.codehaus.org/browse/MRELEASE-323

Now I can't attach a small test to the issue for time purpose, the
release is close :-(
When I have a few free time I'll attach a simple test to the issue.
Until than, if you want you can try to apply my patch and see if resolve
your problems. I created a patch against 2.0-beta-8 but runs also with the
tagged 2.0-beta-7 version.

Bye
Alex

Paul Gier wrote:

Sorry this is not much help, but I haven't had good luck with getting the
release plugin to update my snapshot dependencies either. So I always
update
them manually before doing a release. If you can create a jira issue for
this
(in the release plugin project) and attach a small test project to
reproduce the
problem, I'm sure someone will get around to take a look at this.

alexsil wrote:
Hi all,
I have a project so structured:

au au-business
|
|--- au-sistema

Dependencies in au are:

...
dependencyManagement
dependencies
dependency
groupIdcom.zucchetti.qweb.au/groupId
artifactIdau-business/artifactId
version${project.version}/version
/dependency

!-- external dependencies--
dependency
groupIdcom.zucchetti.qweb.framework/groupId
artifactIdsistema/artifactId
version03.00.02-SNAPSHOT/version
/dependency
dependency
groupIdcom.zucchetti.qweb.framework/groupId
artifactIdbusiness/artifactId
version03.00.02-SNAPSHOT/version
/dependency
/dependencies
/dependencyManagement
...

Dependencies in au-business are:
...
dependencies
dependency
groupIdcom.zucchetti.qweb.framework/groupId
artifactIdbusiness/artifactId
/dependency
/dependencies
...

Dependencies in au-sistema are:
...
dependencies
dependency
groupIdcom.zucchetti.qweb.au/groupId
artifactIdau-business/artifactId
/dependency
dependency
groupIdcom.zucchetti.qweb.framework/groupId
artifactIdsistema/artifactId
/dependency
/dependencies
...

When I make a mvn release:clean release:prepare the plugin, correctly,
ask
me to resolve SNAPSHOTs dependencies. (framework-business
framework-sistema)
Unfortunatly at the end of the process only framework-sistema has been
modified, while framework-business no.
I've debuged the problem and I found that if I force the two
dependencies
(framework-sistema, framework-business) in the parent pom (pom of au)
all
run fine (also if the process to resolve SNAPSHOT dependencies get
prompted
tree times ... too much I say ...).
Is this the correct behavior ?
I hope no, becouse I should modify al my poms.

Morever , the flag updateDependencies=false doesn't run. I think it
has
not managed.

Best regards
Alex

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

--
View this message in context:
http://www.nabble.com/Release-plugin-%28prepare%29-doesn%27t--update-more-than-one-dependencies-in-multi-modules-project-tp15293510s177p15710300.html
Sent from the Maven - Users mailing

jaxws-maven-plugin jaxws:wsgen - Could not find class file

2008-02-27 Thread Henri Gomez

I get the same error reference in this thread :

http://www.mail-archive.com/users@maven.apache.org/msg72977.html

Did someone know if this problem is planned to be fixed in jaxws-maven-plugin ?

Regards

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

Re: Problem with snapshots

2008-02-27 Thread Papapara Tudu



[EMAIL PROTECTED] wrote:
 
 The problem is that maven assumes that the -SNAPSHOT is the newest, not
 the oldest version available.
 
 You obviously have projects that declare dependencies on just -SNAPSHOT,
 but want the latest *dated* version to be used. So I suggest you delete
 the original -SNAPSHOT version, or rename it to have an appropriate date
 suffix.
 
The problem is that when I install new versions of that jar, they don't get
picked up by the build - although the -SNAPHSOT version is NOT the newest
anymore then. 

And this all has to work without deleting anything from the internal or
local repositories - otherwise the problem will reoccur whenever new
snapshots are created.

I believe my understanding is correct: here's a quote from the Better
builds with Maven book:

You'll see that it is treated differently than when it was installed in the
local repository. The filename
that is used is similar to proficio-api-1.0-20060211.131114-1.jar. In this
case, the version
used is the time that it was deployed (in the UTC timezone) and the build
number. If you were to
deploy again, the time stamp would change and the build number would
increment to 2.
This technique allows you to continue using the latest version by declaring
a dependency on 1.0-
SNAPSHOT, or to lock down a stable version by declaring the dependency
version to be the specific
equivalent such as 1.0-20060211.131114-1.

Papapara Tudu
-- 
View this message in context: 
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15711423.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Problem with snapshots

2008-02-27 Thread Papapara Tudu



Jeff MAURY wrote:
 
 This is because the file name with the timestamp is something internal to
 the repository. When the dependency is resolved to your WAR, the original
 file name is restored based on the artifactId and the version you mention
 in
 your POM.
 Maybe if you put Maven in debug mode, you could see that the file
 retrieved
 from your local repository is the one with the timestamp.
 
OK but I believe it should still work in the following way: when I build a
referencing project, it takes the latest version of the jar (so that will be
the project-2.2-20080226.143100-1.jar and not project-2.2-SNAPSHOT.jar) and
puts it in the output war file.
What it does though is it just takes the project-2.2-SNAPSHOT.jar file and
puts it in the output war file.

Papapara Tudu

-- 
View this message in context: 
http://www.nabble.com/Problem-with-snapshots-tp15709789s177p15711493.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Cargo: custom ctx path for deployment

2008-02-27 Thread Clifton

Thanx Jeff,

But my problem isn't with Cargo or the container. Rather its a Maven
misunderstanding. I need a way for one profile to override the properties of
another is what it realy boils down to. If that can't be done then I need a
different approach.

Jeff MAURY wrote:

Clifton,

I remember I had problems with the context property of Cargo: it didn't
work
at all but I can't remember which container was involved.

Regards
Jeff MAURY

On Wed, Feb 27, 2008 at 4:38 AM, Clifton [EMAIL PROTECTED] wrote:

http://devserver:8080/webapp1
http://devserver:8080/webapp2
http://devserver:8080/webapp3

I'd like to set a dev profile called dev-ccc and have it deploy the war
files like so:

http://devserver:8080/ccc-webapp1
http://devserver:8080/ccc-webapp2
http://devserver:8080/ccc-webapp3

Team-wide super pom:
project
!-- other stuff --
properties
webapp.root.ctx/ccc-/webapp.root.ctx
/properties
/project

Project root pom
project
!-- other stuff --
properties
webapp.root.ctx//webapp.root.ctx
/properties
/project

context${webapp.root.ctx}webapp1/context
/properties
/deployable
/deployables
/deployer
/configuration
executions
execution
phasedeploy/phase
/execution
/executions
/plugin
/project

Could somebody lend a hand? Thanx a bunch in advance!

-Cliff
--
View this message in context:
http://www.nabble.com/Cargo%3A-custom-ctx-path-for-deployment-tp15705398s177p15705398.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

--
View this message in context:
http://www.nabble.com/Cargo%3A-custom-ctx-path-for-deployment-tp15705398s177p15711506.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Dependency plugin

2008-02-27 Thread Shakun Gupta


Hi All,
I am using the dependency plugin to copy all the dependencies to an 
output directory. But, the dependencies are also copied in my 
target/dependency directory, i.e., the default directory for this 
plugin. Can you please suggest how to avoid this.


Regards,
Shakun

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

Maven jar-plugin

2008-02-27 Thread Shakun Gupta


Hi All,
I am using Maven 2, and i added the configuration of jar-plugin and 
war-plugin. I am able to assemble the war at a different place using 
outputDirectory property. But, this does not work with jar-plugin. I 
have read in the forums that this is an issue with the jar plugin and 
this will be updated in JIRA. May i know if my understanding is correct. 
And if yes, then which version of the jar-plugin contains this fix.


Regards,
Shakun

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

MvnIndex.org launched

2008-02-27 Thread Lukas Krecan

I have written small Eclipse plugin that simplifies POM editing. It 
provides code competition of groupId, artifactId and version in POM 
dependencies. You can download it here http://mvnindex.org/. Moreover, 
you can search for artifacts on-line on the same page and download index 
of Maven central repository.


Be aware that development is in early stage so there are probably some 
bugs. Do not hesitate and report them to JIRA as well as all ideas for 
enhancement.


Best regards

Lukas


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

Re: Javascript support

2008-02-27 Thread nicolas de loof

Declare your js source directory at plugin level :

plugin
 artifactIdjavascript-maven-plugin/artifact
 configuration
  sourceDirectorymy/source/directory/sourceDirectory
 /configuration

Maybe the plugin should use the project.sourceDirectory as the compile goal
is only relevant in a pure javascript project...

Nico.


2008/2/27, Adrian Herscu [EMAIL PROTECTED]:

 Hi Nicolas,

 How do I specify a different source directory?
 I have looked into the sources and found this:

 http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/javascript-maven-plugin/src/main/java/org/codehaus/mojo/javascript/CompileMojo.java
 Tried the sourceDirectorymy/source/directory/sourceDirectory under
 the build section and got this:
 [INFO]
 
 [INFO] basedir
 C:\documents\pm\project-trunks\wirexn\sandbox\extjs-client-sample
 \src\main\javascript does not exist
 [INFO]
 
 [INFO] Trace
 java.lang.IllegalStateException: basedir
 C:\documents\pm\project-trunks\wirexn\s
 andbox\extjs-client-sample\src\main\javascript does not exist
  at
 org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:
 542)
  at
 org.codehaus.mojo.javascript.CompileMojo.execute(CompileMojo.java:130
 )
  at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
 nManager.java:443)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
 ultLifecycleExecutor.java:539)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
 fecycle(DefaultLifecycleExecutor.java:480)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
 ltLifecycleExecutor.java:459)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
 dleFailures(DefaultLifecycleExecutor.java:311)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
 ts(DefaultLifecycleExecutor.java:278)
  at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
 fecycleExecutor.java:143)
  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:39)
  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
  at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
  at
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

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


 Adrian.



 nicolas de loof wrote:
  The war-package process source scripts and place them in the packaging
  folder used by the war plugin to create the exploded war, before
 archivaing
  a .war.
 
  Nico
 
  2008/2/26, Adrian Herscu [EMAIL PROTECTED]:
  Harlan, thanks for your fast reply. It works!
  However, I am not sure what the goalwar-package/goal does (as in
 the
  example here:
 
 
 http://mojo.codehaus.org/javascript-maven-tools/guide-webapp-development.html
  )
 
  Adrian.
 
 
 
  Harlan Iverson wrote:
  The javascript plugin is currently sandboxed, so following these
  instructions should make it available:
 
  http://mojo.codehaus.org/using-sandbox-plugins.html
 
  The other option is to download the source and run mvn install
 locally.
  The
  location in the plugin's maven site is wrong, it is here:
 
  http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/
 
  You'll need to check out the top level, as the plugin depends on other
  modules.
 
  Good luck.
  Harlan
 
 
  On Mon, Feb 25, 2008 at 12:40 PM, Adrian Herscu [EMAIL PROTECTED]
  wrote:
  Hi all,
 
  In which repository is this plugin hosted?
  I am getting:
 
  Missing:
  --
  1)
 
 
 
 org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT
 
Try downloading the file manually from the project website.
 
Then, install it using the command:
mvn install:install-file -DgroupId=org.codehaus.mojo.javascript
  -Dartifact
  Id=javascript-maven-plugin \
-Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
  -Dfile=/path/to/file
  Alternatively, if you host your own repository you can deploy the
 file
  there:
  mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.javascript
  -DartifactId=j
  avascript-maven-plugin \
-Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
  -Dfile=/path/to/file \
 -Durl=[url] -DrepositoryId=[id]
 
Path to dependency:

Re: MvnIndex.org launched

2008-02-27 Thread Henri Gomez

 I have written small Eclipse plugin that simplifies POM editing. It
  provides code competition of groupId, artifactId and version in POM
  dependencies. You can download it here http://mvnindex.org/. Moreover,
  you can search for artifacts on-line on the same page and download index
  of Maven central repository.

Seems good.

Question: How do you generate the central-index.txt ? The idea is to
make this plugin search/index artifact in an internal repo instead of
central one ?

Regards

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

Re: Javascript support

2008-02-27 Thread Adrian Herscu


Hi Nicolas,

How do I specify a different source directory?
I have looked into the sources and found this:
http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/javascript-maven-plugin/src/main/java/org/codehaus/mojo/javascript/CompileMojo.java
Tried the sourceDirectorymy/source/directory/sourceDirectory under 
the build section and got this:
[INFO] 

[INFO] basedir 
C:\documents\pm\project-trunks\wirexn\sandbox\extjs-client-sample

\src\main\javascript does not exist
[INFO] 


[INFO] Trace
java.lang.IllegalStateException: basedir 
C:\documents\pm\project-trunks\wirexn\s

andbox\extjs-client-sample\src\main\javascript does not exist
at 
org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:

542)
at 
org.codehaus.mojo.javascript.CompileMojo.execute(CompileMojo.java:130

)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi

nManager.java:443)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa

ultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi

fecycle(DefaultLifecycleExecutor.java:480)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau

ltLifecycleExecutor.java:459)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan

dleFailures(DefaultLifecycleExecutor.java:311)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen

ts(DefaultLifecycleExecutor.java:278)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi

fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.

java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces

sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

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


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

Adrian.



nicolas de loof wrote:

The war-package process source scripts and place them in the packaging
folder used by the war plugin to create the exploded war, before archivaing
a .war.

Nico

2008/2/26, Adrian Herscu [EMAIL PROTECTED]:

Harlan, thanks for your fast reply. It works!
However, I am not sure what the goalwar-package/goal does (as in the
example here:

http://mojo.codehaus.org/javascript-maven-tools/guide-webapp-development.html
)

Adrian.



Harlan Iverson wrote:

The javascript plugin is currently sandboxed, so following these
instructions should make it available:

http://mojo.codehaus.org/using-sandbox-plugins.html

The other option is to download the source and run mvn install locally.

The

location in the plugin's maven site is wrong, it is here:

http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/

You'll need to check out the top level, as the plugin depends on other
modules.

Good luck.
Harlan


On Mon, Feb 25, 2008 at 12:40 PM, Adrian Herscu [EMAIL PROTECTED]

wrote:

Hi all,

In which repository is this plugin hosted?
I am getting:

Missing:
--
1)



org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT


  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=org.codehaus.mojo.javascript
-Dartifact
Id=javascript-maven-plugin \
  -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.javascript
-DartifactId=j
avascript-maven-plugin \
  -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file \
   -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1)
org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-S
NAPSHOT
2)
org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-
SNAPSHOT

--
1 required artifact is missing.

for artifact:




org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-SNAPSHOT

from the specified remote repositories:
  [EMAIL PROTECTED] (http://webdav.wirexn.net/snapshots),
  central (http://repo1.maven.org/maven2),
  wirexn.net (http://webdav.wirexn.net/repository)


TIA,
Adrian.

nicolas de loof wrote:

need to host the site in the embeded jetty server of continuum

2008-02-27 Thread Arun Kathirvel Sarojam

HI,

 i am using  continuum and maven2 for continous integration. the 
build will generate a site for my application. i am planning to use the 
embeded jetty server that comes with continuum for hosting this site.  can 
any body suggest me how to do this. i tried to create a directory in 
continuum/apps and copied the html files  in that directory but jetty is 
not recongnising that directory.



advance thanks

Arun K S





DISCLAIMER: 

The information in this e-mail and any attachment is intended only for 
the person to whom it is addressed and may contain confidential and/or 
privileged material. If you have received this e-mail in error, kindly 
contact the sender and destroy all copies of the original communication. 
IBS makes no warranty, express or implied, nor guarantees the accuracy, 
adequacy or completeness of the information contained in this email or any 
attachment and is not liable for any errors, defects, omissions, viruses 
or for resultant loss or damage, if any, direct or indirect.

Re: Maven jar-plugin

2008-02-27 Thread Wendy Smoak

On Wed, Feb 27, 2008 at 5:08 AM, Shakun Gupta [EMAIL PROTECTED] wrote:

  I am using Maven 2, and i added the configuration of jar-plugin and
  war-plugin. I am able to assemble the war at a different place using
  outputDirectory property. But, this does not work with jar-plugin. I
  have read in the forums that this is an issue with the jar plugin and
  this will be updated in JIRA. May i know if my understanding is correct.
  And if yes, then which version of the jar-plugin contains this fix.

You can search JIRA for the issue and find out the fix version (if
any):  http://jira.codehaus.org/browse/MJAR

Then check to see what's been released:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/

Is it this one?  http://jira.codehaus.org/browse/MJAR-16

-- 
Wendy

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

Re: MvnIndex.org launched

2008-02-27 Thread Rune Flobakk


Simple and very useful!

Would it be possible to get completion if one starts to enter the 
artifactId, and, if the artifactId is unique regardless of the groupId, 
to get the groupId tag and value filled in automatically? Or perhaps 
immediately get a completion popup when the artifactId is chosen of any 
available matching groupIds if 1 ?


It is very useful at its present stage, so I am merely suggesting :)

Thank you!

- Rune

Lukas Krecan skrev:
I have written small Eclipse plugin that simplifies POM editing. It 
provides code competition of groupId, artifactId and version in POM 
dependencies. You can download it here http://mvnindex.org/. Moreover, 
you can search for artifacts on-line on the same page and download index 
of Maven central repository.


Be aware that development is in early stage so there are probably some 
bugs. Do not hesitate and report them to JIRA as well as all ideas for 
enhancement.


Best regards

Lukas


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

Re: Adding a Project using XML-RPC - Broken?

2008-02-27 Thread kroe


Code is below.  I have verified that 55 is a project group ID by viewing the
source on the add project page.  Adding the same project works through the
add project page.

ContinuumXmlRpcClient continuumClient = new ContinuumXmlRpcClient(new
URL(SCMConstants.CONTINUUM_XMLRPC_URL)
, SCMConstants.CONTINUUM_USERNAME
, SCMConstants.CONTINUUM_PASSWORD);

continuumClient.addMavenTwoProject(http://svnrepositoryurl/branches/branch/project/pom.xml;,
55);

Thanks,
-Ken




olamy wrote:
 
 looks related to CONTINUUM-1590 ?
 
 --
 Olivier
 
 2008/2/27, Emmanuel Venisse [EMAIL PROTECTED]:
 Can we see your code?


  Emmanuel


  On Wed, Feb 27, 2008 at 1:01 AM, kroe [EMAIL PROTECTED] wrote:

  
   I am tinkering with the ContinuumXmlRpcClient and think I found a bug.
When
   calling addMavenTwoProject and specifying the project group id I get
 an
   exception.  Am I doing something wrong, or is this method broken?
  
   Thanks,
   -Ken
  
   INFO   | jvm 1| 2008/02/26 18:05:53 |
   org.apache.xmlrpc.XmlRpcException:
   Failed to invoke method addMavenTwoProject in class
   org.apache.maven.continuum.x
   mlrpc.server.ContinuumServiceImpl: null
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
  
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.invoke
   (ContinuumXmlRpcMetaDataHand
   ler.java:164)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
  
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.execute
   (ContinuumXmlRpcMetaDataHan
   dler.java:133)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcServerWorker.execute(
   XmlRpcServerWorker.java:43)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcServer.execute(XmlRpcServer.java:83)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.server.XmlRpcStreamServer.execute(
   XmlRpcStreamServer.java:182)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.apache.xmlrpc.webserver.XmlRpcServletServer.execute(
   XmlRpcServletServer.java:103)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
 org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcServlet.doPost(
   ContinuumXmlRpcServlet.java:193)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:830)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(
   FilterDispatcher.java:189)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
   PageFilter.java:118)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
   PageFilter.java:52)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   com.opensymphony.webwork.dispatcher.ActionContextCleanUp.doFilter(
   ActionContextCleanUp.java:88)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
   WebApplicationHandler.java:821)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(
   WebApplicationHandler.java:471)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
  
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.jetty.servlet.WebApplicationContext.handle(
   WebApplicationContext.java:633)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpServer.service(HttpServer.java:909)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpConnection.service(HttpConnection.java:816)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at
   org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)
   INFO   | jvm 1| 2008/02/26 18:05:53 |   at

Re: Dependency plugin

2008-02-27 Thread Wayne Fay

Is this really a problem for you, or just an annoyance?

Wayne

On 2/27/08, Shakun Gupta [EMAIL PROTECTED] wrote:
 Hi All,
 I am using the dependency plugin to copy all the dependencies to an
 output directory. But, the dependencies are also copied in my
 target/dependency directory, i.e., the default directory for this
 plugin. Can you please suggest how to avoid this.

 Regards,
 Shakun

 -
 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: need to host the site in the embeded jetty server of continuum

You can't.

A better way would be to use the continuum webapp instead of the standalone
version and to install in in a web container like tomcat or jetty. Then
you'll can do what you want.

Emmanuel

On Wed, Feb 27, 2008 at 2:08 PM, Arun Kathirvel Sarojam [EMAIL PROTECTED]
wrote:


 HI,

  i am using  continuum and maven2 for continous integration. the
 build will generate a site for my application. i am planning to use the
 embeded jetty server that comes with continuum for hosting this site.  can
 any body suggest me how to do this. i tried to create a directory in
 continuum/apps and copied the html files  in that directory but jetty is
 not recongnising that directory.



 advance thanks

 Arun K S



 *

 DISCLAIMER:** *

 The information in this e-mail and any attachment is intended only for
 the person to whom it is addressed and may contain confidential and/or
 privileged material. If you have received this e-mail in error, kindly
 contact the sender and destroy all copies of the original communication. IBS
 makes no warranty, express or implied, nor guarantees the accuracy, adequacy
 or completeness of the information contained in this email or any attachment
 and is not liable for any errors, defects, omissions, viruses or for
 resultant loss or damage, if any, direct or indirect.

Re: Cargo: custom ctx path for deployment

2008-02-27 Thread VUB Stefan Seidel


Clifton wrote:

I need a way for one profile to override the properties of
another is what it realy boils down to. 


You gave yourself the answer, didn't you? Just declare a profile for 
dev, set the property to the dev value within the profile. Activate the 
profile using settings.xml, or mvn -P 


regards,

Stefan
--
best regards,

Stefan Seidel
software developer

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

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

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

Re: maven-eclipse-plugin 2.4 versioned project

Hello:

Thanks so much for the response.  Yes, I agree that it would be ideal if the 
name of the generated jar/war/ear file is kept same as the project directory 
name -- I believe that's what finalName does as per the docs (?).  However, my 
teammates responsible for maven builds don't like the idea at all.. tried 
really hard to convince otherwise even before we ran into this issue.  They 
want the generated file name template to contain project POM version, e.g. 
given POM project name myproject and POM version 1.0, the name of the 
generated JAR file will be myproject-1.0.jar.  Same goes for WAR and EAR 
modules.   And as soon as version'd project names are used, where the physical 
directory name does not contain POM version numbers obviously, it causes RAD 
6/7 loose configuration to fail miserably, in context of WebSphere v6.1 runtime.

Since you brought up maven-eclipse-plugin 2.5, it seems like it's pretty close 
to being officially realized.  Do you have the exact timeframe as to when it 
will be?  Days.. weeks.. months?

I will take a look at the maven-eclipse-plugin 2.5 SNAPSHOT code.  The
alternative is to recompile maven-eclipse-plugin 2.4 with the one-line
code change as outlined earlier.. which I plan on doing today.  Any
thoughts on this approach?

Regards
Salman Moghal

- Original Message 
From: Siarhei Dudzin [EMAIL PROTECTED]
To: Maven Users List users@maven.apache.org
Sent: Wednesday, February 27, 2008 5:01:44 AM
Subject: Re: maven-eclipse-plugin 2.4  versioned project

I've 
done 
quite 
some 
troubleshooting 
around 
RAD6+maven. 
I 
would 
advise 
to
override 
the 
finalName 
for 
the 
artifact 
so 
it 
doesn't 
have 
version 
at 
the
end.
It's 
even 
better 
if 
those 
match 
the 
project 
directory 
names.

maven-eclipse-plugin 
2.5-SNAPSHOT 
has 
quite 
a 
lot 
of 
improvements 
in 
RAD6/7
support. 
It 
is 
currently 
only 
1 
jira 
issue 
away 
from 
being 
released.

Siarhei

On 
Wed, 
Feb 
27, 
2008 
at 
9:04 
AM, 
Salman 
Moghal 
[EMAIL PROTECTED] 
wrote:

 
I've 
been 
pouring 
through 
maven-eclipse-plugin 
2.4 
code 
and 
realized 
that
 
there 
is 
potentially 
a 
problem 
with
 
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass
 
(line 
125), 
IMHO:

  
  
writer.addAttribute( 
ATTR_DEPLOY_NAME,
 
config.getProject().getArtifactId() 
);

 
It 
seems 
like 
the 
code 
above 
assumes 
deploy-name 
cannot 
contain 
version
 
numbers, 
project 
name 
templates 
etc. 
It 
would 
be 
great 
if 
the 
code 
could
 
follow 
similar 
structured 
approach 
for 
setting/getting 
the 
project 
name 
as
 
in 
org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter 
(line
 
169),
 
which 
generates 
.project 
file:

  
  
writer.writeText( 
config.getEclipseProjectName() 
);

 
Here 
the 
project 
name 
is 
set 
during 
configuration/dependancy 
resolution
 
phase 
by 
org.apache.maven.plugin.eclipse.EclipsePlugin 
and 
later 
used 
by
 
the
 
EclipseProjectWriter 
class.

 
So 
I'm 
curious 
if 
this 
issue 
could 
be 
resolved 
by 
simply 
using
 
getEclipseProjectName() 
method 
in
 
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass:

  
  
writer.addAttribute( 
ATTR_DEPLOY_NAME, 
config.getEclipseProjectName()
 
);

 
Please 
advise..

 
--
 
Salman 
Moghal

 
- 
Original 
Message 
-
 
From: 
Salman 
Moghal 
[EMAIL PROTECTED]
 
To: 
users@maven.apache.org
 
Sent: 
Tuesday, 
February 
26, 
2008 
3:38 
PM
 
Subject: 
maven-eclipse-plugin 
2.4 
 
versioned 
projects


 
 
Hello:
 

 
 
I'm 
using 
maven-eclipse-plugin 
v2.4 
to 
generate 
WTP 
1.5 
resource 
for
 
 
Eclipse 
3.2.x 
/ 
RAD 
v6.x 
environment.  
The 
goal 
of 
this 
exercise 
is 
to
 
 
take 
advantage 
of 
Eclipse 
3.2 
/  
RAD 
v6.x
 
 
integrated 
development, 
debugging, 
and 
hot 
code 
deployment 
features.
  
The
 
 
runtime 
environment 
is 
WebSphere 
Application 
Server 
v6.1.  
Eclipse 
/ 
RAD
 
 
also 
have 
M2Eclipse 
plugin 
installed 
for 
dependency 
management, 
etc.
 
 
There 
is 
one 
slight 
issue 
that 
has 
me 
scratching 
my 
head 
for 
a 
few 
days.
 
 
It 
has 
to 
do 
with 
generated 
WTP 
v1.5 
files.
 

 
 
Essentially, 
maven 
eclipse 
plugin 
goal 
eclipse:m2eclipse 
generates 
all
 
 
WTP 
1.5 
files 
correctly.  
However, 
once
 
 
addVersionToProjectNametrue/addVersionToProjectName 
is 
added 
to
 
plugin
 
 
config,  
.settings/org.eclipse.wst.common.component 
contains 
an
 
incorrect
 
 
entry.  
The 
goal 
generates 
the 
.project 
WTP 
file 
properly 
with 
a 
project
 
 
name 
containing 
the 
POM 
version 
number, 
but 
the 
corresponding
 
 
.settings/org.eclipse.wst.common.component 
contains 
an 
incorrect 
value
 
for
 
 
wb-module 
deploy-name=..  
The 
value 
of 
deploy-name=  
does 
not
 
 
contain 
a 
POM 
version 
number 
along 
with 
the 
project 
name.
 

 
 
The 
reason 
why 
having 
a 
version 
number 
in 
wb-module 
deploy-name= 
entry
 
is
 
 
important 
is 
because 
if 
the 
EAR 
/ 
WAR

RE: Best practice to represent an arbitrary collection of jars asa single dependency?

2008-02-27 Thread Brown, Carlton

Yes, we have a similar problem, not RAD but something like it.   Your
solution below is more or less what I figure I'll have to do.   It's a
variation on the other solutions mentioned, but it helps clear things up
for me.

So if I'm reading below correctly, you're essentially ignoring the real
version of the artifact and mapping them all as version 6.3.9 (which is
presumably the version of RAD you're using)?

If the virtual POM specifies a master version of (for example 6.3.9), I
guess one could install all the individual jars with their actual
version numbers (derived from the jar filename or manifest).   It's just
a small additional effort if I've decided to throw in the towel and
script a mass install.

Question:  I notice that using dotted notation in groupId expands to a
directory structure during installation or deployment.  Does this
behavior also hold for artifactId?

-Original Message-
From: Olivier Dehon [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 26, 2008 9:48 PM
To: Maven Users List
Subject: Re: Best practice to represent an arbitrary collection of jars
asa single dependency?

I had to resolve a similar issue when trying to compile RAD projects
with Maven. RAD comes with WebSphere runtime JARs in a specific
directory (which would be provided on the WebSphere server). By default,
RAD uses those runtime libraries without the need to specify the
dependency in the .classpath explicitly (RAD defines the concept of a
container for that purpose).

To be able to build the RAD project with Maven, I uploaded all of the
runtime JARs as artifacts in my repository, and created a
dependency-only pom project that has all those dependencies.

Then, to build the project with Maven, I simply have to add a dependency
on that pom project, and set it as provided scope to emulate in Maven
the RAD build environment.

Once the project compiles ok, running mvn dependency:analyze helps
trimming down those provided dependencies to only the ones that are
actually needed.

Uploading all jars from a directory to the repository is actually a very
easily scriptable task with a decent shell, if you are installing the
JARs with the same groupId and version for all of them.

For example (untested, but you get the idea):

for lib in *.jar; do
  artifact=`basename $lib .jar`
  mvn install:install-file \
-DgroupId=com.somecorp -Dversion=6.3.9 \
-DartifactId=$artifact \
-Dpackaging=jar -Dfile=$lib

  echo \dependency\
  \artifactId\$artifact\/artifactId\
  \groupId\com.somecorp\/groupId\
  \version\6.3.9\/version\
\/dependency\  somecorp-meta.pom done

Just edit somecorp-meta.pom after that to add header and footer and
install it with install:install-file also.

I hope this helps.

-Olivier

On Tue, 2008-02-26 at 12:41 -0600, Wayne Fay wrote:
 This simply is not a feature that currently exists in Maven, and for a

 lot of reasons, I don't see it being a feature that will be 
 implemented any time soon.
 
 Your best bet is the list all artifacts as dependencies in a pom, and

 depend on it option that I suggested earlier. This in combination 
 with Archiva, Artifactory, Proximity etc would be the right solution

 in my book.
 
 But, I don't think your projects actually need all 50 of those 
 artifacts. So the best solution is to specify the proper dependencies 
 explicitly in each project, and use a shared parent with a 
 dependencyManagement section that helps you manage versions of 
 artifacts.
 
 Wayne
 
 On 2/26/08, Brown, Carlton [EMAIL PROTECTED] wrote:
  I want to take a single directory of ~50 jars and specify that as a 
  single dependency.
 
  I'm explicitly trying to avoid specifying them as 50 separate 
  dependencies in a pom file, or breaking them out in 50 different 
  module subdirectories under an internal Archiva repository.  It 
  sounded to me as if this is what you were suggesting, quite a bit of
work.
 
  Perhaps I'm not wording the question correctly, as it seems like 
  this would be a very common situation.
 
   -Original Message-
   From: Wayne Fay [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, February 26, 2008 11:49 AM
   To: Maven Users List
   Subject: Re: Best practice to represent an arbitrary collection of
  jars as
   a single dependency?
  
   I guess we don't understand what you want/need, as it sounds a lot

   like what we're suggesting. You can manage the artifacts 
   themselves by using Archiva etc rather than asking Maven to 
   download direct from the Internet.
  
   An alternative is to unzip each jar into a shared directory and 
   then re-jar all of it. But I don't know if that would actually 
   work due to log4j.xml collisions etc.
  
   Wayne
  
   On 2/26/08, Brown, Carlton [EMAIL PROTECTED] wrote:
These approaches both involve resolving each jar as an 
individual separate dependency, a large amount of manual effort 
for a couple of reasons.  I'd have to specify 50 new 
dependencies in the POM, and

Integration Tests

2008-02-27 Thread vitor lundberg

hello,

in the maven lifecycle  we have the integration tests.
Can some one help me to understand how to implement thoses tests ??

thx,
Vitor

Re: Integration Tests

2008-02-27 Thread Luca Marrocco

Hi Vitor,
the simplest way is to create you integration test as junit classes
under src/test/java directory.


Luca

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

Re: maven-eclipse-plugin 2.4 versioned projec

2008-02-27 Thread Siarhei Dudzin

On Wed, Feb 27, 2008 at 5:37 PM, Salman Moghal [EMAIL PROTECTED] wrote:


 Thanks so much for the response.  Yes, I agree that it would be ideal if
 the name of the generated jar/war/ear file is kept same as the project
 directory name -- I believe that's what finalName does as per the docs (?).
  However, my teammates responsible for maven builds don't like the idea at
 all.. tried really hard to convince otherwise even before we ran into this
 issue.  They want the generated file name template to contain project POM
 version, e.g. given POM project name myproject and POM version 1.0, the
 name of the generated JAR file will be myproject-1.0.jar.  Same goes for
 WAR and EAR modules.   And as soon as version'd project names are used,
 where the physical directory name does not contain POM version numbers
 obviously, it causes RAD 6/7 loose configuration to fail miserably, in
 context of WebSphere v6.1 runtime.


It is indeed as you mentioned finalName.
If they don't want to have final name fixed you could probably somehow parse
the ibm-specific deployment descriptors. Because artifact names are actually
hardcoded there. So if your version changes - you have a problem.




 Since you brought up maven-eclipse-plugin 2.5, it seems like it's pretty
 close to being officially realized.  Do you have the exact timeframe as to
 when it will be?  Days.. weeks.. months?


Hard to say, my impression is that it's in the state of days for a few
weeks now...



 I will take a look at the maven-eclipse-plugin 2.5 SNAPSHOT code.  The
 alternative is to recompile maven-eclipse-plugin 2.4 with the one-line
 code change as outlined earlier.. which I plan on doing today.  Any
 thoughts on this approach?


It's likely you will run into many more issues. To know which ones you can
see at all the closed issues that are scheduled for 2.5 release. I can tell
you in advance - if you use webservices you will have a problem.

It's really easier just to use 2.5-SNAPSHOT (unless you use release plugin).

Siarhei

Re: Integration Tests

2008-02-27 Thread vitor lundberg

Thx for replay Luc,

but the problem is if I create my integration test under src/test/java my
integration test will starts like a unit test under the lifecyle test and
I wish that my integration test start after the package steep.
so if I put my  classes under the same repertory as the tests classes maven
dont make the differences
that is a way to make a difference thoses tests ?

On Wed, Feb 27, 2008 at 5:47 PM, Luca Marrocco [EMAIL PROTECTED]
wrote:

 Hi Vitor,
 the simplest way is to create you integration test as junit classes
 under src/test/java directory.


 Luca

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

What does: Skipping disabled repository central really mean?

2008-02-27 Thread Chris Helck

Hi,

A certain user of mine gets Skipping disabled repository central when
mvn (2.0.8) tries to download a plugin. I've printed the effective-pom
and effective-settings and I don't see anything redirection of central
with mirrors or repository. 

It certainly sounds like mvn is not looking in the central repo when it
tries to download a plugin. But I don't see why it is disabled. Can
anyone explain? Below is the effective pom and settings:



Effective POM for project 'ebs:md_build_instructions:jar:1.0-SNAPSHOT'


?xml version=1.0?project
  parent
artifactIdmd_parent/artifactId
groupIdebs/groupId
version1.4-SNAPSHOT/version
  /parent
  modelVersion4.0.0/modelVersion
  groupIdebs/groupId
  artifactIdmd_build_instructions/artifactId
  namemd_build_instructions/name
  version1.0-SNAPSHOT/version
  urlhttp://www.ebs.com/url

  build
 
sourceDirectory/home/cc/perforce/MarketData/build/maven2/build_instruc
tions/src/main/java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
 
testSourceDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
tructions/src/test/java/testSourceDirectory
 
outputDirectory/home/cc/perforce/MarketData/build/maven2/build_instruc
tions/target/classes/outputDirectory
 
testOutputDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
tructions/target/test-classes/testOutputDirectory
resources
  resource
 
directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
src/main/resources/directory
  /resource
/resources
testResources
  testResource
 
directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
src/test/resources/directory
  /testResource
/testResources
 
directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
target/directory
finalNamemd_build_instructions-1.0-SNAPSHOT/finalName
plugins
  plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
  source1.5/source
  target1.5/target
/configuration
  /plugin
  plugin
artifactIdmaven-one-plugin/artifactId
version1.2/version
executions
  execution
goals
  goalinstall-maven-one-repository/goal
  goaldeploy-maven-one-repository/goal
/goals
configuration
 
remoteRepositoryIdcom.ebs.development.repo/remoteRepositoryId
 
remoteRepositoryUrlscp://172.16.12.10/apps/local/apache2/htdocs/maven
/remoteRepositoryUrl
/configuration
  /execution
/executions
  /plugin
  plugin
artifactIdmaven-site-plugin/artifactId
version2.0-beta-6/version
executions
  execution
idcreate site/id
phasepackage/phase
goals
  goalsite/goal
/goals
  /execution
  execution
iddeploy site/id
phasedeploy/phase
goals
  goaldeploy/goal
/goals
  /execution
/executions
configuration
  localesen/locales
/configuration
  /plugin
  plugin
artifactIdmaven-surefire-plugin/artifactId
version2.4.2/version
configuration
  useFilefalse/useFile
  excludes
exclude**/*ITest.java/exclude
exclude**/Abstract*Test.java/exclude
  /excludes
/configuration
  /plugin
  plugin
artifactIdmaven-help-plugin/artifactId
version2.0.2/version
  /plugin
/plugins
  /build
  repositories
repository
  iddev-legacy/id
  namelegacy/name
  urlhttp://172.16.12.10/maven/url
  layoutlegacy/layout
/repository
repository
  iddev-vendor/id
  namevendor/name
  urlhttp://172.16.12.10/maven2/dev/repo//url
/repository
repository
  iddev-product/id
  nameproducts/name
  urlhttp://172.16.12.10/maven2/dev-product/repo//url
/repository
repository
  snapshots
enabledfalse/enabled
  /snapshots
  idcentral/id
  nameMaven Repository Switchboard/name
  urlhttp://repo1.maven.org/maven2/url
/repository
  /repositories
  pluginRepositories
pluginRepository
  releases
updatePolicynever/updatePolicy
  /releases
  snapshots
enabledfalse/enabled
  /snapshots
  idcentral/id
  nameMaven Plugin Repository/name
  urlhttp://repo1.maven.org/maven2/url
/pluginRepository
  /pluginRepositories
  reporting
outputDirectorytarget/site/outputDirectory
plugins
  plugin
artifactIdmaven-changes-plugin/artifactId
reportSets
  reportSet
reports
  reportchanges-report/report
/reports
  /reportSet

Re: Integration Tests

2008-02-27 Thread Luca Marrocco

2008/2/27, vitor lundberg [EMAIL PROTECTED]:
  I wish that my integration test start after the package steep.
  so if I put my  classes under the same repertory as the tests classes maven
  dont make the differences
  that is a way to make a difference thoses tests ?

i havent tried this feature using maven so i'm sure that i can help
you, i'm sorry. Surfing on internet i have found this article that can
help you to solve your issue
http://adminsight.de/2006/04/04/integration-and-unit-test-strategies-with-maven2/


Luca

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

Re: maven-eclipse-plugin 2.4 versioned projec

Thanks again for the prompt response..

It
is
indeed
as
you
mentioned
finalName.
If
they
don't
want
to
have
final
name
fixed
you
could
probably
somehow
parse
the
ibm-specific
deployment
descriptors.
Because
artifact
names
are
actually
hardcoded
there.
So
if
your
version
changes
-
you
have
a
problem.

Well as far as I have seen, the artificat-id is only buried in the WTP
resources. More specifically, .settings/org.eclipse.wst.common.component.
This file essentially contains the runtime deployment details for the RAD
projects. Additionally, the file used by RAD when exporting an EAR, for
example, and, as in our case, when deploying EAR to WebSphere Unit Test
environment from within RAD in loose-config mode. That's when RAD creates
WORKSPACE/.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR_NAME/looseconfig.xmi
that in turns contains references to the physical location of class files.
And this is when everything gets screwed up.. because looseconfig.xmi is
generated based on .settings/org.eclipse.wst.common.component.

I had been thinking about doing exactly as you suggested, to manipulate
.settings/org.eclipse.wst.common.component once the WTP resources have been
generated. But because of lack of Maven 2 knowledge, couldn't find any way to
execute arbitrary platform-specific (.bat for indows and .sh for *nix) scripts
from maven-eclipse-plugin.

Looking at the code, I see that there is a slight problem.. The right way to
fix it would be to change the code. I hope that the issue will be addressed in
the new 2.5 plugin.

It's
likely
you
will
run
into
many
more
issues.
To
know
which
ones
you
can
see
at
all
the
closed
issues
that
are
scheduled
for
2.5
release.
I
can
tell
you
in
advance
-
if
you
use
webservices
you
will
have
a
problem.

It's
really
easier
just
to
use
2.5-SNAPSHOT
(unless
you
use
release
plugin).

Thanks for the heads up. Luckily, we don't have Web Services.. yet! But we do
intend to implement that. By then I'm hoping that maven-eclipse-plugin 2.5
plugin will be released.

Will speak with our maven team to see if we can use the snapshot code.

Regards
Salman Moghal

Re: What does: Skipping disabled repository central really mean?

Are you sure you have the connectivity to the central repository. I've seen
this message once a connection is attempted against central and it fails:
the repository is then disabled by Maven for further attempts.

Regards
Jeff MAURY

On Wed, Feb 27, 2008 at 6:05 PM, Chris Helck [EMAIL PROTECTED]
wrote:

 Hi,

 A certain user of mine gets Skipping disabled repository central when
 mvn (2.0.8) tries to download a plugin. I've printed the effective-pom
 and effective-settings and I don't see anything redirection of central
 with mirrors or repository.

 It certainly sounds like mvn is not looking in the central repo when it
 tries to download a plugin. But I don't see why it is disabled. Can
 anyone explain? Below is the effective pom and settings:

 
 
 Effective POM for project 'ebs:md_build_instructions:jar:1.0-SNAPSHOT'
 
 
 ?xml version=1.0?project
  parent
artifactIdmd_parent/artifactId
groupIdebs/groupId
version1.4-SNAPSHOT/version
  /parent
  modelVersion4.0.0/modelVersion
  groupIdebs/groupId
  artifactIdmd_build_instructions/artifactId
  namemd_build_instructions/name
  version1.0-SNAPSHOT/version
  urlhttp://www.ebs.com/url

  build

 sourceDirectory/home/cc/perforce/MarketData/build/maven2/build_instruc
 tions/src/main/java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory

 testSourceDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
 tructions/src/test/java/testSourceDirectory

 outputDirectory/home/cc/perforce/MarketData/build/maven2/build_instruc
 tions/target/classes/outputDirectory

 testOutputDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
 tructions/target/test-classes/testOutputDirectory
resources
  resource

 directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
 src/main/resources/directory
  /resource
/resources
testResources
  testResource

 directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
 src/test/resources/directory
  /testResource
/testResources

 directory/home/cc/perforce/MarketData/build/maven2/build_instructions/
 target/directory
finalNamemd_build_instructions-1.0-SNAPSHOT/finalName
plugins
  plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
  source1.5/source
  target1.5/target
/configuration
  /plugin
  plugin
artifactIdmaven-one-plugin/artifactId
version1.2/version
executions
  execution
goals
  goalinstall-maven-one-repository/goal
  goaldeploy-maven-one-repository/goal
/goals
configuration

 remoteRepositoryIdcom.ebs.development.repo/remoteRepositoryId

 remoteRepositoryUrlscp://172.16.12.10/apps/local/apache2/htdocs/maven
 /remoteRepositoryUrl
/configuration
  /execution
/executions
  /plugin
  plugin
artifactIdmaven-site-plugin/artifactId
version2.0-beta-6/version
executions
  execution
idcreate site/id
phasepackage/phase
goals
  goalsite/goal
/goals
  /execution
  execution
iddeploy site/id
phasedeploy/phase
goals
  goaldeploy/goal
/goals
  /execution
/executions
configuration
  localesen/locales
/configuration
  /plugin
  plugin
artifactIdmaven-surefire-plugin/artifactId
version2.4.2/version
configuration
  useFilefalse/useFile
  excludes
exclude**/*ITest.java/exclude
exclude**/Abstract*Test.java/exclude
  /excludes
/configuration
  /plugin
  plugin
artifactIdmaven-help-plugin/artifactId
version2.0.2/version
  /plugin
/plugins
  /build
  repositories
repository
  iddev-legacy/id
  namelegacy/name
  urlhttp://172.16.12.10/maven/url
  layoutlegacy/layout
/repository
repository
  iddev-vendor/id
  namevendor/name
  urlhttp://172.16.12.10/maven2/dev/repo//url
/repository
repository
  iddev-product/id
  nameproducts/name
  urlhttp://172.16.12.10/maven2/dev-product/repo//url
/repository
repository
  snapshots
enabledfalse/enabled
  /snapshots
  idcentral/id
  nameMaven Repository Switchboard/name
  urlhttp://repo1.maven.org/maven2/url
/repository
  /repositories
  pluginRepositories
pluginRepository
  releases
updatePolicynever/updatePolicy
  /releases
  snapshots
enabledfalse/enabled
  /snapshots
  idcentral/id
  nameMaven Plugin Repository/name

Re: Integration Tests

2008-02-27 Thread Paul Benedict

See this posting:
http://mail-archives.apache.org/mod_mbox/maven-users/200801.mbox/[EMAIL 
PROTECTED]

Paul

On Wed, Feb 27, 2008 at 11:06 AM, Luca Marrocco [EMAIL PROTECTED]
wrote:

 2008/2/27, vitor lundberg [EMAIL PROTECTED]:
   I wish that my integration test start after the package steep.
   so if I put my  classes under the same repertory as the tests classes
 maven
   dont make the differences
   that is a way to make a difference thoses tests ?

 i havent tried this feature using maven so i'm sure that i can help
 you, i'm sorry. Surfing on internet i have found this article that can
 help you to solve your issue

 http://adminsight.de/2006/04/04/integration-and-unit-test-strategies-with-maven2/


 Luca

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

Is there any way to control the number of snapshot produced?

2008-02-27 Thread Baz

Hi,

Is there a way that we can control the total number of snapshot of one
specific version? I think I have seen it somewhere and forget about the
syntax.

Thank you.

A.

How to set the classifier of an Artifact for install-plugin ?

2008-02-27 Thread Guillaume Durand


Hello,

I wrote a packaging plugin replacing the jar-plugin and accepting a 
classifier as parameter to generate the proper artifact name. Once the 
artifact is created I use Artifact.setFile with the newly created artifact.
It works fine but the install-plugin copies the artifact into the 
repository without the classifier.

If the package plugin is jar-plugin the classifier is kept though.

How do I set in my plugin the classifier to use for the install-plugin?

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

RE: What does: Skipping disabled repository central really mean?

2008-02-27 Thread Chris Helck

Hi Jeff,

Using a different pom the same user can download from central. Nevertheless, if 
this were the case, how would you correct it?

Regards,
Christopher

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MAURY
Sent: Wednesday, February 27, 2008 12:11 PM
To: Maven Users List
Subject: Re: What does: Skipping disabled repository central really mean?

Are you sure you have the connectivity to the central repository. I've seen 
this message once a connection is attempted against central and it fails:
the repository is then disabled by Maven for further attempts.

Regards
Jeff MAURY

On Wed, Feb 27, 2008 at 6:05 PM, Chris Helck [EMAIL PROTECTED]
wrote:

 Hi,

 A certain user of mine gets Skipping disabled repository central 
 when mvn (2.0.8) tries to download a plugin. I've printed the 
 effective-pom and effective-settings and I don't see anything 
 redirection of central with mirrors or repository.

 It certainly sounds like mvn is not looking in the central repo when 
 it tries to download a plugin. But I don't see why it is disabled. Can 
 anyone explain? Below is the effective pom and settings:

 **
 **
 
 Effective POM for project 'ebs:md_build_instructions:jar:1.0-SNAPSHOT'
 **
 **
 
 ?xml version=1.0?project
  parent
artifactIdmd_parent/artifactId
groupIdebs/groupId
version1.4-SNAPSHOT/version
  /parent
  modelVersion4.0.0/modelVersion
  groupIdebs/groupId
  artifactIdmd_build_instructions/artifactId
  namemd_build_instructions/name
  version1.0-SNAPSHOT/version
  urlhttp://www.ebs.com/url

  build

 sourceDirectory/home/cc/perforce/MarketData/build/maven2/build_instr
 uc
 tions/src/main/java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory

 testSourceDirectory/home/cc/perforce/MarketData/build/maven2/build_i
 ns tructions/src/test/java/testSourceDirectory

 outputDirectory/home/cc/perforce/MarketData/build/maven2/build_instr
 uc tions/target/classes/outputDirectory

 testOutputDirectory/home/cc/perforce/MarketData/build/maven2/build_i
 ns tructions/target/test-classes/testOutputDirectory
resources
  resource

 directory/home/cc/perforce/MarketData/build/maven2/build_instruction
 s/
 src/main/resources/directory
  /resource
/resources
testResources
  testResource

 directory/home/cc/perforce/MarketData/build/maven2/build_instruction
 s/
 src/test/resources/directory
  /testResource
/testResources

 directory/home/cc/perforce/MarketData/build/maven2/build_instruction
 s/
 target/directory
finalNamemd_build_instructions-1.0-SNAPSHOT/finalName
plugins
  plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
  source1.5/source
  target1.5/target
/configuration
  /plugin
  plugin
artifactIdmaven-one-plugin/artifactId
version1.2/version
executions
  execution
goals
  goalinstall-maven-one-repository/goal
  goaldeploy-maven-one-repository/goal
/goals
configuration

 remoteRepositoryIdcom.ebs.development.repo/remoteRepositoryId

 remoteRepositoryUrlscp://172.16.12.10/apps/local/apache2/htdocs/mave
 n
 /remoteRepositoryUrl
/configuration
  /execution
/executions
  /plugin
  plugin
artifactIdmaven-site-plugin/artifactId
version2.0-beta-6/version
executions
  execution
idcreate site/id
phasepackage/phase
goals
  goalsite/goal
/goals
  /execution
  execution
iddeploy site/id
phasedeploy/phase
goals
  goaldeploy/goal
/goals
  /execution
/executions
configuration
  localesen/locales
/configuration
  /plugin
  plugin
artifactIdmaven-surefire-plugin/artifactId
version2.4.2/version
configuration
  useFilefalse/useFile
  excludes
exclude**/*ITest.java/exclude
exclude**/Abstract*Test.java/exclude
  /excludes
/configuration
  /plugin
  plugin
artifactIdmaven-help-plugin/artifactId
version2.0.2/version
  /plugin
/plugins
  /build
  repositories
repository
  iddev-legacy/id
  namelegacy/name
  urlhttp://172.16.12.10/maven/url
  layoutlegacy/layout
/repository
repository
  iddev-vendor/id
  namevendor/name
  urlhttp://172.16.12.10/maven2/dev/repo//url
/repository
repository
  iddev-product/id
  nameproducts/name
  urlhttp://172.16.12.10/maven2/dev-product/repo//url
/repository
repository
  snapshots
enabledfalse/enabled

Re: What does: Skipping disabled repository central really mean?

Are you running on Vista ?

Jeff MAURY


On Wed, Feb 27, 2008 at 6:51 PM, Chris Helck [EMAIL PROTECTED]
wrote:

 Hi Jeff,

 Using a different pom the same user can download from central.
 Nevertheless, if this were the case, how would you correct it?

 Regards,
 Christopher

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff
 MAURY
 Sent: Wednesday, February 27, 2008 12:11 PM
 To: Maven Users List
 Subject: Re: What does: Skipping disabled repository central really
 mean?

 Are you sure you have the connectivity to the central repository. I've
 seen this message once a connection is attempted against central and it
 fails:
 the repository is then disabled by Maven for further attempts.

 Regards
 Jeff MAURY

 On Wed, Feb 27, 2008 at 6:05 PM, Chris Helck [EMAIL PROTECTED]
 wrote:

  Hi,
 
  A certain user of mine gets Skipping disabled repository central
  when mvn (2.0.8) tries to download a plugin. I've printed the
  effective-pom and effective-settings and I don't see anything
  redirection of central with mirrors or repository.
 
  It certainly sounds like mvn is not looking in the central repo when
  it tries to download a plugin. But I don't see why it is disabled. Can
  anyone explain? Below is the effective pom and settings:
 
  **
  **
  
  Effective POM for project 'ebs:md_build_instructions:jar:1.0-SNAPSHOT'
  **
  **
  
  ?xml version=1.0?project
   parent
 artifactIdmd_parent/artifactId
 groupIdebs/groupId
 version1.4-SNAPSHOT/version
   /parent
   modelVersion4.0.0/modelVersion
   groupIdebs/groupId
   artifactIdmd_build_instructions/artifactId
   namemd_build_instructions/name
   version1.0-SNAPSHOT/version
   urlhttp://www.ebs.com/url
 
   build
 
  sourceDirectory/home/cc/perforce/MarketData/build/maven2/build_instr
  uc
  tions/src/main/java/sourceDirectory
 scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
 
  testSourceDirectory/home/cc/perforce/MarketData/build/maven2/build_i
  ns tructions/src/test/java/testSourceDirectory
 
  outputDirectory/home/cc/perforce/MarketData/build/maven2/build_instr
  uc tions/target/classes/outputDirectory
 
  testOutputDirectory/home/cc/perforce/MarketData/build/maven2/build_i
  ns tructions/target/test-classes/testOutputDirectory
 resources
   resource
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instruction
  s/
  src/main/resources/directory
   /resource
 /resources
 testResources
   testResource
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instruction
  s/
  src/test/resources/directory
   /testResource
 /testResources
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instruction
  s/
  target/directory
 finalNamemd_build_instructions-1.0-SNAPSHOT/finalName
 plugins
   plugin
 artifactIdmaven-compiler-plugin/artifactId
 version2.0.2/version
 configuration
   source1.5/source
   target1.5/target
 /configuration
   /plugin
   plugin
 artifactIdmaven-one-plugin/artifactId
 version1.2/version
 executions
   execution
 goals
   goalinstall-maven-one-repository/goal
   goaldeploy-maven-one-repository/goal
 /goals
 configuration
 
  remoteRepositoryIdcom.ebs.development.repo/remoteRepositoryId
 
  remoteRepositoryUrlscp://172.16.12.10/apps/local/apache2/htdocs/mave
  n
  /remoteRepositoryUrl
 /configuration
   /execution
 /executions
   /plugin
   plugin
 artifactIdmaven-site-plugin/artifactId
 version2.0-beta-6/version
 executions
   execution
 idcreate site/id
 phasepackage/phase
 goals
   goalsite/goal
 /goals
   /execution
   execution
 iddeploy site/id
 phasedeploy/phase
 goals
   goaldeploy/goal
 /goals
   /execution
 /executions
 configuration
   localesen/locales
 /configuration
   /plugin
   plugin
 artifactIdmaven-surefire-plugin/artifactId
 version2.4.2/version
 configuration
   useFilefalse/useFile
   excludes
 exclude**/*ITest.java/exclude
 exclude**/Abstract*Test.java/exclude
   /excludes
 /configuration
   /plugin
   plugin
 artifactIdmaven-help-plugin/artifactId
 version2.0.2/version
   /plugin
 /plugins
   /build
   repositories
 repository
   iddev-legacy/id
   namelegacy/name
   urlhttp://172.16.12.10/maven/url
   layoutlegacy/layout
 /repository
 repository
   iddev-vendor/id

RE: What does: Skipping disabled repository central really mean?

2008-02-27 Thread Chris Helck

No, Ubuntu.
-Chris 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff MAURY
Sent: Wednesday, February 27, 2008 12:57 PM
To: Maven Users List
Subject: Re: What does: Skipping disabled repository central really mean?

Are you running on Vista ?

Jeff MAURY


On Wed, Feb 27, 2008 at 6:51 PM, Chris Helck [EMAIL PROTECTED]
wrote:

 Hi Jeff,

 Using a different pom the same user can download from central.
 Nevertheless, if this were the case, how would you correct it?

 Regards,
 Christopher

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
 Jeff MAURY
 Sent: Wednesday, February 27, 2008 12:11 PM
 To: Maven Users List
 Subject: Re: What does: Skipping disabled repository central really 
 mean?

 Are you sure you have the connectivity to the central repository. I've 
 seen this message once a connection is attempted against central and 
 it
 fails:
 the repository is then disabled by Maven for further attempts.

 Regards
 Jeff MAURY

 On Wed, Feb 27, 2008 at 6:05 PM, Chris Helck [EMAIL PROTECTED]
 wrote:

  Hi,
 
  A certain user of mine gets Skipping disabled repository central
  when mvn (2.0.8) tries to download a plugin. I've printed the 
  effective-pom and effective-settings and I don't see anything 
  redirection of central with mirrors or repository.
 
  It certainly sounds like mvn is not looking in the central repo when 
  it tries to download a plugin. But I don't see why it is disabled. 
  Can anyone explain? Below is the effective pom and settings:
 
  
  **
  **
  
  Effective POM for project 'ebs:md_build_instructions:jar:1.0-SNAPSHOT'
  
  **
  **
  
  ?xml version=1.0?project
   parent
 artifactIdmd_parent/artifactId
 groupIdebs/groupId
 version1.4-SNAPSHOT/version
   /parent
   modelVersion4.0.0/modelVersion
   groupIdebs/groupId
   artifactIdmd_build_instructions/artifactId
   namemd_build_instructions/name
   version1.0-SNAPSHOT/version
   urlhttp://www.ebs.com/url
 
   build
 
  sourceDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
  tr
  uc
  tions/src/main/java/sourceDirectory
 scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
 
  testSourceDirectory/home/cc/perforce/MarketData/build/maven2/build
  _i ns tructions/src/test/java/testSourceDirectory
 
  outputDirectory/home/cc/perforce/MarketData/build/maven2/build_ins
  tr uc tions/target/classes/outputDirectory
 
  testOutputDirectory/home/cc/perforce/MarketData/build/maven2/build
  _i ns tructions/target/test-classes/testOutputDirectory
 resources
   resource
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instructi
  on
  s/
  src/main/resources/directory
   /resource
 /resources
 testResources
   testResource
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instructi
  on
  s/
  src/test/resources/directory
   /testResource
 /testResources
 
  directory/home/cc/perforce/MarketData/build/maven2/build_instructi
  on
  s/
  target/directory
 finalNamemd_build_instructions-1.0-SNAPSHOT/finalName
 plugins
   plugin
 artifactIdmaven-compiler-plugin/artifactId
 version2.0.2/version
 configuration
   source1.5/source
   target1.5/target
 /configuration
   /plugin
   plugin
 artifactIdmaven-one-plugin/artifactId
 version1.2/version
 executions
   execution
 goals
   goalinstall-maven-one-repository/goal
   goaldeploy-maven-one-repository/goal
 /goals
 configuration
 
  remoteRepositoryIdcom.ebs.development.repo/remoteRepositoryId
 
  remoteRepositoryUrlscp://172.16.12.10/apps/local/apache2/htdocs/ma
  ve
  n
  /remoteRepositoryUrl
 /configuration
   /execution
 /executions
   /plugin
   plugin
 artifactIdmaven-site-plugin/artifactId
 version2.0-beta-6/version
 executions
   execution
 idcreate site/id
 phasepackage/phase
 goals
   goalsite/goal
 /goals
   /execution
   execution
 iddeploy site/id
 phasedeploy/phase
 goals
   goaldeploy/goal
 /goals
   /execution
 /executions
 configuration
   localesen/locales
 /configuration
   /plugin
   plugin
 artifactIdmaven-surefire-plugin/artifactId
 version2.4.2/version
 configuration
   useFilefalse/useFile
   excludes
 exclude**/*ITest.java/exclude
 exclude**/Abstract*Test.java/exclude
   /excludes
 /configuration
   /plugin
   plugin

Re: Integration Tests

2008-02-27 Thread Kalle Korhonen

plugin
artifactIdmaven-surefire-plugin/artifactId
configuration
includes
include**/*UnitTest.java/include
/includes
/configuration
executions
execution
idsurefire-it/id
phaseintegration-test/phase
configuration
includes
include**/*IntegrationTest.java/include
/includes
/configuration
goals
goaltest/goal
/goals
/execution
/executions
/plugin

Kalle

On Wed, Feb 27, 2008 at 8:59 AM, vitor lundberg [EMAIL PROTECTED]
wrote:

 Thx for replay Luc,

 but the problem is if I create my integration test under src/test/java my
 integration test will starts like a unit test under the lifecyle test
 and
 I wish that my integration test start after the package steep.
 so if I put my  classes under the same repertory as the tests classes
 maven
 dont make the differences
 that is a way to make a difference thoses tests ?

 On Wed, Feb 27, 2008 at 5:47 PM, Luca Marrocco [EMAIL PROTECTED]
 wrote:

  Hi Vitor,
  the simplest way is to create you integration test as junit classes
  under src/test/java directory.
 
 
  Luca
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]

How to list goals which are bound to a particular phase?

2008-02-27 Thread Ian Hummel


Hi everyone,

Is there anyway to list the lifecycle and goals that will be run when  
I do e.g. mvn install  without actually running the install?


Thanks,

- ian.



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

Maven release strategy

2008-02-27 Thread Sebastian Johnck

I am comparing the differences between performing one
release from the top most module, which forces a
release of all child modules, vs releasing one child
module at a time. Which is better?

Can any one recommend some good documentation on maven
release strategies?




  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


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

More than one source folder

2008-02-27 Thread Daniele Dellafiore

Is possible to configure pom to have more than one source folder? How?
And if so, does the eclipse plugin support this?

I am managing a pom for a project with external svn java sources that
are, say, under /vendor/projectX/src
If I specify the external source folder as a resource in pom, eclipse
plugins put that folder in the build path but excludes *.java so it is
of no use and is a workaround.

Thanks.

-- 
Daniele Dellafiore
http://blog.ildella.net/

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

Re: More than one source folder

2008-02-27 Thread Sebastian Johnck

Check out build-helper plugin

Here is how I use it

!--Getting the generated source dir added --
plugin
groupIdorg.codehaus.mojo/groupId

artifactIdbuild-helper-maven-plugin/artifactId
version1.0/version
executions
execution
idadd-source/id
phasegenerate-sources/phase
goals
goaladd-source/goal
/goals
configuration
sources

source${basedir}/target/generated-sources/java/source
/sources
/configuration
/execution
/executions
/plugin
--- Daniele Dellafiore [EMAIL PROTECTED] wrote:

 Is possible to configure pom to have more than one
 source folder? How?
 And if so, does the eclipse plugin support this?
 
 I am managing a pom for a project with external svn
 java sources that
 are, say, under /vendor/projectX/src
 If I specify the external source folder as a
 resource in pom, eclipse
 plugins put that folder in the build path but
 excludes *.java so it is
 of no use and is a workaround.
 
 Thanks.
 
 -- 
 Daniele Dellafiore
 http://blog.ildella.net/
 

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



  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

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

Re: maven-eclipse-plugin 2.4 versioned project

2008-02-27 Thread Arnaud HERITIER

and another task not recorded : to test the plugin with all 2.0.X version to
update the minimum requirement.

Arnaud

On Wed, Feb 27, 2008 at 11:01 AM, Siarhei Dudzin [EMAIL PROTECTED]
wrote:

 I've done quite some troubleshooting around RAD6+maven. I would advise to
 override the finalName for the artifact so it doesn't have version at the
 end.
 It's even better if those match the project directory names.

 maven-eclipse-plugin 2.5-SNAPSHOT has quite a lot of improvements in
 RAD6/7
 support. It is currently only 1 jira issue away from being released.

 Siarhei

 On Wed, Feb 27, 2008 at 9:04 AM, Salman Moghal [EMAIL PROTECTED] wrote:

  I've been pouring through maven-eclipse-plugin 2.4 code and realized
 that
  there is potentially a problem with
 
 org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass
  (line 125), IMHO:
 
 writer.addAttribute( ATTR_DEPLOY_NAME,
  config.getProject().getArtifactId() );
 
  It seems like the code above assumes deploy-name cannot contain version
  numbers, project name templates etc. It would be great if the code could
  follow similar structured approach for setting/getting the project name
 as
  in org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter (line
  169),
  which generates .project file:
 
 writer.writeText( config.getEclipseProjectName() );
 
  Here the project name is set during configuration/dependancy resolution
  phase by org.apache.maven.plugin.eclipse.EclipsePlugin and later used by
  the
  EclipseProjectWriter class.
 
  So I'm curious if this issue could be resolved by simply using
  getEclipseProjectName() method in
 
 org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriterclass
 :
 
 writer.addAttribute( ATTR_DEPLOY_NAME, config.getEclipseProjectName()
  );
 
  Please advise..
 
  --
  Salman Moghal
 
  - Original Message -
  From: Salman Moghal [EMAIL PROTECTED]
  To: users@maven.apache.org
  Sent: Tuesday, February 26, 2008 3:38 PM
  Subject: maven-eclipse-plugin 2.4  versioned projects
 
 
   Hello:
  
   I'm using maven-eclipse-plugin v2.4 to generate WTP 1.5 resource for
   Eclipse 3.2.x / RAD v6.x environment.  The goal of this exercise is to
   take advantage of Eclipse 3.2 /  RAD v6.x
   integrated development, debugging, and hot code deployment features.
   The
   runtime environment is WebSphere Application Server v6.1.  Eclipse /
 RAD
   also have M2Eclipse plugin installed for dependency management, etc.
   There is one slight issue that has me scratching my head for a few
 days.
   It has to do with generated WTP v1.5 files.
  
   Essentially, maven eclipse plugin goal eclipse:m2eclipse generates
 all
   WTP 1.5 files correctly.  However, once
   addVersionToProjectNametrue/addVersionToProjectName is added to
  plugin
   config,  .settings/org.eclipse.wst.common.component contains an
  incorrect
   entry.  The goal generates the .project WTP file properly with a
 project
   name containing the POM version number, but the corresponding
   .settings/org.eclipse.wst.common.component contains an incorrect value
  for
   wb-module deploy-name=..  The value of deploy-name=  does not
   contain a POM version number along with the project name.
  
   The reason why having a version number in wb-module deploy-name=
 entry
  is
   important is because if the EAR / WAR module is deployed to WebSphere
   runtime in loose configuration mode, the runtime complains about not
   being able to locate corresponding modules.  Loose configuration
 allows
   the class files to reside in Eclipse / RAD workspace and speeds up the
  EAR
   deployment process many folds since no real EAR is generated and
  installed
   into WebSphere.  Eclipse / RAD loose config file is located under
  
 
 WORKSPACE/.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR
   NAME/looseconfig.xmi.
  
   Note that if I manually make the change to the generated
   .settings/org.eclipse.wst.common.component file by adding version
 number
   along with the project name, the runtime doesn't complain and
 everything
   works well in loose configuration mode.
  
   May be I'm missing something in maven-eclipse-plugin configuration.
  Here's
   what I have:
  
   !-- maven-eclipse-plugin config for generating WTP 1.5 resources for
  WAR
   and EARs --
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-eclipse-plugin/artifactId
  
 configuration
   manifest
 ${basedir}/src/main/resources/META-INF/MANIFEST.MF
   /manifest
  
   addVersionToProjectNametrue/addVersionToProjectName
   useProjectReferencesfalse/useProjectReferences
  
   wtpmanifesttrue/wtpmanifest
   wtpapplicationxmltrue/wtpapplicationxml
   wtpversion1.5/wtpversion
  
   additionalBuildcommands
  
   buildcommandcom.ibm.etools.common.migration.MigrationBuilder
  /buildcommand
   buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand

Re: maven-eclipse-plugin 2.4 versioned project