Re: [m2] scm:checkout
If I understand this right the scm plugin will not read the connection tag in the pom.xml and requires a system variable to be defined to point it to the source repository. How do I use this feature in a multiproject environment, where each child project is a different module in the same source repository. Will it read other information such as the 'tag' element from the pom.xml. Thanks Sid --- Emmanuel Venisse [EMAIL PROTECTED] wrote: yes, it's a pb I just see, you need to add your password to the scm connection m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid:my-password@my.cvs.server.com:my-cvs-repository:my-module Emmanuel [EMAIL PROTECTED] wrote: Thanks for the tip, Emmanual I run the scm:checkout with the system property defined, as follows: cvs login my password m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receive the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [scm:checkout] [INFO] [INFO] [scm:checkout] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Cannot run checkout command : [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Cannot run checkout command : at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:77) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:497) at org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:201) at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:160) at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:65) ... 16 more Caused by: org.apache.maven.scm.ScmException: password is required at org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:94) at org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57) at org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) ... 20 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu Sep 15 07:06:46 PDT 2005 [INFO] Final Memory: 2M/4M [INFO] It doesn't seem to be recognizing my 'cvs login' state/information. Is there anonther system property I should be setting? Thanks for any help! John -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Thursday, September 15, 2005 12:23 AM To: Maven Users List Subject: Re: [m2] scm:checkout checkout mojo don't look at scmConnection in pom.
Customn dependency scopes
Hi, I've set up a simple web-app (war) project with Maven 2. Now I need to place some artifacts from my repository (a few jar's accessed by JNLP) in the root of the war. Just declaring them as dependencies puts them in the WEB-INF/lib directory. Is it possible to define a new kind of dependency scope (for example 'client') and then copy the artifacts in the 'package' goal to the right location? Thanks Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] source:jar, phase-binding, and build numbers
Hi all, I have a project built using m2. I want the project to install/deploy a source-code JAR along with the binaries JAR (on both the install and deploy phases). I've added the following section in the pom.xml file: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution goals goaljar/goal /goals /execution /executions /plugin /plugins /build It works very nice, except for one problem: the sources JAR always gets a new build number. For instance, assuming I clean my local repo, and then run m2 install, the local repo will contain: myproject-20050925.155953-1.jar myproject-20050925.155953-2-sources.jar Shouldn't they have the same build number? This causes a problem because the maven-metadata.xml file specifies that the current build number is 2, and so, projects depending on that project can't find the file (since there's no binary JAR for build number 2, only for build 1). Am I doing something wrong? Thanks, Arik. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Unable to Deploy via SCP with Maven 2 Beta 1
It's probably something in my environment, as I've deployed successfully at work. I'm trying to set things up to work at home on my own network, and I can't get a deploy of a POM to work via SCP. I'm running Maven 2 on Windows XP. The server I'm trying to copy files to is a Debian linux box. I can SSH to it with the username and password in my settings.xml file using Putty and Cygwin. I can copy files using WinSCP. I can copy a file using scp in Cygwin. I'm not sure how else to troubleshoot from here. I know my settings.xml file is being read, because if I get rid of the password, the error changes to tell me that I have to provide a private key. Here's the details: DistributionManagement section of my pom: distributionManagement repository idinternal/id nameInternal Respository/name urlscp://192.168.0.101/home/maven2/url /repository /distributionManagement My settings.xml: settings servers server idinternal/id usernamemaven2/username passwordpassword/password /server /servers /settings Error message: [INFO] [deploy:deploy] [INFO] Retrieving previous build number from internal [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Error deploying artifact [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error deploying artifact at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:154) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:45 2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:438) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:302) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:89) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:138) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to retrieve metadata at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositor yMetadataManager.java:212) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositor yMetadataManager.java:183) at org.apache.maven.artifact.transform.SnapshotTransformation.resolveLatestSnapshotBuildNumber(SnapshotTransform ation.java:130) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForDeployment(SnapshotTransformation.java :75) at org.apache.maven.artifact.transform.DefaultArtifactTransformationManager.transformForDeployment(DefaultArtifa ctTransformationManager.java:58) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:62) ... 17 more Caused by: org.apache.maven.wagon.TransferFailedException: Authentication failed: at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:401) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:256) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositor yMetadataManager.java:198)
[m2] Archetype Plugin problem generating Mojo type project (beta-1)
Hi, I created a plugin skeleton using the following command: m2 archetype:create -DgroupId=com.mycompany.app -DartifactId=my-plugin -DarchetypeArtifactId=maven-archetype-mojo When I try to install the plugin, M2 gives me this error: $ m2 install [INFO] - --- [INFO] Building Maven Mojo Archetype [INFO] task-segment: [install] [INFO] - --- [INFO] [plugin:descriptor] [INFO] [resources:resources] [WARNING] * Using defaults for missing POM org.apache.maven:maven-plugin-api:pom:2.0 -beta-1-SNAPSHOT * [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Main Error: Unable to download the artifact from any repository org.apache.maven:maven-plugin-api:2.0-beta-1-SNAPSHOT:jar from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) com.mycompany.app:my-plugin:maven-plugin:1.0-SNAPSHOT 2) org.apache.maven:maven-plugin-api:jar:2.0-beta-1-SNAPSHOT Root error: Unable to download the artifact from any repository [INFO] - --- [INFO] Total time: 5 seconds [INFO] Finished at: Sun Sep 25 13:49:00 EDT 2005 [INFO] Final Memory: 3M/6M [INFO] - --- So I look at the generated pom.xml and I found this: dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0-beta-1-SNAPSHOT/version /dependency If I remove -SNAPSHOT, the build completes successfully. Is this a bug? Thanks, Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] jar artifact with par extension
Hi all,
I'm having the same problem - what is the best solution for this use case?
On 9/14/05, Piotr Bzdyl [EMAIL PROTECTED] wrote:
Hello,
(I was writing to this mailing list before partially about this problem:
Demo application based on JBoss DVD trailblaizer)
I tried to create following project:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdnet.bzdyl.demo/groupId
artifactIddemo/artifactId
version1.0-SNAPSHOT/version
/parent
groupIdnet.bzdyl.demo/groupId
artifactIddemo-par/artifactId
packagingjar/packaging
dependencies
dependency
groupIdjavax.persistence/groupId
artifactIdejb/artifactId
version3.0-public_review/version
scopecompile/scope
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
finalNameExtpar/finalNameExt
/configuration
/plugin
/plugins
/build
/project
To make this project work I patched maven-jar-plugin adding finalNameExt
property (I submitted patch to MNG-699).
m2 package works fine and generates demo-par-{version}.par in the target
directory. But m2 install doesn't work because it tries to copy
target/demo-par-{version}.jar instead of par. Is that mean that I should
create separate plugin (ie. maven-par-plugin) and add new packaging type
(to the maven-core I guess)?
I have the same problem in another project where I set packaging to jar
and finalNameExt to ejb3.
Best regards,
Piotrek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] properties
Hi John,
Don't know if it's a bug but
properties
m2.version2.0-beta-2-SNAPSHOT/m2.version
/properties
.
version${m2.version}/version
does NOT work.
But, without the . in the property name, it does work. I.e.
properties
m2version2.0-beta-2-SNAPSHOT/m2version
/properties
.
version${m2version}/version
This works.
Cheers,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] properties
I guess a lot of people are going to want to use dotted properties, so
we should support it.
It probably is attempting to do reflection on m2.
- Brett
On 9/26/05, Chris Berry [EMAIL PROTECTED] wrote:
Hi John,
Don't know if it's a bug but
properties
m2.version2.0-beta-2-SNAPSHOT/m2.version
/properties
.
version${m2.version}/version
does NOT work.
But, without the . in the property name, it does work. I.e.
properties
m2version2.0-beta-2-SNAPSHOT/m2version
/properties
.
version${m2version}/version
This works.
Cheers,
-- Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] source:jar, phase-binding, and build numbers
It's a bug, please put it in JIRA. - Brett On 9/26/05, Arik Kfir [EMAIL PROTECTED] wrote: Hi all, I have a project built using m2. I want the project to install/deploy a source-code JAR along with the binaries JAR (on both the install and deploy phases). I've added the following section in the pom.xml file: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-source-plugin/artifactId executions execution goals goaljar/goal /goals /execution /executions /plugin /plugins /build It works very nice, except for one problem: the sources JAR always gets a new build number. For instance, assuming I clean my local repo, and then run m2 install, the local repo will contain: myproject-20050925.155953-1.jar myproject-20050925.155953-2-sources.jar Shouldn't they have the same build number? This causes a problem because the maven-metadata.xml file specifies that the current build number is 2, and so, projects depending on that project can't find the file (since there's no binary JAR for build number 2, only for build 1). Am I doing something wrong? Thanks, Arik. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Unable to Deploy via SCP with Maven 2 Beta 1
We've seen this with a couple of people using passwords, though it works for me. It's possibly the server settings not allowing a password based login. Auth fail means it connected, but did not authenticate. I'm not sure if we can get jsch to log any more, so the best way to debug is probably to check the ssh server logs if you can. It will indicate what you attempted. - Brett On 9/26/05, Stephen Duncan [EMAIL PROTECTED] wrote: It's probably something in my environment, as I've deployed successfully at work. I'm trying to set things up to work at home on my own network, and I can't get a deploy of a POM to work via SCP. I'm running Maven 2 on Windows XP. The server I'm trying to copy files to is a Debian linux box. I can SSH to it with the username and password in my settings.xml file using Putty and Cygwin. I can copy files using WinSCP. I can copy a file using scp in Cygwin. I'm not sure how else to troubleshoot from here. I know my settings.xml file is being read, because if I get rid of the password, the error changes to tell me that I have to provide a private key. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customn dependency scopes
Scope is a default for the packaging rule, not a packaging rule in itself. There is an open JIRA for the war plugin to allow this (specifically for applets and jnlp). It has not yet been implemented. You can work around it by writing your own small plugin (or use the antrun plugin), to copy the jar into place in an earlier phase. Cheers, Brett On 9/25/05, Tim Kettler [EMAIL PROTECTED] wrote: Hi, I've set up a simple web-app (war) project with Maven 2. Now I need to place some artifacts from my repository (a few jar's accessed by JNLP) in the root of the war. Just declaring them as dependencies puts them in the WEB-INF/lib directory. Is it possible to define a new kind of dependency scope (for example 'client') and then copy the artifacts in the 'package' goal to the right location? Thanks Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] scm:checkout
checkout is meant to be used when you don't have the project already. - Brett On 9/25/05, Sidart Kurias [EMAIL PROTECTED] wrote: If I understand this right the scm plugin will not read the connection tag in the pom.xml and requires a system variable to be defined to point it to the source repository. How do I use this feature in a multiproject environment, where each child project is a different module in the same source repository. Will it read other information such as the 'tag' element from the pom.xml. Thanks Sid --- Emmanuel Venisse [EMAIL PROTECTED] wrote: yes, it's a pb I just see, you need to add your password to the scm connection m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid:my-password@my.cvs.server.com:my-cvs-repository:my-module Emmanuel [EMAIL PROTECTED] wrote: Thanks for the tip, Emmanual I run the scm:checkout with the system property defined, as follows: cvs login my password m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receive the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [scm:checkout] [INFO] [INFO] [scm:checkout] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Cannot run checkout command : [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Cannot run checkout command : at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:77) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:497) at org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:201) at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:160) at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:65) ... 16 more Caused by: org.apache.maven.scm.ScmException: password is required at org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:94) at org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57) at org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) ... 20 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu Sep 15 07:06:46 PDT 2005 [INFO] Final Memory: 2M/4M [INFO] It doesn't seem to be recognizing my 'cvs login' state/information. Is there anonther system property I should be setting?
Re: [m2] Archetype Plugin problem generating Mojo type project (beta-1)
Yes. Can you file it in JIRA? Thanks, Brett On 9/26/05, Eric Jacob [EMAIL PROTECTED] wrote: Hi, I created a plugin skeleton using the following command: m2 archetype:create -DgroupId=com.mycompany.app -DartifactId=my-plugin -DarchetypeArtifactId=maven-archetype-mojo When I try to install the plugin, M2 gives me this error: $ m2 install [INFO] - --- [INFO] Building Maven Mojo Archetype [INFO] task-segment: [install] [INFO] - --- [INFO] [plugin:descriptor] [INFO] [resources:resources] [WARNING] * Using defaults for missing POM org.apache.maven:maven-plugin-api:pom:2.0 -beta-1-SNAPSHOT * [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Main Error: Unable to download the artifact from any repository org.apache.maven:maven-plugin-api:2.0-beta-1-SNAPSHOT:jar from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) com.mycompany.app:my-plugin:maven-plugin:1.0-SNAPSHOT 2) org.apache.maven:maven-plugin-api:jar:2.0-beta-1-SNAPSHOT Root error: Unable to download the artifact from any repository [INFO] - --- [INFO] Total time: 5 seconds [INFO] Finished at: Sun Sep 25 13:49:00 EDT 2005 [INFO] Final Memory: 3M/6M [INFO] - --- So I look at the generated pom.xml and I found this: dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0-beta-1-SNAPSHOT/version /dependency If I remove -SNAPSHOT, the build completes successfully. Is this a bug? Thanks, Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1 or 2] Odd project structure... how much pain will this be?
Brett Porter wrote:
Is it worthwhile publishing a few documents that show how various
project types would be set up for m2, like this?
- Brett
On 9/24/05, Kenney Westerhof [EMAIL PROTECTED] wrote:
On Fri, 23 Sep 2005, Eric Biesterfeld wrote:
You're pretty much set up for maven use, except for the 'overlay' system.
I'll demonstrate using maven2.
I see:
/base/pom.xml - base project
/base/client/pom.xml - grouping project for all clients, has parent ../pom.xml
/base/client/X/pom.xml - project for client X, has parent ../pom.xml
As you compile the client/a/java/* to the base/target/ I expect those
classes don't 'overlay' existing ones, because your build will break - the
base classes are always newer than the client/a sourcefiles.
So now you get 1 + count(clients) jars. For each client, that's 2 jars. If
you can live with that, then so far it's easy. If not, you can add
an 'assembly' goal to each client/a/pom.xml (ofcourse configuration
specified in client/pom.xml) to merge the two jars.
Btw, each client/a/pom.xml has a dependency on base/pom.xml.
For the property/html overlay: the property part (which is probably
going to end up in a jar /META-INF/ somewhere?) the assembly plugin
and/or the resources plugin could take care of that.
You need to use the unpack goal to unpack the base dependency
into client/a/target/classes/ (${project.build.outputDirectory}
(or another location if they shouldn't end up in the jar).
This goal is bound to the 'generate-resources' lifecycle phase.
Then maven2 will copy your client a's resources to the same location,
overwriting the other ones.
Or you could just specify a resources section in the client a pom
that has '../../html' in it. Be sure to specify that section
before the resources section that defines the client a resources.
That order will have the effect of client a's resources overwriting
the existing ones.
But it would ofcourse be best to have disjunct sets of resources
for base and the client projects, so that the client projects just 'add'
to the base project, not change it's behavior.
Maybe you can factor out the common features in the client projects,
and make projects for each of those features.
Then each client project just depends on the features that are appropriate
for that client. But it's probable that this won't work in your particular
case.
So, here are some ideas. Hope it helps!
I've worked at a number of shops that followed development practices similar to these, where they had base project contents and by customer customizations.
So, yes, I think that publishing documents, or even full or partial project mockups that demonstrated various strategies for the configuration of M2 projects would be really helpful to people. And a a feature of Maven Evangelism I believe that this would be particularly useful for teams that are interested in computing the price of migrating projects/project families from existing build systems to Maven.
And if the Maven use-case files were updated and kept in sync with the
examples, that would be even better.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven multi-source directory ?
Marouane Amraoui wrote: there is way to specify multi source directory in maven project : example my source files : 1.frwk1/src/java 2.frwk2/src/java i want make only one project maven and only one artifact frwk.jar that containe both source frwk1 and frwk2. Hi, I take it that you are using Maven 1.X.X, yes? I'm not clear where your project.xml file is, but if you've declared 1 location as the sourceDirectory/sourceDirectory you can use syntax something like this: preGoal name=java:compile path id=additional.src.path pathelement location=src/resources/ pathelement location=target/java/ /path maven:addPath id=maven.compile.src.set refid=additional.src.path/ /preGoal You create a path which contains any src directory trees that you want to add and then you add that path to the existing maven.compile.src.set specification. Hope that this helps. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Archetype Plugin problem generating Mojo type project (beta-1)
Brett Porter wrote: Yes. Can you file it in JIRA? Thanks, Brett On 9/26/05, Eric Jacob [EMAIL PROTECTED] wrote: Hi, I created a plugin skeleton using the following command: m2 archetype:create -DgroupId=com.mycompany.app -DartifactId=my-plugin -DarchetypeArtifactId=maven-archetype-mojo When I try to install the plugin, M2 gives me this error: $ m2 install [INFO] - --- [INFO] Building Maven Mojo Archetype [INFO] task-segment: [install] [INFO] - --- [INFO] [plugin:descriptor] [INFO] [resources:resources] [WARNING] * Using defaults for missing POM org.apache.maven:maven-plugin-api:pom:2.0 -beta-1-SNAPSHOT * [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Main Error: Unable to download the artifact from any repository org.apache.maven:maven-plugin-api:2.0-beta-1-SNAPSHOT:jar from the specified remote repositories: central (http://repo1.maven.org/maven2) Path to dependency: 1) com.mycompany.app:my-plugin:maven-plugin:1.0-SNAPSHOT 2) org.apache.maven:maven-plugin-api:jar:2.0-beta-1-SNAPSHOT Root error: Unable to download the artifact from any repository [INFO] - --- [INFO] Total time: 5 seconds [INFO] Finished at: Sun Sep 25 13:49:00 EDT 2005 [INFO] Final Memory: 3M/6M [INFO] - --- So I look at the generated pom.xml and I found this: dependency groupIdorg.apache.maven/groupId artifactIdmaven-plugin-api/artifactId version2.0-beta-1-SNAPSHOT/version /dependency If I remove -SNAPSHOT, the build completes successfully. Is this a bug? Thanks, Eric - 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] Done! Bug #:* *MNG-1016 Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
using maven.test.skip
Hi, all,
I have written a custom plugin for a in-house project which will produce a
ear file at the end.
There is a number of goals defined in this plugin. One of these is:
goal name=projecct:ear-build description=Invokes ejb:install and
war:install goal
j:set var=maven.test.skip value=false/
ant:echo{maven.test.skip} is set to ${maven.test.skip}/ant:echo
attainGoal name=ejb:install/
j:if test=${maven.test.failure}
fail message=There were test failures!/
/j:if
j:set var=maven.test.skip value=true/
ant:echo{maven.test.skip} is set to ${maven.test.skip}/ant:echo
attainGoal name=war:install/
j:set var=maven.test.skip value=false/
/goal
Basically i want to skip the junit test in war:install (ejb:install will
invoke the junit test). However the trick does not work. The junit test in
war:install is not skipped, even though from ant:echo I can see it is set to
true. Any suggestion to how to debug/solve this problem?
Cheers,
AK
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: using maven.test.skip
Anthony Kong wrote:
Hi, all,
I have written a custom plugin for a in-house project which will produce a
ear file at the end.
There is a number of goals defined in this plugin. One of these is:
goal name=projecct:ear-build description=Invokes ejb:install and
war:install goal
j:set var=maven.test.skip value=false/
ant:echo{maven.test.skip} is set to ${maven.test.skip}/ant:echo
attainGoal name=ejb:install/
j:if test=${maven.test.failure}
fail message=There were test failures!/
/j:if
j:set var=maven.test.skip value=true/
ant:echo{maven.test.skip} is set to ${maven.test.skip}/ant:echo
attainGoal name=war:install/
j:set var=maven.test.skip value=false/
/goal
Basically i want to skip the junit test in war:install (ejb:install will
invoke the junit test). However the trick does not work. The junit test in
war:install is not skipped, even though from ant:echo I can see it is set to
true. Any suggestion to how to debug/solve this problem?
You might want to try the following:
preGoal name=ejb:install
j:set var=maven.test.skip.value value=false/
/preGoal
preGoal name=war:install
j:set var=maven.test.skip.value value=true/
/preGoal
preGoal name=test:test
maven:set plugin=maven-test-plugin var=maven.test.skip
value=${maven.test.skip.value}/
/preGoal
The reason that I would recommend this strategy is as follows:
1) you cannot rely upon a single setting of maven.test.skip.
2) because your effort to set the value of maven.test.skip before executing war:install
isn't working, I think that you'll have better results if you inject the
value of maven.test.skip into the maven-test-plugin
3) to do that maven:set is the preferred method, and the way that this set of
code ought to work is that you should be able to explicitly set the value of
maven.test.skip in the test plugin as you execute it
If this doesn't work, please try the following modification to the j:set var
tags:
j:set var=maven.test.skip.value value={appropriate value} scope=parent/
and if that doesn't work, feel free to report the fact and we can try to debug
whatever it is that is going on.
Hope that this helps.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Unable to Deploy via SCP with Maven 2 Beta 1
For the record, this was because plain text passwords were not enabled on the server (different to keyboard-interactive). - Brett On 9/26/05, Brett Porter [EMAIL PROTECTED] wrote: We've seen this with a couple of people using passwords, though it works for me. It's possibly the server settings not allowing a password based login. Auth fail means it connected, but did not authenticate. I'm not sure if we can get jsch to log any more, so the best way to debug is probably to check the ssh server logs if you can. It will indicate what you attempted. - Brett On 9/26/05, Stephen Duncan [EMAIL PROTECTED] wrote: It's probably something in my environment, as I've deployed successfully at work. I'm trying to set things up to work at home on my own network, and I can't get a deploy of a POM to work via SCP. I'm running Maven 2 on Windows XP. The server I'm trying to copy files to is a Debian linux box. I can SSH to it with the username and password in my settings.xml file using Putty and Cygwin. I can copy files using WinSCP. I can copy a file using scp in Cygwin. I'm not sure how else to troubleshoot from here. I know my settings.xml file is being read, because if I get rid of the password, the error changes to tell me that I have to provide a private key. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] scm:checkout
I have the projects in CVS. I want to start building them with Maven. But for the first time, I would need to check the projects out individually, and not use the multiproject capabilities to get the sources from cvs. Updates can use the multiproject capabilities. Is that 'use case' correct. Thanks Sid --- Brett Porter [EMAIL PROTECTED] wrote: checkout is meant to be used when you don't have the project already. - Brett On 9/25/05, Sidart Kurias [EMAIL PROTECTED] wrote: If I understand this right the scm plugin will not read the connection tag in the pom.xml and requires a system variable to be defined to point it to the source repository. How do I use this feature in a multiproject environment, where each child project is a different module in the same source repository. Will it read other information such as the 'tag' element from the pom.xml. Thanks Sid --- Emmanuel Venisse [EMAIL PROTECTED] wrote: yes, it's a pb I just see, you need to add your password to the scm connection m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid:my-password@my.cvs.server.com:my-cvs-repository:my-module Emmanuel [EMAIL PROTECTED] wrote: Thanks for the tip, Emmanual I run the scm:checkout with the system property defined, as follows: cvs login my password m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receive the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [scm:checkout] [INFO] [INFO] [scm:checkout] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Cannot run checkout command : [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Cannot run checkout command : at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:77) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:497) at org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:201) at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:160) at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:65) ... 16 more Caused by: org.apache.maven.scm.ScmException: password is required at org.apache.maven.scm.provider.cvslib.command.login.CvsPass.execute(CvsPass.java:94) at org.apache.maven.scm.provider.cvslib.command.login.CvsLoginCommand.executeLoginCommand(CvsLoginCommand.java:57) at org.apache.maven.scm.login.AbstractLoginCommand.executeCommand(AbstractLoginCommand.java:44)
Re: [m2] scm:checkout
If you have a multiproject hierachy, then currently Maven requires that they be in the same tree, so the first checkout would be the root of that (likewise for an update). - Brett On 9/26/05, Sidart Kurias [EMAIL PROTECTED] wrote: I have the projects in CVS. I want to start building them with Maven. But for the first time, I would need to check the projects out individually, and not use the multiproject capabilities to get the sources from cvs. Updates can use the multiproject capabilities. Is that 'use case' correct. Thanks Sid --- Brett Porter [EMAIL PROTECTED] wrote: checkout is meant to be used when you don't have the project already. - Brett On 9/25/05, Sidart Kurias [EMAIL PROTECTED] wrote: If I understand this right the scm plugin will not read the connection tag in the pom.xml and requires a system variable to be defined to point it to the source repository. How do I use this feature in a multiproject environment, where each child project is a different module in the same source repository. Will it read other information such as the 'tag' element from the pom.xml. Thanks Sid --- Emmanuel Venisse [EMAIL PROTECTED] wrote: yes, it's a pb I just see, you need to add your password to the scm connection m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid:my-password@my.cvs.server.com:my-cvs-repository:my-module Emmanuel [EMAIL PROTECTED] wrote: Thanks for the tip, Emmanual I run the scm:checkout with the system property defined, as follows: cvs login my password m2 scm:checkout -DconnectionUrl=scm:cvs:pserver:my-userid@my.cvs.server.com:my-cvs-repository:my-module and receive the following response: [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [scm:checkout] [INFO] [INFO] [scm:checkout] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Cannot run checkout command : [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Cannot run checkout command : at org.apache.maven.scm.plugin.CheckoutMojo.execute(CheckoutMojo.java:77) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) at org.apache.maven.cli.MavenCli.main(MavenCli.java:316) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.cvslib.CvsScmProvider.login(CvsScmProvider.java:497) at org.apache.maven.scm.provider.AbstractScmProvider.login(AbstractScmProvider.java:201) at org.apache.maven.scm.provider.AbstractScmProvider.checkOut(AbstractScmProvider.java:160) at
