How to get project version in an xdoc
Im writting a XDoc document that will be used by the site plugin. In this
document I need to write the version of the project.
I have tried to write ${project.version} but when the site is generated, it is
not replaced by the project version.
Is it possible to get the project version in an Xdoc used by the site plugin ?
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses.
Re: [m2] disappearing dependency
On 05/03/07, John J. Franey [EMAIL PROTECTED] wrote: In your pom, taglibs/standard is not specified as a dependency. Its in dependencyManagement but dependencyManagement has no effect on the dependency graph of the project.Put tagslib/standard within the dependencies element and see what flies. Thanks for your help ! But actually, taglibs/standard is specified as a dependency, in the web/pom.xml sub-project (see my first email for the complete pom-xml). I dont think that I should have it as a dependency in the main pom, as this jar should only be included in the web sub-project. But I might be wrong ... Any other idea ? Guillaume -- Jabber : [EMAIL PROTECTED] Skype : Guillaume.Lederrey Projects : * http://rwanda.wordpress.com/ * http://rwandatech.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] disappearing dependency
any chance the exclusion in parent pom cancels it out? -D On 3/6/07, Guillaume Lederrey [EMAIL PROTECTED] wrote: On 05/03/07, John J. Franey [EMAIL PROTECTED] wrote: In your pom, taglibs/standard is not specified as a dependency. Its in dependencyManagement but dependencyManagement has no effect on the dependency graph of the project.Put tagslib/standard within the dependencies element and see what flies. Thanks for your help ! But actually, taglibs/standard is specified as a dependency, in the web/pom.xml sub-project (see my first email for the complete pom-xml). I dont think that I should have it as a dependency in the main pom, as this jar should only be included in the web sub-project. But I might be wrong ... Any other idea ? Guillaume -- Jabber : [EMAIL PROTECTED] Skype : Guillaume.Lederrey Projects : * http://rwanda.wordpress.com/ * http://rwandatech.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems adding Maven2 project through URL
Hi Chris, thanks for your reply. I tried your suggestion, but i didn't realize the correct directory structure, so this won't work for me. Also this solution has one drawback, i have to synchronize my svn repo with this directory by hand, like you do with that shell script. To make it short, i decided to install apache httpd with svn support to our devel server, and now we have svn and http access to subversion repo. And with that nice style sheet from TortoiseSVN 1) we got a simple but nice web frontend. Continuum works also, everything is fine. Thanks again Roland 1) http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/contrib/other/svnindex Chris Russell schrieb: Hi Roland, I never could get it to pull from SVN (svn://se-scm.oracle.com/se/ml3/trunk/orion/apps/helpdesk). My workaround was to create a similar directory structure on the same linux box as Continuum, and upload the POM's there (but it doesn't have to be the same machine). I created this new set of directories under the http root area for apache (i.e. apache/htdocs). Then I could give Continuum a url like this: http://wd2013.us.oracle.com:/pom.xml and it would then pull in my project and sub-projects. I realize that you didn't install apache. To make things easier, I also created a shell script to do the copying of my POM files from their checkout location to the htdocs directory as I was always making some kind of change. I'm new to Continuum, so I hope that there's a better way to do this. Thanks, Chris Roland Klein wrote: What i forgot releasing the project with Maven from the command line works fine. Also accessing the subversion repository with svn ls svn://host/project/trunk works. But there is no http access, because i am to lazy to install apache with svn_mod to acess subversion when it is working with svn:// Thanks Roland Roland Klein schrieb: Hi All, i'm having trouble to add a project with modules to Continuum providing an URL. i tried following URL's: scm:svn:svn://host/project/trunk/pom.xml svn:svn://host/project/trunk/pom.xml svn://host/project/trunk/pom.xml scm:svn:svn://host/project/trunk svn:svn://host/project/trunk svn://host/project/trunk in each case i got the error [ You must provide a valid url ] First i searched the mailing list and found some older posts like following: http://www.nabble.com/forum/ViewPost.jtp?post=3104276framed=yskin=177 In this post Emmanuel Venisse stated, that the scm through the svn protocol will be supported in a future version, ok this post is from Feb 24, 2006, so maybe obsolet. Then i found this from Feb 19,2007 http://www.nabble.com/forum/ViewPost.jtp?post=9042261framed=yskin=177 there Emmanuel refer to the Maven 2 URL format definition (http://maven.apache.org/scm/subversion.html). So my questions are, do i have to specify the filename pom.xml in the URL? Should i build Continuum from HEAD, to get latest version, and in this latest version is the svn protocol supported? My env: - Windows 2000 - Maven 2.0.4 - Continuum 1.0.3 Thanks in advance Roland -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571
Re: Problems adding Maven2 project through URL
Hi Alexander, as i wrote Chris, i installed apache also and now everything works. Thanks to you Roland Morgovsky, Alexander (US - Glen Mills) schrieb: Here is the set-up which I have. I have Apache Web Server in front of SVN, and I add POM's in Continuum by using http://username:password@host/url of source code. I am using Maven 2, and I made sure that my settings.xml was in the home directory of the user who started the Continuum server. Please let us know if this helps. Thanks. -Original Message- From: Chris Russell [mailto:[EMAIL PROTECTED] Sent: Friday, March 02, 2007 10:08 AM To: continuum-users@maven.apache.org Subject: Re: Problems adding Maven2 project through URL Hi Roland, I never could get it to pull from SVN (svn://se-scm.oracle.com/se/ml3/trunk/orion/apps/helpdesk). My workaround was to create a similar directory structure on the same linux box as Continuum, and upload the POM's there (but it doesn't have to be the same machine). I created this new set of directories under the http root area for apache (i.e. apache/htdocs). Then I could give Continuum a url like this: http://wd2013.us.oracle.com:/pom.xml and it would then pull in my project and sub-projects. I realize that you didn't install apache. To make things easier, I also created a shell script to do the copying of my POM files from their checkout location to the htdocs directory as I was always making some kind of change. I'm new to Continuum, so I hope that there's a better way to do this. Thanks, Chris Roland Klein wrote: What i forgot releasing the project with Maven from the command line works fine. Also accessing the subversion repository with svn ls svn://host/project/trunk works. But there is no http access, because i am to lazy to install apache with svn_mod to acess subversion when it is working with svn:// Thanks Roland Roland Klein schrieb: Hi All, i'm having trouble to add a project with modules to Continuum providing an URL. i tried following URL's: scm:svn:svn://host/project/trunk/pom.xml svn:svn://host/project/trunk/pom.xml svn://host/project/trunk/pom.xml scm:svn:svn://host/project/trunk svn:svn://host/project/trunk svn://host/project/trunk in each case i got the error [ You must provide a valid url ] First i searched the mailing list and found some older posts like following: http://www.nabble.com/forum/ViewPost.jtp?post=3104276framed=yskin=177 In this post Emmanuel Venisse stated, that the scm through the svn protocol will be supported in a future version, ok this post is from Feb 24, 2006, so maybe obsolet. Then i found this from Feb 19,2007 http://www.nabble.com/forum/ViewPost.jtp?post=9042261framed=yskin=177 there Emmanuel refer to the Maven 2 URL format definition (http://maven.apache.org/scm/subversion.html). So my questions are, do i have to specify the filename pom.xml in the URL? Should i build Continuum from HEAD, to get latest version, and in this latest version is the svn protocol supported? My env: - Windows 2000 - Maven 2.0.4 - Continuum 1.0.3 Thanks in advance Roland This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571
[m2] dependency order in 2.0.5
Hello, I'd like to have more information about the new way to resolve dependencies in maven 2.0.5. In the release notes, you write ...when two exist at the same depth in the dependency graph, by matching the first encountered.. Picking up the FIRST element means there's a sorted list somewhere... But how are dependencies sorted in the parsing ? I've changed the order of dependencies in the pom many times to test the behaviour, and I noticed that nothing changed at all ! At the same depth, the dependency resolution order shown in the log (with the -X option) is always the same. I guess some kind of hash map may be used to store dependencies, and iterating on this map always gives the exact same order each time ?? So I agree that this method will be totally determinist, but wouldn't it be better to take the MOST RECENT version when you have two identical artefacts at the same depth level ? In this latest maven version, users have no way to influence on the dependency to be used by ordering manually the items in the pom, so they're forced to put these dependencies at a higher level in the graph, which will unnecessarily increase the poms size... What's your point of view about that ? Thanks for your help ! Isabelle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] disappearing dependency
Might be ... but it did work correctly before I added the dependency on ojdbc ... strange ... I'll check and let you know. On 06/03/07, Dan Tran [EMAIL PROTECTED] wrote: any chance the exclusion in parent pom cancels it out? On 3/6/07, Guillaume Lederrey [EMAIL PROTECTED] wrote: On 05/03/07, John J. Franey [EMAIL PROTECTED] wrote: In your pom, taglibs/standard is not specified as a dependency. Its in dependencyManagement but dependencyManagement has no effect on the dependency graph of the project.Put tagslib/standard within the dependencies element and see what flies. But actually, taglibs/standard is specified as a dependency, in the web/pom.xml sub-project (see my first email for the complete pom-xml). I dont think that I should have it as a dependency in the main pom, as this jar should only be included in the web sub-project. But I might be wrong ... -- Jabber : [EMAIL PROTECTED] Skype : Guillaume.Lederrey Projects : * http://rwanda.wordpress.com/ * http://rwandatech.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Plugin does not exist or no valid version could be found
Thorsten, how can I determine the proxy I use? (NTLM or not) And which post you are referring to? -- Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: Re: Plugin does not exist or no valid version could be found
Hi, Thorsten, how can I determine the proxy I use? (NTLM or not) You should ask your network administrator; (s)he should be able to tell you that... And which post you are referring to? Don't remember; I only know that I have seen several posts about NTLM proxies Cheers Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] multi project interdependencies
Actually, it looks like what was happening is the error which was being caught by the compiler was a result of a private method name mismatch being called from the same class. There would really be no way for module a level above the module/dependency which has changed to know which classes in it's own module would be affected by the dependency change. Even Ant based projects which string targets together w/depends statements would result in the same behavior I am seeing w/Maven2. So, I would think a best practice here would be to perform a mvn clean install at the top level pom(where the modules are listed in my single level module list) every time a dependency module is rebuilt. Do you agree? franz see wrote: Good day to you, M, The steps I mentioned in my previous post still occurred. However, the compiler plugin does not compile if there are no changes in the source code. But in your example, it seems as though that it should have been recompiled. You may want to file a jira issue for that ( see [1] ). Cheers, Franz [1] http://jira.codehaus.org/browse/MCOMPILER mark_in_gr wrote: I don't believe this is correct, at least I am not able to get this to work. For example, if I have the following structure: Project Parent Module A Module B where Module B depends on Module A. If I force an issue in some code in Module A which is used in Module B and should case a compile time error in a class in Module B, then build(mvn package or mvn install) at the Project Parent Level, the code in Module A compiles(I see the message Compiling 1 source file to . . .), however, no classes in Module B are compiled!!(I see Nothing to compile - all classes are up to date). So, how is code in Module B going to be made aware of, say, a method being changed in a class in Module A??? if I run a mvn clean package or mvn clean install, everything works correctly seeing that all modules are completed rebuilt from scratch, but this goes against an incremental build process and is not an acceptable practice. My Project Parent level has a POM only, which Module A and Module B listed as Modules. In the Module B pom, Module A is listed as a dependency w/compile scope using the standard conventions(artifactId, groupId, etc.) and set up to use a snapshot. franz see wrote: Good day to you, M, Actually, it's subproject A - compile subproject A - test subproject A - jar subproject A - install subproject A - deploy subproject B - compile - in need of a subproject A jar (searching in repostitory) subproject B - test - proceeds only if an OLDER version is found subproject B - jar subproject B - install subproject B - deploy IRC, maven2 will first group your tasks to segments. And then those task segments would be executed one at a time. When one task segment finishes, the next will begin. All non-aggregating goals will be set as one task segment, then every aggregating goal will have their own task segment. Aggregating goals are those that run only on the project that you invoked it upon, while non-aggregating goals are those that run on the project you invoked it upon, plus, all modules under it. The project on which a non-aggregating goal will run on would then be ordered according to dependency, making sure that the dependencies are built before the dependees. The task segment for the non-aggregating goals would then be executed to each of those projects and according to which build lifecycle phase they are bound to. Thus, with a project project-a, with two modules, module-a and module-b, where module-b depends on module-a, if you run mvn deploy on project-a, the order of the projects would be project-a module-a module-b And on each project, the goals compiler:compile, surefire:test, jar:jar, install:install, deploy:deploy (among others) would be executed on each. Thus, it's like having cd project-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd module-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd ..\module-b mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy ( more or less ). Cheers, Franz meberts wrote: Hi, you're saying: If a dependency of your maven project does not exist when you execute a maven command, then that project will not bulid ( assuming ofcourse the maven command requires a pom to execute ). This would be an even bigger problem during install/deploy calls: What would then happen if changed some parts in subproject A and B and try to use parts of A in B? Since A will not be deployed/installed prior to the compilation of B, you might download the wrong version of A from the repository. This would lead to broken builds!? Currently it is like that: subproject A - compile
RE: [m2] [ANN] Artifactory - new Maven 2 proxy repository
This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Well, Artifactory actually started out as a series as patches on m2proxy and ended in a complete rewrite of it. The extras that we did came from real world requirements. The old m2proxy might still answer your every need in your development environment, and that's fine. Artifactory is used today by a couple of very large distributed development environments and that's where it really makes a difference. It offers everything that m2proxy used to offer + enterprise features such as: - Ability to deploy a mesh of proxies, each site proxying another. - Enhanced security for controlling who can deploy/undeploy to where. - Multiple local repositories support with control on what can be deployed to each repo, either by include/exclude patterns or by snapshot/releases. - Optional authenticated download of artifacts from local repositories - Web based deployment, including extraction a pom embedded in a deployed jar for a single transaction deployment of both jar and its pom. - HTTP(s) or WebDav deployment - Advanced indexing - Much improved web UI There's a more detailed feature description at: http://www.jfrog.org/sites/artifactory/latest/introduction.html Yoav Kalle Korhonen-2 wrote: Interesting. To this date, there's at least maven-proxy ( http://maven-proxy.codehaus.org/), Proximity ( http://proximity.abstracthorizon.org/), Archiva ( http://maven.apache.org/archiva/) and now, Artifactory, for more of less the same purpose. They are all Apache2 type licensed. We still use maven-proxy, and while it's only at version 0.2 and its development has stopped, we haven't seen any issues with it. Are any of these based on other's codebase or separate efforts and does anybody have any idea what the practical differences between all these are to the end user? Kalle On 3/4/07, Yoav Landman [EMAIL PROTECTED] wrote: Hi all, We would like to announce the immediate availability of Artifactory, a Maven 2 enterprise proxy. Artifactory offers advanced proxying, caching and security facilities to answer the needs of a robust, reproducible and independent build environment using Maven 2. It uses a JSR-170 Java Content Repository (JCR) for storage, which makes it extremely easy to manage searchable metadata, and provide extended features such as security, transacted operations, auditing, locking, etc. Artifactory is distributed under APLv2 at http://artifactory.sourceforge.net. It is currently available as a downloadable archive, that can be run out of the box (with default settings). An install script to run it as a Linux service is also provided. A (limited) guest live demo is available at http://www.jfrog.org/artifactory/ You are welcome to give it a go! Cheers, Yoav Landman, The Artifactory Team -- View this message in context: http://www.nabble.com/-ANN--Artifactory---new-Maven-2-proxy-repositor y-tf3344299s177.html#a9301347 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/-ANN--Artifactory---new-Maven-2-proxy-repository-tf3344299s177.html#a9305322 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail:
Does Cargo use the proxy settings in my settings.xml?
Hi *,
following the instructions in the Maven 2 quick reference card PDF I tried to
let Maven deploy a web app to Tomcat via Cargo:
build
plugins
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
executions
execution
idtomcat-execution/id
phasepackage/phase
goals
goalstart/goal
/goals
configuration
waittrue/wait
container
containerIdtomcat5x/containerId
zipUrlInstaller
urlhttp://www.apache.org/dist/tomcat/tomcat-5/v5.0.30/bin/jakarta-tomcat-5.0.30.zip/url
installDir${installDir}/installDir
/zipUrlInstaller
/container
configuration
home${project.build.directory}/tomcat5x//home
/configuration
/configuration
/execution
/executions
/plugin
...
Unfortunately mvn -X integration-test doesn't work; Cargo doesn't download
Tomcat:
*snip*
[DEBUG] Configuring mojo 'org.codehaus.cargo:cargo-maven2-plugin:0.2:start' --
[DEBUG] (s) home =
d:\workspaces\sukv-maven\SUKV_2\module-war\war-standalone\target\tomcat5x
[DEBUG] (f) configuration = [EMAIL PROTECTED]
[DEBUG] (s) containerId = tomcat5x
[DEBUG] (s) url =
http://www.apache.org/dist/tomcat/tomcat-5/v5.0.30/bin/jakarta-tomcat-5.0.30.zip
[DEBUG] (f) zipUrlInstaller = [EMAIL PROTECTED]
[DEBUG] (s) container = [EMAIL PROTECTED]
[DEBUG] (f) localRepository = [local] - file://D:\Dokumente und
Einstellungen\H2841\.m2\repository
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) repositories = [[ukv.releases] -
file:///d:/maven-repositories/releases, [ukv.snapshots] -
file:///d:/maven-repositories/snapshots, [central] -
http://repo1.maven.org/maven2, [codehaus-release-repo] -
http://repository.codehaus.org, [codehaus-snapshot-repo] -
http://snapshots.repository.codehaus.org, [apache.snapshot] -
http://people.apache.org/maven-snapshot-repository/]
[DEBUG] (f) wait = true
[DEBUG] -- end configuration --
[INFO] [cargo:start {execution: tomcat-execution}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to download
[http://www.apache.org/dist/tomcat/tomcat-5/v5.0.30/bin/jakarta-tomcat-5.0.30.zip]
Connection timed out: connect
[INFO]
[DEBUG] Trace
org.codehaus.cargo.container.ContainerException: Failed to download
[http://www.apache.org/dist/tomcat/tomcat-5/v5.0.30/bin/jakarta-tomcat-5.0.30.zip]
at
org.codehaus.cargo.container.installer.ZipURLInstaller.download(ZipURLInstaller.java:228)
at
org.codehaus.cargo.container.installer.ZipURLInstaller.install(ZipURLInstaller.java:105)
at org.codehaus.cargo.maven2.Container.setupHome(Container.java:254)
at
org.codehaus.cargo.maven2.Container.createContainer(Container.java:181)
at
org.codehaus.cargo.maven2.AbstractCargoMojo.createContainer(AbstractCargoMojo.java:332)
at
org.codehaus.cargo.maven2.ContainerStartMojo.execute(ContainerStartMojo.java:53)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
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:330)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
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:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: in cargo code: java.net.ConnectException: Connection timed out:
connect
at
Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository
Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Well, Artifactory actually started out as a series as patches on m2proxy and ended in a complete rewrite of it. The extras that we did came from real world requirements. The old m2proxy might still answer your every need in your development environment, and that's fine. Artifactory is used today by a couple of very large distributed development environments and that's where it really makes a difference. It offers everything that m2proxy used to offer + enterprise features such as: - Ability to deploy a mesh of proxies, each site proxying another. - Enhanced security for controlling who can deploy/undeploy to where. - Multiple local repositories support with control on what can be deployed to each repo, either by include/exclude patterns or by snapshot/releases. - Optional authenticated download of artifacts from local repositories - Web based deployment, including extraction a pom embedded in a deployed jar for a single transaction deployment of both jar and its pom. - HTTP(s) or WebDav deployment - Advanced indexing - Much improved web UI There's a more detailed feature description at: http://www.jfrog.org/sites/artifactory/latest/introduction.html Yoav Kalle Korhonen-2 wrote: Interesting. To this date, there's at least maven-proxy ( http://maven-proxy.codehaus.org/), Proximity ( http://proximity.abstracthorizon.org/), Archiva ( http://maven.apache.org/archiva/) and now, Artifactory, for more of less the same purpose. They are all Apache2 type licensed. We still use maven-proxy, and while it's only at version 0.2 and its development has stopped, we haven't seen any issues with it. Are any of these based on other's codebase or separate efforts and does anybody have any idea what the practical differences between all these are to the end user? Kalle On 3/4/07, Yoav Landman [EMAIL PROTECTED] wrote: Hi all, We would like to announce the immediate availability of Artifactory, a Maven 2 enterprise proxy. Artifactory offers advanced
RE: Problems adding Maven2 project through URL
Sounds good, thanks. -Original Message- From: Roland Klein [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 4:54 AM To: continuum-users@maven.apache.org Subject: Re: Problems adding Maven2 project through URL Hi Alexander, as i wrote Chris, i installed apache also and now everything works. Thanks to you Roland Morgovsky, Alexander (US - Glen Mills) schrieb: Here is the set-up which I have. I have Apache Web Server in front of SVN, and I add POM's in Continuum by using http://username:password@host/url of source code. I am using Maven 2, and I made sure that my settings.xml was in the home directory of the user who started the Continuum server. Please let us know if this helps. Thanks. -Original Message- From: Chris Russell [mailto:[EMAIL PROTECTED] Sent: Friday, March 02, 2007 10:08 AM To: continuum-users@maven.apache.org Subject: Re: Problems adding Maven2 project through URL Hi Roland, I never could get it to pull from SVN (svn://se-scm.oracle.com/se/ml3/trunk/orion/apps/helpdesk). My workaround was to create a similar directory structure on the same linux box as Continuum, and upload the POM's there (but it doesn't have to be the same machine). I created this new set of directories under the http root area for apache (i.e. apache/htdocs). Then I could give Continuum a url like this: http://wd2013.us.oracle.com:/pom.xml and it would then pull in my project and sub-projects. I realize that you didn't install apache. To make things easier, I also created a shell script to do the copying of my POM files from their checkout location to the htdocs directory as I was always making some kind of change. I'm new to Continuum, so I hope that there's a better way to do this. Thanks, Chris Roland Klein wrote: What i forgot releasing the project with Maven from the command line works fine. Also accessing the subversion repository with svn ls svn://host/project/trunk works. But there is no http access, because i am to lazy to install apache with svn_mod to acess subversion when it is working with svn:// Thanks Roland Roland Klein schrieb: Hi All, i'm having trouble to add a project with modules to Continuum providing an URL. i tried following URL's: scm:svn:svn://host/project/trunk/pom.xml svn:svn://host/project/trunk/pom.xml svn://host/project/trunk/pom.xml scm:svn:svn://host/project/trunk svn:svn://host/project/trunk svn://host/project/trunk in each case i got the error [ You must provide a valid url ] First i searched the mailing list and found some older posts like following: http://www.nabble.com/forum/ViewPost.jtp?post=3104276framed=yskin=177 In this post Emmanuel Venisse stated, that the scm through the svn protocol will be supported in a future version, ok this post is from Feb 24, 2006, so maybe obsolet. Then i found this from Feb 19,2007 http://www.nabble.com/forum/ViewPost.jtp?post=9042261framed=yskin=177 there Emmanuel refer to the Maven 2 URL format definition (http://maven.apache.org/scm/subversion.html). So my questions are, do i have to specify the filename pom.xml in the URL? Should i build Continuum from HEAD, to get latest version, and in this latest version is the svn protocol supported? My env: - Windows 2000 - Maven 2.0.4 - Continuum 1.0.3 Thanks in advance Roland This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] -- Roland Klein Tel: +49 40 65803 209 Fax: +49 40 65803 392 [EMAIL PROTECTED] MTG Marinetechnik GmbH - Wandsbeker Koenigstr. 62 - D 22041 Hamburg GF Dipl.-Ing. Ullrich Keil Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66 USt.-IdNr.: DE 1186 70571
Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository
Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Well, Artifactory actually started out as a series as patches on m2proxy and ended in a complete rewrite of it. The extras that we did came from real world requirements. The old m2proxy might still answer your every need in your development environment, and that's fine. Artifactory is used today by a couple of very large distributed development environments and that's where it really makes a difference. It offers everything that m2proxy used to offer + enterprise features such as: - Ability to deploy a mesh of proxies, each site proxying another. - Enhanced security for controlling who can deploy/undeploy to where. - Multiple local repositories support with control on what can be deployed to each repo, either by include/exclude patterns or by snapshot/releases. - Optional authenticated download of artifacts from local repositories - Web based deployment, including extraction a pom embedded in a deployed jar for a single transaction deployment of both jar and its pom. - HTTP(s) or WebDav deployment - Advanced indexing - Much improved web UI There's a more detailed feature description at: http://www.jfrog.org/sites/artifactory/latest/introduction.html Yoav Kalle Korhonen-2 wrote: Interesting. To this date, there's at least maven-proxy ( http://maven-proxy.codehaus.org/), Proximity ( http://proximity.abstracthorizon.org/), Archiva ( http://maven.apache.org/archiva/) and now, Artifactory, for more of less the same purpose. They are all Apache2 type licensed. We still use maven-proxy, and while it's only at version 0.2 and its development has stopped, we haven't seen any issues with it. Are any of these based on other's codebase or separate efforts and does anybody have any idea what the practical differences between all these are to the end user? Kalle On 3/4/07, Yoav Landman [EMAIL PROTECTED] wrote: Hi all, We would like to announce the immediate availability of Artifactory, a Maven 2 enterprise proxy. Artifactory offers
Adding project with many sub modules
Hi all, I am using continuum to build a project which contains upwards of 90+ modules in a nested hierarchy. When I create a new project from the root pom I end up getting a project for each sub pom as well. Is there any way to change this behavior so only the single project gets created. Or perhaps a quick way to batch delete all the sub projects. Thanks, -Justin
RE: Adding project with many sub modules
See http://jira.codehaus.org/browse/CONTINUUM-1178 I was thinking about creating a patch to do this. I looked into it and the modification would be pretty simple but I just haven't had the time yet. :) -Original Message- From: Justin Deoliveira [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 9:29 AM To: continuum-users@maven.apache.org Subject: Adding project with many sub modules Hi all, I am using continuum to build a project which contains upwards of 90+ modules in a nested hierarchy. When I create a new project from the root pom I end up getting a project for each sub pom as well. Is there any way to change this behavior so only the single project gets created. Or perhaps a quick way to batch delete all the sub projects. Thanks, -Justin The sender believes that this E-mail and any attachments were free of any harmful and malicious code or defects when sent. The sender is not liable for any loss or damage arising in any way from this message or its attachments. Confidentiality Note: This e-mail is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, is prohibited. If you have received this e-mail in error, please inform the sender, and destroy the original message and all copies.
RE: [m2] [ANN] Artifactory - new Maven 2 proxy repository
Thanks for the quick reply. I still can't get web dav to work. I did exactly what you suggested. Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies to maven's lib folder. - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav org/apache/commons/httpclient/URIException Anything else I need to do? I am using Maven 2.0.5. However, I now managed to use HTTP upload: distributionManagement repository idartifactory-server/id urlhttp://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement Still, I would love to be able to use web dav as well. Which way would be better? What's the preferred/most reliable way to deploy to an Artifactory repository? Thanks, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederic Simon Sent: Dienstag, 6. März 2007 15:01 To: Maven Users List Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Well, Artifactory actually started out as a series as patches on m2proxy and ended in a complete rewrite of it. The extras that we did came from real world requirements. The old m2proxy might still answer your every need in your development environment, and that's fine. Artifactory is used today by a couple of very large distributed development environments and that's where it really makes a difference. It offers everything that m2proxy used to offer + enterprise features such as: - Ability to deploy a mesh of proxies, each site proxying another. - Enhanced security for controlling who can deploy/undeploy to where. -
Re: Archetype: create resources as companions to java source files
Any point in me looking at it at this point? The structure you have in the quickstart matches what I'm trying to do. On 3/3/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 3/3/07, Wendy Smoak [EMAIL PROTECTED] wrote: Howard, can you take a look at it? It demonstrates your use case with a .properties file, and also one with html files for Javadoc that I ran into with an archetype for Shale. FYI: http://jira.codehaus.org/browse/ARCHETYPE-65 Restore the ability to package non-Java resources -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Username and password for deploy plugin
Thanks. Yes that issue is similar to what I'm asking for. I linked my issue to that one, and voted for it. I also found this issue which is the same as what I was asking for: http://jira.codehaus.org/browse/WAGON-52 On Sat, 2007-03-03 at 16:50 +0530, Gregory Kick wrote: I think that you might be talking about what was reported in http://jira.codehaus.org/browse/MNG-553 . This issue was reported a long time ago and doesn't seem to be getting much attention anymore... Maybe a few more votes for it? On 3/3/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 2/28/07, Paul Gier [EMAIL PROTECTED] wrote: Is there a way to supply a username and password for a remote repository on the command line instead of in the settings.xml? It would be helpful if the deploy plugin could prompt the user as needed for this information. The password could be hidden from view this way, and developers would not have to worry about configuring settings.xml. Specifically, I would like to have this feature for the wagon-webdav plugin, but I think it could apply to all the deploy related plugins. No idea if it takes userid/password on the command line, but there is some work in the gpg plugin to prompt for a passphrase (and mask it). Perhaps that could be borrowed. (wagon-webdav isn't a plugin, is it? I only know it as an artifact that needs to be configured as a build extension or otherwise added to Maven since it doesn't support dav by default.) -- Wendy - 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] [ANN] Artifactory - new Maven 2 proxy repository
You just got into a maven extensions issue. Maven extensions needs to be in the maven local repository so they will be activated, not in the lib dir. I also did a mistake in my command it is -Dpackaging=jar not -Dtype=... The dav wagon is on repo1.maven.org. If you cannot access it deploy the jar (and check the embeded pom deployed should have dependencies) with artifactory web interface. If pom deployment fails, deploy the pom by itself. Then you can use artifactory as repository and maven should download and activate web-dav. If Artifactory is behind Apache (with mod_jk), you may get dav protocol errors. Good luck. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: Thanks for the quick reply. I still can't get web dav to work. I did exactly what you suggested. Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies to maven's lib folder. - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav org/apache/commons/httpclient/URIException Anything else I need to do? I am using Maven 2.0.5. However, I now managed to use HTTP upload: distributionManagement repository idartifactory-server/id urlhttp://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement Still, I would love to be able to use web dav as well. Which way would be better? What's the preferred/most reliable way to deploy to an Artifactory repository? Thanks, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederic Simon Sent: Dienstag, 6. März 2007 15:01 To: Maven Users List Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED] /url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy
Re: [m2] How to specify the next version of a project when releasing (in batch mode) ?
Not starting with a letter, but letters are used in the version of the Xpp3 parser: http://www.extreme.indiana.edu/dist/java-repository/xpp3/jars/ Yes I'm extremely familiar with Xpp3... I've even filed a few bugs against it a while back when the versions and classifiers in the poms weren't quite correct. But that doesn't *start* with a letter so it doesn't count -- I think we're all familiar with alpha, beta, rc, etc versioning elements. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Plugin does not exist or no valid version could be found
Search the mailing list archives at Nabble.com for ntlm... As I recall, many people are using a program called ntlmaps when they are dealing with NTLM proxies. But I don't know any specifics as I've not had to deal with them as yet. Wayne On 3/6/07, Thorsten Heit [EMAIL PROTECTED] wrote: Hi, Thorsten, how can I determine the proxy I use? (NTLM or not) You should ask your network administrator; (s)he should be able to tell you that... And which post you are referring to? Don't remember; I only know that I have seen several posts about NTLM proxies Cheers Thorsten - 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] dependency order in 2.0.5
I'm not sure about how maven does this, but matching the first encountered does not necessarily imply anything sorted. On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I'd like to have more information about the new way to resolve dependencies in maven 2.0.5. In the release notes, you write ...when two exist at the same depth in the dependency graph, by matching the first encountered.. Picking up the FIRST element means there's a sorted list somewhere... But how are dependencies sorted in the parsing ? I've changed the order of dependencies in the pom many times to test the behaviour, and I noticed that nothing changed at all ! At the same depth, the dependency resolution order shown in the log (with the -X option) is always the same. I guess some kind of hash map may be used to store dependencies, and iterating on this map always gives the exact same order each time ?? So I agree that this method will be totally determinist, but wouldn't it be better to take the MOST RECENT version when you have two identical artefacts at the same depth level ? In this latest maven version, users have no way to influence on the dependency to be used by ordering manually the items in the pom, so they're forced to put these dependencies at a higher level in the graph, which will unnecessarily increase the poms size... What's your point of view about that ? Thanks for your help ! Isabelle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Profiles, settings, and distributionManagement
Hi, I'm confused. I want to have two profiles with different repositories and distributionManagement elements. I've created a settings.xml and defined the new profiles in it. Putting repositories in settings.xml is ok, but putting distributionManagement seems to be illegal. Why? What's wrong with saying that dev builds deploy artifacts to server A, and cert builds deploy to server B? Is there a philosophical idea that settings.xml is only used for bootstrapping? How do I handle this correctly? Do I add profile iddev/id repositories.../repositories /profile To settings.xml and then override in the POM with profile iddev/id distributionManagement.../distributionManagement /profile This seems awkward. Thanks, Christopher Helck Thank you for being part of it. The information contained in this e-mail is confidential. This e-mail is intended only for the stated addressee. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system. EBS Dealing Resources International Limited. Registered address: 2 Broadgate, London EC2M 7UR, United Kingdom. Registered number 2669861. EBS Dealing Resources, Inc, registered in Delaware. Address: Harborside Financial Center, 1100 Plaza Five, 12th Floor Jersey City, New Jersey 07311-4996 and One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA. EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku, Tokyo 104-0033, Japan.
Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository
Just a simple question about artifactory features : Does it support BOTH maven1 style and maven2 style for artifact requests ? For example, if my repo has javax/servlet/servlet-api/2.3/servlet- api-2.3.jar and I ask for /javax.servlet/jars/servlet-api-2.3.jar, do I get the expected jar ? If answer is yes, will artifactiry handle maven2 meta-data for relocation ? If I request servletapi/jars/servletapi-2.3.jar will it read the servletapi-2.3.pom and use relocation infos to return the relocated servlet-api-2.3.jar ? thanks. 2007/3/6, Frederic Simon [EMAIL PROTECTED]: You just got into a maven extensions issue. Maven extensions needs to be in the maven local repository so they will be activated, not in the lib dir. I also did a mistake in my command it is -Dpackaging=jar not -Dtype=... The dav wagon is on repo1.maven.org. If you cannot access it deploy the jar (and check the embeded pom deployed should have dependencies) with artifactory web interface. If pom deployment fails, deploy the pom by itself. Then you can use artifactory as repository and maven should download and activate web-dav. If Artifactory is behind Apache (with mod_jk), you may get dav protocol errors. Good luck. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: Thanks for the quick reply. I still can't get web dav to work. I did exactly what you suggested. Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies to maven's lib folder. - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav org/apache/commons/httpclient/URIException Anything else I need to do? I am using Maven 2.0.5. However, I now managed to use HTTP upload: distributionManagement repository idartifactory-server/id urlhttp://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement Still, I would love to be able to use web dav as well. Which way would be better? What's the preferred/most reliable way to deploy to an Artifactory repository? Thanks, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederic Simon Sent: Dienstag, 6. März 2007 15:01 To: Maven Users List Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED] /url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without
[m2] How to have target/classes in the plugin classpath?
Hi,
I can't figure out how what I should do to make the target/classes content
(populated in the compile phase) be in the classpath of the plugin,
because the plugin needs to access some resources..
My MOJO definition is just:
/*
* @goal run
* @requiresDependencyResolution runtime
* @execute phase=compile
* @phase process-classes
*
*/
public class LauncherMojo extends AbstractMojo {
// ...
}
Any suggestion?
Thanks a lot in advance,
Alessio Pace.
Would maven 2 help me with some dependencies evolution issues ?
Hi all, [Using Maven 1 can maven 2 help me here ?] I have a common dependency D (jar), used by multiple main modules Ma, Mb (wars), all bundled into an ear E (the jar is not deployed in the webapp, but in the ear). The first version of the ear E is easy to build. D1, Ma1, Mb1, E1. When only a part of the ear dependencies evolves, making a new version of the ear is much more complex. For example, we add features in Ma (so Ma2) , which requires modification (let's say compatible with D1) of the common dependency D (so D2), but no change on Mb (Mb1). When I try to create E2, using D2 in the project.xml, we have the following issues : - I have no automated way to check that Mb1 runs with D2 without creating a new version of Mb (whose only difference would be a single line in project.xml) - E2 doesn't work, because Mb1 inside, has a manifest which looks up for D-1.jar, whereas E2 contains D-2.jar. I would need to issue a new version of Mb just to declare new versions of dependencies ? Now actually our project has a dozen of common dependences (the D above) and 4 ou 5 wars (the Ms above). I fear configuration management will become a nightmare. Would Maven 2 help me build a E2 without issuing new versions of every unmodified module ? I find the maven 2 transitive dependency feature quite confusing on paper. Thanks in advance for your help.
included features with PDE-maven-plugin
Hello
I am using the PDE-maven plugin to build plugins.
I have a first core plugin. I placed a pom.xml in the features repository
and the build is ok. It takes into account the features and all the plugins
listed in it.
Then I have a second plugin, which features includes my first core plugin's
features. The PDE-maven plugin detects correctly this dependency and places
the needed first plugins in the temprorary repository of the second features
plugin. So it seems ok. Then it builds the second plugin itself, and this
build failed because it can't find the first plugins ! Actually, when I am
looking in the build.xml file, I see that the javac classpath pointed to the
/plugins repositories instead of the temp repository of the features, where,
juste before, the right plugins have been placed !
I don't know if I am clear enough, but it is really a problem for me because
I can't build plugins that depends on others plugins.
If someone has any ideas...
Magali Helene
--
in my build.xml of the plugin:
javac destdir=${temp.folder}/arpchangerclient.jar.bin
failonerror=${javacFailOnError} verbose=${javacVerbose}
debug=${javacDebugInfo} includeAntRuntime=no
bootclasspath=${bootclasspath} source=${javacSource}
target=${javacTarget}
compilerarg line=${compilerArg}/
classpath
pathelement path=../../../../../../../Program
Files/eclipse
3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar/
pathelement path=../../../../../../../Program
Files/eclipse 3.0.2/eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar/
.
.
.
pathelement path=../FR - Plugin Core/arpcore.jar/
pathelement path=../NL - Plugin Core/arpcoreus.jar/
/classpath
src path=src//
/javac
instead of ?
pathelement path=${pluginTemp}/FR - Plugin
Core/arpcore.jar/
pathelement path=${pluginTemp}/NL - Plugin
Core/arpcoreus.jar/
--
View this message in context:
http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9335496
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
server side includes for site
Is there something like server side includes for site/xdocs? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: After attempting download from repo1, build fails?
Sounds like a transient network failure caused the pom download to fail, which caused the rest of your build to fail. What exactly is the question/problem? Wayne On 3/6/07, Dees, Ian (GE Healthcare) [EMAIL PROTECTED] wrote: Hi list, I'm trying to upgrade surefire to version 2.3. I switched the dependency version in our projects' POM files on and did a build on my local machine, allowing it through our proxy to determine what new files were needed. I copied these updates and dependencies over to our local repository (we don't have a maven proxy set up yet) and ran the build on the nightly-build server (which we purposefully don't allow through the proxy). Anyway, instead of attempting to download the new surefire-2.3 from the local repository, the build failed (and did not continue) when it could not reach repo1: [DEBUG] Skipping disabled repository plugin-snapshots [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-pl ugin/2.3/maven-surefire-plugin-2.3.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-surefire-plugin Reason: Error getting POM for 'org.apache.maven.plugins:maven-surefire-plugin' from the repository: Error transferring file org.apache.maven.plugins:maven-surefire-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), ge-central (http://maven/svn/3p-lib/main) Does this make sense? Thanks, Ian - 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]
After attempting download from repo1, build fails?
Hi list, I'm trying to upgrade surefire to version 2.3. I switched the dependency version in our projects' POM files on and did a build on my local machine, allowing it through our proxy to determine what new files were needed. I copied these updates and dependencies over to our local repository (we don't have a maven proxy set up yet) and ran the build on the nightly-build server (which we purposefully don't allow through the proxy). Anyway, instead of attempting to download the new surefire-2.3 from the local repository, the build failed (and did not continue) when it could not reach repo1: [DEBUG] Skipping disabled repository plugin-snapshots [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-pl ugin/2.3/maven-surefire-plugin-2.3.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-surefire-plugin Reason: Error getting POM for 'org.apache.maven.plugins:maven-surefire-plugin' from the repository: Error transferring file org.apache.maven.plugins:maven-surefire-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2), ge-central (http://maven/svn/3p-lib/main) Does this make sense? Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] How to get project version in an xdoc
I have found a solution in a previous thread:
http://www.nabble.com/-M2--Insert-variables-in-xdoc-apt-files-tf1956665s177.html#a5371135
That fix my problem
JC Walmetz wrote:
Im writting a XDoc document that will be used by the site plugin. In this
document I need to write the version of the project.
I have tried to write ${project.version} but when the site is generated,
it is not replaced by the project version.
Is it possible to get the project version in an Xdoc used by the site
plugin ?
-
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions ! Profitez des connaissances, des opinions et des expériences
des internautes sur Yahoo! Questions/Réponses.
--
View this message in context:
http://www.nabble.com/How-to-get-project-version-in-an-xdoc-tf3354200s177.html#a9335686
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: included features with PDE-maven-plugin
Does the second plugin has its own feature.xml?
On 3/6/07, Magali Helene [EMAIL PROTECTED] wrote:
Hello
I am using the PDE-maven plugin to build plugins.
I have a first core plugin. I placed a pom.xml in the features repository
and the build is ok. It takes into account the features and all the
plugins
listed in it.
Then I have a second plugin, which features includes my first core
plugin's
features. The PDE-maven plugin detects correctly this dependency and
places
the needed first plugins in the temprorary repository of the second
features
plugin. So it seems ok. Then it builds the second plugin itself, and this
build failed because it can't find the first plugins ! Actually, when I am
looking in the build.xml file, I see that the javac classpath pointed to
the
/plugins repositories instead of the temp repository of the features,
where,
juste before, the right plugins have been placed !
I don't know if I am clear enough, but it is really a problem for me
because
I can't build plugins that depends on others plugins.
If someone has any ideas...
Magali Helene
--
in my build.xml of the plugin:
javac destdir=${temp.folder}/arpchangerclient.jar.bin
failonerror=${javacFailOnError} verbose=${javacVerbose}
debug=${javacDebugInfo} includeAntRuntime=no
bootclasspath=${bootclasspath} source=${javacSource}
target=${javacTarget}
compilerarg line=${compilerArg}/
classpath
pathelement path=../../../../../../../Program
Files/eclipse
3.0.2/eclipse/plugins/org.eclipse.core.runtime_3.0.2/runtime.jar/
pathelement path=../../../../../../../Program
Files/eclipse 3.0.2/eclipse/plugins/org.eclipse.osgi_3.0.1/core.jar/
.
.
.
pathelement path=../FR - Plugin Core/arpcore.jar/
pathelement path=../NL - Plugin
Core/arpcoreus.jar/
/classpath
src path=src//
/javac
instead of ?
pathelement path=${pluginTemp}/FR - Plugin
Core/arpcore.jar/
pathelement path=${pluginTemp}/NL - Plugin
Core/arpcoreus.jar/
--
View this message in context:
http://www.nabble.com/included-features-with-PDE-maven-plugin-tf3356596s177.html#a9335496
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: deploying an axis service
Thanks Robert. I was able to use the assembly plugin to copy the artifacts into the axis lib. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Watkins Sent: Monday, March 05, 2007 5:38 PM To: Maven Users List Subject: Re: deploying an axis service On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: But, lets say for example all I had was a command line app. I want to build and run my app. In order to run it, I need all the dependencies. How would I get them all copied to the same place for easy access? That's what the assembly plugin is for; amongst other things, it can pull copies of your compile runtime dependent artifacts together for you to package. -- Software is too expensive to build cheaply Robert Watkins http://twasink.net/ [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
binding goals to a phase
I'm trying to get my build to execute goals of a plugin during a phase. There is plenty of documentation available how to do this, but I can't get it to work. Is there a setting somewhere that I need to turn executions on? The XML below will run fine with mvn antrun:run, but when I run mvn compile, the antrun:run goal does not get executed. Any ideas what I could be doing wrong? I'm using 2.0.5 plugin artifactIdmaven-antrun-plugin/artifactId configuration tasks echoHurray it Worked!/echo /tasks /configuration executions execution idsomeid/id goals goalrun/goal /goals phasecompile/phase inheritedfalse/inherited /execution /executions /plugin Kurt
Re: [m2] Build-number plug-in and install goal conflict?
There's no way to do this that I know of. The install goal generates it's own finalName and ignores any finalName that has been specified in the build section of the pom, while the package goal, for instance, respects the finalName. It's not got anything to do with the build number plugin. J On 5-Mar-07, at 12:37 PM, Satish wrote: Is it possible to retrieve the SVN version number to map the build number during mvn install and pulling this to bundle as part of war/jar file. -- Julian Wood [EMAIL PROTECTED] Software Engineer Teaching Learning Centre University of Calgary http://tlc.ucalgary.ca
Re: binding goals to a phase
Is this description in the pom you are running, or in a parent pom? If the latter, you have inherited turned off so it won't work. If the former, could you send the command-line args you use and the output? This shouldn't happen. Eric On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get my build to execute goals of a plugin during a phase. There is plenty of documentation available how to do this, but I can't get it to work. Is there a setting somewhere that I need to turn executions on? The XML below will run fine with mvn antrun:run, but when I run mvn compile, the antrun:run goal does not get executed. Any ideas what I could be doing wrong? I'm using 2.0.5 plugin artifactIdmaven-antrun-plugin/artifactId configuration tasks echoHurray it Worked!/echo /tasks /configuration executions execution idsomeid/id goals goalrun/goal /goals phasecompile/phase inheritedfalse/inherited /execution /executions /plugin Kurt -- Eric Redmond http://codehaus.org/~eredmond
Tools.jar Apple
Hello, I am trying to get the jaxws-maven-plugin up and running on my box. Evidently Apple has been kind enough to stick tools.jar elsewhere. Any reason why the snippet below wouldn't work? -Ryan Snippet: plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdjaxws-maven-plugin/artifactId version1.0-beta-1-SNAPSHOT/version executions execution goals goalwsgen/goal /goals /execution /executions configuration seinet.cuprak.ryanportal/sei genWsdltrue/genWsdl /configuration dependencies dependency groupIdsun.jdk/groupId artifactIdtools/artifactId version1.5.0/version systemPath/System/Library/Frameworks/ JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath scopesystem/scope /dependency /dependencies /plugin /plugins - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tools.jar Apple
I don't think you need to add tools.jar as a dependency on Mac. See http://maven.apache.org/general.html#tools-jar-dependency Chris -Original Message- From: Ryan Cuprak [mailto:[EMAIL PROTECTED] Sent: Tuesday, 06 March, 2007 13:19 To: Maven Users List Subject: Tools.jar Apple Hello, I am trying to get the jaxws-maven-plugin up and running on my box. Evidently Apple has been kind enough to stick tools.jar elsewhere. Any reason why the snippet below wouldn't work? -Ryan Snippet: plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdjaxws-maven-plugin/artifactId version1.0-beta-1-SNAPSHOT/version executions execution goals goalwsgen/goal /goals /execution /executions configuration seinet.cuprak.ryanportal/sei genWsdltrue/genWsdl /configuration dependencies dependency groupIdsun.jdk/groupId artifactIdtools/artifactId version1.5.0/version systemPath/System/Library/Frameworks/ JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath scopesystem/scope /dependency /dependencies /plugin /plugins - 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: Tools.jar Apple
That didn't work either, complete pom.xml is below... this is really baffling. I have it sprinkled liberally throughout the file. 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 groupIdnet.cuprak.ryanportal/groupId artifactIdryanportal/artifactId packagingwar/packaging version1.0-SNAPSHOT/version nameryanportal Maven Webapp/name urlhttp://maven.apache.org/url dependencies dependency groupIdsun.jdk/groupId artifactIdtools/artifactId version1.5.0/version systemPath/System/Library/Frameworks/JavaVM.framework/ Versions/1.5/Classes/classes.jar/systemPath scopesystem/scope /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId version2.1/version /dependency dependency groupIdcom.sun.xml.ws/groupId artifactIdjaxws-rt/artifactId version2.1EA1/version /dependency dependency groupIdjavax.jws/groupId artifactIdjsr181/artifactId version1.0/version /dependency dependency groupIdcom.sun.xml/groupId artifactIdjaxws-tools/artifactId version2.0EA3/version /dependency /dependencies build finalNameryanportal/finalName plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdjaxws-maven-plugin/artifactId version1.0-beta-1-SNAPSHOT/version executions execution goals goalwsgen/goal /goals /execution /executions configuration seinet.cuprak.ryanportal/sei genWsdltrue/genWsdl /configuration dependencies dependency groupIdsun.jdk/groupId artifactIdtools/artifactId version1.5.0/version systemPath/System/Library/Frameworks/ JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath scopesystem/scope /dependency /dependencies /plugin /plugins /build repositories repository idCodehaus Snapshots/id urlhttp://snapshots.repository.codehaus.org//url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idCodehaus Snapshots/id urlhttp://snapshots.repository.codehaus.org//url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories profiles profile iddefault-tools.jar/id activation property namejava.vendor/name valueSun Microsystems Inc./value /property /activation dependencies dependency groupIdcom.sun/groupId artifactIdtools/artifactId version1.5.0/version scopesystem/scope systemPath/System/Library/Frameworks/ JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath /dependency /dependencies /profile /profiles /project On Mar 6, 2007, at 2:21 PM, Chris Hilton wrote: I don't think you need to add tools.jar as a dependency on Mac. See http://maven.apache.org/general.html#tools-jar-dependency Chris -Original Message- From: Ryan Cuprak [mailto:[EMAIL PROTECTED] Sent: Tuesday, 06 March, 2007 13:19 To: Maven Users List Subject: Tools.jar Apple Hello, I am trying to get the jaxws-maven-plugin up and running on my box. Evidently Apple has been kind enough to stick tools.jar elsewhere. Any reason why the snippet below wouldn't work? -Ryan Snippet: plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdjaxws-maven-plugin/artifactId version1.0-beta-1-SNAPSHOT/version executions execution
Re: Tools.jar Apple
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] PVCS SCM
I'm afraid the donation of a plugin by serena is in a bad way. Few month ago we ask to Serena if it was planned. Their answer was NO. It looks it somewhere in a wish list. Maybe if you are a Serena Customer you can contact their support. In JIRA there is a startup for a PVCS plugin (just the checkout from what I remember). I have implement some more task but that's not tested. I'll try to find the bug in JIRA and to add my plugins. I use it to release my projects with the release plugin. Gregory Kick-2 wrote: A while back there was some talk of a PVCS integration being donated. Did anything ever come of that? Has anyone successfully used maven with pvcs? Thanks, -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/PVCS-SCM-tf3353835s177.html#a9339363 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: Tools.jar Apple
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
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: binding goals to a phase
Yes, it is in the pom that I am running. Here is the output. Thanks. C:\ BrightonCommonmvn compile [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - medstat:BrightonCommon:jar:1.0-SNAPSHOT [INFO]task-segment: [compile] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/jsr170/jcr/1.0/jcr-1.0.pom [WARNING] Unable to get resource 'jsr170:jcr:pom:1.0' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom [WARNING] Unable to get resource 'axis:axis-jaxrpc:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom [WARNING] Unable to get resource 'axis:axis-saaj:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/google/gwt/user/1.2.22/user-1.2.22.pom [WARNING] Unable to get resource 'com.google.gwt:user:pom:1.2.22' from repository central (http://repo1.maven.org/maven2 ) [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Mar 06 14:39:37 EST 2007 [INFO] Final Memory: 3M/6M [INFO] Kurt -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 2:16 PM To: Maven Users List Subject: Re: binding goals to a phase Is this description in the pom you are running, or in a parent pom? If the latter, you have inherited turned off so it won't work. If the former, could you send the command-line args you use and the output? This shouldn't happen. Eric On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get my build to execute goals of a plugin during a phase. There is plenty of documentation available how to do this, but I can't get it to work. Is there a setting somewhere that I need to turn executions on? The XML below will run fine with mvn antrun:run, but when I run mvn compile, the antrun:run goal does not get executed. Any ideas what I could be doing wrong? I'm using 2.0.5 plugin artifactIdmaven-antrun-plugin/artifactId configuration tasks echoHurray it Worked!/echo /tasks /configuration executions execution idsomeid/id goals goalrun/goal /goals phasecompile/phase inheritedfalse/inherited /execution /executions /plugin Kurt -- Eric Redmond http://codehaus.org/~eredmond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Order of plugin execution
Hello... Could the users of assembly plugin tell me to which phase of the lifecycle they bind the assembly plugin to? Also, how do I order the execution of plugins attached to the same phase in the scope of the current POM? Any help appreciated... Regards, /U -- Original message -- From: [EMAIL PROTECTED] I assumed that order of execution of plugins would be the order in which they are listed in the current POM and found out soon that that is a naive assumption (in M2). I also see that the problem exposes the complexity of Maven's POM inheritance that its quite difficult to determine the order of execution of plugins from ancestor/parent/current POMs. I have run into the problem in running the assembly plugin; I am creating a zip assembly of my resources and hence need to run resources:resources followed by assembly:attached in the 'install' phase of build lifecycle (pl see below). The parent/ancestor POM does not specify any overrides for either of the two plugins (resources or assembly). I see tha tth eproblem is described and solution suggested at http://docs.codehaus.org/display/MAVEN/Suppression,+Ordering,+and+Replacement+of +Plugins+and+Mojos+Bindings but do not see that Maven 2.0.4 has the executionOrder tags. To sum it up, when 'mvn install' is run, I need this POM to execute resources:resources followed by assembly:attached. What is the simplest way to accomplish this? Any hints greatly appreciated! Thanks, /U // Current POM plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId !-- ! Make sure that that when 'mvn install' is run, resources ! will be copied to the target directory for assembly plugin ! (below) to act on. !-- executions execution idinstall-resources/id !-- this is used for inheritance merges -- phaseinstall/phase !-- append to the packaging phase. -- goals goalresources/goal !-- goals == mojos -- /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/main/assembly/package.xml/descriptor /configuration !-- ! Bind the assembly plugin to the install goal in the ! build lifecycle. This implies that when 'mvn install' ! is run, this zip assembly will be produced. !-- executions execution idmake-assembly/id !-- this is used for inheritance merges -- phaseinstall/phase !-- append to the packaging phase. -- goals goalattached/goal !-- goals == mojos -- /goals /execution /executions /plugin - 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: Tools.jar Apple
Managed to get around the problem. I edited the pom file under .m2
to point directly at the classes.jar file on MacOS X. A bit of a hack
but it worked.
-Ryan
On Mar 6, 2007, at 2:37 PM, Ryan Cuprak wrote:
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
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: Tools.jar Apple
Apple renames tools.jar to classes.jar?
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Managed to get around the problem. I edited the pom file under .m2
to point directly at the classes.jar file on MacOS X. A bit of a hack
but it worked.
-Ryan
On Mar 6, 2007, at 2:37 PM, Ryan Cuprak wrote:
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
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: binding goals to a phase
Your configuration element with the task definition needs to be specified within the context of the execution 'someid', not the standard plugin configuration element. plugin artifactIdmaven-antrun-plugin/artifactId executions execution idsomeid/id phasecompile/phase configuration tasks echoHurray it Worked!/echo /tasks /configuration goals goalrun/goal /goals inheritedfalse/inherited /execution /executions /plugin Hope this helps, -Brad On Tue, 2007-03-06 at 14:43 -0500, [EMAIL PROTECTED] wrote: Yes, it is in the pom that I am running. Here is the output. Thanks. C:\ BrightonCommonmvn compile [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - medstat:BrightonCommon:jar:1.0-SNAPSHOT [INFO]task-segment: [compile] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/jsr170/jcr/1.0/jcr-1.0.pom [WARNING] Unable to get resource 'jsr170:jcr:pom:1.0' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom [WARNING] Unable to get resource 'axis:axis-jaxrpc:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom [WARNING] Unable to get resource 'axis:axis-saaj:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/google/gwt/user/1.2.22/user-1.2.22.pom [WARNING] Unable to get resource 'com.google.gwt:user:pom:1.2.22' from repository central (http://repo1.maven.org/maven2 ) [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Mar 06 14:39:37 EST 2007 [INFO] Final Memory: 3M/6M [INFO] Kurt -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 2:16 PM To: Maven Users List Subject: Re: binding goals to a phase Is this description in the pom you are running, or in a parent pom? If the latter, you have inherited turned off so it won't work. If the former, could you send the command-line args you use and the output? This shouldn't happen. Eric On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get my build to execute goals of a plugin during a phase. There is plenty of documentation available how to do this, but I can't get it to work. Is there a setting somewhere that I need to turn executions on? The XML below will run fine with mvn antrun:run, but when I run mvn compile, the antrun:run goal does not get executed. Any ideas what I could be doing wrong? I'm using 2.0.5 plugin artifactIdmaven-antrun-plugin/artifactId configuration tasks echoHurray it Worked!/echo /tasks /configuration executions execution idsomeid/id goals goalrun/goal /goals phasecompile/phase inheritedfalse/inherited /execution /executions /plugin Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: binding goals to a phase
Thanks Brad. I've tried that setup and it doesn't work either. -Original Message- From: Brad Szabo [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 3:19 PM To: Maven Users List Subject: RE: binding goals to a phase Your configuration element with the task definition needs to be specified within the context of the execution 'someid', not the standard plugin configuration element. plugin artifactIdmaven-antrun-plugin/artifactId executions execution idsomeid/id phasecompile/phase configuration tasks echoHurray it Worked!/echo /tasks /configuration goals goalrun/goal /goals inheritedfalse/inherited /execution /executions /plugin Hope this helps, -Brad On Tue, 2007-03-06 at 14:43 -0500, [EMAIL PROTECTED] wrote: Yes, it is in the pom that I am running. Here is the output. Thanks. C:\ BrightonCommonmvn compile [INFO] Scanning for projects... [INFO] [INFO] Building Unnamed - medstat:BrightonCommon:jar:1.0-SNAPSHOT [INFO]task-segment: [compile] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repo1.maven.org/maven2/jsr170/jcr/1.0/jcr-1.0.pom [WARNING] Unable to get resource 'jsr170:jcr:pom:1.0' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom [WARNING] Unable to get resource 'axis:axis-jaxrpc:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom [WARNING] Unable to get resource 'axis:axis-saaj:pom:1.4' from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/com/google/gwt/user/1.2.22/user-1.2.22.pom [WARNING] Unable to get resource 'com.google.gwt:user:pom:1.2.22' from repository central (http://repo1.maven.org/maven2 ) [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Mar 06 14:39:37 EST 2007 [INFO] Final Memory: 3M/6M [INFO] Kurt -Original Message- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 2:16 PM To: Maven Users List Subject: Re: binding goals to a phase Is this description in the pom you are running, or in a parent pom? If the latter, you have inherited turned off so it won't work. If the former, could you send the command-line args you use and the output? This shouldn't happen. Eric On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get my build to execute goals of a plugin during a phase. There is plenty of documentation available how to do this, but I can't get it to work. Is there a setting somewhere that I need to turn executions on? The XML below will run fine with mvn antrun:run, but when I run mvn compile, the antrun:run goal does not get executed. Any ideas what I could be doing wrong? I'm using 2.0.5 plugin artifactIdmaven-antrun-plugin/artifactId configuration tasks echoHurray it Worked!/echo /tasks /configuration executions execution idsomeid/id goals goalrun/goal /goals phasecompile/phase inheritedfalse/inherited /execution /executions /plugin Kurt - 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] [ANN] Artifactory - new Maven 2 proxy repository
Reading your needs, for first import of a lot of artifacts, you should use the Import/Export feature, which enables you to load in one click a full tree of a maven repository. That will give you a sense of the Derby DB speed ;-) I updated the doc http://www.jfrog.org/sites/artifactory/latest/firstImport.html On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: Thanks for the quick reply. I still can't get web dav to work. I did exactly what you suggested. Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies to maven's lib folder. - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav org/apache/commons/httpclient/URIException Anything else I need to do? I am using Maven 2.0.5. However, I now managed to use HTTP upload: distributionManagement repository idartifactory-server/id urlhttp://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement Still, I would love to be able to use web dav as well. Which way would be better? What's the preferred/most reliable way to deploy to an Artifactory repository? Thanks, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederic Simon Sent: Dienstag, 6. März 2007 15:01 To: Maven Users List Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED] /url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of the box. Accessing the Web interface, you are then stuck with the login screen because the default credentials are not documented anywhere. I had to connect to the embedded Derby database to find them out. I then moved on and tried to set it up on Tomcat. After fiddling yet for another while, I discovered it needs a system property to be present. I don't like that. Anyways, it seems to be running fine now. The next step where I need help is in deploying to a local repository. I tried both HTTP and DAV without success. Using HTTP, the artifact was uploaded and then yielded an HTTP 500 error, DAV didn't work because the wagon was not found, even though I installed it and followed all the tips I found for using WebDAV with Maven. I am stuck now and would appreciate further help. I'd like to repeat that the product does look promising. Chances are good that we may replace Maven Proxy with it once we get these problems sorted. And please enhance the docs! Thanks, Reinhard -Original Message- From: Yoav Landman [mailto:[EMAIL PROTECTED] Sent: Montag, 5. März 2007 07:14 To: users@maven.apache.org Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Well, Artifactory actually started out as a series as patches on m2proxy and ended in a complete rewrite of it. The extras that we did came from real world requirements. The old m2proxy might still answer your every need in your development environment, and that's fine. Artifactory is used today by a
Re: Tools.jar Apple
There is no tools.jar on Mac. Instead, the classes from tools.jar are
included in a larger classes.jar file. Don't ask me...
Wayne
On 3/6/07, Dan Tran [EMAIL PROTECTED] wrote:
Apple renames tools.jar to classes.jar?
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Managed to get around the problem. I edited the pom file under .m2
to point directly at the classes.jar file on MacOS X. A bit of a hack
but it worked.
-Ryan
On Mar 6, 2007, at 2:37 PM, Ryan Cuprak wrote:
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Build dependencies into the jar file?
Dear All, What would be the best way to build all the dependencies into the resulting JAR file? I want the JAR file to be double-clickable. With Ant, I was using zipfileset. With Maven2 I have no idea how to run it on all the dependent JARs. Any help is appreciated, Sasha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Order of plugin execution
Assemblies bundle files into an artifact, so they tend to belong in the package phase. Eric On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello... Could the users of assembly plugin tell me to which phase of the lifecycle they bind the assembly plugin to? Also, how do I order the execution of plugins attached to the same phase in the scope of the current POM? Any help appreciated... Regards, /U -- Original message -- From: [EMAIL PROTECTED] I assumed that order of execution of plugins would be the order in which they are listed in the current POM and found out soon that that is a naive assumption (in M2). I also see that the problem exposes the complexity of Maven's POM inheritance that its quite difficult to determine the order of execution of plugins from ancestor/parent/current POMs. I have run into the problem in running the assembly plugin; I am creating a zip assembly of my resources and hence need to run resources:resources followed by assembly:attached in the 'install' phase of build lifecycle (pl see below). The parent/ancestor POM does not specify any overrides for either of the two plugins (resources or assembly). I see tha tth eproblem is described and solution suggested at http://docs.codehaus.org/display/MAVEN/Suppression,+Ordering,+and+Replacement+of +Plugins+and+Mojos+Bindings but do not see that Maven 2.0.4 has the executionOrder tags. To sum it up, when 'mvn install' is run, I need this POM to execute resources:resources followed by assembly:attached. What is the simplest way to accomplish this? Any hints greatly appreciated! Thanks, /U // Current POM plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-resources-plugin/artifactId !-- ! Make sure that that when 'mvn install' is run, resources ! will be copied to the target directory for assembly plugin ! (below) to act on. !-- executions execution idinstall-resources/id !-- this is used for inheritance merges -- phaseinstall/phase !-- append to the packaging phase. -- goals goalresources/goal !-- goals == mojos -- /goals /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptorsrc/main/assembly/package.xml/descriptor /configuration !-- ! Bind the assembly plugin to the install goal in the ! build lifecycle. This implies that when 'mvn install' ! is run, this zip assembly will be produced. !-- executions execution idmake-assembly/id !-- this is used for inheritance merges -- phaseinstall/phase !-- append to the packaging phase. -- goals goalattached/goal !-- goals == mojos -- /goals /execution /executions /plugin - 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] -- Eric Redmond http://codehaus.org/~eredmond
Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository
We currently support only Maven 2 clients. Technically, it should not be too difficult to add Maven 1, but we never needed it since none of the organizations we used Artifactory with was using Maven 1 for managing enterprise builds. As for support for relocation, I would assume this logic is embedded into the Maven client itself, so there should be no problem here nicolas de loof-2 wrote: Just a simple question about artifactory features : Does it support BOTH maven1 style and maven2 style for artifact requests ? For example, if my repo has javax/servlet/servlet-api/2.3/servlet- api-2.3.jar and I ask for /javax.servlet/jars/servlet-api-2.3.jar, do I get the expected jar ? If answer is yes, will artifactiry handle maven2 meta-data for relocation ? If I request servletapi/jars/servletapi-2.3.jar will it read the servletapi-2.3.pom and use relocation infos to return the relocated servlet-api-2.3.jar ? thanks. 2007/3/6, Frederic Simon [EMAIL PROTECTED]: You just got into a maven extensions issue. Maven extensions needs to be in the maven local repository so they will be activated, not in the lib dir. I also did a mistake in my command it is -Dpackaging=jar not -Dtype=... The dav wagon is on repo1.maven.org. If you cannot access it deploy the jar (and check the embeded pom deployed should have dependencies) with artifactory web interface. If pom deployment fails, deploy the pom by itself. Then you can use artifactory as repository and maven should download and activate web-dav. If Artifactory is behind Apache (with mod_jk), you may get dav protocol errors. Good luck. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: Thanks for the quick reply. I still can't get web dav to work. I did exactly what you suggested. Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies to maven's lib folder. - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav org/apache/commons/httpclient/URIException Anything else I need to do? I am using Maven 2.0.5. However, I now managed to use HTTP upload: distributionManagement repository idartifactory-server/id urlhttp://localhost:8080/artifactory/[EMAIL PROTECTED]/url /repository /distributionManagement Still, I would love to be able to use web dav as well. Which way would be better? What's the preferred/most reliable way to deploy to an Artifactory repository? Thanks, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederic Simon Sent: Dienstag, 6. März 2007 15:01 To: Maven Users List Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository Hi, Thanks for the comments, I will try to fix the doc, please review http://www.jfrog.org/sites/artifactory/latest/install.html where we talk about first admin user and system properties. For deploying you first local repository, we use the import from local disk feature. You need to create a clean maven repo tree with the standard groupId/artifactId/version/files on a disk accessible by Artifactory and then go to the import page and set the root folder of the above tree. For web dav, me I'm using a dummy pom.xml that looks like: ?xml version=1.0? 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 groupIdorg.artifactory.deploy-test/groupId artifactIdaye/artifactId version1.0-SNAPSHOT/version packagingjar/packaging distributionManagement repository idartifactory-server/id urldav:http://localhost:8080/artifactory/[EMAIL PROTECTED] /url /repository /distributionManagement build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build /project and from where this pom sits you can run: mvn deploy:deploy-file -DrepositoryId=artifactoryServer -Durl=dav:http://... -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... -Dclassifier=... Hope it helps. On 3/6/07, Reinhard Nägele [EMAIL PROTECTED] wrote: This looks quite interesting, and I started to play around with it. The biggest problem is the poor documentation. With Jetty, you can quickly start it out of
Re: Build dependencies into the jar file?
mvn assembly:assemble -DdescriptorId=jar-with-dependencies http://maven.apache.org/plugins/maven-assembly-plugin/ Eric On 3/6/07, Sasha O [EMAIL PROTECTED] wrote: Dear All, What would be the best way to build all the dependencies into the resulting JAR file? I want the JAR file to be double-clickable. With Ant, I was using zipfileset. With Maven2 I have no idea how to run it on all the dependent JARs. Any help is appreciated, Sasha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond
Selenium, profiles and executing certain browsers on certain OSs
I'm using the salenese Ant task to run some Selenium tests in my project.
I want tests to run in Firefox on all platforms, and Firefox and IE when
running on Windows. I've got everything working using the XML below, but
it's quite verbose. Is there a way to simplify, or is this the recommended
strategy?
profiles
profile
id${cargo.container}/id
activation
property
name!maven.test.skip/name
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version0.2/version
...
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName}//
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdorg.openqa.selenium.server/groupId
artifactIdselenium-server/artifactId
version0.9.1-SNAPSHOT/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
profile
idwindows/id
activation
os
familyWindows/family
/os
/activation
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName}//
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*iexplore
timeoutInSeconds=180
results=${project.build.directory}/selenium-ie-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName}//
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/Selenium%2C-profiles-and-executing-certain-browsers-on-certain-OSs-tf3358368s177.html#a9341212
Separation, webapp
Hi, To keep the users happy, I want to filter what projects they can see. There doesn't seem to be a build in feature for this (I see the user admin can block adding/edit/delete/etc of projects, but seems that all of the projects always show up on the home page). Is there a way to do this, or is our idea of installing 2 instances of Continuum the best approach? Does it also make sense to get the webapp version and install that onto Tomcat/Jboss or something similar? Thanks Gabriel Misura 20111 120th Ave NE, Cube 2337D Bothell, WA MSN: [EMAIL PROTECTED] Office: 425-288-6217
Re: [m2] multi project interdependencies
Good day to you, M, Yes, the current solution that I know of is to use mvn clean install. That is why that continuum uses that as its default build ( to prevent any adverse effect ). I am not sure though if the maven developers can find an alternative to that. On top of my head, I can only think of something like a force.compile for the maven-compiler-plugin. Cheers, Franz mark_in_gr wrote: Actually, it looks like what was happening is the error which was being caught by the compiler was a result of a private method name mismatch being called from the same class. There would really be no way for module a level above the module/dependency which has changed to know which classes in it's own module would be affected by the dependency change. Even Ant based projects which string targets together w/depends statements would result in the same behavior I am seeing w/Maven2. So, I would think a best practice here would be to perform a mvn clean install at the top level pom(where the modules are listed in my single level module list) every time a dependency module is rebuilt. Do you agree? franz see wrote: Good day to you, M, The steps I mentioned in my previous post still occurred. However, the compiler plugin does not compile if there are no changes in the source code. But in your example, it seems as though that it should have been recompiled. You may want to file a jira issue for that ( see [1] ). Cheers, Franz [1] http://jira.codehaus.org/browse/MCOMPILER mark_in_gr wrote: I don't believe this is correct, at least I am not able to get this to work. For example, if I have the following structure: Project Parent Module A Module B where Module B depends on Module A. If I force an issue in some code in Module A which is used in Module B and should case a compile time error in a class in Module B, then build(mvn package or mvn install) at the Project Parent Level, the code in Module A compiles(I see the message Compiling 1 source file to . . .), however, no classes in Module B are compiled!!(I see Nothing to compile - all classes are up to date). So, how is code in Module B going to be made aware of, say, a method being changed in a class in Module A??? if I run a mvn clean package or mvn clean install, everything works correctly seeing that all modules are completed rebuilt from scratch, but this goes against an incremental build process and is not an acceptable practice. My Project Parent level has a POM only, which Module A and Module B listed as Modules. In the Module B pom, Module A is listed as a dependency w/compile scope using the standard conventions(artifactId, groupId, etc.) and set up to use a snapshot. franz see wrote: Good day to you, M, Actually, it's subproject A - compile subproject A - test subproject A - jar subproject A - install subproject A - deploy subproject B - compile - in need of a subproject A jar (searching in repostitory) subproject B - test - proceeds only if an OLDER version is found subproject B - jar subproject B - install subproject B - deploy IRC, maven2 will first group your tasks to segments. And then those task segments would be executed one at a time. When one task segment finishes, the next will begin. All non-aggregating goals will be set as one task segment, then every aggregating goal will have their own task segment. Aggregating goals are those that run only on the project that you invoked it upon, while non-aggregating goals are those that run on the project you invoked it upon, plus, all modules under it. The project on which a non-aggregating goal will run on would then be ordered according to dependency, making sure that the dependencies are built before the dependees. The task segment for the non-aggregating goals would then be executed to each of those projects and according to which build lifecycle phase they are bound to. Thus, with a project project-a, with two modules, module-a and module-b, where module-b depends on module-a, if you run mvn deploy on project-a, the order of the projects would be project-a module-a module-b And on each project, the goals compiler:compile, surefire:test, jar:jar, install:install, deploy:deploy (among others) would be executed on each. Thus, it's like having cd project-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd module-a mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy cd ..\module-b mvn compiler:compiler mvn surefire:test mvn jar:jar mvn install:install mvn deploy:deploy ( more or less ). Cheers, Franz meberts wrote: Hi, you're saying: If a dependency of your maven project does not exist when you execute a maven command, then that project will not bulid ( assuming ofcourse the maven command requires a pom to
MultiModule checkstyle config
I've been trying to reproduce the example setup described in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html The example doesn't show me the pom.xml file to be used for the build-tools module. I tried making the obvious pom for it with a parent section, I get a cyclic reference error. I tried removing the parent section, but then it fails to actually include the build-tools module in the reactor build and bombs out with a failed to resolve artifact. So, how does it really work ? -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Hibernate3 Maven Plugin 2.0-alpha-1 released
Johann Reyes skrev: Hello David Thanks for the report, documentation has been fixed. Thanks - I'm using annotations, and call the goals goalhbm2hbmxml/goal goalhbm2cfgxml/goal Is there any way to prevent the plugin from trying to connect to the DB - as the annotations are source for the mapping? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Best practices for using mvn release, then releasing against the branch
When we use the release plugin it works well by: - Changing our x.x-SNAPSHOT to x.x - Checks in and tags our code with the x.x version number - Changes x.x to x.x+1. We would like to have some way of starting a branch from the tagged code and have it change our x.x to x.x.1-SNAPSHOT so we can release using the branched version number. Does something like this exist? Should we do the release step differently? Is there a better way of handling this? Thanks Neil Hart
Re: Archetype: create resources as companions to java source files
On 3/6/07, Howard Lewis Ship [EMAIL PROTECTED] wrote: Any point in me looking at it at this point? The structure you have in the quickstart matches what I'm trying to do. I think we have the info we need at this point. Thanks for bringing this up, it's something I noticed a while ago but never had time to track down. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Maven2] xmlbeans-maven-plugin Issue -- StAX transitive dependencies
Hey everyone, I am having a terrible time with xmlbeans-maven-plugin and transitive StAX issues relating to xmlbeans-jsr173-api.jar. I am using Maven 2.0.5. The error Maven is throwing is that it cannot find the xmlbeans-jsr173-api.jar. I know this jar does not exist in a public repository and that the stax-api.jar needs to be used instead. I am trying to do that, but things are not working out. The start of the problem is that xmlbeans-maven-plugin-2.0 has a dependency on stax-1.1.1-dev.jar, which has a subsequent dependency on xmlbeans-jsr173-api.jar. Even though the xmlbeans-maven-plugin-2.0 POM specifically excludes xmlbeans-jsr173-api.jar from the stax-1.1.1-dev declaration, my build is still trying to resolve it. This is obviously a bug in itself, but I am trying to work around it. I am trying to override the StAX version in the xmlbeans-maven-plugin dependency section to be 1.2.0, but I am getting inconsistent results on my box. Somehow, the 1.1.1-dev version is still getting into the resolution mix and being resolved first. My attempt to override the version to 1.2.0 does not appear to work. Is this broken, or am I wrong about the ability to override plugin dependencies? It appears that the dependency I declare is just being added, not actually overriding the one declared in the xmlbeans-maven-plugin POM. Can someone please clarify if this is by design or a bug. plugin groupIdorg.codehaus.mojo/groupId artifactIdxmlbeans-maven-plugin/artifactId executions execution goals goalxmlbeans/goal /goals /execution /executions dependencies !-- Adding version 1.2.0 in attempt to avoid transitive dependency on xmlbeans-jsr173-api -- dependency groupIdstax/groupId artifactIdstax/artifactId version1.2.0/version scoperuntime/scope /dependency /dependencies /plugin Now it would appear that I am getting involved with the nearness algorithm for determining which version of a dependency is resolved when two exist at the same depth in the dependency graph. This was supposed to be fixed for Maven 2.0.5 in MNG-2794 so that the version encountered first gets resolved. My next question is, how do you determine or influence which version gets encountered first? Is it based upon declaration order in the POM? If so, why does it not work if I add the stax-1.2.0.jar dependency to a plugin declared before xmlbeans-maven-plugin in my pom.xml? I have also tried to explicitly declare the stax-1.2.0.jar as a direct dependency in my POM. That does not work either! Do plugin dependencies trump all others including locally declared dependencies? Now for the really funky part... if I add a few dependencies to the POM, all of a sudden the stax-1.2.0.jar does get resolved first. The jars to the best of my knowledge do not declare any dependencies on StAX. I tested it out with several different sets of unrelated jars. I could consistently get the build to work after adding 5 or 6 more seemingly random jars to my dependency list. I am at a loss. How can I avoid a transitive dependency declared in a plugin aside from modifying the plugin's pom.xml and making it available locally? Any help and clarification will be greatly appreciated! Thanks, -Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Hibernate3 Maven Plugin 2.0-alpha-1 released
Hello David Actually yes, set the export flag to false Regards Johann Reyes -Original Message- From: David J. M. Karlsen [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 8:21 PM To: Maven Users List Subject: Re: [ANN] Hibernate3 Maven Plugin 2.0-alpha-1 released Johann Reyes skrev: Hello David Thanks for the report, documentation has been fixed. Thanks - I'm using annotations, and call the goals goalhbm2hbmxml/goal goalhbm2cfgxml/goal Is there any way to prevent the plugin from trying to connect to the DB - as the annotations are source for the mapping? - 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]
Maven newbie alert - incorrect archetype version.
Hello. I am a Maven newbie. Having discovered the merit in using Maven over Ant on Monday, I downloaded and started fiddling with it yesterday. I am rather fresh. My problem relates to the following error when trying to create a new JBI BC project with maven. I am following the tutorial at http://incubator.apache.org/servicemix/hello-world-bc.html to create my own BC; a fact I think is unrelated to the problem I am having. When I run the following command: mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling / -DarchetypeArtifactId=servicemix-binding-component / -DarchetypeVersion=3.1-incubating-SNAPSHOT / -DgroupId=au.com.wcg.bindingcomponent.executeshellscript / -DartifactId=WCGExecuteSchellScriptBindingComponent I find the following error in my maven output: [INFO] Failed to resolve artifact. GroupId: org.apache.servicemix.tooling ArtifactId: servicemix-binding-component Version: 3.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository Try downloading the file manually from the project website. Looking at the tutorial, I find that it has been courteous enough to include a link to the Top level ServiceMix POM, only this link points to a page that no longer exists. I have done some searching, and, not knowing exactly what it is that I am supposed to be finding, have here made this request for help. Does anyone know where the POM I need is? Help would be very much appreciated, Owen.
RE: Maven newbie alert - incorrect archetype version.
These might be of interest too: H:\CurrentProjectsmvn --version Maven version: 2.0.5 H:\CurrentProjectsjava -version java version 1.5.0_11 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode) Owen. -Original Message- From: Owen Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 1:41 PM To: users@maven.apache.org Subject: Maven newbie alert - incorrect archetype version. Hello. I am a Maven newbie. Having discovered the merit in using Maven over Ant on Monday, I downloaded and started fiddling with it yesterday. I am rather fresh. My problem relates to the following error when trying to create a new JBI BC project with maven. I am following the tutorial at http://incubator.apache.org/servicemix/hello-world-bc.html to create my own BC; a fact I think is unrelated to the problem I am having. When I run the following command: mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling / -DarchetypeArtifactId=servicemix-binding-component / -DarchetypeVersion=3.1-incubating-SNAPSHOT / -DgroupId=au.com.wcg.bindingcomponent.executeshellscript / -DartifactId=WCGExecuteSchellScriptBindingComponent I find the following error in my maven output: [INFO] Failed to resolve artifact. GroupId: org.apache.servicemix.tooling ArtifactId: servicemix-binding-component Version: 3.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository Try downloading the file manually from the project website. Looking at the tutorial, I find that it has been courteous enough to include a link to the Top level ServiceMix POM, only this link points to a page that no longer exists. I have done some searching, and, not knowing exactly what it is that I am supposed to be finding, have here made this request for help. Does anyone know where the POM I need is? Help would be very much appreciated, Owen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Selenium, profiles and executing certain browsers on certain OSs
Sure... pull the build configurations out of the profiles into the project
build and replace the ant config values with properties... then use the
profiles to set those property values.
Eric
On 3/6/07, mraible [EMAIL PROTECTED] wrote:
I'm using the salenese Ant task to run some Selenium tests in my
project.
I want tests to run in Firefox on all platforms, and Firefox and IE when
running on Windows. I've got everything working using the XML below, but
it's quite verbose. Is there a way to simplify, or is this the
recommended
strategy?
profiles
profile
id${cargo.container}/id
activation
property
name!maven.test.skip/name
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version0.2/version
...
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdorg.openqa.selenium.server/groupId
artifactIdselenium-server/artifactId
version0.9.1-SNAPSHOT/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
profile
idwindows/id
activation
os
familyWindows/family
/os
/activation
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*iexplore
timeoutInSeconds=180
results=${project.build.directory}/selenium-ie-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
/profiles
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/Selenium%2C-profiles-and-executing-certain-browsers-on-certain-OSs-tf3358368s177.html#a9341212
Sent from the Maven - Users mailing list archive at Nabble.com.
Building using Maven tool
Hi, Can anybody of the Maven Users group help me resolve the issue. I am trying to build a java project with Maven2.And stuck with some package not found error at compile time.The required package includes all the jars and libs , even I have kept it inside the project directory structure ,Maven is not considering it for compilation.So my question is, can somebody please throw some light on where to specify the lib classpath for maven execution.For your lookup I am attaching the error code here, with the hope that Fisheye team will respond with a positive solution: D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[10,28] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[15,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[17,38] package com.sun.msv.grammar does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[23,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[17,37] package com.sun.xml.bind.unmarshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[14,24] package com.sun.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[15,35] package com.sun.xml.bind.marshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[16,35] package com.sun.xml.bind.serializer does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[147,31] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[19,4] cannot find symbol symbol : class DocumentDeclaration location: interface org.cdisc.ns.odm.v1.impl.runtime.ValidatableObject D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[194,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[223,4] cannot find symbol symbol : class Tracer location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,49] cannot find symbol symbol : class AbortSerializationException location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[176,17] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[189,20] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[209,22] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[221,28] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[232,22] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[83,23] package com.sun.msv.grammar does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[83,52] cannot find symbol symbol : class JAXBException location: interface org.cdisc.ns.odm.v1.impl.runtime.GrammarInfo D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[185,135] package com.sun.xml.bind does not exist
Re: Maven newbie alert - incorrect archetype version.
Looks like the artifacts you need are in the Apache Snapshots repository on people.apache.org: http://people.apache.org/maven-snapshot-repository/org/apache/servicemix/tooling/servicemix-binding-component/ Also note the hello-world-bc webpage says at the top Work In Progress. So this is more complex than most Maven interactions. The easiest way forward is thus: 1. Create a directory blah and a file pom.xml inside it 2. Paste the following into the file 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 groupIdblah/groupId artifactIdtest/artifactId packagingjar/packaging version1.0-SNAPSHOT/version nameblah test/name repositories repository idApache Snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /repository /repositories pluginRepositories pluginRepository idApache Snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url snapshots enabledtrue/enabled /snapshots releases enabledfalse/enabled /releases /pluginRepository /pluginRepositories dependencies dependency artifactIdservicemix-binding-component/artifactId groupIdorg.apache.servicemix.tooling/groupId version3.1-incubating-SNAPSHOT/version /dependency /dependencies /project 3. Then run mvn test and allow the files to download 4. Now go back to your original directory and attempt to run the mvn archetype:create ... command again However... I just did this and ran into an error about META-INF/archetype.xml missing, so realistically you should send a support request type email to the ServiceMix developers and see if they can help you get things going... Or wait until this hello-world-bc example is finished. Wayne On 3/6/07, Owen Thomas [EMAIL PROTECTED] wrote: These might be of interest too: H:\CurrentProjectsmvn --version Maven version: 2.0.5 H:\CurrentProjectsjava -version java version 1.5.0_11 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode) Owen. -Original Message- From: Owen Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 1:41 PM To: users@maven.apache.org Subject: Maven newbie alert - incorrect archetype version. Hello. I am a Maven newbie. Having discovered the merit in using Maven over Ant on Monday, I downloaded and started fiddling with it yesterday. I am rather fresh. My problem relates to the following error when trying to create a new JBI BC project with maven. I am following the tutorial at http://incubator.apache.org/servicemix/hello-world-bc.html to create my own BC; a fact I think is unrelated to the problem I am having. When I run the following command: mvn archetype:create -DarchetypeGroupId=org.apache.servicemix.tooling / -DarchetypeArtifactId=servicemix-binding-component / -DarchetypeVersion=3.1-incubating-SNAPSHOT / -DgroupId=au.com.wcg.bindingcomponent.executeshellscript / -DartifactId=WCGExecuteSchellScriptBindingComponent I find the following error in my maven output: [INFO] Failed to resolve artifact. GroupId: org.apache.servicemix.tooling ArtifactId: servicemix-binding-component Version: 3.1-incubating-SNAPSHOT Reason: Unable to download the artifact from any repository Try downloading the file manually from the project website. Looking at the tutorial, I find that it has been courteous enough to include a link to the Top level ServiceMix POM, only this link points to a page that no longer exists. I have done some searching, and, not knowing exactly what it is that I am supposed to be finding, have here made this request for help. Does anyone know where the POM I need is? Help would be very much appreciated, Owen. - 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: Building using Maven tool
i think you are missing required jar in repository or you have not provided in your pom like com.sun.xml.bind.util does not work on the following area in your pom dependencies dependencyhttp://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_dependency groupId/ artifactId/ version/ type/ classifier/ scope/ systemPath/ exclusions exclusionhttp://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_exclusion artifactId/ groupId/ /exclusion /exclusions optional/ /dependency /dependencies On 3/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Can anybody of the Maven Users group help me resolve the issue. I am trying to build a java project with Maven2.And stuck with some package not found error at compile time.The required package includes all the jars and libs , even I have kept it inside the project directory structure ,Maven is not considering it for compilation.So my question is, can somebody please throw some light on where to specify the lib classpath for maven execution.For your lookup I am attaching the error code here, with the hope that Fisheye team will respond with a positive solution: D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[10,28] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[15,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[17,38] package com.sun.msv.grammar does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[23,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[17,37] package com.sun.xml.bind.unmarshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[14,24] package com.sun.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[15,35] package com.sun.xml.bind.marshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[16,35] package com.sun.xml.bind.serializer does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[147,31] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[19,4] cannot find symbol symbol : class DocumentDeclaration location: interface org.cdisc.ns.odm.v1.impl.runtime.ValidatableObject D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[194,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[223,4] cannot find symbol symbol : class Tracer location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,49] cannot find symbol symbol : class AbortSerializationException location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[176,17] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[189,20] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[209,22] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer
Re: Building using Maven tool
Maven2 does not use jars in a project lib directory for compilation etc. Instead you must construct a pom.xml file with proper dependencies declared etc. I suggest you read the Better Builds with Maven free e-book, available as a PDF from http://www.mergere.com to get up to speed on how Maven2 works and to help construct the pom.xml file you require. Wayne On 3/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, Can anybody of the Maven Users group help me resolve the issue. I am trying to build a java project with Maven2.And stuck with some package not found error at compile time.The required package includes all the jars and libs , even I have kept it inside the project directory structure ,Maven is not considering it for compilation.So my question is, can somebody please throw some light on where to specify the lib classpath for maven execution.For your lookup I am attaching the error code here, with the hope that Fisheye team will respond with a positive solution: D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[10,28] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[15,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[17,38] package com.sun.msv.grammar does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[23,35] package com.sun.xml.bind.util does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[17,37] package com.sun.xml.bind.unmarshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[14,24] package com.sun.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[15,35] package com.sun.xml.bind.marshaller does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[16,35] package com.sun.xml.bind.serializer does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\w3\_2000\_09\xmldsig_\impl\SPKIDat aTypeImp l.java:[147,31] package com.sun.msv.verifier does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Valid atableOb ject.java:[19,4] cannot find symbol symbol : class DocumentDeclaration location: interface org.cdisc.ns.odm.v1.impl.runtime.ValidatableObject D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[10,22] package javax.xml.bind does not exist D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[194,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Unmar shalling Context.java:[223,4] cannot find symbol symbol : class Tracer location: interface org.cdisc.ns.odm.v1.impl.runtime.UnmarshallingContext D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,22] cannot find symbol symbol : class ValidationEvent location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[66,49] cannot find symbol symbol : class AbortSerializationException location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[176,17] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[189,20] cannot find symbol symbol : class IdentifiableObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[209,22] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[221,28] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\XMLSe rializer .java:[232,22] cannot find symbol symbol : class JAXBObject location: interface org.cdisc.ns.odm.v1.impl.runtime.XMLSerializer D:\sde3.0\workspace\BuildPoc\jaxb\org\cdisc\ns\odm\v1\impl\runtime\Gramm arInfo.j ava:[83,23] package
Re: Best practices for using mvn release, then releasing against the branch
You're not the first person who has asked for this functionality, but as far as I know, it does not currently exist in the release plugin. The release plugin only handles a few very specific use cases at the moment. Feel free to add an enhancement request to the JIRA for release plugin for this feature, but please search before adding as I'd expect its already been posted. Wayne On 3/6/07, neil hart [EMAIL PROTECTED] wrote: When we use the release plugin it works well by: - Changing our x.x-SNAPSHOT to x.x - Checks in and tags our code with the x.x version number - Changes x.x to x.x+1. We would like to have some way of starting a branch from the tagged code and have it change our x.x to x.x.1-SNAPSHOT so we can release using the branched version number. Does something like this exist? Should we do the release step differently? Is there a better way of handling this? Thanks Neil Hart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] PVCS SCM
That would be very great. I think the bug you're talking about is at http://jira.codehaus.org/browse/SCM-34 On 3/7/07, JC Walmetz [EMAIL PROTECTED] wrote: I'm afraid the donation of a plugin by serena is in a bad way. Few month ago we ask to Serena if it was planned. Their answer was NO. It looks it somewhere in a wish list. Maybe if you are a Serena Customer you can contact their support. In JIRA there is a startup for a PVCS plugin (just the checkout from what I remember). I have implement some more task but that's not tested. I'll try to find the bug in JIRA and to add my plugins. I use it to release my projects with the release plugin. Gregory Kick-2 wrote: A while back there was some talk of a PVCS integration being donated. Did anything ever come of that? Has anyone successfully used maven with pvcs? Thanks, -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/PVCS-SCM-tf3353835s177.html#a9339363 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gregory Kick [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tools.jar Apple
Since classes.jar is always on the classpath, you could probably just
use an exclusion to disregard the dependency. Otherwise, you
actually end up with classes.jar on your classpath twice.
On 3/7/07, Wayne Fay [EMAIL PROTECTED] wrote:
There is no tools.jar on Mac. Instead, the classes from tools.jar are
included in a larger classes.jar file. Don't ask me...
Wayne
On 3/6/07, Dan Tran [EMAIL PROTECTED] wrote:
Apple renames tools.jar to classes.jar?
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Managed to get around the problem. I edited the pom file under .m2
to point directly at the classes.jar file on MacOS X. A bit of a hack
but it worked.
-Ryan
On Mar 6, 2007, at 2:37 PM, Ryan Cuprak wrote:
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Gregory Kick
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tools.jar Apple
Actually, I take that back... you can define exclusions for
dependencies within a plugin, but it doesn't look like you can define
them for a plugin itself.
Anybody know of a good way to do that?
On 3/7/07, Gregory Kick [EMAIL PROTECTED] wrote:
Since classes.jar is always on the classpath, you could probably just
use an exclusion to disregard the dependency. Otherwise, you
actually end up with classes.jar on your classpath twice.
On 3/7/07, Wayne Fay [EMAIL PROTECTED] wrote:
There is no tools.jar on Mac. Instead, the classes from tools.jar are
included in a larger classes.jar file. Don't ask me...
Wayne
On 3/6/07, Dan Tran [EMAIL PROTECTED] wrote:
Apple renames tools.jar to classes.jar?
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Managed to get around the problem. I edited the pom file under .m2
to point directly at the classes.jar file on MacOS X. A bit of a hack
but it worked.
-Ryan
On Mar 6, 2007, at 2:37 PM, Ryan Cuprak wrote:
The error message is:
Missing:
--
1) sun.jdk:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=sun.jdk -DartifactId=tools \
-Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mojo:jaxws-maven-plugin:maven-plugin:1.0-
beta-1-20070203.171044-8
2) sun.jdk:tools:jar:1.5.0
On the mac, the classes that comprise the tools are located in:
/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Classes/
classes.jar
Googling I come across postings where it is recommend that I alter
the systempath to point to classes.jar.
-Ryan
On Mar 6, 2007, at 2:30 PM, Dan Tran wrote:
jaxws is capable of automatically pickup tools.jar from
${java.home}/lib/tools.jar
( MacOS specific)
What is the error?
you may need to get the latest source and build your self.
-D
On 3/6/07, Ryan Cuprak [EMAIL PROTECTED] wrote:
Hello,
I am trying to get the jaxws-maven-plugin up and running on my
box. Evidently Apple has been kind enough to stick tools.jar
elsewhere.
Any reason why the snippet below wouldn't work?
-Ryan
Snippet:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
version1.0-beta-1-SNAPSHOT/version
executions
execution
goals
goalwsgen/goal
/goals
/execution
/executions
configuration
seinet.cuprak.ryanportal/sei
genWsdltrue/genWsdl
/configuration
dependencies
dependency
groupIdsun.jdk/groupId
artifactIdtools/artifactId
version1.5.0/version
systemPath/System/Library/Frameworks/
JavaVM.framework/Versions/1.5/Classes/classes.jar/systemPath
scopesystem/scope
/dependency
/dependencies
/plugin
/plugins
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Gregory Kick
[EMAIL PROTECTED]
--
Gregory Kick
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Selenium, profiles and executing certain browsers on certain OSs
My current setup only executes Cargo and Selenium when -Dmaven.test.skip=true
is not passed in. If I move the plugin information to the regular build
part of my pom.xml, do I leave the execution information in profiles?
After adding another profile for Selenium on OS X (for Safari), my
integration-testing section is almost 200 lines long. Yes, it does work,
but it does seem awful verbose.
http://rafb.net/p/2hIgrI84.html
Matt
Eric Redmond wrote:
Sure... pull the build configurations out of the profiles into the project
build and replace the ant config values with properties... then use the
profiles to set those property values.
Eric
On 3/6/07, mraible [EMAIL PROTECTED] wrote:
I'm using the salenese Ant task to run some Selenium tests in my
project.
I want tests to run in Firefox on all platforms, and Firefox and IE when
running on Windows. I've got everything working using the XML below, but
it's quite verbose. Is there a way to simplify, or is this the
recommended
strategy?
profiles
profile
id${cargo.container}/id
activation
property
name!maven.test.skip/name
/property
/activation
build
plugins
plugin
groupIdorg.codehaus.cargo/groupId
artifactIdcargo-maven2-plugin/artifactId
version0.2/version
...
/plugin
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdant/groupId
artifactIdant-nodeps/artifactId
version1.6.5/version
/dependency
dependency
groupIdorg.openqa.selenium.server/groupId
artifactIdselenium-server/artifactId
version0.9.1-SNAPSHOT/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
profile
idwindows/id
activation
os
familyWindows/family
/os
/activation
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idlaunch-selenium/id
phaseintegration-test/phase
configuration
tasks
taskdef
resource=selenium-ant.properties
classpath
refid=maven.plugin.classpath/
/taskdef
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*firefox
timeoutInSeconds=180
results=${project.build.directory}/selenium-firefox-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
selenese
suite=src/test/resources/selenium/TestSuite.html
browser=*iexplore
timeoutInSeconds=180
results=${project.build.directory}/selenium-ie-results.html
startURL=http://${cargo.host}:${cargo.port}/${project.build.finalName
}//
/tasks
RE: Maven newbie alert - incorrect archetype version.
Hello again. Thanks for your reply Wayne. I have followed the advice of a respondent to an identical message I put in the ServiceMix user's mailing list, and my actions appear (at least) to have rectified my earlier problem. See the Service Mix response within the thread at: http://www.nabble.com/Maven-newbie-alert---incorrect-archetype-version.- tf3359474s12049.html. However, as the response above states, Maven is now giving me the following errors: ... [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] - ... You advice here would also be greatly appreciated. Thanks, Owen. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 2:55 PM To: Maven Users List Subject: Re: Maven newbie alert - incorrect archetype version. Looks like the artifacts you need are in the Apache Snapshots repository on people.apache.org: http://people.apache.org/maven-snapshot-repository/org/apache/servicemix /tooling/servicemix-binding-component/ Also note the hello-world-bc webpage says at the top Work In Progress. So this is more complex than most Maven interactions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven newbie alert - incorrect archetype version.
Hi If you get the error: Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. then the archtype is broke. This is the file that controls the archetype itself. Try removing the previously downloaded archetype from your local repo and then do a new run. Hermod -Original Message- From: Owen Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 7:16 AM To: Maven Users List Subject: RE: Maven newbie alert - incorrect archetype version. Hello again. Thanks for your reply Wayne. I have followed the advice of a respondent to an identical message I put in the ServiceMix user's mailing list, and my actions appear (at least) to have rectified my earlier problem. See the Service Mix response within the thread at: http://www.nabble.com/Maven-newbie-alert---incorrect-archetype-version.- tf3359474s12049.html. However, as the response above states, Maven is now giving me the following errors: ... [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] - ... You advice here would also be greatly appreciated. Thanks, Owen. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 2:55 PM To: Maven Users List Subject: Re: Maven newbie alert - incorrect archetype version. Looks like the artifacts you need are in the Apache Snapshots repository on people.apache.org: http://people.apache.org/maven-snapshot-repository/org/apache/servicemix /tooling/servicemix-binding-component/ Also note the hello-world-bc webpage says at the top Work In Progress. So this is more complex than most Maven interactions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email with attachments is solely for the use of the individual or entity to whom it is addressed. Please also be aware that DnB NOR cannot accept any payment orders or other legally binding correspondence with customers as a part of an email. This email message has been virus checked by the anti virus programs used in the DnB NOR Group. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
