RE: dependencyManagement help
Lachlan Deck wrote: Hi there, I'm trying to utilise dependency management but am obviously missing something. I've got /pom.xml /frameworks/pom.xml /frameworks/fwk1 ... /frameworks/fwkN /app1/pom.xml -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. The two artifacts to not match. An artifact is defined by groupId, artifactId, type and optional classifier. The type defaults to jar. This might give you an idea ;-) [snip] - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Checkstyle Versions
Hi Brian. Thank you very much for that. I'd asked before but to no avail. Thanks for taking the time to answer. -Chris Brian E. Fox [EMAIL PROTECTED] wrote on 24/04/2008 04:08:18: Chris, this is a commonly requested feature and you can see more info here: http://blogs.sonatype.com/brian/2008/04/23/120896598.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 9:00 PM To: Maven Users List Subject: Checkstyle Versions Hi All. The blurb on Maven 2.0.9 stated that you could force a specific version of a jar, mainly to get newer versions, and the specifically listed checkstyle (amongst others). How do you actually do it? The maven checkstyle plugin uses checkstyle 4.1 and 4.4 is available (and that is what I'm using). Can someone please help me out. Ta. -Chris ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - 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] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencyManagement help
Hi there, On 24/04/2008, at 4:37 PM, Jörg Schaible wrote: -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. The two artifacts to not match. An artifact is defined by groupId, artifactId, type and optional classifier. The type defaults to jar. This might give you an idea ;-) Then I'm not seeing what purpose the dependencyManagement section serves if I've still gotta declare pretty much everything apart from 'version' in other dependency declarations? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dependencyManagement help
Hello, I think dep.mgmt. is meant to declare if an artifact with this groupId/artifactId appears somewhere in the dependency tree, include the version stated here; but don't include it by default. For instance, if your module A depends on module B which in turn depends on module C 1.0 but you'd like to use C 2.0, you can put it in A's dependencyManagement. This is probably good practice as C is not a direct dependency of A. (In particular, if a new version of B comes out that no longer requires C, C will be dropped altogether and not included from A). Greetings, David -Original Message- From: Lachlan Deck [mailto:[EMAIL PROTECTED] Sent: 24 April 2008 08:55 To: Maven Users List Subject: Re: dependencyManagement help Hi there, On 24/04/2008, at 4:37 PM, Jörg Schaible wrote: -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. The two artifacts to not match. An artifact is defined by groupId, artifactId, type and optional classifier. The type defaults to jar. This might give you an idea ;-) Then I'm not seeing what purpose the dependencyManagement section serves if I've still gotta declare pretty much everything apart from 'version' in other dependency declarations? with regards, -- Lachlan Deck - 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: dependencyManagement help
Lachlan Deck wrote: Hi there, On 24/04/2008, at 4:37 PM, Jörg Schaible wrote: -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. The two artifacts to not match. An artifact is defined by groupId, artifactId, type and optional classifier. The type defaults to jar. This might give you an idea ;-) Then I'm not seeing what purpose the dependencyManagement section serves if I've still gotta declare pretty much everything apart from 'version' in other dependency declarations? You inherit version and scope. scope ensures that the artifact is used in the proper way and version will ensure that it is used everywhere in the right version. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [newby] how to include/package private libs/*.jar
It would be something like: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idlist-deps/id phasegenerate-resources/phase goals goallist/goal /goals configuration outputFilefoo.txt/outputFile /configuration /execution /executions plugins /build Hth, Nick S. -Original Message- From: Lachlan Deck [mailto:[EMAIL PROTECTED] Sent: Thu 4/24/2008 04:40 To: Maven Users List Subject: Re: [newby] how to include/package private libs/*.jar Hi Joshua, On 23/04/2008, at 11:23 PM, Joshua ChaitinPollak wrote: On Apr 23, 2008, at 1:05 AM, Lachlan Deck wrote: - append to the text file a list of the jars bundled (prefixing each with a custom path). That's a tricky one. I'd have to say start with the dependency or assembly plugin and see if they can do what you need. I know one of the plugins can put the jars on your classpath in the Manifest, but we don't use the manifest, so I have no experience with it. Right. This is the bit I'm stuck with... Well, I'm not sure if this is helpful or not, but you can do this: mvn -DoutputFile=foo.txt dependency:list which will put your dependencies in a file called foo.txt. You could then use the exec or groovy plugins to process the output file into the format you want. Interesting. Forgive my ignorance (still a maven newbie) but how might I incorporate that into the build lifecycle? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Referencing a dependency via a property
Hi, I would like to be able to refer to a dependency via a property. As an example consider the site phase which runs numerous reporting plugins and such a plugin requires a license. I have the license sitting in the repository as an artefact and I define the artefact as a dependency in the dependency management section. The reporting plugin then relies on a property to define the location of the license. Does Maven allow me to define a property that equates to the artefact? At the moment I workaround this using the dependency plugin to copy the artefact to the maven build directory and then set the property that way Thanks, Robert
I have a problem with maven-changes-plugin version 2.0 again
Hello ! I am trying to use maven-changes-plugin again, version 2.0 with our jira. I have next configurations: ... issueManagement systemJIRA/system urlhttps://svn.cti.ru:8443/jira/BrowseProject.jspa?id=10001/url /issueManagement ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changes-plugin/artifactId version2.0/version configuration jiraUseruser/jiraUser jiraPasswordpassword/jiraPassword /configuration reportSets reportSet reports reportjira-report/report /reports /reportSet /reportSets /plugin ... I get next log: --- [DEBUG] Generating /home/myjava/eclipse_pr/Project/project-super-pom/trunk/target/site/jira-report.html [INFO] Generating JIRA Report report. [DEBUG] JIRA lives at: https://my.ru:8443/jira [DEBUG] Login URL: https://my.ru:8443/jira/login.jsp?os_destination=/secure/os_username=svn_searcheros_password= [DEBUG] Successfully logged in into JIRA. [INFO] Downloading from JIRA at: https://my.ru:8443/jira/secure/IssueNavigator.jspa?view=rsspid=10001statusIds=6resolutionIds=1sorter/field=createdsorter/order=DESCsorter/field=prioritysorter/order=DESCtempMax=100reset=truedecorator=none Apr 24, 2008 2:43:49 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [DEBUG] Downloading from JIRA was successful --- This url: https://my.ru:8443/jira/secure/IssueNavigator.jspa?view=rsspid=10001statusIds=6 resolutionIds=1sorter/field=createdsorter/order=DESCsorter/field=prioritysorter/order=DESCte properly open in browser, but jira report is empty ! That I do wrong? Thanks in advance. -- Best Regards, Eugene Batogov a.k.a JohnBat26. e-mail: [EMAIL PROTECTED] IM: ICQ: 198710313, Yahoo/AIM/Google/Jabber(jabber.ru)/MSN/Skype: JohnBat26. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven pde rcp to build
Hi, Have a look on Carlos's blog http://www.jroller.com/carlossg/entry/slides_from_eclipsecon Cheers, Vincent 2008/4/21 [EMAIL PROTECTED]: I have been looking for a while for this solution. Has anyone been able to run this tutorial to complete? http://mojo.codehaus.org/pde-maven-plugin/examples/simple_product.html I have looked through many emails just to get the project to build in maven with Eclipse 3.3.2 as target. Now I am at a point where it builds with 0 errors. I had to change the pom.xml packaging setting from ZIP to JAR. So I tried to run it from the dos with: *java -jar simple_application-1.0-SNAPSHOT.jar * I get nothing. No errors, no failure,. nothing! Here is my pom.xml; 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 groupIdtest.pde_maven_plugin/groupId artifactIdsimple_application/artifactId packagingjar/packaging nameSimple Plugin PDE Example/name version1.0-SNAPSHOT/version descriptionA Simple Plugin PDE Example/description build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdpde-maven-plugin/artifactId extensionstrue/extensions configuration eclipseInstallC:\Program Files\JavaWorkEnv\eclipse/eclipseInstall pdeProductFilenamesimple_product.product/pdeProductFilename pdeBuildVersion3.3.2.v20071019/pdeBuildVersion /configuration /plugin /plugins /build /project Any leads to get this to run from dos as jar or how to get the zip packaging setting to build? Here is the error if I have zip as packaging setting. mvn install [INFO] Scanning for projects... [INFO] [INFO] Building Simple Plugin PDE Example [INFO]task-segment: [install] [INFO] [INFO] [pde:ext] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] C:\Program Files\JavaWorkEnv\eclipse\startup.jar not found. Have you set up your -DeclipseInstall? [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Mon Apr 21 12:12:30 CDT 2008 [INFO] Final Memory: 3M/8M [INFO] Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
I have a problem with maven-release-plugin !
Hello ! I am trying to use maven-release-plugin. Our project is consist of 3 levels. 1. At top is SUPER-POM 2. At middle are pom files of subsystems, which have parent - SUPER-POM. 3. At bottom ara pom files of components, which have parent - pom file subsystem. Our SUPER-POM file present base line of development. But when I am trying invoke: mvn release:prepare against subsystem pom-file, plugin ask about releasing SUPER-POM, then I type required number of version SUPER-POM. Plugin are resuming execution releasing. BUT After execution mvn release:prepare, version SUPER-POM in parent tag of subsystem POM remain prior ?!? This is bug, or I something do wrong? Thanks in advance. -- Best Regards, Eugene Batogov a.k.a JohnBat26. e-mail: [EMAIL PROTECTED] IM: ICQ: 198710313, Yahoo/AIM/Google/Jabber(jabber.ru)/MSN/Skype: JohnBat26. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: How can I send a single file by scp without generate maven2 repository directory structure in remote machine?
Hi, Very good! Now, I have two options to do scp: http://myfaces.apache.org/wagon-maven-plugin/usage.html and http://docs.atlassian.com/maven-upload-plugin/1.1/ I will test both. Thank you very much! Thanks Nick to your hint. I will try to do a plugin to wsconsume of jbossws -Mensagem original- De: Luke Daley [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 23 de abril de 2008 19:46 Para: Maven Users List Assunto: Re: How can I send a single file by scp without generate maven2 repository directory structure in remote machine? Also, http://docs.atlassian.com/maven-upload-plugin/1.1/ LD. - 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: dependencyManagement help
Then I'm not seeing what purpose the dependencyManagement section serves if I've still gotta declare pretty much everything apart from 'version' in other dependency declarations? The group/artifact/classifier/type are part of the identifier and those must match. The scope and version can be centrally controlled in the depMgt section and this saves you from having potentially conflicting versions in multiple modules. It also makes it easier to upgrade later. Additionally, depMgt will also override any transitive dependency versions (even if you don't directly use them) so it's a way to manage those as well. -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/brian/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
code location for junit and cobetura plugins
Hi,
I have several projects that I currently build with maven. I want to
start using the junit and cobertura plugins however the junit code does not
live under the src folder. It is in project/test.
Is there a parameter that I can set that tells maven the location to look in
for the junti code, for example, ${basedir}/tests, for both these plugins?
I have seen the one in the cobertura plugin but I think it assumes the junit
code lives under the src folder pattern.
I would perfer not to move the code or to try and use an ant task to
relocate it during the build if I can set the location with a simple
parameter.
Thanks,
Mark
--
View this message in context:
http://www.nabble.com/code-location-for-junit-and-cobetura-plugins-tp16850553s177p16850553.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Naming snapshots with alphas / betas
Questions on best practices. Lets say I'm working toward version 1.0, releasing snapshots as I go. But I also want to release a few alphas and betas. Would you name the versions 1.0-alpha-1-SNAPSHOT 1.0-alpha-1 1.0-alpha-2-SNAPSHOT 1.0-alpha-2 ... or 1.0-SNAPSHOT 1.0-alpha-1 1.0-SNAPSHOT 1.0-alpha-2 ... I can see where the former is a bit clearer as to the order in which versions were released. But if you don't have a set plan ahead of time as to how many alphas / betas will be cut, the names might not really work (for example 1.0-alpha-3-SNAPSHOT - 1.0-beta-1). -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: How can I send a single file by scp without generate maven2 repository directory structure in remote machine?
Hi Wendy, I tested your plugin and worked! I think that other people need of this plugin, but don´t find in web. You can talk with maven developer to add the url http://myfaces.apache.org/wagon-maven-plugin/index.html in http://maven.apache.org/plugins/index.html Thank you very much! -Mensagem original- De: Claudio Ranieri [mailto:[EMAIL PROTECTED] Enviada em: quinta-feira, 24 de abril de 2008 09:27 Para: Maven Users List Assunto: RES: How can I send a single file by scp without generate maven2 repository directory structure in remote machine? Hi, Very good! Now, I have two options to do scp: http://myfaces.apache.org/wagon-maven-plugin/usage.html and http://docs.atlassian.com/maven-upload-plugin/1.1/ I will test both. Thank you very much! Thanks Nick to your hint. I will try to do a plugin to wsconsume of jbossws -Mensagem original- De: Luke Daley [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 23 de abril de 2008 19:46 Para: Maven Users List Assunto: Re: How can I send a single file by scp without generate maven2 repository directory structure in remote machine? Also, http://docs.atlassian.com/maven-upload-plugin/1.1/ LD. - 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: code location for junit and cobetura plugins
Have you tried declaring a
testSourceDirectorypath/to/your/tests/testSourceDirectory in the
build section of your pom ?
Regards,
Salvador
Mark-E wrote:
Hi,
I have several projects that I currently build with maven. I want to
start using the junit and cobertura plugins however the junit code does not
live under the src folder. It is in project/test.
Is there a parameter that I can set that tells maven the location to look in
for the junti code, for example, ${basedir}/tests, for both these plugins?
I have seen the one in the cobertura plugin but I think it assumes the junit
code lives under the src folder pattern.
I would perfer not to move the code or to try and use an ant task to
relocate it during the build if I can set the location with a simple
parameter.
Thanks,
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Naming snapshots with alphas / betas
Siegmann Daniel, NY wrote: Questions on best practices. Lets say I'm working toward version 1.0, releasing snapshots as I go. But I also want to release a few alphas and betas. Would you name the versions 1.0-alpha-1-SNAPSHOT 1.0-alpha-1 1.0-alpha-2-SNAPSHOT 1.0-alpha-2 ... or 1.0-SNAPSHOT 1.0-alpha-1 1.0-SNAPSHOT 1.0-alpha-2 ... I can see where the former is a bit clearer as to the order in which versions were released. But if you don't have a set plan ahead of time as to how many alphas / betas will be cut, the names might not really work (for example 1.0-alpha-3-SNAPSHOT - 1.0-beta-1). Use the former, the latter might create problems in dependency resolution. E.g. we used the latter pattern originally also for minor releases (1.0 -- 1.0-SNAPSHOT -- 1.0.1 -- 1.0-SNAPSHOT), but it turned out that 1.0-SNAPSHOT 1.0 1.0.1 So, when we returned after the 1.0 release to 1.0-SNAPSHOT the dependency resolution never selected the SNAPSHOT version anymore from the transitive deps if somewhere a released version was available. I am not quite sure where 1.0-SNAPSHOT is inserted in the version sequence compared to 1.0-alpha-x or 1.0-beta-x, but it might not necessarily the place where you expect and you can get strange errors. Therefore it is best practice to use the SNAPSHOT always with a version that will change for the next SNAPSHOT cycle. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: keep out META-INF/context.xml
I'm not 100% sure (still new at Maven myself) but I believe that copying files to webapp/* takes place in a different phase. So what I think is happening is that you've excluded the context.xml file from your main resources phase, but it gets included in the WAR packaging secondary resource phase, which is when Maven starts dealing with webapp stuff. Try adding this to your POM: plugins plugin artifactIdmaven-war-plugin/artifactId executions execution configuration webResources !-- These resources need to go into WEB-INF, which only exists after the package phase (the normal resources tags are processed in compile generate-sources), so the WAR plug-in handles them instead of the main program. -- resource directory/src/main/webapp/META-INF/directory targetPathWEB-INF/targetPath excludes exclude**/context.xml/exclude /excludes /resource /webResources /configuration /execution /executions /plugin . . (other plugins) . /plugins You might have to change the directory, and I think you might be able to delete the target path element, but I believe that should get the WAR packaging phase to ignore the context file. Hope that helps. ~Dan Allen -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as KBC FP). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided as is, without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkstyle Versions
Looking at the dates of your emails, your original query came before Maven 2.0.9 was released, and this functionality was not available until 2.0.9. So the previous response would have been you can't which is probably why you didn't get one. Wayne On 4/24/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Brian. Thank you very much for that. I'd asked before but to no avail. Thanks for taking the time to answer. -Chris Brian E. Fox [EMAIL PROTECTED] wrote on 24/04/2008 04:08:18: Chris, this is a commonly requested feature and you can see more info here: http://blogs.sonatype.com/brian/2008/04/23/120896598.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 9:00 PM To: Maven Users List Subject: Checkstyle Versions Hi All. The blurb on Maven 2.0.9 stated that you could force a specific version of a jar, mainly to get newer versions, and the specifically listed checkstyle (amongst others). How do you actually do it? The maven checkstyle plugin uses checkstyle 4.1 and 4.4 is available (and that is what I'm using). Can someone please help me out. Ta. -Chris ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - 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] The following message has been automatically added by the Internet mail gateway to comply with the Group's Information Security requirements. This e-mail has arrived via the Internet, and therefore you should be cautious about its origin and content. Replies which contain sensitive information and / or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please contact the IS Service Desk. ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - 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: Internal repository question - stopping repo1
Wayne, Ok thanks. I appreciate the clarification. Right now I have those settings in my company's super pom as I like to call it. Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 7:19 PM To: Maven Users List Subject: Re: Internal repository question - stopping repo1 In short, Maven lies to you when you're using mirrors -- this is a known bug. So even when it hits a mirror, it reports Central. If you only have 1 repo in your organization and all projects will use it (on \\buildmachine in your case), then you certainly could move these repository etc entries into an activeByDefault profile in settings.xml or a shared/common top-level pom. Wayne On 4/23/08, Daniel King [EMAIL PROTECTED] wrote: Wayne, Thanks for the help. Are any of those other settings I have not needed? As far as best practices should any of those settings be in the settings.xml file instead of the POM if possible? I also noticed this in my build output: [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from internal [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central Downloading: file://\\buildMachine\repository/org/apache/maven/plugins/maven-clean-pl ugin/2.2/maven-clean-plugin-2.2.pom 3K downloaded So even though it only went to my internal server, I find it strange that it still states it checked for updates from central. I'm assuming maybe that info prints out before a check is made to see if it needs to hit the central repo and it didn't. Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 3:46 PM To: Maven Users List Subject: Re: Internal repository question - stopping repo1 You need a to set up a mirror pointing to your local repo as a mirrorOf*/mirrorOf in your settings.xml file, and Maven will only go to that server for all of its files. Wayne On 4/23/08, Daniel King [EMAIL PROTECTED] wrote: I'm using Archiva 1.0.2 and Maven 2.0.9 using JDK 1.6 on Windows XP. I've installed Maven on my local machine and Maven and Archiva on a development machine (Not sure if Maven is needed on the dev machine with Archiva but I think it is). For some reason I clear out my local repository and do a build, I see plugins being downloaded from repo1. I thought that those plugins would be downloaded to my internal repository. Then when I clear out the local repository and do a build again it would only get those from my internal repository. However it is still going out to repo1 for plugins. In my project's pom.xml I have the following: repositories repository idinternal/id nameInternal Maven Repository/name layoutdefault/layout urlfile://\\buildMachine\repository/url snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idinternal/id nameInternal Maven Plugin Repository/name urlfile://\\buildMachine\repository/url layoutdefault/layout snapshots enabledfalse/enabled /snapshots releases updatePolicynever/updatePolicy /releases /pluginRepository /pluginRepositories distributionManagement
RE: Internal repository question - stopping repo1
Is there any way to do the same thing (always hit only one internal repo) using only a shared parent pom.xml (and specifically without altering anything in settings.xml, as I know of no automatic way to share a common settings.xml among a team)? Dan -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 3:46 PM To: Maven Users List Subject: Re: Internal repository question - stopping repo1 You need a to set up a mirror pointing to your local repo as a mirrorOf*/mirrorOf in your settings.xml file, and Maven will only go to that server for all of its files. Wayne On 4/23/08, Daniel King [EMAIL PROTECTED] wrote: I'm using Archiva 1.0.2 and Maven 2.0.9 using JDK 1.6 on Windows XP. I've installed Maven on my local machine and Maven and Archiva on a development machine (Not sure if Maven is needed on the dev machine with Archiva but I think it is). For some reason I clear out my local repository and do a build, I see plugins being downloaded from repo1. I thought that those plugins would be downloaded to my internal repository. Then when I clear out the local repository and do a build again it would only get those from my internal repository. However it is still going out to repo1 for plugins. In my project's pom.xml I have the following: repositories repository idinternal/id nameInternal Maven Repository/name layoutdefault/layout urlfile://\\buildMachine\repository/url snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idinternal/id nameInternal Maven Plugin Repository/name urlfile://\\buildMachine\repository/url layoutdefault/layout snapshots enabledfalse/enabled /snapshots releases updatePolicynever/updatePolicy /releases /pluginRepository /pluginRepositories distributionManagement repository idinternal/id urlfile://\\ buildMachine \repository/url /repository snapshotRepository idinternal/id urlfile://\\ buildMachine \repository/url uniqueVersiontrue/uniqueVersion /snapshotRepository /distributionManagement I basically need to setup Maven/Archiva as an internal repository on a build machine and have no network traffic go beyond that build machine ie not going to repo1. So if something isn't on the internal repo then a build smith would go and manually install and bless whatever they need. Security doesn't like the idea of going out to remote repos and just bringing stuff down. So after looking through the archives and reading other posts, I'm confused on what I'm doing wrong. I don't fully understand the servers and mirrors tags and if they even matter to me at this point. Any help would be appreciated even if it is to tell me to read a certain section of the manual again. Thanks, Daniel King -- This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I have a problem with maven-release-plugin !
We have a similar structure, we release the super-pom and the poms of the subsystems always only have a released version of the parent. Nicole On 24/04/2008, Eugene Batogov [EMAIL PROTECTED] wrote: Hello ! I am trying to use maven-release-plugin. Our project is consist of 3 levels. 1. At top is SUPER-POM 2. At middle are pom files of subsystems, which have parent - SUPER-POM. 3. At bottom ara pom files of components, which have parent - pom file subsystem. Our SUPER-POM file present base line of development. But when I am trying invoke: mvn release:prepare against subsystem pom-file, plugin ask about releasing SUPER-POM, then I type required number of version SUPER-POM. Plugin are resuming execution releasing. BUT After execution mvn release:prepare, version SUPER-POM in parent tag of subsystem POM remain prior ?!? This is bug, or I something do wrong? Thanks in advance. -- Best Regards, Eugene Batogov a.k.a JohnBat26. e-mail: [EMAIL PROTECTED] IM: ICQ: 198710313, Yahoo/AIM/Google/Jabber(jabber.ru)/MSN/Skype: JohnBat26. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: passing parameters to plugin Archetype
I did it too. Thanks for your attention.
iiggzz wrote:
I found it out! So if anybody has the same problem go ahead and ask me.
Now I have another problem. I need to specify the path to my files like
this: ${projectName}-mymodule/myfile.txt so after creation it should look
like this: helloworld-mymodule.
--
View this message in context:
http://www.nabble.com/passing-parameters-to-plugin-Archetype-tp16807963s177p16850915.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
jars appear timestamped in wars and zips since 2.0.9
Hi, In Maven 2.0.8 I built my war with maven-war-plugin:2.1-alpha-1 and my zip with maven-assembly-plugin:2.2-beta-2 The war/zip contained dependent jars as jarname-version-SNAPSHOT.jar when the depend jars were located in the localrepository. The war/zip contained dependent jars as jarname-version-timestamp.jar when the depend jars were located in the central (company) repository and first need to be downloaded. The difference was in the mavenmetadata-local.xml, where a localCopytrue/localCopy entry exists: ?xml version=1.0 encoding=UTF-8 ? metadata ... versioning snapshot localCopytrue/localCopy /snapshot ... /versioning /metadata Now, In Maven 2.0.9 I still built my war with maven-war-plugin:2.1-alpha-1 and my zip with maven-assembly-plugin:2.2-beta-2 But now, the mavenmetadata-local.xml file doesn´t contain a localCopytrue/localCopy entry anymore - even if I paste one, it gets deleted during the build ! This results in always getting wars/zips containing dependent jars as jarname-version-timestamp.jar. And that´s not very nice, because in the MANIFEST.MF of same jars the jarname-version-SNAPSHOT.jar is mentioned, which doesn´t match the content of the war/zip, Resulting in NoClassDefFoundError and so on, caused by an invalid classpath The funny point about that story is that with the maven-ear-plugin the jars appear as jarname-version-SNAPSHOT.jar in the generated *.ear. = Any idea how to fix that for the war and zip? Why is there a difference in handling jars between the war, ear and assembly plugins? Isn´t it always the same? Thanx, Torsten
Re: keep out META-INF/context.xml
I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? Thanks Alessandro Ferrucci - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
where to put the 'data' directory for hsqldb?
hi, i am a maven newbie, i want use hsqldb as my development database,normally it need a directroy to store the related files where to put this directory within the maven's directory structure? thanks a lot! oliver.maven 2008-04-24
RE: keep out META-INF/context.xml
Alessandro Ferrucci wrote: I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? You *need* a context.xml for a web app and the context.xml is defined by a configuration parameter. Therefore exclusions don't apply here :) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: where to put the 'data' directory for hsqldb?
Hi Oliver, oliver.maven wrote: hi, i am a maven newbie, i want use hsqldb as my development database,normally it need a directroy to store the related files where to put this directory within the maven's directory structure? thanks a lot! there's no defined place. However, what are you doing with it? E.g. if you need it for unit tests you may keep the files somewhere like src/test/db and copy the complete directory over to target/db (possibly in yout setUp) and point HSQLDB to that place. That way you always stgart with a defined content and you do not modify the files you're keeping in your version control. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep out META-INF/context.xml
Well actually you don't NEED to have the context.xml in a webapp, WEB-INF is required but META-INF/context.xml is not required (perhaps maven assumes that it's required, but that is a different argument). Is there an override param/element to have it excluded? Or am I screwed in this scenario? Is there NO way to do it? Also what do you mean by: context.xml is defined by a configuration paramater On 4/24/08 11:39 AM, Jörg Schaible [EMAIL PROTECTED] wrote: Alessandro Ferrucci wrote: I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? You *need* a context.xml for a web app and the context.xml is defined by a configuration parameter. Therefore exclusions don't apply here :) - Jörg - 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]
Maven2 Newbie - Jar Dependencies
Hi, I am relatively new to maven. I am developing a web app that is dependent on multiple jar files supplied by another vendor. I need to setup my project so it can compile with this vendors jars on the class path, but am not sure of the best way to approach this. I have tried unzipping all the jar files and re-packaging as one big jar, then installing an external dependency, but that breaks some of the Manifest docs in some of the jars. Any suggestions on the simplest way to do this would be appreciated. Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep out META-INF/context.xml
Did you not see Daniel Allen's response to your original email? Did you try his suggested configuration? What happened when you tried, did it not work? Wayne On 4/24/08, Alessandro Ferrucci [EMAIL PROTECTED] wrote: Well actually you don't NEED to have the context.xml in a webapp, WEB-INF is required but META-INF/context.xml is not required (perhaps maven assumes that it's required, but that is a different argument). Is there an override param/element to have it excluded? Or am I screwed in this scenario? Is there NO way to do it? Also what do you mean by: context.xml is defined by a configuration paramater On 4/24/08 11:39 AM, Jörg Schaible [EMAIL PROTECTED] wrote: Alessandro Ferrucci wrote: I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? You *need* a context.xml for a web app and the context.xml is defined by a configuration parameter. Therefore exclusions don't apply here :) - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 Newbie - Jar Dependencies
mvn install:install-file each of the vendor jars independently. Then specify a dependency on each of them in your project's pom.xml file. This is the usual way to declare dependencies. Is there a reason this is not acceptable? Wayne On 4/24/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I am relatively new to maven. I am developing a web app that is dependent on multiple jar files supplied by another vendor. I need to setup my project so it can compile with this vendors jars on the class path, but am not sure of the best way to approach this. I have tried unzipping all the jar files and re-packaging as one big jar, then installing an external dependency, but that breaks some of the Manifest docs in some of the jars. Any suggestions on the simplest way to do this would be appreciated. Thanks. - 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: RE: where to put the 'data' directory for hsqldb?
i am not doing unit tests for now , i only want to run the application with hsqldb configured.Previously i put a directory called data in my project's root directory,and used jdbc:hsqldb:data/db-name url to access dabtabse,so where to put the data directory in maven, so that the jdbc:hsqldb:data/ db-name still can work,thank you so much! oliver.maven 2008-04-25 发件人： J�rg_Schaible 发送时间： 2008-04-24 23:46:34 收件人： Maven Users List 抄送： 主题： RE: where to put the 'data' directory for hsqldb? Hi Oliver, oliver.maven wrote: hi, i am a maven newbie, i want use hsqldb as my development database,normally it need a directroy to store the related files where to put this directory within the maven's directory structure? thanks a lot! there's no defined place. However, what are you doing with it? E.g. if you need it for unit tests you may keep the files somewhere like src/test/db and copy the complete directory over to target/db (possibly in yout setUp) and point HSQLDB to that place. That way you always stgart with a defined content and you do not modify the files you're keeping in your version control. - J�rg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: where to put the 'data' directory for hsqldb?
You should try to put it in src/main/resources/data and then access it with the same descriptor (jdbc:hsqldb:data/db-name) Tomas Darbois Edifixio Grenoble - Projet ScorWare 04 76 29 89 27 [EMAIL PROTECTED] -Message d'origine- De : oliver.maven [mailto:[EMAIL PROTECTED] Envoyé : jeudi 24 avril 2008 18:16 À : Maven Users List Objet : Re: RE: where to put the 'data' directory for hsqldb? i am not doing unit tests for now , i only want to run the application with hsqldb configured.Previously i put a directory called data in my project's root directory,and used jdbc:hsqldb:data/db-name url to access dabtabse,so where to put the data directory in maven, so that the jdbc:hsqldb:data/ db-name still can work,thank you so much! oliver.maven 2008-04-25 发件人： J鰎g_Schaible 发送时间： 2008-04-24 23:46:34 收件人： Maven Users List 抄送： 主题： RE: where to put the 'data' directory for hsqldb? Hi Oliver, oliver.maven wrote: hi, i am a maven newbie, i want use hsqldb as my development database,normally it need a directroy to store the related files where to put this directory within the maven's directory structure? thanks a lot! there's no defined place. However, what are you doing with it? E.g. if you need it for unit tests you may keep the files somewhere like src/test/db and copy the complete directory over to target/db (possibly in yout setUp) and point HSQLDB to that place. That way you always stgart with a defined content and you do not modify the files you're keeping in your version control. - J鰎g - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2Eclipse -workspace resolution
On Thu, Apr 24, 2008 at 12:46 AM, Salgar, Mehmet (external) [EMAIL PROTECTED] wrote: snip I would try to find the JIRA for m2eclipse and write this there... snip Sounds like you may be running into this (or a variation of)... http://jira.codehaus.org/browse/MNGECLIPSE-438
profile legacy problem
Hi, I have a problem with legacy in maven 2, i've configured a profile called myProfilein my POM parent and i have my project pom which inherits this pom parent, but when i execute mvn -PmyProfile myProject the profile is not activated, can you see the problem thanks -- View this message in context: http://www.nabble.com/profile-legacy-problem-tp16851033s177p16851033.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep out META-INF/context.xml
I tried Daniel's suggestion but that unfortunately did not work. Alessandro Ferrucci :) On 4/24/08 12:13 PM, Wayne Fay [EMAIL PROTECTED] wrote: Did you not see Daniel Allen's response to your original email? Did you try his suggested configuration? What happened when you tried, did it not work? Wayne On 4/24/08, Alessandro Ferrucci [EMAIL PROTECTED] wrote: Well actually you don't NEED to have the context.xml in a webapp, WEB-INF is required but META-INF/context.xml is not required (perhaps maven assumes that it's required, but that is a different argument). Is there an override param/element to have it excluded? Or am I screwed in this scenario? Is there NO way to do it? Also what do you mean by: context.xml is defined by a configuration paramater On 4/24/08 11:39 AM, Jörg Schaible [EMAIL PROTECTED] wrote: Alessandro Ferrucci wrote: I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? You *need* a context.xml for a web app and the context.xml is defined by a configuration parameter. Therefore exclusions don't apply here :) - Jörg - 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]
Re: keep out META-INF/context.xml
Hello folks, I solved this issue, what got it to work was including warSourceExcludes META-INF/context.xml /warSourceExcludes In the configuration element of my maven-war-plugin. Thanks for Alan Stoll for pointing this out. Alessandro Ferrucci :) On 4/24/08 1:27 PM, Alessandro Ferrucci [EMAIL PROTECTED] wrote: I tried Daniel's suggestion but that unfortunately did not work. Alessandro Ferrucci :) On 4/24/08 12:13 PM, Wayne Fay [EMAIL PROTECTED] wrote: Did you not see Daniel Allen's response to your original email? Did you try his suggested configuration? What happened when you tried, did it not work? Wayne On 4/24/08, Alessandro Ferrucci [EMAIL PROTECTED] wrote: Well actually you don't NEED to have the context.xml in a webapp, WEB-INF is required but META-INF/context.xml is not required (perhaps maven assumes that it's required, but that is a different argument). Is there an override param/element to have it excluded? Or am I screwed in this scenario? Is there NO way to do it? Also what do you mean by: context.xml is defined by a configuration paramater On 4/24/08 11:39 AM, Jörg Schaible [EMAIL PROTECTED] wrote: Alessandro Ferrucci wrote: I'm just bumping this email back up the listserv stack to see if anyone knows how I can do this :) thanks Alessandro Ferrucci Alessandro Ferrucci wrote: hey guys I'm trying to exclude a context.xml from a webapp. I have the following snippet in my build element: resources resource directorysrc/main/resources/directory excludes exclude**/application.jmx.properties/exclude exclude**/log4j.properties/exclude /excludes /resource resource directorysrc/main/java/webapp/META-INF/directory excludes exclude**/context.xml/exclude /excludes /resource /resources my directory structure over context.xml looks like this: src/main/java/webapp/META-INF/context.xml context.xml is still not being excluded, but application.jmx.properties and log4j.properties are, anyone know what gives? You *need* a context.xml for a web app and the context.xml is defined by a configuration parameter. Therefore exclusions don't apply here :) - Jörg - 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]
RE: Naming snapshots with alphas / betas
Use the former, the latter might create problems in dependency resolution. Good point, thanks. ~Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding maven-compiler-plugin to super POM
Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp16851994s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Adding maven-compiler-plugin to super POM
In your pom.xml file add the following: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -Original Message- From: mikeottinger [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 4:06 PM To: users@maven.apache.org Subject: Adding maven-compiler-plugin to super POM Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp168519 94s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Adding maven-compiler-plugin to super POM
You need to specify this pom as a parent element in your child pom...simply adding it in the parent directory doesn't magically do it for you ;-) Also, super-pom is normally reserved to mean the pom included in the maven core...the true super pom. A more appropriate term is a corporate pom for a corp wide setup, or just a parent pom. -Original Message- From: mikeottinger [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 4:06 PM To: users@maven.apache.org Subject: Adding maven-compiler-plugin to super POM Hello, I'm trying to come up with a way such that new maven projects I create are ready to use JDK 1.5 by inheritance from a super POM. I'm having no luck, hence this post. I'm new to maven (thanks to this forum for telling me maven defaults to jdk 1.3) so super POMs are a little unfamiliar to me, from searching this forum I'm told that creating a pom.xml in the parent directory of my project somehow does the trick. I created one, added the plugin for maven-compiler-plugin, ran mvn install, but I still get jdk compiling errors. Does anyone have any suggestions in setting a jdk level globally for my environment? Are super POMs even the way to go? I tend to create a lot of little projects for prototyping and having to tell Maven I want jdk 1.5 for each of them is annoying. Thanks in advance! -- View this message in context: http://www.nabble.com/Adding-maven-compiler-plugin-to-super-POM-tp168519 94s177p16851994.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-checkstyle-plugin basedir
I'm trying to migrating my build process from Ant to Maven and have been
struggling quite a bit so far.
I want to integrate CheckStyle into the build, so I've added the
following:
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
configuration
failOnViolationfalse/failOnViolation
enableRulesSummaryfalse/enableRulesSummary
configLocationconfig/CheckStyle Rules.xml/configLocation
/configuration
/plugin
/plugins
/reporting
My CheckStyle Rules.xml file is location in project base
directory/config.
I'm receiving the following error:
C:\workspace\sharesmvn checkstyle:check -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'checkstyle'.
[INFO]
[INFO] Building shares
[INFO]task-segment: [checkstyle:check]
[INFO]
[INFO] Preparing checkstyle:check
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderRe
sourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
in any resource loader.
[INFO] Velocimacro : error using VM library template
VM_global_library.vm : org.apache.velocity.exception.Res
ourceNotFoundException: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro : VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
may NOT replace previous VM definition
s
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
be global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [checkstyle:checkstyle]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: Failed during checkstyle configuration
Property ${basedir} has not been set
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has
occurred in Checkstyle report generation.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle
(DefaultLifecycleExecutor.j
ava:931)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Defaul
tLifecycleExecutor.java:767
)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.
java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleEx
ecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.ja
va:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
Re: [newby] how to include/package private libs/*.jar
Hi Nick, On 24/04/2008, at 6:50 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: It would be something like: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idlist-deps/id phasegenerate-resources/phase goals goallist/goal /goals configuration outputFilefoo.txt/outputFile /configuration /execution /executions plugins /build Nice. Thanks for that. And/Or I suppose I could use antrun to transform the output as needed. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-checkstyle-plugin basedir
That is a weird one, but try changing your configLocation to :
configLocation${basedir}/config/CheckStyle Rules.xml/configLocation
This will give an absolute path to checkstyle. You also might want to
get rid of the space in the file name.
-Original Message-
From: Hart, Leo [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 24, 2008 5:56 PM
To: users@maven.apache.org
Subject: maven-checkstyle-plugin basedir
I'm trying to migrating my build process from Ant to Maven and have been
struggling quite a bit so far.
I want to integrate CheckStyle into the build, so I've added the
following:
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
configuration
failOnViolationfalse/failOnViolation
enableRulesSummaryfalse/enableRulesSummary
configLocationconfig/CheckStyle Rules.xml/configLocation
/configuration
/plugin
/plugins
/reporting
My CheckStyle Rules.xml file is location in project base
directory/config.
I'm receiving the following error:
C:\workspace\sharesmvn checkstyle:check -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'checkstyle'.
[INFO]
[INFO] Building shares
[INFO]task-segment: [checkstyle:check]
[INFO]
[INFO] Preparing checkstyle:check
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderRe
sourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] **
[INFO] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org\apache\velocity\runtime\defaults\velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive:
org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template :
VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm'
in any resource loader.
[INFO] Velocimacro : error using VM library template
VM_global_library.vm : org.apache.velocity.exception.Res
ourceNotFoundException: Unable to find resource 'VM_global_library.vm'
[INFO] Velocimacro : VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in
templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline
may NOT replace previous VM definition
s
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will
be global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [checkstyle:checkstyle]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in Checkstyle report generation.
Embedded error: Failed during checkstyle configuration
Property ${basedir} has not been set
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error has
occurred in Checkstyle report generation.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle
(DefaultLifecycleExecutor.j
ava:931)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Defaul
tLifecycleExecutor.java:767
)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:529)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.
java:512)
at
RE: profile legacy problem
I have a problem with legacy in maven 2, i've configured a profile called myProfilein my POM parent and i have my project pom which inherits this pom parent, but when i execute mvn -PmyProfile myProject the profile is not activated, can you see the problem Yes it's right over oh you don't include anything to look at. NeverMind. ;-) Seriously though, a little snippet of your pom with the profile definition and an explanation about why you think it's not activated would help. A few tips. Try mvn help:effective-profiles -PmyProfile and see if your profile is listed. Then try mvn help:effective-pom -PmyProfile to see what the pom looks like...this might help you figure out what is happening. -- Brian Fox Apache Maven PMC http://blogs.sonatype.com/brian/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using a distribution built by the assembly plugin as a dependency...
Hello, In the FAQ located at: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html It says the following: Can I use an artifact created by the assembly plugin as a dependency? and the short answer is yes but it doesn't give an example. Does anyone have an example of how to do this? Thanks in advance. Michael.
RE: Using a distribution built by the assembly plugin as a dependency...
Actually yes: http://blogs.sonatype.com/brian/2008/04/17/120848550.html -Original Message- From: Michael Ransley [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 7:21 PM To: users@maven.apache.org Subject: Using a distribution built by the assembly plugin as a dependency... Hello, In the FAQ located at: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html It says the following: Can I use an artifact created by the assembly plugin as a dependency? and the short answer is yes but it doesn't give an example. Does anyone have an example of how to do this? Thanks in advance. Michael. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ant ftp from mave plugin works on one project but not another
Hi All,
Recently I found out from this forum how to get an ant ftp target to work
from maven.
I got it working one one project, but the exact same plugin did not work on
another project on another machine.
It gave me errors as if I did not have the dependencies correct
this is the error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Could not create task or type of type: ftp.
This is the plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
dependencies
/dependency
!-- add dependency so ftp will run --
dependency
groupIdant/groupId
artifactIdant-commons-net/artifactId
version1.6.5/version
/dependency
dependency
groupIdcommons-net/groupId
artifactIdcommons-net/artifactId
version1.4.1/version
/dependency
/dependencies
executions
execution
idantrun_installer/id
phaseinstall/phase
configuration
tasks
echo${project.parent.parent.basedir}/echo
property name=stamp
value=${stamp.version}/
property name=env.IA_PATH_NRM_HOME
value=${project.parent.parent.basedir}/
ant antfile=./resources/ant/build.xml
inheritRefs=true
target name=installer/
/ant
!-- add the ftp copy to the build --
ftp server=ftp.server.net
userid=user1 password=pass
remotedir=installer
fileset
dir=/target/vem_Build_Output/Web_Installers/InstData/Windows/NoVM
include
name=**/*.exe/
include
name=**/*.bin/
/fileset
/ftp
/tasks
/configuration
Any thoughts on why this would work in one project but not another?
Thanks
goals
goalrun/goal
/goals
/execution
/executions
/plugin
--
View this message in context:
http://www.nabble.com/ant-ftp-from-mave-plugin-works-on-one-project-but-not-another-tp16863813s177p16863813.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: ant ftp from mave plugin works on one project but not another
I have an idea: maven uses the first plugin config it sees, so if that
other project is using ant anywhere else, and it runs first, the
dependency won't actually be used.
-Original Message-
From: bheath [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 24, 2008 7:58 PM
To: users@maven.apache.org
Subject: ant ftp from mave plugin works on one project but not another
Hi All,
Recently I found out from this forum how to get an ant ftp target to
work
from maven.
I got it working one one project, but the exact same plugin did not work
on
another project on another machine.
It gave me errors as if I did not have the dependencies correct
this is the error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: Could not create task or type of type: ftp.
This is the plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
dependencies
/dependency
!-- add dependency so ftp will run --
dependency
groupIdant/groupId
artifactIdant-commons-net/artifactId
version1.6.5/version
/dependency
dependency
groupIdcommons-net/groupId
artifactIdcommons-net/artifactId
version1.4.1/version
/dependency
/dependencies
executions
execution
idantrun_installer/id
phaseinstall/phase
configuration
tasks
echo${project.parent.parent.basedir}/echo
property name=stamp
value=${stamp.version}/
property name=env.IA_PATH_NRM_HOME
value=${project.parent.parent.basedir}/
ant antfile=./resources/ant/build.xml
inheritRefs=true
target name=installer/
/ant
!-- add the ftp copy to the
build --
ftp
server=ftp.server.net userid=user1 password=pass
remotedir=installer
fileset
dir=/target/vem_Build_Output/Web_Installers/InstData/Windows/NoVM
include
name=**/*.exe/
include
name=**/*.bin/
/fileset
/ftp
/tasks
/configuration
Any thoughts on why this would work in one project but not another?
Thanks
goals
goalrun/goal
/goals
/execution
/executions
/plugin
--
View this message in context:
http://www.nabble.com/ant-ftp-from-mave-plugin-works-on-one-project-but-
not-another-tp16863813s177p16863813.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
API to figure out the exact URL of a deployed artifact?
Hello, I would like to write a generic mojo to download a deployed artifact with given groupId, artifactId, and version as params. For snapshot, i like to get the latest one. I spent some times with deploy plugin hoping for a clue but not finding any thing yet. Suggestions are greatly appreciated. Thanks -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: API to figure out the exact URL of a deployed artifact?
How is that different than the dependency:copy where it takes all those things? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 11:20 PM To: Maven Users List Subject: API to figure out the exact URL of a deployed artifact? Hello, I would like to write a generic mojo to download a deployed artifact with given groupId, artifactId, and version as params. For snapshot, i like to get the latest one. I spent some times with deploy plugin hoping for a clue but not finding any thing yet. Suggestions are greatly appreciated. Thanks -Dan - 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: API to figure out the exact URL of a deployed artifact?
to use dependency plugin, user have to declare the artifact as dependency. for my case, I would like to allow user to pass them in as -D properties do you think we can overwrite the dependency value as properties? any how let me try this method first. Thanks -D On Thu, Apr 24, 2008 at 8:29 PM, Brian E. Fox [EMAIL PROTECTED] wrote: How is that different than the dependency:copy where it takes all those things? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 11:20 PM To: Maven Users List Subject: API to figure out the exact URL of a deployed artifact? Hello, I would like to write a generic mojo to download a deployed artifact with given groupId, artifactId, and version as params. For snapshot, i like to get the latest one. I spent some times with deploy plugin hoping for a clue but not finding any thing yet. Suggestions are greatly appreciated. Thanks -Dan - 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: API to figure out the exact URL of a deployed artifact?
Brian, the dependency plugin works, but there are a few issues that I need to address for my client: 1. I am dealing with large artifacts ( order of 100M like installer ), download this type of snappshot artifacts thru dependency will consume large amount diskspace over time. But this can be resolved via another plugin ( not yet develop ) to purge the artifact location in local repo. 2. Even if issue in one can be resolved in another plugin, my user will need to configure bunch of configurations in the pom dependency, maven-dependency-plugin, purge plugin, and my plugin. Now if can achieve what I need in initial email then they only need to configure my plugin alone, which is much nicer. any how, I you know away to get the direct URL please let me know Thanks for the inputs. -D On Thu, Apr 24, 2008 at 8:39 PM, Dan Tran [EMAIL PROTECTED] wrote: to use dependency plugin, user have to declare the artifact as dependency. for my case, I would like to allow user to pass them in as -D properties do you think we can overwrite the dependency value as properties? any how let me try this method first. Thanks -D On Thu, Apr 24, 2008 at 8:29 PM, Brian E. Fox [EMAIL PROTECTED] wrote: How is that different than the dependency:copy where it takes all those things? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 11:20 PM To: Maven Users List Subject: API to figure out the exact URL of a deployed artifact? Hello, I would like to write a generic mojo to download a deployed artifact with given groupId, artifactId, and version as params. For snapshot, i like to get the latest one. I spent some times with deploy plugin hoping for a clue but not finding any thing yet. Suggestions are greatly appreciated. Thanks -Dan - 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: API to figure out the exact URL of a deployed artifact?
Hi Dan! I think i generally understand your problem, since i have a similar scenario: 120MB of testdata + many ~30MB ears packaged for and needed by my OperationsInfrastructure guys in the US. But, would you like to cope with all the different setup scenarios, like archiva, maven-proxy, etc? Didn't you need to either extend wagon or check the settings.xml cascade to lookup all needed things by yourself? For me, I simply gave the deeplink to our internal repo's ear directory to my OI guys, and they can download all the files they need via a html browser. But then again, they only can access my internal repo via a ssh tunnel over a jumpbox, so any direct download (also via maven) would fail anyway. For me, it would be nice to configure a plugin which sends an email with a simple http href pointing to the artifact to a list of given email adresses. If the mail body is inside the plugin config, it would also be possible to fill the actual artifact name, version, etc via a maven variable. just a few thoughts, hope this isn't too confusing ;) LieGrü, strub --- Dan Tran [EMAIL PROTECTED] schrieb: Brian, the dependency plugin works, but there are a few issues that I need to address for my client: 1. I am dealing with large artifacts ( order of 100M like installer ), download this type of snappshot artifacts thru dependency will consume large amount diskspace over time. But this can be resolved via another plugin ( not yet develop ) to purge the artifact location in local repo. 2. Even if issue in one can be resolved in another plugin, my user will need to configure bunch of configurations in the pom dependency, maven-dependency-plugin, purge plugin, and my plugin. Now if can achieve what I need in initial email then they only need to configure my plugin alone, which is much nicer. any how, I you know away to get the direct URL please let me know Thanks for the inputs. -D On Thu, Apr 24, 2008 at 8:39 PM, Dan Tran [EMAIL PROTECTED] wrote: to use dependency plugin, user have to declare the artifact as dependency. for my case, I would like to allow user to pass them in as -D properties do you think we can overwrite the dependency value as properties? any how let me try this method first. Thanks -D On Thu, Apr 24, 2008 at 8:29 PM, Brian E. Fox [EMAIL PROTECTED] wrote: How is that different than the dependency:copy where it takes all those things? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, April 24, 2008 11:20 PM To: Maven Users List Subject: API to figure out the exact URL of a deployed artifact? Hello, I would like to write a generic mojo to download a deployed artifact with given groupId, artifactId, and version as params. For snapshot, i like to get the latest one. I spent some times with deploy plugin hoping for a clue but not finding any thing yet. Suggestions are greatly appreciated. Thanks -Dan - 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] __ Gesendet von Yahoo! Mail. Mehr Möglichkeiten, in Kontakt zu bleiben. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: API to figure out the exact URL of a deployed artifact?
--- Mark Struberg [EMAIL PROTECTED] schrieb: For me, it would be nice to configure a plugin which sends an email with a simple http href pointing to the artifact to a list of given email adresses. If the mail body is inside the plugin config, it would also be possible to fill the actual artifact name, version, etc via a maven variable. To make things more clear: The first part of the href does not change at all, only the artifact version does. So I'd hardcode this in my email body. LieGrü, strub __ Gesendet von Yahoo! Mail. Mehr Möglichkeiten, in Kontakt zu bleiben. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
