Re: SCM tag 1.5.
thanks a lot for your prompt help. regards, sanjay On 7/31/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Not presently. You can use the command to do this until we > have one built in. > > - Brett > > On 8/1/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > > Is there a way to do cvs rtag, w/o checkout the whole project? > > This is what I plan to do > > 1. In the build script , tag a project at 11:00 PM > > 2. Checkout project for a tag. > > 3. Build it >
Re: SCM tag 1.5.
Not presently. You can use the command to do this until we have one built in. - Brett On 8/1/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > Is there a way to do cvs rtag, w/o checkout the whole project? > This is what I plan to do > 1. In the build script , tag a project at 11:00 PM > 2. Checkout project for a tag. > 3. Build it - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: SCM tag 1.5.
-- Forwarded message -- From: Sanjay Choudhary <[EMAIL PROTECTED]> Date: Jul 31, 2005 11:01 PM Subject: Re: SCM tag 1.5. To: Brett Porter <[EMAIL PROTECTED]> Is there a way to do cvs rtag, w/o checkout the whole project? This is what I plan to do 1. In the build script , tag a project at 11:00 PM 2. Checkout project for a tag. 3. Build it Sanjay On 7/31/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > > perfect, works like a charm :-) > I was trying maven.scm.sticky.tag. > Sanjay > > On 7/31/05, Brett Porter <[EMAIL PROTECTED] > wrote: > > > > The URL stays the same, but you need to specify maven.scm.tag. > > > > Cheers > > Brett > > > > On 8/1/05, Sanjay Choudhary < [EMAIL PROTECTED]> wrote: > > > My mistake, I didn't specify the repository path. Darn.!! > > > > > > what should be the URL to checkout something out of the branch? I > > tried > > > various combinations but none worked :-( > > > > > > Thanks, > > > Sanjay > > > > > > > > > > > > On 7/31/05, Brett Porter < [EMAIL PROTECTED]> wrote: > > > > It appears the connection it is using is > > > > > > > scm:cvs:pserver:[EMAIL PROTECTED]:commonearproject > > > > > > > > This is invalid (after the hostname, you need to rest of the root, > > > > then : and then the module, here you just have the module) > > > > > > > > It is probably being picked up from the project.xml in the current > > > > directory - this command is designed to run when there is no project > > > > > > in the current directory. > > > > > > > > To set the password, you should manually do a "cvs login" command > > > > outside of maven first. > > > > > > > > - Brett > > > > > > > > On 8/1/05, Sanjay Choudhary < [EMAIL PROTECTED]> wrote: > > > > > Hi All, > > > > > My configuration details are as below > > > > > 1. Maven SCM Plug In 1.5 > > > > > 2. Source Control Repository CVS > > > > > I am doing something very simple, that is checkout a project from > > a cvs > > > > > repository. Command is as below:- > > > > > maven scm:bootstrap - > > > > > > > > Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED] > > > > > :NAOL_Conversion_2_NKP_R5/CodeTableEJB > > > > > NAOL_Conversion_2_NKP_R5 is branch name and CodeTableEJB is the > > project > > > > > name. > > > > > I get the error > > > > > > > > > > build:start: > > > > > > > > > > scm:find-connection: > > > > > [echo] Using connection: > > > scm:cvs:pserver:[EMAIL PROTECTED] > > > > > :commonearproject > > > > > > > > > > scm:checkout: > > > > > [echo] Checking out > > > scm:cvs:pserver:[EMAIL PROTECTED] > > > > > :commonearproject > > > > > > > > > > BUILD FAILED > > > > > File.. C:\Documents and > > > Settings\choudhsa\.maven\cache\maven- > > > > > scm-plugin-1.5\plugin.jelly > > > > > Element... scm:checkout > > > > > Line.. 110 > > > > > Column 233 > > > > > The scm url is invalid. > > > > > Total time: 4 seconds > > > > > Finished at: Sun Jul 31 19:43:24 PDT 2005 > > > > > What is it I am doing wrong? > > > > > How can I specify my cvs password? (other than setting it in > > properties > > > > > file). As you can see, I am using pserver and not ssh. > > > > > Please advice. > > > > > Thanks, > > > > > Sanjay > > > > > > > > > > > > > > > > > > > > > > > >
Re: SCM tag 1.5.
The URL stays the same, but you need to specify maven.scm.tag. Cheers Brett On 8/1/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > My mistake, I didn't specify the repository path. Darn.!! > > what should be the URL to checkout something out of the branch? I tried > various combinations but none worked :-( > > Thanks, > Sanjay > > > > On 7/31/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > It appears the connection it is using is > > > scm:cvs:pserver:[EMAIL PROTECTED]:commonearproject > > > > This is invalid (after the hostname, you need to rest of the root, > > then : and then the module, here you just have the module) > > > > It is probably being picked up from the project.xml in the current > > directory - this command is designed to run when there is no project > > in the current directory. > > > > To set the password, you should manually do a "cvs login" command > > outside of maven first. > > > > - Brett > > > > On 8/1/05, Sanjay Choudhary < [EMAIL PROTECTED]> wrote: > > > Hi All, > > > My configuration details are as below > > > 1. Maven SCM Plug In 1.5 > > > 2. Source Control Repository CVS > > > I am doing something very simple, that is checkout a project from a cvs > > > repository. Command is as below:- > > > maven scm:bootstrap - > > > > Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED] > > > :NAOL_Conversion_2_NKP_R5/CodeTableEJB > > > NAOL_Conversion_2_NKP_R5 is branch name and CodeTableEJB is the project > > > name. > > > I get the error > > > > > > build:start: > > > > > > scm:find-connection: > > > [echo] Using connection: > scm:cvs:pserver:[EMAIL PROTECTED] > > > :commonearproject > > > > > > scm:checkout: > > > [echo] Checking out > scm:cvs:pserver:[EMAIL PROTECTED] > > > :commonearproject > > > > > > BUILD FAILED > > > File.. C:\Documents and > Settings\choudhsa\.maven\cache\maven- > > > scm-plugin-1.5\plugin.jelly > > > Element... scm:checkout > > > Line.. 110 > > > Column 233 > > > The scm url is invalid. > > > Total time: 4 seconds > > > Finished at: Sun Jul 31 19:43:24 PDT 2005 > > > What is it I am doing wrong? > > > How can I specify my cvs password? (other than setting it in properties > > > file). As you can see, I am using pserver and not ssh. > > > Please advice. > > > Thanks, > > > Sanjay > > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCM tag 1.5.
My mistake, I didn't specify the repository path. Darn.!! what should be the URL to checkout something out of the branch? I tried various combinations but none worked :-( Thanks, Sanjay On 7/31/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > It appears the connection it is using is > scm:cvs:pserver:[EMAIL PROTECTED]:commonearproject > > This is invalid (after the hostname, you need to rest of the root, > then : and then the module, here you just have the module) > > It is probably being picked up from the project.xml in the current > directory - this command is designed to run when there is no project > in the current directory. > > To set the password, you should manually do a "cvs login" command > outside of maven first. > > - Brett > > On 8/1/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > > Hi All, > > My configuration details are as below > > 1. Maven SCM Plug In 1.5 > > 2. Source Control Repository CVS > > I am doing something very simple, that is checkout a project from a cvs > > repository. Command is as below:- > > maven scm:bootstrap - > > Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED] > > :NAOL_Conversion_2_NKP_R5/CodeTableEJB > > NAOL_Conversion_2_NKP_R5 is branch name and CodeTableEJB is the project > > name. > > I get the error > > > > build:start: > > > > scm:find-connection: > > [echo] Using connection: > scm:cvs:pserver:[EMAIL PROTECTED] > > :commonearproject > > > > scm:checkout: > > [echo] Checking out scm:cvs:pserver:[EMAIL PROTECTED] > > :commonearproject > > > > BUILD FAILED > > File.. C:\Documents and Settings\choudhsa\.maven\cache\maven- > > scm-plugin-1.5\plugin.jelly > > Element... scm:checkout > > Line.. 110 > > Column 233 > > The scm url is invalid. > > Total time: 4 seconds > > Finished at: Sun Jul 31 19:43:24 PDT 2005 > > What is it I am doing wrong? > > How can I specify my cvs password? (other than setting it in properties > > file). As you can see, I am using pserver and not ssh. > > Please advice. > > Thanks, > > Sanjay > > > > >
Re: [m2] Adding tools.jar to classpath
On Sun, 31 Jul 2005, Andy Glick wrote: > Is there a specific reason why tools.jar can't or shouldn't be placed in > the JDK's JRE/lib/ext directory. I've been doing that for about 7 years > now, and I haven't been aware of any problems. But maybe I don't know > what to look out for. Not really, it just ends up in the classpath then. A few reasons though: - tools.jar is part of the JDK, not the JRE, so it wasn't meant to be put there; - it'll only work for you :) -- Kenney Westerhof - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCM tag 1.5.
It appears the connection it is using is scm:cvs:pserver:[EMAIL PROTECTED]:commonearproject This is invalid (after the hostname, you need to rest of the root, then : and then the module, here you just have the module) It is probably being picked up from the project.xml in the current directory - this command is designed to run when there is no project in the current directory. To set the password, you should manually do a "cvs login" command outside of maven first. - Brett On 8/1/05, Sanjay Choudhary <[EMAIL PROTECTED]> wrote: > Hi All, > My configuration details are as below > 1. Maven SCM Plug In 1.5 > 2. Source Control Repository CVS > I am doing something very simple, that is checkout a project from a cvs > repository. Command is as below:- > maven scm:bootstrap - > Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED] > :NAOL_Conversion_2_NKP_R5/CodeTableEJB > NAOL_Conversion_2_NKP_R5 is branch name and CodeTableEJB is the project > name. > I get the error > > build:start: > > scm:find-connection: > [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED] > :commonearproject > > scm:checkout: > [echo] Checking out scm:cvs:pserver:[EMAIL PROTECTED] > :commonearproject > > BUILD FAILED > File.. C:\Documents and Settings\choudhsa\.maven\cache\maven- > scm-plugin-1.5\plugin.jelly > Element... scm:checkout > Line.. 110 > Column 233 > The scm url is invalid. > Total time: 4 seconds > Finished at: Sun Jul 31 19:43:24 PDT 2005 > What is it I am doing wrong? > How can I specify my cvs password? (other than setting it in properties > file). As you can see, I am using pserver and not ssh. > Please advice. > Thanks, > Sanjay > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SCM tag 1.5.
Hi All, My configuration details are as below 1. Maven SCM Plug In 1.5 2. Source Control Repository CVS I am doing something very simple, that is checkout a project from a cvs repository. Command is as below:- maven scm:bootstrap - Dmaven.scm.url=scm:cvs:pserver:[EMAIL PROTECTED] :NAOL_Conversion_2_NKP_R5/CodeTableEJB NAOL_Conversion_2_NKP_R5 is branch name and CodeTableEJB is the project name. I get the error build:start: scm:find-connection: [echo] Using connection: scm:cvs:pserver:[EMAIL PROTECTED] :commonearproject scm:checkout: [echo] Checking out scm:cvs:pserver:[EMAIL PROTECTED] :commonearproject BUILD FAILED File.. C:\Documents and Settings\choudhsa\.maven\cache\maven- scm-plugin-1.5\plugin.jelly Element... scm:checkout Line.. 110 Column 233 The scm url is invalid. Total time: 4 seconds Finished at: Sun Jul 31 19:43:24 PDT 2005 What is it I am doing wrong? How can I specify my cvs password? (other than setting it in properties file). As you can see, I am using pserver and not ssh. Please advice. Thanks, Sanjay
Re: Setting maven.repo.list dynamically - possible bug?
On 7/29/05, Lach, Thierry <[EMAIL PROTECTED]> wrote: I'm trying to set maven.repo.list in a plugin but it does not seem to work. We are using ear:deploy to copy ear files not only to the maven repository, but to pseudo-repositories on our test and production application servers to help ensure that all versions on all servers are identical. We use a convention that a production deploy version number ends in a -prod. I'm trying to write my plugin so that maven.repo.list is set to the maven repository and the two test servers if not a production, and to the maven repository, two test servers, and the three production servers if it IS a production version. Brett Porter wrote: THis is a limitation of maven:get/set - the plugin must be initialised first. Try adding xmlns:artifact="artifact" to your maven.xml/plugin.jelly. Alternatively, use j:set scope="parent" var="maven.repo.list" ... Lach, Thierry replied: I was not able to get it to work at all using maven:set/get - even after including the artifact xmlns in both plugin.jelly and the calling maven.xml - and even after executing as part of a pregoal for "build:start". I WAS able to get it running using , but not precisely the way I wanted. I tried to execute the in a tag defined in the plugin that was called by the preGoal in the plugin, but it didn't work. It only worked when the preGoal in my plugin.jelly directly executed the . I ask: What is "it" that declaring the artifact namespace is supposed to do, and how should that be different, if it should, from what one might expect that setting would do? Brett, do you have any sense why Thierry couldn't inject a property into the plugin when he included the artifact namespace in both his plugin and his maven.xml file, but that it worked when he set the scope to parent? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[clover] Release a clover plugin (1.10?) for Clover 1.3.9?
Hello: Can we get a released version of the clover plugin (1.10?) for Clover 1.3.9? Thanks, Gary
Re: [m2] Adding tools.jar to classpath
Roman Bruggisser wrote: I'm new to maven and I'm wondering if there is a way to add tools.jar to the classpath without placing it in the repository. Thanks for any ideas. Kenney Westerhof wrote: On Sun, 31 Jul 2005, Roman Bruggisser wrote: Hi, There aren't any. However it should be on the classpath if you use the jdk. A better solution is to add it to the classpath at runtime. See http://svn.plexus.codehaus.org/trunk/plexus-components/plexus-compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java?rev=2369&view=markup for an example. Is there a specific reason why tools.jar can't or shouldn't be placed in the JDK's JRE/lib/ext directory. I've been doing that for about 7 years now, and I haven't been aware of any problems. But maybe I don't know what to look out for. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clear plugin repository problem
On Sun, 31 Jul 2005, Jon Strayer wrote: Maven 2 doesn't have a 'clear' plugin. Don't you mean to use m2 clean:clean ? -- Kenney > I'm getting this exception when I try to run "m2 clear:clear" > > [INFO] Retrieving release information for maven-clear-plugin > FATAL ERROR: Error executing Maven for a project > For more information, run with the -e flag > pht018c://appl/wfa/WBNT/core> clear; m2 -e clear:clear test > + Error stacktraces are turned on. > [INFO] > > [INFO] Building Core > [INFO] > > [INFO] maven-clear-plugin: checking for updates from central-plugins > [INFO] Retrieving release information for maven-clear-plugin > FATAL ERROR: Error executing Maven for a project > Error stacktrace: > org.apache.maven.reactor.ReactorException: Error executing project > within the reactor > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) > at org.codehaus.classworlds.Launcher.main(Launcher.java:363) > Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: > Error resolving plugin version > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) > at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) > ... 9 more > Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: > Error resolving version for > 'org.apache.maven.plugins:maven-clear-plugin': Cannot resolve RELEASE > version of this plugin. > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) > at > org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) > ... 14 more > Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: > Unable to find release for artifact > org.apache.maven.plugins:maven-clear-plugin:maven-plugin:RELEASE > org.apache.maven.plugins:maven-clear-plugin:RELEASE:maven-plugin > > from the specified remote repositories: > http://repo1.maven.org/maven2/plugins > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) > at > org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) > ... 17 more > Caused by: > org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: > Unable to find release for artifact > org.apache.maven.plugins:maven-clear-plugin:maven-plugin:RELEASE > at > org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) > at > org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:51) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:84) > ... 18 more > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: > Unable to locate resource in repository > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:310) >
Clear plugin repository problem
I'm getting this exception when I try to run "m2 clear:clear" [INFO] Retrieving release information for maven-clear-plugin FATAL ERROR: Error executing Maven for a project For more information, run with the -e flag pht018c://appl/wfa/WBNT/core> clear; m2 -e clear:clear test + Error stacktraces are turned on. [INFO] [INFO] Building Core [INFO] [INFO] maven-clear-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-clear-plugin FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:190) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving plugin version at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:537) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:149) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:133) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) ... 9 more Caused by: org.apache.maven.plugin.version.PluginVersionResolutionException: Error resolving version for 'org.apache.maven.plugins:maven-clear-plugin': Cannot resolve RELEASE version of this plugin. at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:570) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:130) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:192) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:528) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to find release for artifact org.apache.maven.plugins:maven-clear-plugin:maven-plugin:RELEASE org.apache.maven.plugins:maven-clear-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:88) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveReleaseVersion(DefaultPluginVersionManager.java:566) ... 17 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to find release for artifact org.apache.maven.plugins:maven-clear-plugin:maven-plugin:RELEASE at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.retrieveFromRemoteRepository(ReleaseArtifactTransformation.java:86) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:104) at org.apache.maven.artifact.transform.ReleaseArtifactTransformation.transformForResolve(ReleaseArtifactTransformation.java:51) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:84) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:310) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:242) at org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:94) at org.apache.maven.artifact.transform.
Re: [m2] Adding tools.jar to classpath
On Sun, 31 Jul 2005, Roman Bruggisser wrote: Hi, There aren't any. However it should be on the classpath if you use the jdk. A better solution is to add it to the classpath at runtime. See http://svn.plexus.codehaus.org/trunk/plexus-components/plexus-compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java?rev=2369&view=markup for an example. -- Kenney > Hi > > > > I'm new to maven and I'm wondering if there is a way to add tools.jar to the > classpath without placing it in the repository. > > Thanks for any ideas. > > > > Roman > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Adding tools.jar to classpath
Hi I'm new to maven and I'm wondering if there is a way to add tools.jar to the classpath without placing it in the repository. Thanks for any ideas. Roman
Re: [m2] compiling from 2 different dirs
On Sun, 2005-07-31 at 14:51 +0100, Adam Hardy wrote:
> Sorry my mistake. maven-xdoclet-plugin is calling
> project.addCompileSourceRoot() but in its current version, it does not
> accept any config, and the default
> ${project.build.directory}/generated-sources/xdoclet must be used.
>
> Just for anyone searching the mail archives with this problem.
This is typically the pattern employed by plug-ins generating sources.
Where the output is directed to:
${project.build.directory}/generated-sources/
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] compiling from 2 different dirs
Sorry my mistake. maven-xdoclet-plugin is calling
project.addCompileSourceRoot() but in its current version, it does not
accept any config, and the default
${project.build.directory}/generated-sources/xdoclet must be used.
Just for anyone searching the mail archives with this problem.
Adam Hardy on 30/07/05 18:22, wrote:
maven-xdoclet-plugin isn't calling project.addCompileSourceRoot()
Unfortunately.
How can I set this myself in my pom? I have played around with stuff
like this:
org.apache.maven.plugins
maven-compiler-plugin
src/main/java
${project.build.directory}/generated-src
but i either get a Failure executing javac (but could not parse the
error) or maven ignores it completely.
Is there a way to do this for 2 directories?
Adam
Jesse McConnell on 29/07/05 19:48, wrote:
well, the xdoclet plugin should be calling
project.addCompileSourceRoot( outputDirectory );
in order to add the generated files to the compile phase..
mostly these are generated into target/generated-sources I believe,
that why they are blown away with the default clean targets. I don't
see source for the xdoclet plug in either mojo or the m2 repos though
so I can't say for sure.
but yes, it is easy to do
On 7/29/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
Adam Hardy on 28/07/05 16:39, wrote:
(2) Even if I could get the xdoclet to run in m2, I can't figure out
how to include a second source directory (containing the xdoclet
generated classes). Is it just a comma-delimited list in the
attribute of the pom?
If I run xdoclet to generate some EJB code in a seperate directory (I
don't want it in the version control system), can I get maven to
compile it along with the normal code in src/main/java?
As quoted in the paragraph above, I can't work out how to get m2 to do
that.
Or is it better to put it straight into the src/main/java tree with
the rest? I could always tell cvs to ignore it - although this would
be error prone.
-
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] Multiple levels of repositories
Thanks It worked just as you said. And to put it mildly, m2 is a huge huge improvement wrt m1.x IMO. Thanks Sid --- Brett Porter <[EMAIL PROTECTED]> wrote: > Maven proxy basically acts as an internal mirror of > ibiblio, working > around the need for all devs to have internet access > and saving > bandwidth. It should work with Maven2 unmodified - > but I've not heard > from anyone trying it. > > What it sounds like you want is to actually have 2 > different remote > repositories, which is actually a good setup - one > for your builds and > then the outside world one. The outside world one > and the local > developer ones come standard, so all you need to add > is the internal > company repository, which you can do with the > element > in the POM. This should be in a parent inherited by > every project > using that environment. > > Finally, you should put that repository in the > section of the same POM so > that when > artifacts are deployed they end up there. > > Cheers, > Brett > > On 7/30/05, Sidart Kurias <[EMAIL PROTECTED]> > wrote: > > All, > > > > I would like to set up multiple levels of > > repositories. One local for the developer, to > which > > snapshots will be deployed, one on the intranet > [for > > versioned releases] and the third are the true > remote > > repositories. Libraries should be fetched from the > > intranet repository before going off to ibiblio > etc... > > I read an earlier post relating to Maven 1.x, > that > > suggested using the maven-proxy servlet. Is that > still > > the recommended way in m2 or is there another way > to > > do it? > > > > Thanks > > Sid > > > > > > > > > > > Start your day with Yahoo! - make it your home > page > > http://www.yahoo.com/r/hs > > > > > > > - > > 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] > > Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
