force maven to redownload/refresh released dependencies
is there a way to force a project to refresh certain dependencies every build? i.e. replicate SNAPSHOT behaviour with released artifacts S
Re: force maven to redownload/refresh released dependencies
ok, thanks basically for liability reasons for a certain project, we have to provide specific times of when a project was built and when/where all its dependencies were retrieved at/from we have to ensure a sanitary build for all these JARs and a complete log of going from 0 to 100 for the build; so we are faced with either clearing out the .m2 each time I was wondering if there was a way to force this through maven On Fri, Jul 30, 2010 at 12:57 PM, Manos Batsis manos_li...@geekologue.comwrote: On 07/30/2010 07:16 PM, Wayne Fay wrote: is there a way to force a project to refresh certain dependencies every build? i.e. replicate SNAPSHOT behaviour with released artifacts Absolutely not. Released artifacts MUST NOT CHANGE. +1, never ever ;-) Released artifact versioning is supposed to guarantee consistency. Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: force maven to redownload/refresh released dependencies
not my organization - our client wants a log of everything that came down the pipe to create this build, that's all it's not a matter of worry or concern, so no need to be overly dramatic some companies just want a complete audit trail of what they paid for, which is fine by me I'm looking for technical solutions because I'm in a technical role, not policy advice; sometimes in this business you delivery what you're paid to deliver regardless of whether it makes sense to you we cannot respond to our clients saying the guys on the maven list told us that your request is stupid deleting the m2 works, I was just curious to see if there was a switch in maven to force all downloads again On Fri, Jul 30, 2010 at 2:47 PM, Jason van Zyl ja...@sonatype.com wrote: On Jul 30, 2010, at 2:21 PM, Shan Syed wrote: ok, thanks basically for liability reasons for a certain project, we have to provide specific times of when a project was built and when/where all its dependencies were retrieved at/from we have to ensure a sanitary build for all these JARs and a complete log of going from 0 to 100 for the build; so we are faced with either clearing out the .m2 each time I was wondering if there was a way to force this through maven Put the artifacts in a repository manager where you download the released artifact once and then manage it from your infrastructure. Once the artifact is within your infrastructure the released artifact is not going to change unless someone from within your organization changes it. They shouldn't, and can't if your permissions are setup correctly, and so the requirement of using the same artifacts and their origin becomes moot. If your organization cares that much about liability concerns then you absolutely should not be connecting to the outside world every time you build. On Fri, Jul 30, 2010 at 12:57 PM, Manos Batsis manos_li...@geekologue.comwrote: On 07/30/2010 07:16 PM, Wayne Fay wrote: is there a way to force a project to refresh certain dependencies every build? i.e. replicate SNAPSHOT behaviour with released artifacts Absolutely not. Released artifacts MUST NOT CHANGE. +1, never ever ;-) Released artifact versioning is supposed to guarantee consistency. Manos - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha
Re: force maven to redownload/refresh released dependencies
it only applies to our final release cuts, not our day-to-day just once for this project really; I wanted to insert such this switch (if existed) in our delivery build profile we use archiva for everything else, and actually only make use of public maven repositories when we up a version of our dependencies, which is rare because of change control it's all weird stuff, I know, but sometimes I just don't question it On Fri, Jul 30, 2010 at 4:51 PM, Wayne Fay wayne...@gmail.com wrote: deleting the m2 works, I was just curious to see if there was a switch in maven to force all downloads again This makes absolutely no sense, doesn't change your BOM, and is just wasteful. Consumes bandwidth unnecessarily from a resource that is being used by the whole Maven community. I'd think that if you had enough developers doing this on every machine on a consistent basis (eg every build), it might add up to enough traffic to get you on a blacklist somewhere... You really need to install Nexus or another MRM, this is just plain dumb. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: force maven to redownload/refresh released dependencies
no, this isn't in regard to our own published artifacts I regret starting this thread, I apologize I didn't mean this question to be an affront to maven conventions - I just need to figure out a better way to capture a full log they even want a log of how the build environment was downloaded and installed On Fri, Jul 30, 2010 at 5:04 PM, Paul Benedict pbened...@apache.org wrote: There is a maxim to follow when deploying: do not redeploy a version more than once. Once you deploy version X.Y.Z, it should never be updated, and those who download it never need to download it again. So, back to the original problem, are you guys doing that? On Fri, Jul 30, 2010 at 3:57 PM, Shan Syed shan...@gmail.com wrote: it only applies to our final release cuts, not our day-to-day just once for this project really; I wanted to insert such this switch (if existed) in our delivery build profile we use archiva for everything else, and actually only make use of public maven repositories when we up a version of our dependencies, which is rare because of change control it's all weird stuff, I know, but sometimes I just don't question it On Fri, Jul 30, 2010 at 4:51 PM, Wayne Fay wayne...@gmail.com wrote: deleting the m2 works, I was just curious to see if there was a switch in maven to force all downloads again This makes absolutely no sense, doesn't change your BOM, and is just wasteful. Consumes bandwidth unnecessarily from a resource that is being used by the whole Maven community. I'd think that if you had enough developers doing this on every machine on a consistent basis (eg every build), it might add up to enough traffic to get you on a blacklist somewhere... You really need to install Nexus or another MRM, this is just plain dumb. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
understanding SNAPSHOTS.. where?
simple question; on this page http://maven.apache.org/guides/getting-started/index.html it states: *version* This element indicates the version of the artifact generated by the project. Maven goes a long way to help you with version management and you will often see the SNAPSHOT designator in a version, which indicates that a project is in a state of development. We will discuss the use of snapshots and how they work further on in this guide. I can't find the mentioned details on the use of snapshots I conceptually understand it of course, I just want to read what maven says about it directly thanks, S
what happened to release:update-versions?
is it gone? perhaps in favor of the http://mojo.codehaus.org/versions-maven-plugin/ plugin? mvn release:update-versions ... [INFO] Required goal not found: release:update-versions in org.apache.maven.plugins:maven-release-plugin:2.0-beta-8 and mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:update-versions ... [INFO] Required goal not found: org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:update-versions in org.apache.maven.plugins:maven-release-plugin:2.0-beta-9
applying finalName of dependencies when project is packaging
I know there is already a lot of discussion around the topic of artifacts not using finalName when they are installed into a repository (remote or local), but is there a way to enforce that the dependencies, when packaged into the using project, are packaged with their finalNames? example: Project A (a POM that ZIPs its WAR dependencies) uses B, C, D, etc.. as dependencies (all WARs) B's finalName is Bee, C's is Cee, etc... by default, when A packages, it creates a ZIP of all its dependencies (using an assembly descriptor), with their fully qualified repository names, as expected is there an easy way to ask maven to use the finalNames for the dependencies instead? S
Re: applying finalName of dependencies when project is packaging
Hi, We have a very large set of WAR projects (web services, web applications, static websites, etc) as part of a product offering. Various versions and combinations of these are delivered to clients, but there is no immediate understand of who gets what WARs, what versions, etc. So I am using maven to manage this: I have a POM for each delivery, which just has the dependencies listed, and an assembly descriptor that ZIPs them all conveniently, for deployment/DL to various environments. Each developer has specified a finalName for their WAR, but there is no convention, some require just the version info lopped off, some need a totally different name from their artifact, etc.. there is no reliable way to calculate the desired finalName, for various business reasons. So in my ZIPs for each set of packaged goods, I would like the WARs to have their finalNames, as opposed to their fully qualified maven names. Shan On Tue, Jul 20, 2010 at 4:54 PM, Kalle Korhonen kalle.o.korho...@gmail.comwrote: Always a good idea to state *why* you might want to do this so people can provide alternatives. AFAIK the answer is no to your question, but if, for example, you just want to use the artifact name and strip out the version info from the filename, you can use outputFileNameMapping (see http://maven.apache.org/plugins/maven-assembly-plugin/component.html ). Kalle On Tue, Jul 20, 2010 at 1:26 PM, Shan Syed shan...@gmail.com wrote: I know there is already a lot of discussion around the topic of artifacts not using finalName when they are installed into a repository (remote or local), but is there a way to enforce that the dependencies, when packaged into the using project, are packaged with their finalNames? example: Project A (a POM that ZIPs its WAR dependencies) uses B, C, D, etc.. as dependencies (all WARs) B's finalName is Bee, C's is Cee, etc... by default, when A packages, it creates a ZIP of all its dependencies (using an assembly descriptor), with their fully qualified repository names, as expected is there an easy way to ask maven to use the finalNames for the dependencies instead? S - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Relationsship pom.xml and build.xml from Ant
maven/POMs can make use of ant build scripts, so be wary of this scenario; it is fairly common to use ant via maven So if I get a project which contains a pom.xml and a build.xml then the developer offers to use either Ant or Maven. If I select Maven then I can delete build.xml. If I select Ant then I can delete pom.xml without harm. also a project can have various components that build in different ways, so again, I wouldn't make the above assumption there is no way to convert an ant build script into a maven POM, because ant scripts don't have any kind of enforced convention; it would be impossible to write such a converter On Wed, Jul 14, 2010 at 1:02 PM, benxs bxsto...@yahoo.co.uk wrote: Sorry for this Maven newbie question but I want to clarify the relationsship between pom.xml and Ant's build.xml. Are the following statements correct? pom.xml is solely Maven related build.xml is solely Ant related Both do not (never) depend on each other (are e.g. included). So if I get a project which contains a pom.xml and a build.xml then the developer offers to use either Ant or Maven. If I select Maven then I can delete build.xml. If I select Ant then I can delete pom.xml without harm. Is there a way to convert a build.xml into a pom.xml and vice versa? Ok in case of pom.xml - build.xml I would loose some functionality but this should not be the question at this point. Is there such a converter? Thank you Ben -- View this message in context: http://maven.40175.n5.nabble.com/Relationsship-pom-xml-and-build-xml-from-Ant-tp1092912p1092912.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Relationsship pom.xml and build.xml from Ant
you can reference an external build file within the ant-run plugin, so
something like:
..
ant antfile=${basedir}/build.xml
target name=test/
/ant
..
taken from the second example
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
chances are that in your case:
-the two separate builds are required to build the overall project,
and maybe they didn't have time to migrate certain parts of the ant
build to maven
or
-the maven build references the ant one and invokes it
and/or
-the ant is used for something other than an actual build (ant is
still a great tool for other stuff)
On Wed, Jul 14, 2010 at 1:37 PM, benxs bxsto...@yahoo.co.uk wrote:
maven/POMs can make use of ant build scripts, so be wary of this
scenario; it is fairly common to use ant via maven
Thank you. But how do I find out if a pom.xml uses a build.xml in the same
directory?
Do I have to search for a
includebuild.xml/include
or a
callbuild.xml/call
statement in pom.xml?
Ben
--
View this message in context:
http://maven.40175.n5.nabble.com/Relationsship-pom-xml-and-build-xml-from-Ant-tp1092912p1092935.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: antrun plugin resolving properties referencing properties
just to clarify, are you using the antrun plugin for maven or the
maven tasks for ant?
On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg akr...@pragmatrading.com wrote:
I'm trying to access the project.build.directory property which is defined in
my pom as
build
directory${project.basedir}/target/directory
In ant I have this setup:
artifact:pom id=project-pom file=pom.xml /
property name=outputdir value=${project-pom.build.directory}/
However when I run my ant build, outputdir is being set to the literal value
${project.basedir}/target rather than antrun expanding the variable
${project.basedir}. Has anyone else run into this issue?
Disclaimer: http://pragmatrading.com/disclaimer.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven ant tasks resolving properties referencing properties
that's weird - I think your syntax is correct
there's an example here:
http://hohonuuli.blogspot.com/2007/03/boostrapping-mavens-antlib-maven.html
what happens if you remove the directory value from your pom and allow
it to use the default?
On Wed, Jul 14, 2010 at 6:27 PM, Adam Krieg akr...@pragmatrading.com wrote:
Forgive me, I meant Maven ant tasks. I'm trying to reference information
defined in the pom from my build.xml.
-Original Message-
From: Shan Syed [mailto:shan...@gmail.com]
Sent: Wednesday, July 14, 2010 6:23 PM
To: Maven Users List
Subject: Re: antrun plugin resolving properties referencing properties
just to clarify, are you using the antrun plugin for maven or the
maven tasks for ant?
On Wed, Jul 14, 2010 at 6:06 PM, Adam Krieg akr...@pragmatrading.com wrote:
I'm trying to access the project.build.directory property which is defined
in my pom as
build
directory${project.basedir}/target/directory
In ant I have this setup:
artifact:pom id=project-pom file=pom.xml /
property name=outputdir value=${project-pom.build.directory}/
However when I run my ant build, outputdir is being set to the literal value
${project.basedir}/target rather than antrun expanding the variable
${project.basedir}. Has anyone else run into this issue?
Disclaimer: http://pragmatrading.com/disclaimer.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Disclaimer: http://pragmatrading.com/disclaimer.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Customized Maven congfiguration
build your projects using maven, then orchestrate your build with something like hudson http://hudson-ci.org/ you can set various triggers on how to kick off a build (time/cron based, or monitor CVS for changes) you can also invoke deploy plugins and what not through maven On Tue, Jul 6, 2010 at 8:48 AM, Paulwintech paulwint...@gmail.com wrote: Hi All, I am a new user to maven. And i have the following queries. In my concern we use CVS as repository ant for build. Whenever a new build is created we have a procedure like first updating CVS and then creating build using ant and then taking the new build and copying it in a new folder etc., now using maven i need automate the below tasks, by calling maven 1. CVS update 2. Build using ant 3. Copy the newly created build to some folder 4. Upload and deploy in remote server 5. Test cases to check whether site is working fine 6. Sending a mail to a group stating the deployment status please help on this... Thanks Paulwintech -- View this message in context: http://maven.40175.n5.nabble.com/Customized-Maven-congfiguration-tp900309p900309.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
is there a way to query maven for all the X type of modules it just built?
If I have a multi-module project made up of JARs and WARs and ZIPs and... etc is there a way to commit an action on, for example, all the WARs that were just built, without having to specify particular projects? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: is there a way to query maven for all the X type of modules it just built?
ah cool, looks like something that could be written as a mojo? who knows my problem is that I am using Hudson to build a few multimodule projects, which will have an increasing number of WARs as the company grows Hudson gives me convoluted URLs to specific builds, which I manually maintain in an ANT script (a script that is put onto target machines, and invoked to download all the WARs of a specific build) I would like all the WAR projects in my multimodule project to identify themselves to a running file, which could be an artifact itself; which could then be downloaded/included by my ant script, to make sure at any time, I have links to all the WARs in Hudson produced by a single build this is all so I don't have to maintain a list of tons and tons of WARs; I want it generated automatically S On Tue, Jul 6, 2010 at 4:01 PM, Ron Wheeler rwhee...@artifact-software.com wrote: On 06/07/2010 2:24 PM, Shan Syed wrote: If I have a multi-module project made up of JARs and WARs and ZIPs and... etc is there a way to commit an action on, for example, all the WARs that were just built, without having to specify particular projects? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This is something that I have been asking about for the past 2 weeks with no success so far. I have tried the artifactIdmaven-assembly-plugin/artifactId version2.2-beta-2/version with a dependencySet It will bundle everything up but it unpacks all the dependencies of the JAR files and builds an output file (tar and zip) in my case that includes all the JARs that I have build which include their dependencies and adds the dependencies again at the top level. It seems that there is no switch or option to tell the plug-in to just get the JAR files that are dependencies of the packaging project and zip them up without looking inside. In my case, I want a zip/tar pair that include all the WARs that will go into tomcat/webapps and another pair that include all of the sharable JARs that need to go into tomcat/lib. Ron - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: change version?
http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html On Tue, Jul 6, 2010 at 5:06 PM, Frank Maritato fmarit...@attinteractive.com wrote: I have a multimodule maven project and I want to change the version number. Unfortunately, it looks like I have to manually edit each pom.xml (or write some sort of perl script) to accomplish this. Is there a better, cooler, faster way to do this? Maybe with a plugin of some sort? -- Frank Maritato - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
altDeploymentRepository - deploy plugin
how can I specify security info (username/password) for the target repo, using this parameter with the deploy:deploy goal? it takes the URL, format, and ID only thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: altDeploymentRepository - deploy plugin
ah ok - I was looking for a completely decoupled way (via command line) of specifying all deployment params, without having to change config On Fri, Jul 2, 2010 at 5:06 PM, Anders Hammar and...@hammar.net wrote: The username/password goes in the settings.xml. You use the id to reference that. http://maven.apache.org/settings.html#Servers /Anders On Fri, Jul 2, 2010 at 22:29, Shan Syed shan...@gmail.com wrote: how can I specify security info (username/password) for the target repo, using this parameter with the deploy:deploy goal? it takes the URL, format, and ID only thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Package Speed
also, consider breaking the WAR up into different webapps, if you can, architecturally 50 dependencies is pretty big On Fri, Jun 25, 2010 at 10:22 AM, Wayne Fay wayne...@gmail.com wrote: Copying webapp resources[C:\Users\7yw\netbeans_workspace\BioKDF\src\main\webapp] Webapp assembled in[75025 msecs] Reduce the amount of code being processed, or increase cpu speed, or increase i/o speed (ramdisk or ssd). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Package Speed
I don't know what your webapp does, so it's hard for me to describe how it could be broken up; but personally, if I had a webapp that relied on 50 dependencies (and as a result, 50+ jars), I would try to identify how I could modularize it and move the service layer to actual independent web services or something, that are called/invoked by the actual front-end On Fri, Jun 25, 2010 at 10:36 AM, Rajasekar Karthik karthik...@gmail.comwrote: Shared library is a good option - will give it a try! Most of the back-end functionality are services! Breaking the webapp into multiple webapps? Do you mean by functionality? If not, what did you mean? My disk speed is around 7200 RPM (SATA). -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Package-Speed-tp511260p511357.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Package Speed
this has to do with what's in your WAR, perhaps analyze what dependencies its using, and where they are coming from Maven is just like any other program; you can throw hardware at it to speed it up On Thu, Jun 24, 2010 at 4:41 PM, Rajasekar Karthik karthik...@gmail.comwrote: Hi, How can Maven's package of war be speed up? Currently, it is extremely slow - around 7 minutes or more. I even set the following options -DMAVEN_OPTS=-Xms64m –Xmx512m (higher Xmx to see if it will increase speed - but, it does not) Other options being set and command (invoked through NetBeans) mvn.bat -Dnetbeans.deploy=true -Dnetbeans.execution=true -DMAVEN_OPTS=-Xms64m –Xmx512m package -- Best Regards, Rajasekar Karthik karthik...@gmail.com
Re: How to deploy artifact without version in name?
do you need the artifact's file name to retain the groupId/version info? if not, specify finalNamemoduleA/finalName in the build section of your POM On Tue, Jun 22, 2010 at 10:54 AM, D D dawi...@gmail.com wrote: Hello, Is there an easy way to deploy an artifact such it doesn't include version in its name? For example: when moduleA is deployed through 'mvn deploy' I get moduleA-X.Y-SNAPSHOT.jar but what I need is moduleA.jar. Thanks, Dave
Re: using javascript dependencies in a webapp (war packaging)
I'm considering moving my solution to using the concept of WAR overlays; a WAR project that requires certain javascripts specifies those as project dependencies, which themselves are simple WAR projects with only js files in their correct paths they get slapped onto the using WARs, and presto, no weirdness with copying and unzipping directly On Tue, Jun 15, 2010 at 6:23 PM, Haszlakiewicz, Eric ehas...@transunion.com wrote: -Original Message- From: Shan Syed [mailto:shan...@gmail.com] I've worked on projects that share common javascript files, so I used a simple assembly descriptor to zip each set of files and install them as maven artifacts WAR projects then just specified them as dependencies in their POMs it's nice then to be able to treat these artifacts like any other project (versioned, deployable to a repo, etc) I used the maven-dependency plugin to unzip them to a standard folder we didn't require any parsing or compiling of the js, so this worked out fine for simple packaging and unzipping I ended up doing something similar. In case anyone else needs to do this in the future the steps I took were: 1) Create a jar file containing prototype-1.6.1.js at the top level [*1]. I also included a hand written README file in the META-INF directory with information about where the js file came from. 2) I deployed this to my local nexus repository as org.prototypejs:prototype:jar:1.6.1 3) I added the dependency to my webapp's pom.xml file with the provided scope. That scope is needed to prevent the jar file from being included in the war. (for some reason using compile scope didn't omit it) 4) I added the overlay configuration to the maven-war-plugin as described in my original message. Since the README file is in the META-INF directory it doesn't get included. And now I get the js file extracted from the dependency jar file and included in the right place in the war file. This probably wouldn't work if prototypejs actually provided their own artifact, since the js file would probably be in a subdirectory, and there's no way to tell maven to rearrange things. However, in that case, I think I'd be able to use the maven-dependency plugin to unpack it to a temporary location, and then use some inline tasks in a maven-antrun-plugin to move the files to the right place. I've done this in other projects I've worked on and it's kind of annoying that maven doesn't support stuff like this natively, but at least it works. eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: using javascript dependencies in a webapp (war packaging)
I've worked on projects that share common javascript files, so I used a simple assembly descriptor to zip each set of files and install them as maven artifacts WAR projects then just specified them as dependencies in their POMs it's nice then to be able to treat these artifacts like any other project (versioned, deployable to a repo, etc) I used the maven-dependency plugin to unzip them to a standard folder we didn't require any parsing or compiling of the js, so this worked out fine for simple packaging and unzipping On Mon, Jun 14, 2010 at 6:23 PM, Haszlakiewicz, Eric ehas...@transunion.com wrote: I've got a webapp that uses javascript files from third party projects. For instance, one of the files we use is prototype.js. It seems like this must be something that many people have done in the past, but I can't seem to find much information about it. The first issue I have is that I can't seem to find a maven repository that has this file (or any of the other javascript scripts I use). Is there one? Since I couldn't find one, I uploaded a copy to my local repository (Nexus) using: ?xml version=1.0 encoding=UTF-8? project xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; modelVersion4.0.0/modelVersion groupIdorg.prototypejs/groupId artifactIdprototype/artifactId version1.6.1/version packagingjs/packaging urlhttp://prototypejs.org/assets/2009/8/31/prototype.js/url /project and I then added an entry to the pom for my webapp: dependency groupIdorg.prototypejs/groupId artifactIdprototype/artifactId typejs/type version1.6.1/version /dependency but I can't figure out how to get this to actually get included into the war file. I tried configuring an overlay, but it doesn't seem to do anything: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId configuration overlays overlay groupIdorg.prototypejs/groupId artifactIdprototype/artifactId typejs/type targetPathcommon/javascript/targetPath /overlay /overlays /configuration /plugin All I see is a warning when I run mvn package: [WARNING] Skip unpacking dependency file[/u/ehaszla/.m2/repository/org/prototypejs/prototype/1.6.1/prototype -1.6.1.js with unknown extension[js] I want to end up with a file called prototype-1.6.1.js in the common/javascript directory within the war file. How do I get this to work? eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: high-level maven multimodule/inheritance question
Hi, yes, I didn't mean to imply any SCM changes - just one developer, working on different parts of a project tree, and having changes in one area reflect immediately in other areas, without having to manually worry about rebuilding the JAR project, etc On Sat, Jun 12, 2010 at 1:38 AM, Anders Hammar and...@hammar.net wrote: I read the question as one developer working on project A/B/C at the same time he/she is working on war project D/E. For that scenario I see m2eclipse as the best solution. You wouldn't be updating from scm, but just add your own changes. /Anders On Fri, Jun 11, 2010 at 23:19, Ron Wheeler rwhee...@artifact-software.comwrote: On 11/06/2010 5:00 PM, Anders Hammar wrote: Well, one way would be to use m2eclipse and have it resolve workspace projects (default setting when importing a maven project). With automatic build turned on, the developer doesn't have to do anything for changes in A/B/C to take effect. It is not clear that this is a viable way to work. You don't want to take everyone's interim code while testing your own. What is someone goes for lunch or needs to pee? You want developers to work together with SNAPSHOTS so that each person can decide when the thing that they are building is in a state for others to build with. It also means that a developer can set his dependencies on code that he knows and trusts - either a release or a particular SNAPSHOT or the latest SNAPSHOT if he/she is working closely with another developer. Otherwise, you have no idea about what code you are building with and you will lose a lot of time testing and searching for errors in the wrong place. Ron /Anders On Fri, Jun 11, 2010 at 22:40, Shan Syedshan...@gmail.com wrote: example scenario: - there is a super POM, which is the parent for 5 other POMs (A, B, C, D, E), which have their own children too - only A, B, and C are listed as modules in the super POM because the others are logically separate (and also, issuing a build at the top with all the modules enabled causes out of memory issues, even when the memory params are set very high) (so while all projects have the same top POM, the projects that are in D and E are built from those roots) - some WAR projects in D and E have dependencies on JARs created somewhere in A, B, and C So! given this, a developer is actively working on one of these WAR projects in D or E, and also is making modifications to the code in a JAR project in A/B/C How can I force a rebuild of that JAR if there's a change, only through building the WAR that's in D or E? The developer doesn't want to have to build from the top to get A/B/C to refresh and THEN build their WAR; they want it built automatically if there is a change WHILE only issuing one build, on their WAR project. I hope this makes sense - is this something I just don't understand about maven, i.e. this is what it does? or is there a way to force ALL snapshots dependencies to be rebuilt? Or is there some way to make sure a WAR, for example, checks to see if it's local dependencies (i.e. JARs and things that inherit from the same eventual root POM) need to be rebuilt? thanks very much Shan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: War overlay trouble for Pom that produces WAR and JAR
are you using attachClassestrue/attachClasses in your WAR plugin config? you can reference this WAR project's JAR in your project that requires the classes for compile time, using classifierclasses/classifier On Fri, Jun 11, 2010 at 11:03 AM, Starrman sta...@gmail.com wrote: I have a webapp that is to be used as a war overlay. My packaging type is war. It produces myOverlayWebapp.war I have a different webapp myapp1 that depends upon this overlay... Works well. I have another webapp myapp2 that needs to depend upon the classes within the overlay project at compile time but does not need to use the Web artifacts. To accomplish this I forced the Overlay project to produce a JAR and a WAR... (myOverlayWebapp.war and myOverlayWebapp.jar). The pom for the overlay project still has a packaging type of war. In my current project myapp2 I specify the overlay project as a compile time dependency by setting the type of the dependency to jar. The problem with this is that the web artifacts are stll coming into mywebapp2 even though my dependency explicitly specified a JAR not a WAR. Do you have any ideas how I could depend upon the classes during the compile yet not pull in the web artifacts into myapp2? -- View this message in context: http://maven.40175.n5.nabble.com/War-overlay-trouble-for-Pom-that-produces-WAR-and-JAR-tp329411p329411.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: War overlay trouble for Pom that produces WAR and JAR
it's actually Shan ;) just to generalize (not fully sure if this applies to your scenario), if you want a WAR project to produce a JAR locally (within the /lib dir of the webapp), you can use archiveClassestrue/archiveClasses to have the same/similar JAR actually be available as a consumable artifact in other projects, you specify this attachClassestrue/attachClasses which should install it into your local repository if you call install when building your WAR project now, this set of classes is available to your other projects as a dependency, but you need to specify classes as the classifier for example, within another project; dependency groupIdcom/groupId artifactIdwebapps-project/artifactId version???/version classifierclasses/classifier /dependency On Fri, Jun 11, 2010 at 1:45 PM, Jesse Farinacci jie...@gmail.com wrote: Hi Starrman, On Fri, Jun 11, 2010 at 1:27 PM, Starrman sta...@gmail.com wrote: I actually am using common code in both projects... This was the project that I referred to as the myOverlayWebapp.war project... I am trying to use war overlays for the common web components and the common classes. I guess I really don't understand the problem at all then. Any common code should be in some common module that is depended upon your war modules. Do you see a reason why Syed's suggestion wouldn't work? I'm not familiar with the mechanism proposed by Syed. Try it and see. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Building Maven Without Maven Installed
Hi, are you sure netbeans requires Maven 3? http://wiki.netbeans.org/Maven if you're new to Maven, building and understand Maven 3 will be tricky, so it might be a good idea to stick with an older/stable version On Fri, Jun 11, 2010 at 3:17 PM, christianto hendri christianto.hen...@gmail.com wrote: hi , i have 2 problem here could you help me: 1 . i need the maven snapshot because netbeans only can use maven release 3.0 and snapshot version , i have try with 3.0 beta version and i still can't create a maven project , where i can download it 2. i have read the guide to build maven without maven installed but i'cant understand when i enter command ant it's find build.xml , how can i create this build.xml so i can make maven snapshot , i am still new to maven and ant so i didn't understand it thanks for your attention
high-level maven multimodule/inheritance question
example scenario: - there is a super POM, which is the parent for 5 other POMs (A, B, C, D, E), which have their own children too - only A, B, and C are listed as modules in the super POM because the others are logically separate (and also, issuing a build at the top with all the modules enabled causes out of memory issues, even when the memory params are set very high) (so while all projects have the same top POM, the projects that are in D and E are built from those roots) - some WAR projects in D and E have dependencies on JARs created somewhere in A, B, and C So! given this, a developer is actively working on one of these WAR projects in D or E, and also is making modifications to the code in a JAR project in A/B/C How can I force a rebuild of that JAR if there's a change, only through building the WAR that's in D or E? The developer doesn't want to have to build from the top to get A/B/C to refresh and THEN build their WAR; they want it built automatically if there is a change WHILE only issuing one build, on their WAR project. I hope this makes sense - is this something I just don't understand about maven, i.e. this is what it does? or is there a way to force ALL snapshots dependencies to be rebuilt? Or is there some way to make sure a WAR, for example, checks to see if it's local dependencies (i.e. JARs and things that inherit from the same eventual root POM) need to be rebuilt? thanks very much Shan
Re: high-level maven multimodule/inheritance question
it would be nice if you could somehow specify that certain dependencies were transient or something (perhaps in a profile), and have maven go out and execute the same goals on those? On Fri, Jun 11, 2010 at 6:23 PM, Wayne Fay wayne...@gmail.com wrote: It is not clear that this is a viable way to work. You don't want to take everyone's interim code while testing your own. What Well, you can also argue that people should not be checking code that will break other people's builds, right? I agree with the premise that you should depend on build artifacts rather than code unless you're working on that code, in general. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: tools.jar and upload to central
this is a Sun jar that's under a license that prevents it from being available like that using system scope is an ok solution, but as stated elsewhere, hosting your own repository is a great solution for this issue as well as others that you will likely encounter as your project grows try archiva, nexus, artifactory, etc On Wed, Jun 9, 2010 at 3:25 PM, Johannes Schneider maili...@cedarsoft.comwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, at the moment I am creating a project that needs the tools.jar for compilation and at runtime. Therefore I have added dependency with scope system as explained here: http://maven.apache.org/general.html#tools-jar-dependency Is it possible to deploy that artifact to the central repository? Or do there apply any restrictions? Thanks, Johannes - -- Johannes Schneider - blog.cedarsoft.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMD+qPAAoJEAytD9R7Qv6dQj8IANw1QgflG1L8XKSHYlCIyczK m0kNNKr5ULcCAed0a+02AcRPeQyXEmjoONhS3UTWRZ67EtXDtEmRh3UUvBUv1sgy OX4s8VNVKopDSdRaX7oXafg2frhYalyyFIT1qUAXYN2lNNzKH8cH6C0jLXxjvN6S LQMXHCVADuvsh+0ZorZJiwmlhNNLp71hILIx6KLir+baRMgVpwdHFesdA9hREzQC 9uedbZRz2k468byzT5O997/RDqm2gzZeSS0QZSDt92PIOLgWehKVdbc7gZ+86py5 Fw+pynYMI0KavZeTYSdJw4ERM+stwE2gVlPvjoJ97deVbU6WuFdHrAX2H6ZGkLs= =AgSe -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Spring3 WS Archetype
Hi, try the STS IDE itself, not the plugin, if you can: http://www.springsource.com/products/sts On Thu, Jun 3, 2010 at 2:42 PM, Changkowski m.str...@gmx.de wrote: Hi Ron The STS-plugin is installed to eclipse, but when i create a Spring project in eclipse, the project has not the spring directory structure and no spring jar files. I want to setup the project with maven because i hope to simply create, deploy and test the project when it is all setup correctly. ronatartifact wrote: Have you tried with STS? Ron On 03/06/2010 1:16 PM, Changkowski wrote: When i create a new Maven project in Eclipse and choose the archtetype spring-ws-archetype I get the following error message: Missing artifact org.springframework.ws:spring-oxm:jar:2.0.0-M1:compile I just have a file called org.springframework.oxm-3.0.2.RELEASE.jar but that's not accepted. I want to create a webservice with spring 3 not spring 2.x. I think org.springframework.ws:spring-oxm:jar:2.0.0-M1:compile is Spring 2.x. I have no experience with maven. Please help... Changkowski wrote: Yes i installed this plugin to eclipse. mgainty wrote: did you install m2eclipse plugin? http://m2eclipse.sonatype.org/installing-m2eclipse.html ? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Wed, 2 Jun 2010 09:16:08 -0700 From: m.str...@gmx.de To: users@maven.apache.org Subject: Re: Spring3 WS Archetype Thanks shansyed I still have the STS plugin and the m2eclipse plugin integrated in eclipse, but when I just create a new Spring project I have not the directory structure and the xml files i need for a spring 3 ws. When i have the right archetype file i can use it in eclipse with creating a new Maven project or is there another way to do this? shansyed wrote: you could use STS http://www.springsource.com/products/sts to create the WS projects with Spring 3 with proper maven POMs On Wed, Jun 2, 2010 at 11:53 AM, Changkowskim.str...@gmx.de wrote: Hello I'm new to Maven and I have to build several spring webservices with spring 3. When I write mvn archetype:generate to the commandline i can choose at position 245 245: remote - spring-ws-archetype (Spring Web Services Maven2 Archetype.) but the following selection is limited to Spring version 1.0 to 2.0 and not Spring 3.0. Is there a easy way to get an archetype for spring webservices for spring 3? Kind regards, Changkowski -- View this message in context: http://old.nabble.com/Spring3-WS-Archetype-tp28756453p28756453.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Spring3-WS-Archetype-tp28756453p28756746.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Spring3-WS-Archetype-tp28756453p28771437.html Sent from
Re: Multi Module Archetypes
I think Apache Cocoon and MyFaces have archetypes that do this, you could reference their code otherwise, try executing archetype:create-from-project at the root and see what happens? On Wed, Jun 2, 2010 at 11:47 AM, ch...@chrismiles.org wrote: Hi, Is it possible to create an Archetype which will create a full multi module project rather than creating each module individually? I would like to generate the following in one go to reduce complexity. --parent warproject --src --pom.xml ejbproject --src --pom.xml earproject --pom.xml Many Thanks Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Spring3 WS Archetype
you could use STS http://www.springsource.com/products/sts to create the WS projects with Spring 3 with proper maven POMs On Wed, Jun 2, 2010 at 11:53 AM, Changkowski m.str...@gmx.de wrote: Hello I'm new to Maven and I have to build several spring webservices with spring 3. When I write mvn archetype:generate to the commandline i can choose at position 245 245: remote - spring-ws-archetype (Spring Web Services Maven2 Archetype.) but the following selection is limited to Spring version 1.0 to 2.0 and not Spring 3.0. Is there a easy way to get an archetype for spring webservices for spring 3? Kind regards, Changkowski -- View this message in context: http://old.nabble.com/Spring3-WS-Archetype-tp28756453p28756453.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Versioning of company SuperPOM
I don't fully understand your scenario, but do you use the release plugin? http://maven.apache.org/plugins/maven-release-plugin/introduction.html if you maintain your pre-release code as SNAPSHOT so-and-so, this plugin will help you make a release version out of it without having to edit POMs manually On Tue, Jun 1, 2010 at 10:09 AM, Andrew Close acl...@gmail.com wrote: the organization that i currently work at is in the process of updating our POM hierarchy. we're moving to a common company SuperPOM which everyone will inherit from as opposed to the handful of semi-SuperPOMs we have now. :) we currently have over 300 artifacts that are downstream of this architecture and we'll be rolling this model out in phases since it would be very difficult to schedule a release with all of our artifacts at once. we're hoping to take advantage of the common plugin management and dependency management to keep our third party dependencies more manageable. this sounds good, but i'm guessing we'll get halfway through the rollout and realize that we need to make some changes to the SuperPOM, which entails a new version, which means updating all the downstream artifacts so they inherit from the new parent. this could become a very vicious cycle. so, the question i have is how do other large organizations with this model handle versioning their SuperPOMs? do you actually update the version and then go through all the artifacts and update their parent block? or do you keep the SuperPOM at a static version (probably not a very good idea) so all updates are handled dynamically? is there a way to enforce which version of the SuperPOM should be used? or at least warn the developer that there is a newer version of the SuperPOM that they should be inheriting from? -- Andrew Close - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Internal Repository Advice
Artifactory, Nexus, and Archiva are all well regarded; some choose one over the others for their own reasons. I use Archiva http://archiva.apache.org/ because it was extremely easy to get started with. On Tue, Jun 1, 2010 at 10:18 AM, Greg Akins angryg...@gmail.com wrote: I'm moving my companies projects to Maven and need an internal repository. I hesitated to use something like Artifactory because I thought a simple directory structure, under Apache, would be sufficient (did it that way back in the Maven1 days). However, I'm having trouble deploying projects (possibly a problem with my lack of knowledge around scp/ssh and trying to use Wagon with scp for the deploys). Before I get too far down this rabbit hole, I'd like some advice on the best way to proceed (using a free, open-source repository is a MUST.. my company will never pay for a commercial one). Any help is much appreciated. -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: newbie question
please post your entire POM; you don't have to tell the compiler much, but this just reads like you might be missing dependency blocks On Wed, May 26, 2010 at 1:46 PM, Meeusen, Christopher W. meeusen.christop...@mayo.edu wrote: Yes, that did the trick, now new errors though. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project wsaxisM: Compilation failure: Compilation failure: C:\my_clearcase_views\m042872_view\MICS-Team\DIOS\Web Service\wsaxis2_m\src\main\java\com\gehc\ce\ws\GEHCUtils.java:[5,31] package org.apache.axis2.context does not exist C:\my_clearcase_views\m042872_view\MICS-Team\DIOS\Web Service\wsaxis2_m\src\main\java\com\gehc\ce\ws\GEHCUtils.java:[7,33] package com.idx.carecast.ca.common does not exist Getting a bunch of these. Do I have to configure the compiler plugin and explicitly tell it to use the .jars referenced in my build path? Thanks, Chris -Original Message- From: users-return-111617-meeusen.christopher=mayo@maven.apache.org[mailto: users-return-111617-meeusen.christopher=mayo@maven.apache.org] On Behalf Of fradj zayen Sent: Wednesday, May 26, 2010 12:37 PM To: Maven Users List Subject: Re: newbie question hi Chris, I think you didnt't properly configured the compiler plugin. below an extract pom.xml file build ... plugins .. plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin /plugins /build Regards 2010/5/26 Meeusen, Christopher W. meeusen.christop...@mayo.edu Hi, I'm brand new to maven, read through a few books, and built a simple maven project to produce a .jar. I've installed the m2ecplipse pugin and have got it to work properly on a few simple projects. Now I'm having an issue when I try to build a more complex project, which requires at least java 1.5 (because it uses enums and other things). When I build my project I get a clean build, however when I try to do Run As Maven package I get the following errors in the console: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project wsaxisM: Compilation failure: Compilation failure: C:\my_clearcase_views\m042872_view\MICS-Team\DIOS\Web Service\wsaxis2_m\src\main\java\edu\mayo\util\VTInfoType.java:[10,7] enums are not supported in -source 1.3 (use -source 5 or higher to enable enums) public enum VTInfoType I get similar errors for annotations and generics. Anyone know what might be going on? Please help a maven newb! Thanks, Chris -- Zayen Fradj Ingénieur Informaticien Sun Certified Programmer - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: newbie question
you need to specify a dependencies for everything; in the case you depend on a jar that's not publicly available (3rd party vendor, in-house jar, etc), you have a few options: -maintain a repository for these sorts of things, using a tool like archiva, nexus, or artifactory (ideal for teams of more than 1) -install it locally http://maven.apache.org/guides/mini/guide-3rd-party-jars-local.html -specify a local location for the JAR, by using system scope (not the greatest solution) On Wed, May 26, 2010 at 2:00 PM, Meeusen, Christopher W. meeusen.christop...@mayo.edu wrote: I guess I miss understood the concept of dependencies. I thought that it was used only for .jars that were in a repository say commons-lang-2.4, but if you have some api from a vendor, say vendor.jar, that you didn't have to configure a decency for that. -Original Message- From: users-return-111621-meeusen.christopher=mayo@maven.apache.org[mailto: users-return-111621-meeusen.christopher=mayo@maven.apache.org] On Behalf Of Wayne Fay Sent: Wednesday, May 26, 2010 12:50 PM To: Maven Users List Subject: Re: newbie question Getting a bunch of these. Do I have to configure the compiler plugin and explicitly tell it to use the .jars referenced in my build path? No configuration of the compiler plugin should be necessary. You simply need to properly configure your dependency list. Most likely you are simply missing one or more dependencies -- looks like axis2 is the first, but I don't recognize the com.idx one and assume it is an internal artifact that you're working on. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
Thanks, but the problem is that when I do that, both executions occur, even
when I specify inheritance=false.
I basically need to use the same plugin for two different purposes, without
either of them affecting the other; I tried to specify different versions
for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for the
other), but no dice.
Running mvn help:effective-pom on my WAR projects always shows the second
maven-dependency-plugin configuration from the root POM in the
pluginManagement section
BUT
in the actual plugin block, it shows the following (below)
(note the second execution, with not configuration or anything associated
with it)
What is the exact logic for the merging of plugin configs in a multimodule
project?
thanks
S
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idunpack-wsdls/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
outputDirectoryC:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl/outputDirectory
/configuration
/execution
execution
idunpack-javascripts/id
/execution
/executions
configuration
artifactItems
artifactItem
artifactIdsk-javascript-token/artifactId
groupIdcom.securekey.javascript/groupId
version1.0-SNAPSHOT/version
classifierjavascript/classifier
typezip/type
/artifactItem
/artifactItems
/configuration
/plugin
On Thu, May 13, 2010 at 4:54 AM, Kalpak Gadre kalpa...@gmail.com wrote:
I have never tried declaring the same plugin twice, but you can simply
define more executions in the same plugin declaration like,
executions
execution
idone/id
.
.
/execution
execution
idtwo/id
.
.
/execution
/executions
Thanks,
Kalpak
Here's my scenario: I have a large multimodule project whose WARs share
certain dependencies, which are packaged as zips by a few simple
assemblies
I wrote.
I am using the maven-dependency-plugin to unpack the contents of these
zips
into their destination folders in the webapps.
However, to reduce clutter and minimize maintenance, the majority of the
plugin configuration is in the root POM, like so:
(note that I am using the same plugin twice for two different reasons - is
this valid?)
build
pluginManagement
plugins
...
!-- unpacking of JAVASCRIPT dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-javascripts/id
goals
goalunpack/goal
/goals
phasepackage/phase
configuration
outputDirectory${project.build.directory}/war/scripts/outputDirectory
/configuration
/execution
/executions
/plugin
!-- unpacking of WSDL dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-wsdls/id
goals
goalunpack/goal
/goals
phasegenerate-resources/phase
configuration
outputDirectory${project.build.directory}/war/WEB-INF/wsdl/outputDirectory
/configuration
/execution
/executions
/plugin
/plugins
/pluginManagement
/build
Some WARs need the WSDLs, some need the javascript files, while others
don't
need either - it will be up to the developers creating those projects.
Here is an example usage in one of the WARs (note the ID of the execution,
which is expected to be used to merge the whole configuration)
build
plugins
plugin
artifactIdmaven-dependency-plugin/artifactId
groupIdorg.apache.maven.plugins/groupId
inheritedtrue/inherited
executions
execution
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
thanks - how would I set this up?
I tried to specify two profiles in my parent POM, each with their own
pluginManagement blocks, containing a maven-dependency-plugin configuration,
and then activated the profile in the WAR projects' POMs, but there is no
result
I basically want my plugins' meta config stored in the root, and specific
configs applied in the WAR projects
On Thu, May 13, 2010 at 10:26 AM, Timothy Mcginnis
tmcgi...@aessuccess.orgwrote:
What about using profiles? Define 3 profiles; one for wsdl only, one for
javascript only, and one for both. Then have the war project activate the
one it needs.
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
Shan Syed shan...@gmail.com
To:
Maven Users List users@maven.apache.org, kalpa...@gmail.com
Date:
05/13/2010 09:54 AM
Subject:
Re: inheriting and reusing the same plugin for different purposes? doesn't
seem to find the right executions
Thanks, but the problem is that when I do that, both executions occur,
even
when I specify inheritance=false.
I basically need to use the same plugin for two different purposes,
without
either of them affecting the other; I tried to specify different versions
for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for the
other), but no dice.
Running mvn help:effective-pom on my WAR projects always shows the second
maven-dependency-plugin configuration from the root POM in the
pluginManagement section
BUT
in the actual plugin block, it shows the following (below)
(note the second execution, with not configuration or anything associated
with it)
What is the exact logic for the merging of plugin configs in a multimodule
project?
thanks
S
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idunpack-wsdls/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
outputDirectoryC:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl/outputDirectory
/configuration
/execution
execution
idunpack-javascripts/id
/execution
/executions
configuration
artifactItems
artifactItem
artifactIdsk-javascript-token/artifactId
groupIdcom.securekey.javascript/groupId
version1.0-SNAPSHOT/version
classifierjavascript/classifier
typezip/type
/artifactItem
/artifactItems
/configuration
/plugin
On Thu, May 13, 2010 at 4:54 AM, Kalpak Gadre kalpa...@gmail.com wrote:
I have never tried declaring the same plugin twice, but you can simply
define more executions in the same plugin declaration like,
executions
execution
idone/id
.
.
/execution
execution
idtwo/id
.
.
/execution
/executions
Thanks,
Kalpak
Here's my scenario: I have a large multimodule project whose WARs share
certain dependencies, which are packaged as zips by a few simple
assemblies
I wrote.
I am using the maven-dependency-plugin to unpack the contents of these
zips
into their destination folders in the webapps.
However, to reduce clutter and minimize maintenance, the majority of
the
plugin configuration is in the root POM, like so:
(note that I am using the same plugin twice for two different reasons -
is
this valid?)
build
pluginManagement
plugins
...
!-- unpacking of JAVASCRIPT dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-javascripts/id
goals
goalunpack/goal
/goals
phasepackage/phase
configuration
outputDirectory${project.build.directory}/war/scripts/outputDirectory
/configuration
/execution
/executions
/plugin
!-- unpacking of WSDL dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-wsdls/id
goals
goalunpack/goal
/goals
phasegenerate-resources/phase
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
configuration
outputDirectory${project.build.directory}/war/scripts/outputDirectory
/configuration
/execution
/executions
/plugin
/pluginManagement
WAR POM specifies this:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupid
artifactIdmaven-dependency-plugin/artifactId
/plugin
/plugins
/build
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
Shan Syed shan...@gmail.com
To:
Maven Users List users@maven.apache.org
Date:
05/13/2010 12:51 PM
Subject:
Re: inheriting and reusing the same plugin for different purposes? doesn't
seem to find the right executions
thanks - how would I set this up?
I tried to specify two profiles in my parent POM, each with their own
pluginManagement blocks, containing a maven-dependency-plugin
configuration,
and then activated the profile in the WAR projects' POMs, but there is no
result
I basically want my plugins' meta config stored in the root, and specific
configs applied in the WAR projects
On Thu, May 13, 2010 at 10:26 AM, Timothy Mcginnis
tmcgi...@aessuccess.orgwrote:
What about using profiles? Define 3 profiles; one for wsdl only, one
for
javascript only, and one for both. Then have the war project activate
the
one it needs.
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
Shan Syed shan...@gmail.com
To:
Maven Users List users@maven.apache.org, kalpa...@gmail.com
Date:
05/13/2010 09:54 AM
Subject:
Re: inheriting and reusing the same plugin for different purposes?
doesn't
seem to find the right executions
Thanks, but the problem is that when I do that, both executions occur,
even
when I specify inheritance=false.
I basically need to use the same plugin for two different purposes,
without
either of them affecting the other; I tried to specify different
versions
for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for the
other), but no dice.
Running mvn help:effective-pom on my WAR projects always shows the
second
maven-dependency-plugin configuration from the root POM in the
pluginManagement section
BUT
in the actual plugin block, it shows the following (below)
(note the second execution, with not configuration or anything
associated
with it)
What is the exact logic for the merging of plugin configs in a
multimodule
project?
thanks
S
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.1/version
executions
execution
idunpack-wsdls/id
phasegenerate-resources/phase
goals
goalunpack/goal
/goals
configuration
outputDirectoryC:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl/outputDirectory
/configuration
/execution
execution
idunpack-javascripts/id
/execution
/executions
configuration
artifactItems
artifactItem
artifactIdsk-javascript-token/artifactId
groupIdcom.securekey.javascript/groupId
version1.0-SNAPSHOT/version
classifierjavascript/classifier
typezip/type
/artifactItem
/artifactItems
/configuration
/plugin
On Thu, May 13, 2010 at 4:54 AM, Kalpak Gadre kalpa...@gmail.com
wrote:
I have never tried declaring the same plugin twice, but you can simply
define more executions in the same plugin declaration like,
executions
execution
idone/id
.
.
/execution
execution
idtwo/id
.
.
/execution
/executions
Thanks,
Kalpak
Here's my scenario: I have a large multimodule project whose WARs
share
certain dependencies, which are packaged as zips by a few simple
assemblies
I wrote.
I am using the maven-dependency-plugin to unpack the contents of
these
zips
into their destination folders in the webapps.
However, to reduce clutter and minimize maintenance, the majority of
the
plugin configuration is in the root POM, like so:
(note that I am using the same plugin twice for two different reasons
-
is
this valid?)
build
pluginManagement
plugins
...
!-- unpacking of JAVASCRIPT dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-javascripts/id
goals
goalunpack/goal
/goals
phasepackage/phase
configuration
inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
Here's my scenario: I have a large multimodule project whose WARs share
certain dependencies, which are packaged as zips by a few simple assemblies
I wrote.
I am using the maven-dependency-plugin to unpack the contents of these zips
into their destination folders in the webapps.
However, to reduce clutter and minimize maintenance, the majority of the
plugin configuration is in the root POM, like so:
(note that I am using the same plugin twice for two different reasons - is
this valid?)
build
pluginManagement
plugins
...
!-- unpacking of JAVASCRIPT dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-javascripts/id
goals
goalunpack/goal
/goals
phasepackage/phase
configuration
outputDirectory${project.build.directory}/war/scripts/outputDirectory
/configuration
/execution
/executions
/plugin
!-- unpacking of WSDL dependencies --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
inheritedtrue/inherited
executions
execution
idunpack-wsdls/id
goals
goalunpack/goal
/goals
phasegenerate-resources/phase
configuration
outputDirectory${project.build.directory}/war/WEB-INF/wsdl/outputDirectory
/configuration
/execution
/executions
/plugin
/plugins
/pluginManagement
/build
Some WARs need the WSDLs, some need the javascript files, while others don't
need either - it will be up to the developers creating those projects.
Here is an example usage in one of the WARs (note the ID of the execution,
which is expected to be used to merge the whole configuration)
build
plugins
plugin
artifactIdmaven-dependency-plugin/artifactId
groupIdorg.apache.maven.plugins/groupId
inheritedtrue/inherited
executions
execution
idunpack-javascripts/id
/execution
/executions
configuration
artifactItems
artifactItem
artifactIdsk-javascript-token/artifactId
groupIdcom.securekey.javascript/groupId
version${project.version}/version
classifierjavascript/classifier
typezip/type
/artifactItem
/artifactItems
/configuration
/plugin
/plugins
/build
So in general, the plugin configuration in the root POM will enforce some
common things (destination folder, etc), and the usage will actually allow
the developer to select what javascripts they need, without worrying about
other configuration details.
But the problem is when building, it's always the 2nd plugin configuration
in the root POM that gets used, even though I specify the ID in the leaf
POMs; so when I do an overall build, all the javascript files end up in a
WSDL directory, even if I don't reference the WSDL execution at all.
I inverse the order, and the result is the opposite; the javascripts end up
in the right place, but all the WARs that have a WSDL dependency end up with
a scripts directory full of WSDL files.
I was under the impression that the ID is used to merge the configurations
upon building the project, but I'm not seeing this. Is there a way to
specify exactly what configuration to bind to?
Specify two executions within the same plugin causes the same behaviour,
except with both folders.
To generalize, in a multi-module project, how can I use the same plugin for
totally different uses/scenarios?
thanks,
Shan
