which repository contains the 2 artifacts?
hi, i am using nexus indexer,i found i cant download the 1) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1 2) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 what is the address of repostiroy which contains the artifact?i think i should set proxy in nexus. thanks a lot! oliver.maven 2008-05-10
Re: which repository contains the 2 artifacts?
For nexus we recommend making a group and using a mirror of * Both of those artifacts should be in central --Brian On May 10, 2008, at 1:52 AM, oliver.maven [EMAIL PROTECTED] wrote: hi, i am using nexus indexer,i found i cant download the 1) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9- stable-1 2) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 what is the address of repostiroy which contains the artifact?i think i should set proxy in nexus. thanks a lot! oliver.maven 2008-05-10 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: which repository contains the 2 artifacts?
hi Brian Fox thanks for reply! actually i do config the mirror of *.are there any other reason i cant download these artifact? oliver.maven 2008-05-10 发件人： Brian Fox 发送时间： 2008-05-10 17:01:06 收件人： Maven Users List 抄送： 主题： Re: which repository contains the 2 artifacts? For nexus we recommend making a group and using a mirror of * Both of those artifacts should be in central --Brian On May 10, 2008, at 1:52 AM, oliver.maven [EMAIL PROTECTED] wrote: hi, i am using nexus indexer,i found i cant download the 1) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9- stable-1 2) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 what is the address of repostiroy which contains the artifact?i think i should set proxy in nexus. thanks a lot! oliver.maven 2008-05-10 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: artifactory and snapshots vs releases
On Sat, May 10, 2008 at 1:19 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Fri, May 9, 2008 at 7:30 AM, Rick [EMAIL PROTECTED] wrote: Another hopefully quick one... The better builds guide mentions about filenames being used with timestamps appended etc, but yet whenever I do mvn deploy, I never see that timestamp either in my local m2 repo or in my corporate rep snapshots dir, It only ever has the version as I've declared in the pom version for the project. What is an example of a version number you're using? If your version number ends in -SNAPSHOT, and you haven't set uniqueVersion=false in distributionManagement, then you should see timestamped files in the remote snapshotRepository after you deploy. me == moron (mostly:) I 'think' everything is ok. I stated a major falsehood above.. in my local repo things are fine - I apologize I don't know what I was looking at to assume it wasn't working there (maybe I was an idiot and since I was working with Artificatory all day I just quickly saw 1.0-SNAPSHOT and assumed it was a file and not dir to traverse - regardless, I was an idiot there.) However, it is Artificatory I was really confused, since In Artificatory I'll only see something like 1.0-SNAPSHOT.jar listed.. but in the maven-metadata.xml you will see the versioning change when you deploy new ones. I'm assuming that's behaving as normal? (I know this isn't an Artificatory list, but was just curious.) I did see this in their FAQ: Why do you strongly recommend against deploying unique snapshots? Because doing so normally promotes an unmanageable build environment. In practice, unique snapshots are never tracked for the real changes they carry: the snapshot's final name is not human deterministic and its meaning is normally obscure to developers since, by itself, it has no relation to the source it has been compiled against. Moreover, many times snapshots in a multi-module environment are dependent on other snapshots, so you would have to reconstruct by hand a cryptic dependency chain just to get back to a version you believe is stable. Often, the identification process of such a version is, by itself, obscure and is based on common inputs such as yesterday before lunchtime everything worked Therefore, it is highly preferable to use non-unique snapshots in development and, when needing, go back to a stable non-snapshot version by reconstructing one from a specific revision/tag in the VCS, where the meaning of the artifact can be easily tracked. It is advised to have the artifact itself embed the revision/tag (as part of its name or internally) for clear and visible revision tracking. -- Rick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to build sub-module without parent pom?
Do you mean I should add the parent in the sub-module's dependency? [EMAIL PROTECTED] wrote: youhaodeyi schrieb: Sometimes a project has many sub-modules and each of them may have sub-sub-modules. I don't want to get all the source codes. How can I work on a sub-module without its parent pom file? The parent pom just needs to be in a repository that can be seen when you are building the sub-module. So if the sub-module is referencing a released parent pom, there should be no problem. The released pom will be in a repository. If the sub-module is referencing a snapshot version of a parent pom, then someone needs to set up a snapshot repository somewhere, and deploy that parent pom into the snapshot repository. Then when building the sub-module, you just need to have that snapshot repository defined, either by having it in the pom.xml for the sub-module, or by adding it to your personal ~/.m2/settings.xml file. Of course you won't see any changes that people make to that parent pom until they deploy the modified version to the snapshot repository again. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-to-build-sub-module-without-parent-pom--tp17147483p17163006.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: Dependency scope - provided or optional.. ?
Also, in the context of a WAR project, scopeprovided/scope and optionaltrue/optional have different semantics when it comes to inclusion in the manifest's Class-Path or not. (See: http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html ) In my experience, it is usually better to mark dependencies in a JAR project as optionaltrue/optional, since provided scope would be a strong assumption about the context that the JAR is going to be used in. YMMV. -Olivier On Fri, 2008-05-09 at 19:45 -0400, Brian E. Fox wrote: Optional is meant if you have several dependencies that you need to compile, but that a user of your jar might only need one of (think oracle vs mssql bindings). -Original Message- From: Paul Smith [mailto:[EMAIL PROTECTED] Sent: Friday, May 09, 2008 4:42 PM To: Maven Users List Subject: Re: Dependency scope - provided or optional.. ? On 10/05/2008, at 9:38 AM, Brianefox wrote: Provided means to include in the compile do but not in the package (war) Optional means that it wont be pulled in transitively by users of your jar From this, I gather Optional is actually what we want. Would it be fair to say that Optional is a sort of extension to provided. Whereas Provided indicates that it is actually needed downstream, but the downstream projects need to arrange their own bundling of it. A dependency marked as Provided still indicates to the downstream project that they need it to run it. Would you agree that Optional is what we want for log4j? cheers, Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven2 was plugin
Here is my solution mvn org.codehaus.mojo:was6-maven-plugin:1.0-alpha-2:wsListApps -Dwas6.wasHome=C:\webSphere\AppServer -Dwas6.host=123.456.789.123 -Dwas6.conntype=SOAP -Dwas6.user=urUsername -Dwas6.password=urPassword -- View this message in context: http://www.nabble.com/maven2-was-plugin-tp17061567p17163064.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven exec plugin
On Fri, May 9, 2008 at 4:50 AM, avin98 [EMAIL PROTECTED] wrote: I'm trying to run a shell script from a maven goal. Here's my definition build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId executions execution goals goalexec/goal /goals /execution /executions configuration executable/bin/sh/executable arguments argumentrun.sh/argument /arguments /configuration /plugin /plugins /build When I call mvn exec:exec I get the following error [INFO] One or more required plugin parameters are invalid/missing for 'exec:exec' [0] inside the definition for plugin: 'exec-maven-plugin'specify the following: configuration ... executableVALUE/executable /configuration -OR- on the command line, specify: '-Dexec.executable=VALUE' [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.codehaus.mojo:exec-maven-plugin. Reason: Invalid or missing parameters: [Mojo parameter [name: 'executable'; alias: 'null']] for mojo: org.codehaus.mojo:exec-maven-plugin:1.1-beta-1:exec at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:568) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginParameterException: Error configuring: org.codehaus.mojo:exec-maven-plugin. Reason: Invalid or missing parameters: [Mojo parameter [name: 'executable'; alias: 'null']] for mojo: org.codehaus.mojo:exec-maven-plugin:1.1-beta-1:exec at org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters(DefaultPluginManager.java:907) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:612) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Thu May 08 19:49:56 PDT 2008 [INFO] Final Memory: 3M/6M [INFO] I cannot reproduce the problem (see below. I used maven 2.0.8). * exec mojo issues are reported on the mojo user list * please create a test case that reproduces the issuer and tell us more of your environment [EMAIL PROTECTED]:/tmp$ cat run.sh echo Working [EMAIL PROTECTED]:/tmp$ cat pom.xml project modelVersion4.0.0/modelVersion groupIdorg.cb.maven.plugins.exec/groupId artifactIdtest/artifactId version0.1/version packagingjar/packaging build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.1-beta-1/version executions execution goals goalexec/goal /goals /execution /executions configuration executable/bin/sh/executable arguments argumentrun.sh/argument /arguments /configuration /plugin /plugins /build /project [EMAIL PROTECTED]:/tmp$ mvn exec:exec [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO]
Re: How to instruct Maven to run more than one script?
On Sat, May 3, 2008 at 2:20 AM, Tawfik, Sameh E [EMAIL PROTECTED] wrote: Hi, I've two Perl scripts, Before_Build.pl, and After_Build.pl that I need to run the first one before the build starts and the other one after the build is complete. So, what is the command line syntax to run a full build with the above requirements? Extract from the soon to be published FAQ of the exec mojo: Q: How to execute the plugin multiple times ? Use several execution nodes each with a different id. Don't forget to bind each execution to a phase. Read the full answer here: http://article.gmane.org/gmane.comp.java.maven-plugins.mojo.user/1307 I've the following code in my pom.xml: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId executions execution goals goalexec/goal /goals /execution /executions inheritedfalse/inherited configuration executableBefore_Build.pl/executable arguments argument20/argument /arguments /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId executions execution goals goalexec/goal /goals /execution /executions inheritedfalse/inherited configuration executableAfter_Build.pl/executable arguments argument20/argument /arguments /configuration /plugin I can successfully execute the first Perl script Before_Build.pl from the command line, by running the following command: C:\projectsmvn -N exec:exec -Dexec.executable= Before_Build.pl Thanks, Sameh This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jerome Lacoste, +47 40867729, Daglig Leder, CoffeeBreaks AS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven2 was plugin
Thank you for your reply. We have found a similiar solution.
However, I think here is the point needed to be specified clearly : it
requires a WAS installation (or somehow some part of it) on local machine or
smart mapping to a remote WAS installation.
Thanks
easygoing wrote:
Here is my solution
mvn org.codehaus.mojo:was6-maven-plugin:1.0-alpha-2:installApp
-Dwas6.wasHome=C:\webSphere\AppServer -Dwas6.host=xxx.xxx.xxx.xxx
-Dwas6.conntype=SOAP -Dwas6.username=${username}
-Dwas6.password=${password}
-Dwas6.earFile=c:\temp\testWeb_war.ear
In my case,
It works only when there is already deployed application with the same
name with that project's coodinate
( groudId:artifactId:version ) in Websphere server.
so, dont forget deploy the one (have the same name that project's
coodinate) first
I don't know why and I wonder why.
--
View this message in context:
http://www.nabble.com/maven2-was-plugin-tp17061567p17166499.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: Re: which repository contains the 2 artifacts?
Oliver, take a look here: http://www.sonatype.com/book/reference/repository-manager.html# -Original Message- From: oliver.maven [mailto:[EMAIL PROTECTED] Sent: Saturday, May 10, 2008 2:13 AM To: Maven Users List Subject: Re: Re: which repository contains the 2 artifacts? hi Brian Fox thanks for reply! actually i do config the mirror of *.are there any other reason i cant download these artifact? oliver.maven 2008-05-10 发件人： Brian Fox 发送时间： 2008-05-10 17:01:06 收件人： Maven Users List 抄送： 主题： Re: which repository contains the 2 artifacts? For nexus we recommend making a group and using a mirror of * Both of those artifacts should be in central --Brian On May 10, 2008, at 1:52 AM, oliver.maven [EMAIL PROTECTED] wrote: hi, i am using nexus indexer,i found i cant download the 1) org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9- stable-1 2) org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2 what is the address of repostiroy which contains the artifact?i think i should set proxy in nexus. thanks a lot! oliver.maven 2008-05-10 - 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: Dependency scope - provided or optional.. ?
Paul Smith wrote: Could some explain the difference between the dependency scope provided versus optional if there actually is any.. We have converted log4j over to Maven recently and accidently forgot to mark a few dependencies with flags indicating that, while needing for compile time, should not necessarily be enforced on the end user. I refer people to this issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=43304 I originally used 'optional' because I saw this being used in the ActiveMQ project, but now I can't find any real definitive reference to what that means. Taken from the POM reference at http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency optional means: Indicates the dependency is optional for use of this library. While the version of the dependency will be taken into account for dependency calculation if the library is used elsewhere, it will not be passed on transitively. I've read: http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html and that makes no mention of the 'optional' scope type. Is it a legacy marker? It's not a scope, but a separate option on a dependency. So you can have something like this: scopecompile/scope optionaltrue/optional That means that the dependency is needed to compile the project, but it is optional for the end user. Depending on which parts of your projects code he/she uses. An example of this would be javax.mail that is needed by the SMPTAppender. If a user decides that they will never use the SMTPAppender then they do not need to include javax-mail - it is optional. If someone could provide advice here I would appreciate it. Which of your dependencies do you need help with? I did the POM for Commons Logging 1.1.1, so I have a pretty good idea of what's needed. I'd love to see a working POM for log4j, see my patches to the issue mentioned above. cheers, Paul -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
surefire plug in causing build error
I'm getting the following error attempting to build with maven 2. It looks like Plexus is trying to load 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-surefire-plugin:2.4.2:test', whiche looks like the fully qualified Mojo class prepended to the front of the fully qualified 'test surefire goal. I tried using surefire 2.4 and surefire 2.3, same thing. I googled it, but didn't find much. Hoping someone has a suggestion to what this means... - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test': Unable to find the mojo 'org.apache.maven.plu gins:maven-surefire-plugin:2.4.2:test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin' org/apache/maven/surefire/booter/SurefireExecutionException : org/apache/maven/surefire/util/NestedCheckedException [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-surefire-plugin:2.4.2:tes t': Unable to find the mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test' in the plugin 'org.apache.maven.plugins:maven-surefire-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at jrockit.reflect.InitialMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test' in the plugin 'org.apa che.maven.plugins:maven-surefire-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 14 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven.plug ins:maven-surefire-plugin:2.4.2:test', it could not be created at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609) ... 16 more Caused by: org.codehaus.plexus.component.factory.ComponentInstantiationException: Could not instanciate component: role: 'null', implementation: ' org.apache.maven.pl ugin.surefire.SurefirePlugin' at org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62) at org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331) ... 18 more Caused by: java.lang.NoClassDefFoundError:
